Windows 8 build 8250

Build of Windows 8
Release nameConsumer Preview
OS familyWindows NT
Version number6.2
Build number8250
Build revision0
Architecturex86, AMD64, ARM32
Build labwinmain_win8beta
Compiled on2012-02-17
Expiration date
Timebomb2013-01-15 (+333 days)
Repair Content-specific:[a]
Starter (N)
Home Basic (N)
Home Premium (N)
Professional (N, Plus)
Enterprise (N, (N) Evaluation)
Ultimate (N)
Product key
About dialog
TCB.png TCBGallery.png

Windows 8 build 8250 is the official Consumer Preview build of Windows 8, which was officially released to the public on 29 February 2012.[1][2] Binaries from the ARM32 compile of this build were discovered on the Microsoft Symbol Server on 25 May 2022.

New features and changes[edit | edit source]

User interface[edit | edit source]

Start screen[edit | edit source]

  • Minor design updates have been introduced across the Start screen's user interface.
  • The Games Explorer shortcut was removed from the application list.

Logon UI[edit | edit source]

The default lock screen background has been updated.

Branding[edit | edit source]

This is the earliest known build to drop the 2001 flag logo and replace it with the new tilted window logo. The boot screen logo bitmap was changed to utilize a Metro-style betta fish along with the number 8 on the left-hand side.[b] Certain resources (such as the Windows Anytime Upgrade application) still make use of the older logo design. The disk drive icon used to indicate the currently-running Windows installation in the Computer system folder has been changed to use the new Windows flag.

The default desktop wallpaper was changed to a teal-colored wallpaper containing a Metro-style betta fish along with a large-sized number 8 on the left-hand side. The betta fish would also be used on the boot screen for this build. Such wallpapers are specifically exclusive to builds in public release branches such as winmain_win8beta and winmain_win8rc.

Boot Graphics Library (BGFX)[edit | edit source]

System crashes no longer display a sad emoticon by default if a Japanese language pack is present and is being actively used. This change is also present in server builds irrespective of whether a Japanese language pack is active.

Secure Boot Policy[edit | edit source]

This build uses a preliminary version of the Secure Boot Policy, although the on-disk structure is identical to later builds:

  • Signature validation is different: the policy must have a hash in or be signed by a certificate in the UEFI Key Exchange Key signature database.
  • The CanUpdate element is used here; the code using it was removed later but the element remained in the file format. A path to an updated policy can either be set in a UEFI variable; alternatively, for BitLocker where the VMK is sealed by the TPM, an updated policy is read from osdevice:\LatestPolicy.p7b. This policy must have a valid signature.
    • The updated policy must have a PolicyPublisher equal to one of the CanUpdate GUIDs in the loaded policy; also, the policy version must be greater than the loaded policy's version. If all conditions pass, the updated policy is installed to UEFI non-volatile storage and used as the active policy.
  • BCD rules are identical to later builds; that is, BCD elements can be overridden by the policy to either be forcibly ignored, or for deletion to be disallowed from the running OS, or for the element value to be locked to a value or one of several values listed in the policy.
  • Registry rules are not used for low-level cryptographic settings as in later builds but instead are used to override registry values anywhere in HKLM\SYSTEM. The operating system loader winload.e* and NT kernel both have code implementing this functionality; the former uses the policy to override the registry values it reads from that hive.
  • Option flag bits are completely different from later builds; only 3 bits are used, all by the operating system loader; bit 0 disables the Edit Options menu, bit 1 disables the Advanced Options menu, bit 2 is unknown but related to the Advanced Options menu.

Other changes[edit | edit source]

The Win+X context menu (which contains a list of quick shortcuts intended for power users) has been added.

Bugs and quirks[edit | edit source]

Timebomb[edit | edit source]

Installing this build after the timebomb expires will result in it not installing its licensing policies properly, therefore resulting in no timebomb being displayed and personalization features being disabled entirely.

Compatibility[edit | edit source]

To install or run this build in VMware Workstation, the hardware compatibility must be set to version 9.x or lower; otherwise, a KMODE_EXCEPTION_NOT_HANDLED bugcheck will occur.

Transparency effects in the Windows Basic theme[edit | edit source]

When using the Windows Basic (Aero Lite) visual style, transparency effects can be enabled by means of a bug in the Personalization Control Panel (don't persist if you re-selected the created theme). To do so:

  1. Right-click the desktop and open up Personalization. Now click on the "Window Color" link given at the bottom of the window. Keep the window open.
  2. Open a separate personalization window and apply the Windows Basic theme.
  3. Go back to the other personalization window that you opened at the start, uncheck "Enable transparency" option and then re-check it. Click on "Save changes" button. This will cause glass effects to be enabled.

Internet Explorer[edit | edit source]

Depending on copies of this build, when opening the About dialog, it might not render entirely and will close automatically instead.

Gallery[edit | edit source]

Setup[edit | edit source]

Interface[edit | edit source]

Notes[edit | edit source]

  1. These SKUs are only available in this build's Repair Content Package sources; they must be manually staged through the DISM utility in order to install and use them. If attempting to stage a Windows 7 edition, files pertaining to the older inbox games and Windows Media Center resources (specifically Chess.dll, PurblePlace.dll, ShvlRes.dll, and ehres.dll) must be decompressed first, otherwise the staging operation will fail as their compressed variants' SHA-256 hashes will not match the ones expected by their packages' catalog files.
  2. Release Preview build 8277 has a higher build number but uses the old logo as it was not yet upstreamed to mainline branches around 8 February 2012.

References[edit | edit source]