[SOLVED] Windows Server Upgrade 2016 to 2022 failed 0xC1900101 - 0x20017

R

ragde7

Member
Joined
May 11, 2025
Posts
26
Hello everyone,

We have a Dell PowerEdge T340 running Windows Server 2016 Standard, Version 1607, Build 14393.xxx.

We would like to upgrade it to Windows Server 2022 Standard. However, after restarting, we receive the following error message, and the upgrade cannot be completed:

0xC1900101 - 0x20017
The installation failed in the SAFE_OS phase with an error during BOOT operation.

Here are the steps we have taken so far:
  1. Ran sfc /scannow
  2. Ran Dism /Online /Cleanup-Image /ScanHealth
  3. Ran Dism /Online /Cleanup-Image /RestoreHealth
  4. Uninstalled Panda AD 360
  5. Disabled all startup services via msconfig (only Microsoft services left enabled)
  6. Disabled SQL services
  7. Updated all important drivers and removed irrelevant ones
  8. Ran DISM /Online /Cleanup-Image /RestoreHealth /Source:X:\sources\install.wim /LimitAccess
  9. Tried in-place upgrade of Windows Server 2016 but received error 0x800F0830 - 0x20003
It would be amazing if someone could help me out with this.

Thank you in advance.
 

Attachments

Hi @ragde7,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hello and welcome,

Follow the instructions below please.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

Run the command Dism /Online /Cleanup-Image /RestoreHealth in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 
Hey PeterJ,

here are the results of the DISM command:

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.14393.4169

Abbildversion: 10.0.14393.7426

[==========================100.0%==========================] Der Wiederherstellungsvorgang wurde erfolgreich abgeschlossen.
Der Vorgang wurde erfolgreich beendet.

The DISM command was successful, but I'm sending you the CBS.log just to be on the safe side.
 

Attachments

Great.
Try the upgrade again and report the result.
 
Hey PeterJ,

Unfortunately, after the restart, the error 0xC1900101 - 0x20017 occurred again.
 
Provide the following files when available:
- C:\$Windows.~BT\Sources\panther\setupact.log
- C:\$Windows.~BT\Sources\panther\miglog.xml
- C:\Windows\setupapi.log
 
Attach the file C:\Windows\INF\setupapi.dev.log to your next reply.
 
FRST Search
  1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  2. Right-click on the file FRST64.exe and choose Run as administrator.
  3. Copy and paste SearchAll:ksthunk into the Search box and click the Search Files button.
  4. When the scan is complete, a message will display that 'Search.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'Search.txt' to your next reply.
  5. You may close any remaining open windows now.
 
The log looks normal.

Disable Secure Boot:
Restart and boot into the BIOS menu. In the Security or Boot Options settings, find the Secure Boot option and Disable it when available.
 
Hey PeterJ,

Secure Boot is turned off, however, I tried turning both this and TPM 2.0 on and off.
 
Hello PeterJ,

I've checked again, and both Secure Boot and TPM 1.2 (sorry, not TPM 2.0) are disabled.

Do you have any other ideas?

Thank you in advance.

1747681390254.webp
1747681352313.webp
 
Download & Run the tool SetupDiag
  1. Open the website SetupDiag Download Page
  2. Click the Download SetupDiag button.
  3. Create a new folder on your Desktop and nove the file SetupDiag.exe to that folder.
  4. Right-click the "SetupDiag.exe" and click Run as administrator.
  5. When completed, three files are created, "Log.zip," "SetupDiag.exe.config," and "SetupDiagResults.log" in the folder SetupDiag.exe was executed.
  6. Attach only the file "SetupDiagResults.log" to your next reply.
 
Hey PeterJ,

Thanks for the reply.

Can you tell me how long this tool usually takes? I started it about an hour ago, but no files have appeared yet.
 
Normally it runs less than 10 minutes. Just leave it running doing its job.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top