This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 31%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKA%3C/text%3E%3C/svg%3E)
hello,
We have a problem what when we try to upgrade our server from windows server 2019 to 2022 we get this error:
“0xC1900101 – 0x20017 The installation failed in the SAFE_OS phase with an error during boot operation”
How we can fix that problem ?
Thanks for your answer
The error code 0xC1900101 – 0x20017 usually indicates that an incompatible driver is present. This can cause blue screens, system hangs, and unexpected reboots.
Here are some steps you can take to fix this problem:
I try that and nothing help, 1 more thing that we do that on vmware platform. maybe have more offers? :)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 76%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAT%3C/text%3E%3C/svg%3E)
Noted for in place upgrade from Server 2016 to Server 2022 on a VMware VM, I had to shutdown the VM and upgrade the compatibility of that VM from Version 7 to Version 11 before doing the in place upgrade. This for me prevented the blue screen issue. I also had to uninstall the antivirus to prevent a different issue during the upgrade. I would recommend to have a snapshot of the VM done before the upgrade for safety and roll back option.
VM upgrade compatibility instructions: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-AE539AD0-CAE9-4FE9-AD42-00DBA542ED4F.html
An in-place upgrade is very risky and never recommended. Better option is to stand up a new one, patch fully and migrate the roles over to it.
--please don't forget to upvote and Accept as answer if the reply is helpful--
i know that, but we use a lot of service and etc.. so reinstall clean os is very difficult :( So we searching how to upgrade our servers..
Now may be a good time to script out the migration. You can find the relevant log files here.
Please don't forget to close up the thread here by marking answer.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
Not help. after update event viewer don't generate any logs about error.
setup.etl in %windir%\panther 4 days old..
Maybe any recommendation ? :)
Maybe you know where i can download a older iso image of windows server 2022
The only public available downloads from microsoft are here.
https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2022
--please don't forget to upvote and Accept as answer if the reply is helpful--
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 68%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Hello,
Encountering the error code "0xC1900101 – 0x20017" during the upgrade from Windows Server 2019 to Windows Server 2022 indicates that there was an issue during the "SAFE_OS" phase of the installation, specifically related to a boot operation. This error can be caused by various factors, including incompatible drivers, hardware issues, or software conflicts.
To fix this problem, you can try the following steps:
Check system requirements:
Verify that your server meets the minimum system requirements for Windows Server 2022. Ensure that your hardware components (CPU, RAM, disk space) are sufficient for the new version.
Update drivers and firmware:
Ensure that all device drivers and firmware on your server are up-to-date and compatible with Windows Server 2022. Visit the manufacturers' websites to download and install the latest drivers and firmware for your hardware components.
Disconnect non-essential devices:
Disconnect any non-essential external devices, such as printers, USB drives, or external storage, before starting the upgrade. Sometimes, certain peripherals can cause conflicts during the installation process.
Disable third-party software:
Temporarily disable or uninstall any third-party antivirus or security software before the upgrade. These programs might interfere with the installation process.
Run Windows Update:
Before proceeding with the upgrade, ensure that Windows Server 2019 is fully updated with the latest security and cumulative updates.
Perform a clean boot:
Perform a clean boot to start the upgrade process with minimal services and startup programs running. This helps eliminate potential software conflicts. To do this:
Press Win + R, type "msconfig," and press Enter.
In the System Configuration window, go to the "Services" tab, check "Hide all Microsoft services," then click "Disable all."
Go to the "Startup" tab and click "Open Task Manager."
In the Task Manager, disable all startup items.
Close the Task Manager and click "OK" on the System Configuration window.
Restart your server and start the upgrade process again.
Use the Media Creation Tool:
If you're using an ISO file to upgrade, try using the Windows Media Creation Tool to create a bootable USB or DVD for the upgrade. It can sometimes provide better compatibility during the installation process.
Check hardware health:
Verify the health of your server's hardware components. Run diagnostic tools or check the event logs for any hardware-related issues.
Backup data:
Before attempting any major upgrade, it's essential to back up all critical data on your server to prevent data loss in case of any unforeseen issues during the upgrade process.
If you have tried all these steps and are still encountering the same error, it might be helpful to review the setup logs to get more detailed information about the failure. Check the "C:$WINDOWS.~BT\Sources\Panther" folder for the setup logs.
If the problem persists, you can reach out to Microsoft Support or refer to their documentation for more specific troubleshooting steps related to this particular error code.
Always exercise caution when performing major system upgrades, and it's recommended to test the upgrade process in a non-production environment if possible.
I hope this helps! Let me know if you have any further questions.
I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer–
Not help. after update event viewer don't generate any logs about error. setup.etl in %windir%\panther 4 days old.. Maybe any recommendation ? :)
Sounds badly broken, a much safe / cleaner option is to stand up a new one, patch fully and migrate the roles over to it.
--please don't forget to upvote and Accept as answer if the reply is helpful--
i found in forum that other people have same problem, and they works if they updates with older iso image ->SW_DVD9_Win_Server_STD_CORE_2022__64Bit_English_DC_STD_MLF_X22-74290.ISO
Maybe you know where i can download a older iso image of windows server 2022 ? (Without volume licensing.)
Thanks