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: Most helpful
-
Anonymous
2020-03-07T10:01:45+00:00 More details needed. How did you use the Media creation Tool? Did you use Upgrade or did you make an USB and was it made bootable and did you change the BIOS boot manager to have the USB at the top?
Both, I used Media creation Tool for Upgrade but failed ,then made an USB to setup and also failed.
-
Anonymous
2020-03-07T09:57:51+00:00 Hi airborne,
I am Sumit, an Independent Advisor and a 3 year Windows Insider MVP here to help.
Looks like the Setup was not able to update boot code. Logs may tell us more ino.
Let us check the Installation log to find why the update failed. Please share the following logs:
The Panther logs. Files named Setupact.log and Setuperr.log from the following path C:$Windows.~BT\Sources\Panther
The Rollback logs: These usually are created if Windows Update rolls back. Files named Setupact.log and Setuperr.log from the following path C:$Windows.~BT\Sources\Rollback
[Only if the error code is 0xC1900101-0x30018] The Device Install Log from C:/$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
https://answers.microsoft.com/en-us/windows/for...
To upload files here, see the following article. You must copy the logs to the desktop first and then upload.
How to share diagnostic files/logs on Microsoft community
https://answers.microsoft.com/en-us/feedback/fo...
As the log size might be large consider zipping everything before uploading.
Hi Sumit
there are setupact.log and setuperr.log
seems no Setupact.log and Setuperr.log in path C:$Windows.~BT\Sources\Rollback
-
Anonymous
2020-03-07T07:44:24+00:00 More details needed. How did you use the Media creation Tool? Did you use Upgrade or did you make an USB and was it made bootable and did you change the BIOS boot manager to have the USB at the top?
-
![](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(89.60000000000001, 72%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESI%3C/text%3E%3C/svg%3E)
SD - IA 180.3K Reputation points Independent Advisor2020-03-07T07:44:17+00:00 Hi airborne,
I am Sumit, an Independent Advisor and a 3 year Windows Insider MVP here to help.Looks like the Setup was not able to update boot code. Logs may tell us more ino.
Let us check the Installation log to find why the update failed. Please share the following logs:
The Panther logs. Files named Setupact.log and Setuperr.log from the following path C:$Windows.~BT\Sources\Panther
The Rollback logs: These usually are created if Windows Update rolls back. Files named Setupact.log and Setuperr.log from the following path C:$Windows.~BT\Sources\Rollback
[Only if the error code is 0xC1900101-0x30018] The Device Install Log from C:/$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
https://answers.microsoft.com/en-us/windows/for...
To upload files here, see the following article. You must copy the logs to the desktop first and then upload.
How to share diagnostic files/logs on Microsoft community
https://answers.microsoft.com/en-us/feedback/fo...As the log size might be large consider zipping everything before uploading.