System OEMs can use these files to test their platform firmware. HP has released a customer advisory here that describes the issue, lists the affected models and points to updated BIOS versions that address this issue.
These terms do not provide you with any legal rights to any intellectual property in any Microsoft product. A device running Windows 10 has several requirements for booting into the OS. After the device's firmware initializes all the hardware, the device needs to ensure that there is enough power to boot. Afterwards, the device needs to ensure that the device is booting into the appropriate OS depending on if the user wants to perform an update or a restore on the device, or if the user wants to boot the device into the main OS.
To accommodate each of these scenarios, the Windows 10 boot process uses the following components:. The device is powered on and runs the SoC-specific firmware boot loaders, which initialize the hardware on the device and provide emergency flashing functionality.
These applications can utilize UEFI drivers and services. This OS is used specifically for installing updates. Microsoft provides a UEFI flashing application which can be used in non-manufacturing scenarios. The SoC firmware boot loaders initialize the minimal set of hardware required for the device to run.
The SoC firmware boot loaders are designed to finish as fast as possible, and nothing is drawn to the screen while they are running. The SoC firmware boot loaders also contain an emergency flashing capability that allows devices to be flashed when the boot environment is not stable and Full Flash Update FFU image-based flashing using the Microsoft-provided flashing tool is not possible.
Emergency flashing requires tools specific to the SoC. For more information, contact the SoC vendor. Inside the boot environment, individual boot applications started by the Boot Manager provide functionality for all customer-facing scenarios before the device boots.
All components inside the boot environment are provided by Microsoft and cannot be modified, replaced, or omitted by OEMs. The following diagram illustrates some of the key portions of the process that the Boot Manager follows after it is launched by the UEFI environment. After the UEFI environment launches the Boot Manager, the Boot Manager initializes boot libraries , reads the boot configuration database to determine which boot applications to run and in which order to run them.
If you're part of an enterprise, contact your IT administrator if you have any questions or issues with your UEFI password. If you aren't part of an enterprise and choose to create a UEFI password, make sure to document your password in a safe place. If your Surface is part of an enterprise, these settings may be locked or configured to your enterprise specifications. Contact your IT administrator for more information. If you aren't part of an enterprise, the default, out-of-the-box settings should be perfect for you.
If you delete Windows Boot Manager and your Surface is part of an enterprise, contact your IT administrator for support. Displays regulatory information. For more info, see Product safety warnings and instructions. Create a USB recovery drive. Boot Surface from a USB device.
Surface features. The menu options in this section apply to these Surface models:. For more info, see Safety and regulatory information.
To change the state, select the other one. Note : When Secure Boot keys are deleted, Windows displays a red screen during startup. Restart your Surface to enter the password again. When Secure Boot Control is enabled, you have two additional options:. For example, you can disable the microSD card reader so no one can use a microSD card to copy data.
The current setting appears in bold. Select Advanced Device Security and select the option you want. The USB port remains enabled in Windows.
0コメント