Cannot upgrade to Win10 20H2 (Error Code 0xC1900101-0x20017)

I am currently running Win10 Pro Version 1909 (OS Build 18363.1500) and trying to upgrade to Win10 20H2 before the EOL for 1909 in a couple months. I keep getting an error code of 0xC1900101. I have been doing some research on this error and I have already done the following:

Updated drivers (including display and network drivers)
chkdsk /f
sfc /scannow
DISM /Online /Cleanup-Image /Restorehealth
Disabled VM in BIOS
Clean Boot (both Hardware and Software)
Ran "Troubleshoot" for Windows Update in Settings
Tried installing Win10 2004 instead (also failed with same error)

Yet, I still get the same error every time. It gets to the restart after installing 20H2, then just after the Windows logo appears, it restarts again a couple seconds later, then it loads back up still on 1909. It appears to be trying to boot 20H2 after the first reboot, then fails, then reboots again and rolls back to 1909 (when I tried installing from the 2004 .iso, in addition to getting the full error code of 0xC1900101-0x20017, I also got the "Installation failed during SAFE-OS phase with an error during BOOT operation" error after it rebooted).

My hardware is as follows:

Motherboard: AX370-Gaming 5
CPU: AMD Ryzen 5 1600X Six-Core Processor (3.6 GHz)
RAM: 16 GB
Video Card: NVIDIA GeForce 1060 6GB
Primary Drive: 240 GB SSD (35 GB free)
Secondary Drive: 1 TB HDD
(I also have a printer connected, but it is not turned on)

My antivirus is Windows Defender (no third-party AV installed)

After trying everything I could think of (and posting on the Microsoft help section), I thought I would just have to install 20H2 fresh. So I created a bootable USB drive using the latest version of MCT (20H2) and I cannot even boot into WinPE (it just shows the Windows logo for a split second, then a blinking cursor in the top left corner for about 10 seconds, then reboots and starts the cycle over). So I went a step further and created a bootable USB drive using an older version of MCT (1909) on the same USB flash drive, plugged into the same USB slot and it boots into WinPE fine. (Then just for kicks, I created a bootable USB drive from MCT 2004 and it does the same thing as 20H2.)

Clearly there is something the last 2 versions of Windows does not like about my hardware for either upgrade installations or clean installations. The only option left I can think of is to update the BIOS (which is currently F21), but I am a little nervous about doing that as the Gigabyte BIOS update page for my motherboard has a comment about having to update to other older versions of the BIOS before updating to slightly newer versions of the BIOS (i.e. F50a says you need to update to F31 before updating to F40 or later), but the absolute latest version of the BIOS (F50e) does not have that comment (so I don't know if I have to update to F31 first or not before updating to F50e).

Any help would be greatly appreciated.

Thanks!

1900101 = rollback
20017 = probable migration / driver problem



1) List and uninstall all non-Microsoft antivirus software
(This includes always on and manual software.)
(This includes running the applicable antivirus uninstall tools for any AV that could have been incompletely uninstalled)
https://www.bitdefender.com/consumer...t/answer/2625/

2) List and uninstall all non-Microsoft firewall software

3) List all Microsoft and non-Microsoft drive encryption software.
Uninstall all non-Microsoft disk encryption software




4) Please run:

a) V2 and DM:
BSOD - Posting Instructions


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


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


5) Copy and paste the whole script into administrative Powershell (PS) > click OK
> run time approximately 15 - 20 min > post a share link
(this may collect personally identifiable information)
Windowsupgradetroubleshooting.ps1

@zbook

Since @kariya21 cannot boot from a 2004 or 20h2 installation medium, the BIOS update is important first.
Then he should try the update again.
If it still fails, you can always look at the log files.
The main problem at the moment is the bios version.

Tekkie Boy said:

Hello and Welcome on TF @kariya21

You can't avoid the bios update.
For AMD processors and motherboards with old BIOS versions, a BIOS update must be carried out if Windows 10 2004 or 20h2 is to be installed.
Otherwise it comes to your mentioned problem.
If F31 has to be flashed first to go up to F40, you have to flash F31 first.
If there is still a reference to the installation of the latest chipset drivers, install these as well.


Friendly greetings
Sorry for any mistakes. English is not my native language.

Tekkie Boy,

Thanks for the reply!

Is this a known issue for older AMD processors/motherboards (not being able to move from 1909 to a newer version without updating the BIOS first)? If so, I could not find any mention of that on either the AMD website or the Gigabyte website.

@kariya21

I don't know of any manufacturer who has published such information.

But I've had several cases where it was due to the old bios

Here are some of the posts:

System Crash / Reboot when attempting to install Windows 10 : Windows10 (reddit.com)

Can't install windows on my new pc : Windows10 (reddit.com)

New computer can install Ubuntu just fine but is unable to install Windows 10 : Windows10 (reddit.com)

Help! Stuck in build 1909, update has been failing for months : windows (reddit.com)

Can't install Windows 10 from USB Drive (explanation) : windows (reddit.com)

Google Übersetzer

Google Übersetzer

As you can read, there were also new motherboards that also needed a BIOS update.

Tekkie Boy said:

@kariya21

I don't know of any manufacturer who has published such information.

But I've had several cases where it was due to the old bios

Here are some of the posts:

System Crash / Reboot when attempting to install Windows 10 : Windows10 (reddit.com)

Can't install windows on my new pc : Windows10 (reddit.com)

New computer can install Ubuntu just fine but is unable to install Windows 10 : Windows10 (reddit.com)

Help! Stuck in build 1909, update has been failing for months : windows (reddit.com)

Can't install Windows 10 from USB Drive (explanation) : windows (reddit.com)

Google Übersetzer

Google Übersetzer

As you can read, there were also new motherboards that also needed a BIOS update.

Yeah, I see that now. You would think MS or AMD would post that kind of information on their website somewhere....

Anyway, I may have stumbled on to an issue with my hard drive as well. I was trying to make a backup of my hard drive last night with Macrium Reflect Free and I got an error 23 code (CRC error) towards the end of the backup. So I ran chkdsk c: /r and it found some errors and fixed them (I ran chkdsk when I started this upgrade-to-20H2 process a month ago and it found nothing at the time). Then I tried creating another backup last night and I got the same error code. So I ran chkdsk again last night and it found nothing to fix the second time, so I gave up for the night. Now I got up this morning and tried to create a backup and got an error 6 (MFT error) almost immediately. So I ran chkdsk again and it apparently fixed that error (although I could not find where it said it fixed anything). So now I am in the middle of backup attempt number 4 and at least I did not get an error 6 this time.....

Hi,
Where did you get the iso never mind I used the same mct on three rigs none had any issues
Even a desktop from 2009 so yeah old bios lol it is very old and worked mounting the iso.

ThrashZone said:

Hi,
Where did you get the iso never mind I used the same mct on three rigs none had any issues
Even a desktop from 2009 so yeah old bios lol it is very old and worked mounting the iso.

ThrashZone,

I found this while scouring the internet for old versions of Win10 to test my theory about something major changing between Win10 version 1909 and Win10 version 2004:

Here is how you download any Windows 10 version ISO from Microsoft - gHacks Tech News

Hi,
Yeah I mounted an iso on a couple different versions to 20h2 without internet connection and it's never failed.
Not many ms checks when no internet.