[SOLVED] Win10 2004 and Gigabyte H110-S2H ghost drives

[Alan-N]

I have a Gigabyte H110-S2H bios version F25. I'm using UEFI bios and drive is GPT

https://imgur.com/XEYSWqA

View: https://imgur.com/XEYSWqA


With Windows 10 Version 1909 I am OK
If I try and install 2004 update I loose the Windows Boot Manager drive option in the bios, it is there in the F12 boot manger option but inviible. If I select that invisible entry it all works (I also had to do his during the update), but I can never get it to boot without interrupting boot and selecting the invisible entry, even if I play around with the boot sequence and force it to the top OR remove all other options

https://imgur.com/XZFa1yq

View: https://imgur.com/XZFa1yq


If I go into the bios, the drive can be seen BUT not the version with Windows Boot Manager which is needed to get it to boot.
Oddly if I select the "Easy Setup" it can now be seen and I can move it to the first option in the boot sequence, however after saving it still is invisible in the F12 boot manager list. and refuses to be visible in the Classic view

https://imgur.com/wvP0vf7

View: https://imgur.com/wvP0vf7


After backing out 2004 to 1909 it sorts itself with no help from me.
I have performed the update and backout 3 times now (removed a clone drive, fixed a missing entry with BCDedit) and results are consistent. 2004 breaks it, 1909 sorts it

https://imgur.com/IvkTKlE

View: https://imgur.com/IvkTKlE


I can only assume its a bios issue, and something about the windows efi file it does not like

Anyone got any ideas, or have same board with 2004 amd no issues

TIA

 

[SkyNetRising]

Can you show command output of bcdedit, when booted in windows 2004 version ?

Probably "Windows Boot Manager"boot entry looses it's description string.

 

[Alan-N]

Thanks for the suggestion, I made another attempt at the update.

This is the working 1909
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-GB
inherit {globalsettings}
default {current}
resumeobject {e463606c-45c6-11e9-84e4-81acbdb7721f}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Win10 Primary
locale en-GB
inherit {bootloadersettings}
recoverysequence {e463606f-45c6-11e9-84e4-81acbdb7721f}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {e463606c-45c6-11e9-84e4-81acbdb7721f}
nx OptIn
bootmenupolicy Standard

And this is the NOT working 2004
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume3
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-GB
inherit {globalsettings}
default {current}
resumeobject {5fb00dbe-c531-11ea-9349-ea1970aad26e}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-GB
inherit {bootloadersettings}
recoverysequence {5fb00dc0-c531-11ea-9349-ea1970aad26e}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {5fb00dbe-c531-11ea-9349-ea1970aad26e}
nx OptIn
bootmenupolicy Standard

 

[SkyNetRising]

Looks the same. Only resume object and recovery sequence identifiers change.

Remove legacy boot entries from Boot sequence and leave only Windows Boot Manager.

If that doesn't change anything try fixing bootloader with bcdboot command
(execute from elevated command prompt).

bcdboot c:\windows​

 

[Alan-N]

Thanks for that suggestion. I removed legacy devices and I can now do a restart without it failing.

https://imgur.com/gSvvsIm

View: https://imgur.com/gSvvsIm


All options are empty which is a little bit disturbing, but its working
Again the proper entry shows up in the bios "Easy mode" but not in Classic mode.