Windows 10: Upgrade 1909 -> 20H2: BSOD [0xc1900101]

I have been having this issue for a while now. Whenever I try to update to 20H2, it BSODs, only returning the code 0xc1900101. The minidump is always empty, so I am unable to really troubleshoot what the issue is.


So far, I have tried the following:

-Update through Windows Settings

-Update through a USB flash drive

-Update through the Update Assistant


All of these methods return the same BSOD and error in settings.


Further, I have already verified the following:

-All drivers are up-to-date

-BIOS is on the latest version

-No docking station or any other peripherals for that matter are connected to the system while updating



At this point, I'm stumped. I've tried everything I've seen in threads for this issue as I say above, and nothing has worked. I'm now getting daily reminders that Microsoft is cutting support for Ver.1909. I need to get this resolved.


Specs:
-System: Lenovo Thinkpad P53

-CPU: Intel Core i7-9850H

-GPU: nVidia Quadro RTX 4000 8gb vRAM Mobile

-RAM: 64gb DDR4 2666 mHz dual channel

-Drives: 1x 512gb NVME SSD Samsung with my OS, 1x 2tb M.2 SATA SSD Western Digital with files and program libraries

-Windows 10 Ver.1909 Build 18363.1500

:)

 

Inplace-Upgrade W10x64 1909 to 20H2–0xc1900101 critical process died

Inplace-Upgrade from Windows 10 x64 1909 to 20H2 – Setup reports “The installation failed in the FIRST_BOOT phase with an error during BOOT operation” with error codes 0xc1900101 0x30017 ended up in BSOD “critical process died”

“No! Not again! Please! Anything else!“ (Fry in Futurama) – This happed to often with Windows Inplace Upgrades.

Sorry for my poor English, I’m from Germany; as well I tried to translate all German Windows Messages into English, hopefully correctly. It is also my first post here, hope, that you can be patient with me if I’m doing something wrong in this post.

THE PROBLEM:
I’ve tried for many attempts to inplace upgrade Windows 10 x64 1909 to 20H2 with the current MediaCreationTool-Iso-Setup, the GUI-Part seems to run fine, but after it reboots for the first time in the SAFE_OS-Part during the installation it will run in a BSOD critical process died at approximately 38% progress.

WHAT HAVE I ATTEMPED SO FAR (a selection of the imho important steps that I’ve tried till now):
- Drivers updated
- Windows says that all current updates are loaded
- Removed temporally for inplace upgrade AV (KTS & Fortigate Client)
- Just to test it out clean installed a fresh 20H2 parallel on another ssd with no problems
- Due I want to start with out UEFI with Windows Boot Manager because of my old system I validated that my BIOS is configured with Legacy / UEFI and start in CSM mode directly from the SSD that hosts the 1909 that I want to inplace upgrade
- Validated the status and location of WindowsRE with reagentc (which was for me surprisingly at first disabled, now – after reagentc treatment with setimage parameter – it seems to be activated and correct (reagentc / info says afterwards it’s “enabled”
- Backup and rebuild boot record with CSM boot 20H2 from USB stick in cmd environment by using bootrec /fixmbr and bootrec /rebuildbcd and bcdboot C:\Windows /l de-DE /s y: /f ALL
- Running SetupDiag v1.6.0.0 from Microsoft – it says merely that by processing the FindRollbackFailure rule the error 0xc1900101-0x30017 occurred whit the last phase “Safe OS” and last operation “Close log files”; err_6.4.5.exe reports for that error codes “CLOCK_WATCHDOG_TIMEOUT bugcodes.h” / “STATUS_ALERTED ntstatus.h”
- In-deep memory test (just to be sure) with no upcoming errors so far
- In-deep tested every drive with chkdsk & the hdd and ssd manufacture provided test tools with no upcoming errors so far
- Remove programs conflicting with 20H2 (what setup reported to be critical), e. g. VM Works
- And other steps …

For further information I have posted below what the current versions of Tuneup.bat, LOGS.bat, “V2 BSOD Posting Instructions” and “Upgrade_failure_info.bat” from this forum here reported to my system. If you need more information than I will add it so far and fast I can. Because of the big files I have stored it to my website so you can download the zip with this links:
- http://www.station1.de/logs/Tuneup-b...-part-info.zip
- http://www.station1.de/logs/LOGS.zip
- http://www.station1.de/logs/SOLARIS8..._21-06-31).zip
- http://www.station1.de/logs/Upgrade_...t_21-18-11.zip
If it is too inconvenient to you, I can on demand upload the files also in this forum thread if I should to.

I guess at now that it could be a driver problem that is responsible for the BSOD critical process died, but what driver? Where can I search for the solution to this problem?

Sorry for the long post but I wanted to gave any information that seems to me important.
I know, my system is some kind of complex and that makes the problem not easier to solve. But after so many tries I’m running out of ideas – I’m so desperate that it won’t work after spending so many hours and days with it and I’m still unable to find the error.
So I would be very very glad if anybody can help me out of this frustrating situation.

1001 thanks in advance!

Yours sincerely

 

Windows 10 Pro 1909 upgrade to 2004 or 20H2 freezes at 48% 0xC1900101

Hi,

I am a new member and have signed up as I am pulling my hair out trying to figure this out for the past few months.

I currently have Windows 10 Pro 1909 installed and Windows update has tried to install Windows 2004, however whilst installing on reboot it freezes at 48%. I have also tried previously to install 2004 with an ISO mounted and USB however with no luck.

Also I have tried installing Windows 20H2 both with ISO and with USB and again it just fails and freezes at 48%.

I have attached the error message I receive i have to force shutdown (once it freezes) and it rolls back any changes.

Please can anyone help

 

Windows 10 Pro 1909 upgrade to 2004 or 20H2 freezes at 48% 0xC1900101

Hi, I've had a look through that previously and read a lot of articles online whom always suggest I need to remove any peripherals or anything connected to my computer. The thing is I am using a laptop and I have no other equipment attached to it.

Also all my drivers are up to date and Windows 10 Update is fully up to date and I have tried installing from clean boot but it still freezes at 48%

The error message I have suggests that a device driver has stopped responding to the setup as per the below link
https://docs.microsoft.com/en-us/win...res#0xc1900101

How do I find out which driver this is?