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

Anonymous

I have about 25-30 desktop PCs that I am unable to get windows update to complete on. Some of them are running 1909, a few are running 2004, but none of them will update to 20h2. The ones running 1909 wouldn't upgrade to 2004 when that came out either.

I have run setupdiag and here is the outcome of that:

Matching Profile found: FindAbruptDownlevelFailure - 55882B1A-DA3E-408A-9076-23B22A0472BD

SetupDiag version: 1.6.0.0

System Information:

Machine Name = BOS

Manufacturer = Dell Inc.

Model = OptiPlex 3070

HostOSArchitecture = 1033

FirmwareType = UEFI

BiosReleaseDate = 20200206000000.000000+000

BiosVendor = 1.3.1

BiosVersion = 1.3.1

HostOSVersion = 10.0.18363

HostOSBuildString = 18362.1.amd64fre.19h1_release.190318-1202

TargetOSBuildString = 10.0.19041.746 (vb_release_svc_prod1.210106-2232)

HostOSLanguageId =

HostOSEdition = Professional

RegisteredAV = Windows Defender

FilterDrivers = FileInfo

UpgradeStartTime = 1/26/2021 12:19:14 PM

UpgradeEndTime = 1/26/2021 12:31:52 PM

UpgradeElapsedTime = 00:12:38

CV = HWGfItqyI0SWnhx1

ReportId = B466E151-44B3-4339-BBB9-581A63214664

Error: SetupDiag reports abrupt down-level failure.

Last Operation: Finalize

Error: 0x80004005 - 0x60016

LogEntry: 2021-01-26 12:31:39, Error SP Operation failed: Update Boot Code. Error: 0x80004005[gle=0x000000b7]

Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.

Last Setup Phase:

Phase Name: Finalize

Phase Started: 1/26/2021 12:31:34 PM

Phase Ended: 1/1/0001 12:00:00 AM

Phase Time Delta: 00:00:00

Completed Successfully? False

Last Setup Operation:

Operation Name: Update Boot Code

Operation Started: 1/26/2021 12:31:38 PM

Operation Ended: 1/1/0001 12:00:00 AM

Operation Time Delta: 0:00:00:00.0000000

Completed Successfully? False

I have tried clearing all the temp files, I have blown away the softwaredistribution\download folder and those didn't work. I have used a usb drive created using the windows media creation tool and done the upgrade that way and it still fails with the same error.

Now, all of these systems have been imaged using Aomei's Backupper program. I have found some posts that talk about getting this same error when others have imaged drives using different imaging software but no one seems to have fixed it. They talk about the BCD not being able to be changed. I'm not familiar with the BCD and how all that works.

I am trying very hard not to format and reload these machines as they are mission critical systems all at different customer sites of ours. But we also need to have windows updates on, for now I had to turn them off because the system were repeatedly trying to install 20h2 like 3 times a day and rebooting the machines.

I really need help with this.

Thank you!!!

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

45 answers

Anonymous

2021-02-25T23:37:29+00:00

OK, it looks like you need to open an admin command prompt and type the command below. You can copy and paste in a command prompt window so copying the GUID number, including curly brackets is referable to typing it.

bcdedit /delete {afc84874-af1b-4c1d-ad0b-12fee47f8c2d}

The reason for this is the upgrade doesn't like entries without the necessary options. You can see the difference between what you have and what I have below. There are some other situations but hopefully, if the upgrade completes, it will fix those. You do have other entries like this one so this one is not needed.

Yours

Resume from Hibernate

identifier {afc84874-af1b-4c1d-ad0b-12fee47f8c2d}

Mine

Resume from Hibernate

identifier {4319c65a-5f17-11ea-94a8-94b86d91642c}

device partition=C:

path \WINDOWS\system32\winresume.efi

description Windows Resume Application

locale en-US

inherit {resumeloadersettings}

recoverysequence {4319c65d-5f17-11ea-94a8-94b86d91642c}

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

filedevice partition=C:

filepath \hiberfil.sys

bootmenupolicy Standard

debugoptionenabled No
Was this answer helpful?

4 people found this answer helpful.

0 comments No comments
Anonymous

2021-05-05T17:55:08+00:00

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.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2021-02-25T20:44:25+00:00
Here is the output of that command:

Firmware Boot Manager

identifier {fwbootmgr}

displayorder {bootmgr}
```
                    {5abdaa78-cbe1-11e3-a38f-8a37f6cf06ba}

                    {89ea3b12-655f-11eb-bcb7-806e6f6e6963}

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

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

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

                    {5abdaa7c-cbe1-11e3-a38f-8a37f6cf06ba}
```
timeout 1

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 {1bc041a1-7609-11eb-bcca-92af0f159dd0}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Firmware Application (101fffff)

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

