Win10 Update Error "Operation failed: Update Boot Code. Error: 0x80004005[gle=0x000000b7]"

Hi Saltgrass,

I have been following this thread and have a similar issue not being able to upgrade from Windows 10 pro version 1909 to 20H2.

I have gone through most of your steps and after running bcedit /enum all I get the following:

Firmware Boot Manager

---

identifier {fwbootmgr}

displayorder {d2dff0b3-92d2-11ea-8718-806e6f6e6963}

                        {3f421210-0ca1-11eb-880a-806e6f6e6963}

                        {c36bc6b2-8deb-11ea-8717-806e6f6e6963}

                        {c36bc6b3-8deb-11ea-8717-806e6f6e6963}

timeout 0

Windows Boot Manager

---

identifier {bootmgr}

device unknown

path \EFI\Microsoft\Boot\bootmgfw.efi

description Windows Boot Manager

locale en-us

inherit {globalsettings}

default {current}

resumeobject {49c35300-8e5b-11ea-8716-1c1bb5a52d04}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Firmware Application (101fffff)

---

identifier {3f421210-0ca1-11eb-880a-806e6f6e6963}

description Internal Hard Disk or Solid State Disk

Firmware Application (101fffff)

---

identifier {c36bc6b2-8deb-11ea-8717-806e6f6e6963}

description EFI USB Device

Firmware Application (101fffff)

---

identifier {c36bc6b3-8deb-11ea-8717-806e6f6e6963}

description EFI DVD/CDROM

Firmware Application (101fffff)

---

identifier {d2dff0b3-92d2-11ea-8718-806e6f6e6963}

device partition=\Device\HarddiskVolume2

path \EFI\Microsoft\Boot\bootmgfw.efi

description Windows Boot Manager

Windows Boot Loader

---

identifier {current}

device partition=C:

path \Windows\system32\winload.efi

description Windows 10

locale en-us

inherit {bootloadersettings}

isolatedcontext Yes

allowedinmemorysettings 0x15000075

osdevice partition=C:

systemroot \Windows

resumeobject {49c35300-8e5b-11ea-8716-1c1bb5a52d04}

nx OptIn

bootmenupolicy Standard

Resume from Hibernate

---

identifier {49c35300-8e5b-11ea-8716-1c1bb5a52d04}

Windows Memory Tester

---

identifier {memdiag}

device unknown

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}

Is this reference in red causing the problem?

Please advise.

Thanks for your help!

Ok, so I think I finally got this fixed at pretty much all of my sites.

Here is the solution.  If anyone else has this issue where 20h2 won't install and you look in the setuperr log and don't really see anything that jumps out at you here is what you should try.

Open a command prompt and run

bcdedit /enum all 

find the GUID for the "resumeobject" under the "Windows Boot Manager" and copy that GUID.

then run

bcdedit /delete (paste QUID here)

It should come back as successful, now you should be able to update to 20h2 no problems.  

I've done this at about 10 of my sites and it worked every time.

There is a command you might try running on it, perhaps it would correct or add to some of the entries.

It looks to me like the BCD store has been in place for a while and not updated by removing prior options.

Try running the command but make sure you know where the actual Win 10 install is.  I do not use Aomei so you may want to check with them..

Bootrec /rebuildbcd

See if there is anything on the link you might be able to use.  The command will not offer an OS option if it is already in the BCD Store..

I assume you have bootable install media or WinPE available.

Use Bootrec.exe in the Windows RE to troubleshoot startup issues (microsoft.com)

Thank you so much for your reply.  

To be honest with the BCD stuff is a little out of my wheel house as I have never messed with it before you told me to.  So as far as those 3 partly setup boot managers I have no clue.

What I will tell you is that again, I have imaged all these drives from one master using a product called Backupper from a company called Aomei.

After I image these drives I usually have to run a little boot repair utility that Aomei provided me to repair the boot loader so the drive will boot.  I'm not 100% sure what it does, but it comes up in a Windows PE environment and you click a "Repair" button and it reboots and boots to the drive no problem.  

These systems are as vanilla as possible, no dual or multi boot or anything like that, they should just boot into windows and thats it.  

If you are looking at all this weird stuff in the BCD, and you have thoughts on what you would do to fix it, I would love to hear it.  If you think I should delete some of those items or change the properties of others I'm all ears.

When we fixed the first one by deleting one of those BCD objects, I was able to find several of my systems that had that same error with a different GUID so I was able to delete that object on those computers and they would take the update.

I have sense now found more computers that are like this one that don't have the BCD error with the GUID where I can easily delete it and get the update to take.

I'm hoping you can give me some steps that we can fix this one and then I can repeat those steps on the several more that I have like this.

Let me know what you think.

Thanks,

Sorry, I did not pick up your prior response.

Yes, I do have some thoughts.

First, I do not know what this option in your boot manager means.

integrityservices       Enable

Next, you have 3 additional Boot Managers partly set up, do you know what these are.

Firmware Boot Manager

---

identifier              {fwbootmgr}

displayorder            {bootmgr}

                        {5abdaa7a-cbe1-11e3-a38f-8a37f6cf06ba}

                        {5abdaa78-cbe1-11e3-a38f-8a37f6cf06ba}

                        {5abdaa7b-cbe1-11e3-a38f-8a37f6cf06ba}

timeout                 2

Firmware Application (101fffff)

---

identifier              {5abdaa78-cbe1-11e3-a38f-8a37f6cf06ba}

path                    \EFI\Microsoft\Boot\bootmgfw.efi

description             Windows Boot Manager

Firmware Application (101fffff)

---

identifier              {5abdaa7a-cbe1-11e3-a38f-8a37f6cf06ba}

path                    \EFI\Microsoft\Boot\bootmgfw.efi

description             Windows Boot Manager

Firmware Application (101fffff)

---

identifier              {5abdaa7b-cbe1-11e3-a38f-8a37f6cf06ba}

device                  partition=\Device\HarddiskVolume1

path                    \EFI\Boot\BootX64.efi

description             UEFI: WDC WDS500G2B0C-00PXH0

The current boot loader is described asAOMEI Windows Boot and is missing many lines of options and has no recovery option.

You have a resume from Hibernate entry with no options..  sounds familiar, huh?

You have a Windows 8.1 boot loader..

The reagentc /info command shows a GUID number for recovery which is not in your BCD store.

If you could help me understand how this system is supposed to be configured, maybe we can get it straightened out.  You might want to compare the BCD store of this one to some others you have..