Windows 8 build 8056 (fbl grfx dev1)

Windows 8 build 8056 (fbl_grfx_dev1) is a build of Windows 8, which was uploaded to BetaArchive on 19 September 2015.

New features and changes

 * This build renames the Rejuvenate your PC option to Refresh your PC.
 * The History Vault application that was first introduced in build 7878 was renamed to File History in this build.
 * The "Your PC needs to be repaired" screen (used as a fallback screen when Windows tries to enter Automatic Repair but can't due to Recovery either being missing or Windows being too broken to boot Recovery) debuts in this build, albeit with a darker turquoise background instead of its cerulean background seen in later builds, and without the ability to use F8 to enter advanced boot options present yet.

Setup

 * The splash screen now shows a colored Windows logo instead of a white one. Additionally, a gradient has been introduced to the background, as opposed to it being single colored and the color has been changed from teal to blue.
 * Descriptions are now more informal.
 * The progress bar located at the top has been removed, but the stages can still be seen.

eMMC drive support
This build is likely the first Windows 8 build to support eMMC drives.

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

A few changes have occurred since build 8032, mainly focusing on stability and cosmetic updates. Many graphical issues and oddities seen with 8032, including leftover icons from older builds and issues with the graphics and fonts for the tiles, have been fixed, and Metro itself is much more stable. The gradient effect for the background color of the Metro login screen and the Start screen has been removed and the size of the tiles has shrunk. The search pane's close button has also been removed.

When the Share option from the Charms bar is chosen while on the Start screen, it will display "MoGo can't share this, but Windows can share a screenshot instead", hinting at "MoGo" being the codename for the Start screen.

Apps included

 * Immersive Remote Desktop Connection
 * Immersive Control Panel
 * An early but non-functional version of the Windows Store, labelled "MSHelp" on other builds before 8032
 * Immersive IE

Verbose boot removal
In this build, you can no longer append the  boot argument or enable OS Boot Information in msconfig. If you do this, it will just show the build's regular boot screen. Additionally, this also means Safe Mode now uses the regular Windows boot screen as well.

Hardware compatibilities
To install or run this build in VMware Workstation 15 or newer, you must set the hardware compatibility to versions 8.x or 9.x; otherwise, a partially garbled system crash message will occur.

Intel HD graphics
Like most Pre-Release Preview builds, installing latest Intel HD Graphics driver will make the screen blink, making it unusable unless you stop DWM. Using a 2013 or older driver will fix this issue.

Another quirk with Intel drivers is that Windows Vista drivers will work if the user installs this build on a computer that originally had Windows Vista. Before starting the installation, right click the setup file and select Properties. Click on Compatibility and set it to Windows Vista Service Pack 2. Apply and then run the setup file normally and you should have working Intel graphics.

Drivers
On Windows 7 designed tablets/laptops, even if the drivers were newer than 2011, this build will have touch screen, audio and battery drivers working out of the box.

User logon error
If you're running this build on certain hardware (most likely newer hardware), you'll come across that Windows will never log you in after installing. Using the current BIOS date and the BIOS date of 2011-07-27 produces the error, ruling out that as the issue. To fix this issue, restart Windows and press F8 to access advanced boot options. Choose Safe Mode with Networking and Windows should boot. Go to the start menu and search for Regedit Editor, right click that, and run as administrator. Navigate to. Go to the bottom most profile and select it. Once in, double click on  and set its value to 0. Double click on  and also set its value to 0. Restart Windows and you should be in. If you have a .bak profile as well, first rename the profile with no extension as "S-1-5-21-4118428-131-491-1.b" (Sample profile. Keep the name the same, just add .b). Take the one named .bak and remove the extension. Rename the .b profile to .bak. Once done, perform the changes above.

Note: This error may not always appear when clean installing this build and does not occur when upgrading from a previous build.

User Account Control bug
User Account Control will pop up when the user changes the Windows settings, even if it is set to not notify the user when changing those.

Compatibility
Unlike build 8102, this build can run the latest version of Chrome and other programs without trouble. .NET Framework 4.5 is incomplete and unable to run programs that need it.

Device setup
Device setup, if it appears on login, may show up in a broken window.

Windows Classic
This build's Windows Classic fallback style is much flatter than usual, with a broken title bar gradient (only shown in places such as Windows Classic appearance managers from older versions of Windows NT), and controls lacking Windows Classic's lighter shine in most places, with some controls visually losing all their borders like the Taskbar's System Tray. Additionally, if Classic is forced on Explorer the Back/Forward buttons in Explorer are misaligned with the Back/Forward/Recent outline.

Fallback boot screen
Unlike Windows 7's fallback boot screen, which uses Windows Vista's boot screen, this build's one (accessible via ) is a black screen with a borderless progress bar at the top left that doesn't go the whole width of the screen. It has similarities to Windows 2000's boot screen, with them sharing similarly styled progress bar progress (blue blocks) and the same progress bar behaviour of denoting the overall boot progress. In later builds it was reverted back to the Windows Vista boot screen and has remained that way ever since.

hal.dll
Common to most shared Windows 8 builds, this build can still boot successfully on most hardware Windows would otherwise no longer be able to boot on, without the hal.dll file being present. This is in contrast to officially released builds of Windows 8, as well as builds of other Windows versions, which can no longer boot without the file being present, on the same hardware.