path \EFI\Microsoft\Boot\bootmgfw.efi

description Windows Boot Manager

Firmware Application (101fffff)

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

description Diskette Drive

Firmware Application (101fffff)

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

description USB Storage Device

Firmware Application (101fffff)

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

description CD/DVD/CD-RW Drive

Firmware Application (101fffff)

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

description Onboard NIC

Firmware Application (101fffff)

identifier {89ea3b12-655f-11eb-bcb7-806e6f6e6963}

device partition=\Device\HarddiskVolume1

path \EFI\Boot\BootX64.efi

description UEFI: APS-SE20G-256

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 {1bc041a1-7609-11eb-bcca-92af0f159dd0}

nx OptIn

bootmenupolicy Standard

Windows Boot Loader

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

device unknown

path \Windows\system32\winload.efi

description Windows 8.1

locale en-US

inherit {bootloadersettings}

recoverysequence {5abdaa7f-cbe1-11e3-a38f-8a37f6cf06ba}

integrityservices Enable

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

osdevice unknown

systemroot \Windows

resumeobject {5abdaa7d-cbe1-11e3-a38f-8a37f6cf06ba}

nx OptIn

bootmenupolicy Standard

Windows Boot Loader

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

device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{5abdaa80-cbe1-11e3-a38f-8a37f6cf06ba}

path \windows\system32\winload.efi

description Windows Recovery Environment

locale en-US

inherit {bootloadersettings}

displaymessage Recovery

displaymessageoverride Recovery

osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{5abdaa80-cbe1-11e3-a38f-8a37f6cf06ba}

systemroot \windows

nx OptIn

bootmenupolicy Standard

winpe Yes

Resume from Hibernate

identifier {1bc041a1-7609-11eb-bcca-92af0f159dd0}

device partition=C:

path \windows\system32\winresume.efi

description Windows Resume Application

locale en-us

inherit {resumeloadersettings}

isolatedcontext Yes

allowedinmemorysettings 0x15000075

filedevice partition=C:

filepath \hiberfil.sys

bootmenupolicy Standard

debugoptionenabled No

Resume from Hibernate

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

device unknown

path \Windows\system32\winresume.efi

description Windows Resume Application

locale en-US

inherit {resumeloadersettings}

recoverysequence {5abdaa7f-cbe1-11e3-a38f-8a37f6cf06ba}

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

filedevice unknown

filepath \hiberfil.sys

bootmenupolicy Standard

debugoptionenabled No

Resume from Hibernate

identifier {afc84874-af1b-4c1d-ad0b-12fee47f8c2d}

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 Serial

debugport 1

baudrate 115200

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 {5abdaa80-cbe1-11e3-a38f-8a37f6cf06ba}

description Windows Recovery

ramdisksdidevice unknown

ramdisksdipath \Recovery\WindowsRE\boot.sdi
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2021-02-25T20:26:47+00:00

OK, the SQL errors are gone. You are still getting the IIS APPool user errors but I was told they would not stop an upgrade.

I will keep looking through the log but for now, the errors are back to not being able to copy over the BCD Store. So I will need a listing from the command below to see if I can find a problem..

bcdedit /enum all

The line below might be involved and the GUID number may show up in the bcdedit listing.

IBSLIB BCD: BcdCopyObjectEx: Failed to enumerate source elements. Target: {afc84874-af1b-4c1d-ad0b-12fee47f8c2d}
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2021-02-23T19:21:53+00:00

There are several errors concerning the BCD store, but that is after the Migration fails. If you want to check your BCD store, we can do that.

Not much changed in this log.. If you have uninstalled SQL then you may be able to remove the user..

Info MIG Mig::CPlatform::CreateProfileForUser: Called for user (NULL)(NULL) with ProfileSuffix: MSSQL$FPOSSQL, ProfilePath: C:\windows\ServiceProfiles\MSSQL$FPOSSQL

Warning SP Exception trying to create a profile for user. Will try again later.:

Error SP CreateProfileForUser succeeded but the user has no profile. Exiting.

Warning SP Exception trying to create a profile for user. Will try again later.: Win32Exception: CreateProfileForUser is only supported for non-linked profiles with a specific SID.: The request is not supported

Error SP CreateProfileForUser succeeded but the user has no profile. Exiting.

Info Entering MigCloseCurrentStore method

Error SP pSPExecuteApply: Migration phase caught exception: Win32Exception: CreateProfileForUser succeeded but the user has no profile: An internal error occurred.

Info SP SPExecuteFirstBootApply: End run. Result: 0x00000004
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments