-->
You can suppress Windows elements that appear when Windows starts or resumes and can suppress the crash screen when Windows encounters an error that it cannot recover from. This feature is known as Unbranded Boot.
Important
The first user to sign in to the device must be an administrator. This ensures that the RunOnce registry settings correctly apply the settings. Also, when using auto sign-in, you must not configure auto sign-in on your device at design time. Instead, auto sign-in should be configured manually after first signing in as an administrator.
Requirements
Windows 10 Enterprise, Windows 10 Professional, or Windows 10 Education.
Terminology
Turn on, Enable: To make the setting available to the device and optionally apply the settings to the device. Generally 'turn on' is used in the user interface or control panel, whereas 'enable' is used for command line.
Configure: To customize the setting or sub-settings.
Embedded Boot Experience: this feature is called 'Embedded Boot Experience' in Windows 10, build 1511.
Custom Boot Experience: this feature is called 'Custom Boot Experience' in Windows 10, build 1607 and later.
Offense, damager. Order number untuk game plants vs zombie. Sun producer. And makes a party ball break open. Instant kill.
Turn on Unbranded Boot settings
Unbranded Boot is an optional component and is not enabled by default in Windows 10. It must be enabled prior to configuring. For end-users, Unbranded Boot is available through Control Panel > Programs > Programs and Features > Turn Windows features on or off.
If Windows has already been installed you cannot apply a provisioning package to configure Unbranded Boot; instead you must use BDCEdit to configure Unbranded boot if Windows is installed.
BCDEdit is the primary tool for editing the startup configuration and is on your development computer in the %WINDIR%System32 folder. You have administrator rights for it. BCDEdit is included in a typical Windows Preinstallation Environment (Windows PE) 4.0. You can download it from the BCDEdit Commands for Boot Environment in the Microsoft Download Center if needed.
Turn on Unbranded Boot by using Control Panel
- In the Search the web and Windows field, type Programs and Features and either press Enter or tap or click Programs and Features to open it.
- In the Programs and Features window, click Turn Windows features on or off.
- In the Windows Features window, expand the Device Lockdown node, and check or clear the checkbox for Unbranded Boot.
- Click OK. The Windows Features window indicates Windows is searching for required files and displays a progress bar. Once found, the window indicates Windows is applying the changes. When completed, the window indicates the requested changes are completed.
- Click Close to close the Windows Features window.
Configure Unbranded Boot settings at runtime using BCDEdit
Open a command prompt as an administrator.
To disable the F8 key during startup to prevent access to the Advanced startup options menu, type the following:
To disable the F10 key during startup to prevent access to the Advanced startup options menu, type the following:
To suppress all Windows UI elements (logo, status indicator, and status message) during startup, type the following:
Configure Unbranded Boot using Unattend
You can also configure the Unattend settings in the Microsoft-Windows-Embedded-BootExp component to add Unbranded Boot features to your image during the design or imaging phase. You can manually create an Unattend answer file or use Windows System Image Manager (Windows SIM) to add the appropriate settings to your answer file. For more information about the Unbranded Boot settings and XML examples, see the settings in Microsoft-Windows-Embedded-BootExp.
Unbranded Boot settings
The following table shows Unbranded Boot settings and their values.
Setting | Description |
---|
DisableBootMenu | Contains an integer that disables the F8 and F10 keys during startup to prevent access to the Advanced startup options menu. Set to 1 to disable the menu; otherwise; set to 0 (zero). The default value is 0.
|
DisplayDisabled | Contains an integer that configures the device to display a blank screen when Windows encounters an error that it cannot recover from. Set to 1 to display a blank screen on error; otherwise; set to 0 (zero). The default value is 0. |
HideAllBootUI | Contains an integer that suppresses all Windows UI elements (logo, status indicator, and status message) during startup. Set to 1 to suppress all Windows UI elements during startup; otherwise; set to 0 (zero). The default value is 0. |
HideBootLogo | Contains an integer that suppresses the default Windows logo that displays during the OS loading phase. Set to 1 to suppress the default Windows logo; otherwise; set to 0 (zero). The default value is 0. |
HideBootStatusIndicator | Contains an integer that suppresses the status indicator that displays during the OS loading phase. Set to 1 to suppress the status indicator; otherwise; set to 0 (zero). The default value is 0. |
HideBootStatusMessage | Contains an integer that suppresses the startup status text that displays during the OS loading phase. Set to 1 to suppress the startup status text; otherwise; set to 0 (zero). The default value is 0. |
Customize the boot screen using Windows Configuration Designer and Deployment Image Servicing and Management (DISM)
If Windows has not been installed and you are using Windows Configuration Designer to create installation media with settings for Unbranded Boot included in the image, or you are applying a provisioning package during setup, you must enable Unbranded Boot on the installation media with DISM in order for a provisioning package to successfully apply. First you have to create the image or package.
Create a provisioning package or create a new Windows image in Windows Configuration Designer by following the instructions in Create a provisioning package.
In the Available customizations page, select Runtime settings > SMISettings and then set the value for the boot screen settings. The following values are just examples.
- HideAllBootUI=FALSE
- HideBootLogo=FALSE
- HideBootStatusIndicator=TRUE
- HideBootStatusMessage=TRUE
- CrashDumpEnabled=Full dump
Tip
See SMISettings in the Windows Configuration Designer reference for more information about the available SMISettings.
Once you have finished configuring the settings and building the package or image, you use DISM to apply the settings.
Open a command prompt with administrator privileges.
Copy install.wim to a temporary folder on hard drive (in the following steps, it assumes it's called c:wim).
Create a new directory.
Mount the image.
Enable the feature.
Commit the change.
In the following image, the BootLogo is identified by the green outline, the BootStatusIndicator is identified by the red outline, and the BootStatusMessage is identified by the blue outline.
Replace the startup logo
The only supported way to replace the startup logo with a custom logo is to modify the Boot Graphics Resource Table (BGRT) on a device that uses UEFI as the firmware interface. If your device uses the BGRT to include a custom logo, it is always displayed and you cannot suppress the custom logo.
Related topics
HackBGRT is intended as a boot logo changer for UEFI-based Windows systems.
Summary
When booting on a UEFI-based computer, Windows may show a vendor-defined logo which is stored on the UEFI firmware in a section called Boot Graphics Resource Table (BGRT). It's usually very difficult to change the image permanently, but a custom UEFI application may be used to overwrite it during the boot. HackBGRT does exactly that.
Usage
Important: If you mess up the installation, your system may become unbootable! Create a rescue disk before use. This software comes with no warranty. Use at your own risk.
- Make sure that your computer is booting with UEFI.
- Make sure that Secure Boot is disabled, unless you know how to sign EFI applications.
Windows installation
- Get the latest release from the Releases page.
- Start
setup.exe
and follow the instructions.- You may need to manually disable Secure Boot and then retry.
- The installer will launch Notepad for modifying the configuration.
- If you need only one custom image, the defaults are fine.
- Otherwise, check out the examples in the configuration file.
- The installer will launch Paint for creating the image(s).
- You can create multiple images by using Save As.
- Be sure to always use the 24-bit BMP/DIB format.
- If Windows later restores the original boot loader, just reinstall.
- If you wish to change the image or other configuration, just reinstall.
Multi-boot configurations
If you only need HackBGRT for Windows:
- Extract the latest release to
[EFI System Partition]EFIHackBGRT
. - Set
boot=EFIMicrosoftBootbootmgfw.efi
in config.txt
. - Point your boot loader to
EFIHackBGRTbootx64.efi
.
If you need it for other systems as well:
- Extract the latest release to
[EFI System Partition]EFIHackBGRT
. - Set
boot=EFIyour-actual-boot-loader.efi
in config.txt
. - Set
EFIHackBGRTbootx64.efi
as your default boot loader with efibootmgr
or some other EFI boot manager tool.
On 32-bit machines, use bootia32.efi
instead of bootx64.efi
.
Configuration
The configuration options are described in config.txt
, which should be stored in [EFI System Partition]EFIHackBGRTconfig.txt
.
Images
The image path can be changed in the configuration file. The default path is [EFI System Partition]EFIHackBGRTsplash.bmp
.
The image must be a 24-bit BMP file with a 54-byte header. That's a TrueColor BMP3 in Imagemagick, or 24-bit BMP/DIB in Microsoft Paint.
Multiple images may be specified, in which case one is picked at random.
Recovery
If something breaks and you can't boot to Windows, you have the following options:
- Windows installation (or recovery) media can fix boot issues.
- You can copy
[EFI System Partition]EFIHackBGRTbootmgfw-original.efi
into [EFI System Partition]EFIMicrosoftBootbootmgfw.efi
by some other means such as Linux or Windows command prompt.
Building
- Compiler: GCC targeting w64-mingw32
- Compiler flags: see Makefile
- Libraries: gnu-efi