Windows 11 Boot issue

Question

Hi

Last night I attempted to perform an upgrade to Windows 11 Pro 2024/H2 on my PC. This failed, and I'm not sure why. But I want to return my PC to it's previous state. Now, the only way I can boot in successfully is to go to the Boot Menu and select the Windows Boot Menu. From there I boot in just fine, but it doesn't automatically reboot without this extra step,

I'm not sure why this was changed during the upgrade, but I'm happy that my WIndows install is still completely intact. I just need to be able to set it to reboot to the correct place.

Can you shed some light on this please?

Thank you

Rob

Answer 1

Hi Ramesh,

It makes me skittish to attempt this upgrade again. I've never had a WIndows update go so horribly wrong. Any idea why that might happen? I downloaded the update to my F: Drive on the PC, ran the update from there, upon reboot after doing the install, is when the recovery screen popped up. Is it because you can't run an update like that from another drive on the computer?

Answer 2

Hi Robert,

Glad it's fixed by changing the UEFI settings.

By the way, the command-line I posted is to be run from admin Command Prompt. Since the issue is resolved, it's not required now.

Regards,

Answer 3

Hi Ramesh,

Firmware Boot Manager

---

identifier {fwbootmgr}

displayorder {bootmgr}

                    {fa149dbe-8409-11ef-9022-806e6f6e6963} 

timeout 2

Windows Boot Manager

---

identifier {bootmgr}

device partition=\Device\HarddiskVolume1

path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

resumeobject {f5c6a55a-7f9d-11ef-b258-caf636ff3f0f}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Firmware Application (101fffff)

---

identifier {fa149dbe-8409-11ef-9022-806e6f6e6963}

path \EFI\BOOT\BOOTX64.EFI

description UEFI OS

Windows Boot Loader

---

identifier {current}

device partition=C:

path \Windows\system32\winload.efi

description Windows 11

locale en-US

inherit {bootloadersettings}

recoverysequence {f5c6a558-7f9d-11ef-b258-caf636ff3f0f}

displaymessageoverride Recovery

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

osdevice partition=C:

systemroot \Windows

resumeobject {f5c6a556-7f9d-11ef-b258-caf636ff3f0f}

nx OptIn

bootmenupolicy Legacy

Windows Boot Loader

---

identifier {f5c6a558-7f9d-11ef-b258-caf636ff3f0f}

device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{f5c6a559-7f9d-11ef-b258-caf636ff3f0f}

path \windows\system32\winload.efi

description Windows Recovery Environment

locale en-us

inherit {bootloadersettings}

displaymessage Recovery

osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{f5c6a559-7f9d-11ef-b258-caf636ff3f0f}

systemroot \windows

nx OptIn

bootmenupolicy Standard

winpe Yes

Resume from Hibernate

---

identifier {f5c6a556-7f9d-11ef-b258-caf636ff3f0f}

device partition=C:

path \Windows\system32\winresume.efi

description Windows Resume Application

locale en-US

inherit {resumeloadersettings}

recoverysequence {f5c6a558-7f9d-11ef-b258-caf636ff3f0f}

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

filedevice partition=C:

custom:21000026 partition=C:

filepath \hiberfil.sys

bootmenupolicy Standard

debugoptionenabled No

Resume from Hibernate

---

identifier {f5c6a55a-7f9d-11ef-b258-caf636ff3f0f}

device partition=C:

path $WINDOWS.~BT\NewOS\WINDOWS\system32\winresume.efi

description Windows Resume Application

locale en-US

inherit {resumeloadersettings}

isolatedcontext Yes

allowedinmemorysettings 0x15000075

filepath \hiberfil.sys

bootmenupolicy Standard

Windows Memory Tester

---

identifier {memdiag}

device partition=\Device\HarddiskVolume1

path \EFI\Microsoft\Boot\memtest.efi

description Windows Memory Diagnostic

locale en-US

inherit {globalsettings}

badmemoryaccess Yes

EMS Settings

---

identifier {emssettings}

bootems No

Debugger Settings

---

identifier {dbgsettings}

debugtype Local

RAM Defects

---

identifier {badmemory}

Global Settings

---

identifier {globalsettings}

inherit {dbgsettings}

                    {emssettings} 

                    {badmemory} 

Boot Loader Settings

---

identifier {bootloadersettings}

inherit {globalsettings}

                    {hypervisorsettings} 

Hypervisor Settings

---

identifier {hypervisorsettings}

hypervisordebugtype Serial

hypervisordebugport 1

hypervisorbaudrate 115200

Resume Loader Settings

---

identifier {resumeloadersettings}

inherit {globalsettings}

Device options

---

identifier {f5c6a559-7f9d-11ef-b258-caf636ff3f0f}

description Windows Recovery

ramdisksdidevice partition=\Device\HarddiskVolume4

ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options

---

identifier {f5c6a55c-7f9d-11ef-b258-caf636ff3f0f}

description Windows Setup

ramdisksdidevice partition=C:

ramdisksdipath $WINDOWS.~BT\Sources\SafeOS\boot.sdi

FYI: I changed the boot order in the BIOS from UEFI to Windows Boot Drive and I can now boot into WIn 11 without this issue, but I am completely baffled as to why the 2024/H2 update would cause this.

Answer 4

Hi Rob, This is Ramesh.

Please open an admin Command Prompt and run:

BCDEDIT /enum all | clip

(This copies the command's output to the clipboard.)

Press Ctrl + V to paste the output into your reply window.