Closed T-thanha closed 4 years ago
@autkub101 Can you send the output of bcdedit
from a terminal?
identifier {bootmgr} device partition=\Device\HarddiskVolume1 path \efi\microsoft\boot\bootmgfw.efi description Windows Boot Manager locale en-US inherit {globalsettings} default {current} resumeobject {9cd5af37-b438-11ea-a5d9-a379ad374238} displayorder {current} toolsdisplayorder {memdiag} timeout 30
identifier {current} device partition=C: path \WINDOWS\system32\winload.exe description Windows 10 locale en-US inherit {bootloadersettings} recoverysequence {f033339d-aae1-11ea-91da-a022692fe1bd} displaymessageoverride Recovery recoveryenabled Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \WINDOWS resumeobject {9cd5af37-b438-11ea-a5d9-a379ad374238} nx OptIn bootmenupolicy Standard
path \WINDOWS\system32\winload.exe
It appears you are running a BIOS installation, which will not work with a UEFI bootkit.
However, it is interesting that Windows says it has a boot manager entry on the EFI system partition, yet the boot loader is still winload.exe
as if it is a legacy system being loaded by the bootmgr stub.
path \WINDOWS\system32\winload.exe
It appears you are running a BIOS installation, which will not work with a UEFI bootkit.
However, it is interesting that Windows says it has a boot manager entry on the EFI system partition, yet the boot loader is still
winload.exe
as if it is a legacy system being loaded by the bootmgr stub.
do you have a fix?
@autkub101 You can convert your existing Windows installation to UEFI.
Thx you
How to use it ? Boot usb with no uefi and use command umap driver.sys or boot success restart use cmd run administrators umap driver.sys ? Or more
Run with uefi Failed to find the Windows EFI bootloader