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 Nick Wright

Welcome to the Forum.

Is the computer a MSI Z87-GD65 Gaming and i5 4670K? 24 or 32G of memory?
Did you run Win 10 20h2 setup.exe from running windows 1909? Where did you get Win 10 20h2? Is it on a USB flash drive or is it a iso file?

From the Partition wizard disk manager image I can see at least 6 drives attached to the computer.
I suppose that the OS disk is number 6 (CT1000MX), and that it has two recovery partitions. You have a UEFI BIOS, why did you install as Legacy-MBR instead of UEFI-GPT?
I can see more drives that seems to have a OS (Drive 6, 7 and 8).

Open the case side and detach ALL other drives (SATA or Power cable), leaving on only the target disk (6).
Boot from the drive you want to upgrade and run setup.exe
Report

I would start by downloading another Win 10 20h2, mount it on the current C: drive and run setup. Don't forget to detach ALL other drives from the MB.
Link from M$ Win10_20H2_v2_German_x64.iso
Link is valid for 24h (expire 22:54 UTC)

Thank you for the provided link - I download it currently and will report - what's the difference to a original windows ms download? It reads v2 - what does it mean? Are also the German language supported? Can I inplace upgrade without risks with this version?

Many thanks in advance!

- - - Updated - - -

Anyway, I'll tried once is downloaded and report it here ...

Since the initial release of 2010 (20h2) there has been some patches to correct bugs. V2 is the last version and it is the German version.
Once you have it on the target drive, mount it and run setup.
Don't forget to detach ALL other drives from the MB.

Nick Wright said:

Ok, I'll try it - one question left: I have moved by onboard windows explorer file locations the default directories for my own user to another drive (e. g. Desktop, Personal Files, etc.) - should I remove this drive too during inplace upgrade?

If you have moved c:\users to another drive (D:\users), the drive is now part of the OS. YES you must keep the drive connected.
If you have only changed a library properties, (for example setting movies to D:\movies). No, detach the drive.
- Besides, as I mentioned above, by my second try to in place upgrade I have already plugged out any other drives than the main windows drive (which is the cruical ssd) and the 'user' drive (which is the hdd to keep the personal files that are moved from the default location by explorer properties) - that ended up in the same error - should I try it again with the new setup detaching all drives but the system drive? Do I then have first uninstalling again the AV-Software etc? What else must I do to prepare the new setup?
For the data drive, see above. Yes you should uninstall AV-Software etc.

So many thanks in advance!

See red notes

Ok, thanks for the advice - I'll do so - probably during the weekend or next week because of work ... when I'm finally done I report it here.

- - - Updated - - -
@Megahertz: - your iso made my day - wonderful - I don't no exactly why, but your iso had inplace upgraded my kind of complex system to 20H2 without detaching any drive and removing AV software - astonishing to me, but I'm happy to that. E. g. 3dmark directx raytracing feature test runs through without any problems (needs 20H2 and tier 1.1). Some of the drivers don't work anymore and one usb device driver is not recognized, I hope, that driver updates solve this problems, I care about that.

Have you any idea why your iso in contrast to ms iso can inplace upgrade?

Anyway, so many thanks - I couldn't believe before your help, that it can work

The links in the opening post were not able to be opened.
Please post new links if you still need help.