Windows in place update Error 0xC1900101 – 0x4001E

I'll bet a dollar to a donut it will take a clean install to fix it.

glasskuter said:

I'll bet a dollar to a donut it will take a clean install to

Click to expand...

I hope not

Okay, the first and last subkeys should not matter.

Krzyslaw said:

This is what I have in regedit for TabletPC

Click to expand...

That's a different subkey to the one mentioned.

It looks like your DownlevelBuildNumber value is possibly missing. How did you originally install Windows 11? From Windows 10 or a clean install?

See this thread,, specifically post 3 Windows 11, version 22H2 Insider Preview 10.0.22581.200 (ni_release) Install error - 0xc1900101

x BlueRobot said:

Okay, the first and last subkeys should not matter.


That's a different subkey to the one mentioned.

It looks like your DownlevelBuildNumber value is possibly missing. How did you originally install Windows 11? From Windows 10 or a clean install?

Click to expand...

Clean instal from iso from UUPDump. I was at DEV from a long time.
At first it was update from 10 but later I did clean instal of 11.

But it would be strange as I have another PC but on Intel platform that I have updated from 22557.1 to 22598.100 without a problem from the same iso.

In general second PC was configured exactly the same

But AMD platform cannot update while Intel was smooth and without problems.

I will be now out of PC for some time. If someone have any idea write me and I will check everything later

BR

I assume this system is still running the DEV build then and not the RTM version? If you're running a DEV release build then it's going to be full of issues.

The only suggestion I can give at the moment would be to gather a Process Monitor trace while attempting to upgrade:

Capture Process Monitor BootLog
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Select the Options....Enable Boot Logging option. A Enable Boot Logging dialog will come up. Just click OK.
3. Create a folder on your desktop named BootLog.
4. Attempt to upgrade just like you have in the past. Let the machine reboot and revert just like it has in the past.
5. After the machine has rebooted and come back up to the desktop, open Process Monitor again. A message box will come up telling you that a log of boot-time activity was created and ask if you wish to save it. Click Yes and save to the BootLog folder on your desktop.
6. This may take some time as it converts the boot-time data. Allow it to finish.
7. Zip up the entire BootLog folder on your desktop and upload to a file sharing service of your choice for my review. Examples of services to upload to are Dropbox or OneDrive or SendSpace

I had this problem when trying to "promote" a Beta Channel PC to the Dev Channel. The only fix I found that worked for me was to download the Dev Channel ISO from Download Windows Insider Preview ISO, and then to perform a clean install. There's a story about this error from WindowsLatest that appeared a couple of days ago: worth reading.
HTH,
=Ed=

Please logon to Ten Forums to run these scripts.

See the posting instructions in this Ten Forums link that includes links to modify the default language to English:




Run:

V2: BSOD - Posting Instructions - Windows 10 Help Forums

Upgrade_failure_info.bat - Click here to go to the BSOD batch repository to download and run this batch file.



Post share links into this thread using one drive, drop box, or google drive.

Ed Tittel said:

I had this problem when trying to "promote" a Beta Channel PC to the Dev Channel. The only fix I found that worked for me was to download the Dev Channel ISO from Download Windows Insider Preview ISO, and then to perform a clean install. There's a story about this error from WindowsLatest that appeared a couple of days ago: worth reading.
HTH,
=Ed=

Click to expand...

Yep - at least MS acknowledge there is an issue now. No amount of running of diagnostics will solve this issue.

Guys, this early morning I managed to perform in place update to 22598.100 and than updated to 22598.200.

I am at work today but I promise that tommorrow morning I will write all steps I did to repair Windows and to perform update.