Try using bcdedit to remove the entry then check the registry to see if it is gone.. Copy and pasting GUID numbers makes it very easy to make sure the ID is correct..
bcdedit /delete {5ea6dc0b-7e7b-4d4e-af09-58846bdaabda}
1809 update to 1909/2004 failed，error code: 0x80004005 - 0x60016
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
OS version: Windows10 Home 1809
I used Windows update, MediaCreationTool1909, ISO file and USB install for updating to 1909 but all failed. Then I switched to Insider Preview and tried to update to 2004 but still failed.
Logs:
Windows for home | Windows 10 | Install and upgrade
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.
Answer accepted by question author
Anonymous
40 additional answers
Sort by: Oldest
-
Anonymous
2020-06-30T00:14:16+00:00 Hi Guys ! Can you please help me specify which registry string seems to be corrupted in BCDEDIT ? I cannot find 5ea6dc... string on my machine. But the other symptoms are as airborne_76 described. I cannor update to build 2004.
Thanks for help !
C:\WINDOWS\system32>bcdedit -enum all -v
Windows Boot Manager
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
description Windows Boot Manager
locale pl-PL
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {274b7cae-0c46-11e9-890a-e56282a134a5}
resumeobject {274b7cad-0c46-11e9-890a-e56282a134a5}
displayorder {274b7cae-0c46-11e9-890a-e56282a134a5}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
Windows Boot Loader
identifier {043e0de4-560b-11e8-8345-e5f877175978}
Windows Boot Loader
identifier {059b2da8-bacd-11e9-8d35-fb2b1026f800}
Windows Boot Loader
identifier {274b7cab-0c46-11e9-890a-e56282a134a5}
Windows Boot Loader
identifier {274b7cae-0c46-11e9-890a-e56282a134a5}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 10
locale pl-PL
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {059b2da8-bacd-11e9-8d35-fb2b1026f800}
volumebandid 1
displaymessageoverride Recovery
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {274b7cad-0c46-11e9-890a-e56282a134a5}
nx OptIn
bootmenupolicy Standard
Windows Boot Loader
identifier {53dc410d-5af1-11e6-8917-9a7a88ce48f5}
device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{53dc410e-5af1-11e6-8917-9a7a88ce48f5}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale pl-PL
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
displaymessage Recovery
displaymessageoverride Recovery
osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{53dc410e-5af1-11e6-8917-9a7a88ce48f5}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
custom:46000010 Yes
Windows Boot Loader
identifier {96352bff-bcf5-11df-bbd8-bd84c5e8d440}
device ramdisk=[unknown]\Recovery\b3fe415e-b231-11df-a897-e32d9f4c21ad\Winre.wim,{96352c00-bcf5-11df-bbd8-bd84c5e8d440}
path \windows\system32\winload.exe
description Windows Recovery Environment (odzyskano)
locale
osdevice ramdisk=[unknown]\Recovery\b3fe415e-b231-11df-a897-e32d9f4c21ad\Winre.wim,{96352c00-bcf5-11df-bbd8-bd84c5e8d440}
systemroot \windows
winpe Yes
custom:46000010 Yes
Windows Setup
identifier {cbd971bf-b7b8-4885-951a-fa03044f5d71}
device ramdisk=[C:]$WINDOWS.~BT\Sources\SafeOS\winre.wim,{274b7caf-0c46-11e9-890a-e56282a134a5}
bootstatdevice unknown
custom:11000083 unknown
path \windows\system32\winload.exe
description Windows Rollback
locale pl-PL
bootstatfilepath $WINDOWS.~BT\Sources\SafeOS\bootstat.dat
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
restartonfailure Yes
osdevice ramdisk=[C:]$WINDOWS.~BT\Sources\SafeOS\winre.wim,{274b7caf-0c46-11e9-890a-e56282a134a5}
custom:21000152 unknown
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
Resume from Hibernate
identifier {274b7cad-0c46-11e9-890a-e56282a134a5}
device partition=C:
path \WINDOWS\system32\winresume.exe
description Windows Resume Application
locale pl-PL
inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
recoverysequence {059b2da8-bacd-11e9-8d35-fb2b1026f800}
recoveryenabled Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Resume from Hibernate
identifier {becfbb0d-560a-11e8-9c53-6c626d0fd34b}
device partition=C:
path \WINDOWS\system32\winresume.exe
description Windows Resume Application
locale pl-PL
inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
recoverysequence {043e0de4-560b-11e8-8345-e5f877175978}
recoveryenabled Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Windows Memory Tester
identifier {b2721d73-1db4-4c62-bf78-c548a880142d}
device partition=C:
path \boot\memtest.exe
description Diagnostyka pamięci systemu Windows
locale pl-PL
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
badmemoryaccess Yes
EMS Settings
identifier {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
bootems No
Debugger Settings
identifier {4636856e-540f-4170-a130-a84776f4c654}
debugtype Serial
debugport 1
baudrate 115200
RAM Defects
identifier {5189b25c-5558-4bf2-bca4-289b11bd29e2}
Global Settings
identifier {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
inherit {4636856e-540f-4170-a130-a84776f4c654}
{0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Boot Loader Settings
identifier {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
{7ff607e0-4395-11db-b0de-0800200c9a66}
Hypervisor Settings
identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Resume Loader Settings
identifier {1afa9c49-16ab-4a5c-901b-212802da9460}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
Device options
identifier {043e0de5-560b-11e8-8345-e5f877175978}
Device options
identifier {059b2da9-bacd-11e9-8d35-fb2b1026f800}
Device options
identifier {274b7cac-0c46-11e9-890a-e56282a134a5}
Device options
identifier {274b7caf-0c46-11e9-890a-e56282a134a5}
description Windows Setup
ramdisksdidevice partition=C:
ramdisksdipath $WINDOWS.~BT\Sources\SafeOS\boot.sdi
Device options
identifier {96352c00-bcf5-11df-bbd8-bd84c5e8d440}
ramdisksdidevice unknown
ramdisksdipath \Recovery\b3fe415e-b231-11df-a897-e32d9f4c21ad\boot.sdi
Device options
identifier {d5ee3ba1-0c43-11e9-9c68-6c626d0fd34b}
description Windows Setup
ramdisksdidevice partition=C:
ramdisksdipath $WINDOWS.~BT\Sources\SafeOS\boot.sdi
-
Anonymous
2020-06-30T08:02:48+00:00 First of all, check your update setup log
(C:\Windows\WINDOWS\Panther\NewOs\Panther\setupact.log)
Check for errors, like this
2020-04-24 10:47:57, Error IBSLIB BCD: BcdCopyObjectEx: Failed to enumerate source elements. Target: {744ba23a-fed7-11e8-853a-f021ba613df4} Flags: 0x4 Status: c0000024[gle=0x00000002]
...
SP Operation failed: Update Boot Code. Error: 0x80004005[gle=0x000000b7]
Now you see, on my PC was the error in the bcd section {744ba23a-fed7-11e8-853a-f021ba613df4}
After you find the right BCD identifier, that stops the update, you should open the command prompt with admin rights, and run:
bcdedit /delete {744ba23a-fed7-11e8-853a-f021ba613df4}
(Replace the identifier with yours, you find in the error log)
After all, re-run update.
-
Anonymous
2020-06-30T09:19:29+00:00 OK, I see that the problem has much deeper nature. I opened the Panther\setupact.log. The file is lagre, it's 191 MB !!! There are milions of errors but none seem to be relaterd with BCD. Some examplese below:
2020-06-30 02:11:53, Error CONX 0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]
or:
2020-06-30 02:11:56, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddAntiMalwareFiles (616): Failed to construct file asset [c]: [0x80004005][gle=0x80004005]
2020-06-30 02:11:56, Info CONX Windows::Compat::Appraiser::WicaApplicationInventory::GetInventory (295): Finished reading Application Inventory. 351 Apps, 857 Files.
2020-06-30 02:11:56, Info CONX Windows::Compat::Appraiser::WicaEngine::RunComponents (1345): Tier complete: Inventory.
2020-06-30 02:11:56, Info CONX Windows::Compat::Appraiser::WuDriverCoverageDataSource::PrefetchData (611): Default WU service is not on WSUS.
2020-06-30 02:11:56, Info CONX Windows::Compat::Appraiser::WuDriverCoverageDataSource::PrefetchData (705): WU not populated [20H1].
2020-06-30 02:11:58, Info CONX Windows::Compat::Appraiser::WicaEngine::CheckComponentResult (2209): Swallowing error [0x800700e8] for [DatasourceWuDriver].
There are also some errors related with Bitbefender AV free edition but I unistalled it long time ago.
I restored windows image several times with Acronis True Image and I believe the problem may be also related with this. Anyway, thanks for your help so far and any further help will be very much appreciated.
Regards, Tom
-
Anonymous
2020-06-30T11:52:59+00:00 OK I found something that may help. The setuperr shows:
CONX 0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]
An SDD-drive driver problem ?
Thanks, Tom