Windows 8 build 8032

Windows 8 build 8032 is a build of Windows 8. This build is one of the first to fix the issue with window borders not displaying correctly while Desktop Window Manager is enabled and is also the last known build to use Windows 7 branding and SKUs during installation.

History
The earliest publicly shared screenshots of this build were sourced from BetaArchive user Pwned, who posted them to PCBeta on 1 April 2016. On 6 April, a thread discussing the build in question was created on OSBetaArchive.net on 5 April 2016 by a user under the name of intelsystembridge. On 28 December 2018, members of the Chinese community BetaWorld found the build and shared it on the next day. The build was later uploaded to the BetaArchive FTP server on 4 January 2019.

Redpill
The Redlock tool can be used to unlock all of the Redpill levels on this build, including the Start screen.

Some changes have occurred with Metro since build 8014. The Metro Control Panel now has a Personalization section, where the user can change the accent colors and patterns, as well as the lock screen background. While the general design by this point is much closer to 8056, some elements, such as the bigger size of the live tiles, the gradient effect on the Start screen, and some of the icons, resemble 8014.

Most of the placeholder icons in the ribbon of File Explorer introduced in build 8008 have been finally replaced by the ones seen in the RTM. However, some options still have the placeholder icons.

This is the first build to include Metro-style notifications. This can be easily seen when installing a third-party app, as Windows will inform that  or when inserting removable media.

This is the first build to introduce the new Segoe UI font, which will be used fully in Windows 8 build 8130.

Charms bar accessibility
To enable the right-hand charms bar on a non-touchscreen device, open the Registry Editor and navigate to. A DWORD value called  must be created in this key and its value set to 1.

USB 3.0
This build appears to have a broken XHCI driver, and therefore will bugcheck during setup if USB 3.0 is enabled. Disabling USB 3.0 for the VM (or from the BIOS, on real hardware) should fix this problem.

VMware
It's highly recommended to set the hardware compatibility to 8.x or 9.x on VMware Workstation/Player 15 or newer, otherwise, upon boot, the operating system will crash. Specifically, a screen which will say "Your computer needs to restart. Please hold down the power button", such as error 0x0000001E or 0x0000000A. This error would occur right when the system kernel takes over the startup process but immediately crashes.

Aero Glass in Starter and Home Basic SKUs
This build automatically enables Aero Glass transparency even when installing the Starter or Home Basic SKUs, which do not support it. However, changing the color scheme (visual style) to another one and then back to the default one will disable Aero Glass.

Microsoft Confidential in winver
On this build's  dialog box, the text of the disclaimer is colored black instead of the red that is seen in earlier and later builds.

Password bug on Metro login
When using the password reveal feature on the Metro login screen, the text appears scrambled, consisting of a mixture of letters and symbols from various languages such as Arabic, Japanese, Korean and Chinese.

OOBE
The background wallpaper of the unredpilled OOBE seems to be broken.

Themes
There are several exploits with themes, like transparency in the Aero Lite theme and the High contrast themes.

Store
The Store is labelled.

High Contrast (Redpill only)
High Contrast can be incredibly buggy in this build, and some Developer Preview builds following it, when Metro UI is enabled via Redpill unlocking tools like Redlock, with bugs including but not limited to the Start Screen having a completely transparent background, and Aero Lite just not switching to its High Contrast counterpart when High Contrast is on, leading to the exact same issues as trying to use High Contrast on regular Aero.

Additionally, if High Contrast's colour scheme is set by a 3rd-party program, no parts of Metro UI will acknowledge any High Contrast customisations, and changing Themes and back will not retain those customisations either, instead reverting to the standard High Contrast variant.