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}
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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:
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.
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}
Bootrec has to be run from the Recovery environment..
From what I can tell from the setupact.logs, the Recovery environment is broken by the upgrade and get repaired during the process. Your may have just been disabled for that reason.
The upgrade seems to be failing while it is trying to set up a Rollback option, which the install does, just in case. It first shows and error regarding the earlier GUID number and says it failed to get the registry value..
Error IBSLIB BCD: Failed to get registry value. Status: c0000024[gle=0x00000002]
It then shows the following when trying to export the BCD store to the C:$Windows.~BT folder..
Error IBSLIB BCD: BcdExportStore: Failed clone BCD to ??\C:$WINDOWS.~BT\Sources*Rollback*\EFI\Microsoft\Boot\BCD. Status: c0000024[gle=0x00000002]
Then this error where is shows as failing the operation
Error IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Finalize: Failed to backup BCD database from "F:\EFI\Microsoft\Boot\BCD" to "C:$WINDOWS.~BT\Sources\Rollback\EFI\Microsoft\Boot\BCD".[gle=0x00000006]
It goes through this process twice then fails the upgrade. You can search online for some of these phrases or terms and you might run across something. But why the cloning of the BCD store would fail, possibly a bad component it cannot clone. Maybe doing a bcdedit /enum all would show such an entry.
This is the outpost of bcdedit /enum all
PS C:\Windows\system32> bcdedit /enum all
Firmware Boot Manager
identifier {fwbootmgr}
displayorder {bootmgr}
{890f9897-7d40-11e2-8053-9b1bda41daaa}
{86a34c05-5fca-11ea-b828-806e6f6e6963}
timeout 0
Windows Boot Manager
identifier {bootmgr}
device partition=F:
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-us
inherit {globalsettings}
flightsigning Yes
default {current}
resumeobject {244ac0c6-6099-11ea-b829-c46516bcf467}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Firmware Application (101fffff)
identifier {86a34c05-5fca-11ea-b828-806e6f6e6963}
description USB Drive (UEFI)
Firmware Application (101fffff)
identifier {890f9897-7d40-11e2-8053-9b1bda41daaa}
device partition=F:
description Solid State Disk
Windows Boot Loader
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 10
locale en-us
inherit {bootloadersettings}
recoverysequence {244ac0c8-6099-11ea-b829-c46516bcf467}
displaymessageoverride StartupRepair
recoveryenabled Yes
isolatedcontext Yes
flightsigning Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {244ac0c6-6099-11ea-b829-c46516bcf467}
nx OptIn
bootmenupolicy Standard
Windows Boot Loader
identifier {244ac0c8-6099-11ea-b829-c46516bcf467}
device ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{244ac0c9-6099-11ea-b829-c46516bcf467}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-us
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{244ac0c9-6099-11ea-b829-c46516bcf467}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
Windows Boot Loader
identifier {890f989a-7d40-11e2-8053-9b1bda41daaa}
device unknown
path \Windows\system32\winload.efi
description Windows
locale en-US
inherit {bootloadersettings}
recoverysequence {890f989b-7d40-11e2-8053-9b1bda41daaa}
recoveryenabled Yes
osdevice unknown
systemroot \Windows
resumeobject {890f9899-7d40-11e2-8053-9b1bda41daaa}
nx OptIn
Windows Boot Loader
identifier {890f989b-7d40-11e2-8053-9b1bda41daaa}
device ramdisk=[unknown]\Recovery\890f989b-7d40-11e2-8053-9b1bda41daaa\Winre.wim,{890f989c-7d40-11e2-8053-9b1bda41daaa}
path \windows\system32\winload.efi
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[unknown]\Recovery\890f989b-7d40-11e2-8053-9b1bda41daaa\Winre.wim,{890f989c-7d40-11e2-8053-9b1bda41daaa}
systemroot \windows
nx OptIn
winpe Yes
Resume from Hibernate
identifier {244ac0c0-6099-11ea-b829-c46516bcf467}
device partition=C:
path \Windows\system32\winresume.efi
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Resume from Hibernate
identifier {244ac0c2-6099-11ea-b829-c46516bcf467}
device partition=C:
path \Windows\system32\winresume.efi
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Resume from Hibernate
identifier {244ac0c4-6099-11ea-b829-c46516bcf467}
device partition=C:
path \Windows\system32\winresume.efi
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Resume from Hibernate
identifier {244ac0c6-6099-11ea-b829-c46516bcf467}
device partition=C:
path \Windows\system32\winresume.efi
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
recoverysequence {244ac0c8-6099-11ea-b829-c46516bcf467}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Resume from Hibernate
identifier {5ea6dc0b-7e7b-4d4e-af09-58846bdaabda}
Resume from Hibernate
identifier {890f9899-7d40-11e2-8053-9b1bda41daaa}
device unknown
path \Windows\system32\winresume.efi
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
debugoptionenabled No
Windows Memory Tester
identifier {memdiag}
device partition=F:
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 {244ac0c9-6099-11ea-b829-c46516bcf467}
description Windows Recovery
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\WindowsRE\boot.sdi
Device options
identifier {890f989c-7d40-11e2-8053-9b1bda41daaa}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\890f989b-7d40-11e2-8053-9b1bda41daaa\boot.sdi
I really need to see a picture of your Disk Management window.. The below entry is really strange..
Firmware Application (101fffff)
identifier {890f9897-7d40-11e2-8053-9b1bda41daaa}
device partition=F:
description Solid State Disk