|
| 1 | +--- |
| 2 | +title: Upgrade Fails and Generates Error Code 0xC1900101-0x20017 |
| 3 | +description: Provides steps to resolve Windows upgrade failures that generate error code 0xC1900101-0x20017. |
| 4 | +ms.date: 10/16/2025 |
| 5 | +manager: dcscontentpm |
| 6 | +audience: itpro |
| 7 | +ms.topic: troubleshooting |
| 8 | +ms.reviewer: kaushika, warrenw, v-tappelgate |
| 9 | +ms.custom: |
| 10 | +- sap:windows setup,upgrade and deployment\installing or upgrading windows |
| 11 | +- pcy:WinComm Devices Deploy |
| 12 | +appliesto: |
| 13 | +- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a> |
| 14 | +- ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a> |
| 15 | +--- |
| 16 | +# Upgrade fails and generates error code 0xC1900101-0x20017 |
| 17 | + |
| 18 | +This article discusses how to resolve Windows upgrade failures that generate error code 0xC1900101-0x20017. This error can affect both Windows Client and Windows Server editions. |
| 19 | + |
| 20 | +## Symptoms |
| 21 | + |
| 22 | +When you try to upgrade Windows, you see either of the following behaviors occur: |
| 23 | + |
| 24 | +- The Windows upgrade process fails during the SAFE_OS or BOOT phases, or while it cleans up external drivers. In this situation, Windows rolls back to the previous version. |
| 25 | +- The Windows upgrade appears to finish. However, the computer doesn't restart. |
| 26 | + |
| 27 | +Additionally, you might see other error codes get returned, such as 0x00000005. |
| 28 | + |
| 29 | +## Cause |
| 30 | + |
| 31 | +This error typically results from driver or hardware configuration issues, or conflicts with third-party software. Such issues include the following examples: |
| 32 | + |
| 33 | +- Outdated or incompatible drivers, especially drivers for network adapters, storage controllers, or external devices. For example, PVSCSI controllers are known to cause this issue. |
| 34 | +- Conflicts with third-party software, including antivirus programs and security tools such as CrowdStrike. |
| 35 | +- Incorrect driver settings, such as CSagent altitude configurations in CrowdStrike. |
| 36 | +- Hardware configurations or dynamic update settings that interfere with the upgrade process. |
| 37 | + |
| 38 | +## Resolution |
| 39 | + |
| 40 | +> [!IMPORTANT] |
| 41 | +> Establish a robust backup and recovery plan before you upgrade the operating system, particularly in production environments. |
| 42 | +
|
| 43 | +### Step 1: Make sure that the computer satisfies the upgrade prerequisites |
| 44 | + |
| 45 | +To verify that your computer meets the requirements for Windows or Windows Server, see the following articles: |
| 46 | + |
| 47 | +- [Windows 11 requirements](/windows/whats-new/windows-11-requirements) |
| 48 | +- [Hardware requirements for Windows Server](/windows-server/get-started/hardware-requirements) |
| 49 | + |
| 50 | +### Step 2: Review event logs |
| 51 | + |
| 52 | +Use Event Viewer to review the system logs. In particular, look for any events that might be related to driver or hardware issues. |
| 53 | + |
| 54 | +If you identify an issue that you can fix, fix that issue and then try again to upgrade. |
| 55 | + |
| 56 | +### Step 3: Make sure that Windows and third-party drivers are up to date |
| 57 | + |
| 58 | +1. Use the Windows Update **Check for updates** function to make sure that any available Important updates, hardware updates, and driver updates were installed. To make sure that you installed all these updates, you might have to check for updates several times. |
| 59 | +1. Check third-party drivers and download any updates. You can find third-party drivers and installation instructions for any hardware you added to your device on the manufacturer's website. |
| 60 | + |
| 61 | +### Step 4: Check Device Manager for errors |
| 62 | + |
| 63 | +1. Open Device Manager (devmgmt.msc). In the list of devices, look for any device that's marked by a yellow exclamation mark. These devices have driver errors. |
| 64 | + |
| 65 | + > [!NOTE] |
| 66 | + > You might have to select each category to expand the list of devices. |
| 67 | +
|
| 68 | +1. To repair a driver error, right-click the marked device, and then select either **Update Driver Software** or **Uninstall**. |
| 69 | + |
| 70 | +After you resolve all the errors in Device Manager, try to upgrade again. |
| 71 | + |
| 72 | +### Step 5: Check the BIOS |
| 73 | + |
| 74 | +Make sure that the BIOS and firmware for the device are up to date. If it's necessary, check the device manufacturer's website. |
| 75 | + |
| 76 | +### Step 6: Repair or remove unsigned drivers |
| 77 | + |
| 78 | +Check for any unsigned drivers, and repair or remove them. Drivers might not be properly signed in the following circumstances: |
| 79 | + |
| 80 | +- You disabled driver signature verification (highly not recommended). |
| 81 | +- A catalog file (file that has a *.cat extension) that's used to sign a driver is corrupted or missing. If a catalog file is corrupted or missing, the driver appears to be unsigned, even though it should be signed. |
| 82 | + |
| 83 | +To check your system for unsigned drivers, follow these steps: |
| 84 | + |
| 85 | +1. Open an administrative Command Prompt window, and run the `sigverif` command. |
| 86 | +1. In the File signature Verification tool, select **Start**. |
| 87 | +1. After the tool runs, it provides a list of the names, locations, and versions of any unsigned drivers that it found. To see the log that the tool created, select **Advanced** > **View Log** (the log includes the unsigned driver information, and might also list the associated catalog files). |
| 88 | +1. Check whether the identified drivers have problems. In some cases, the problem might be related to the catalog file instead of the driver itself. To perform a detailed driver check, download [sigcheck.zip](https://download.sysinternals.com/files/Sigcheck.zip), and extract the tool to a directory on your computer, for example: C:\sigcheck. |
| 89 | +1. At the command prompt, change to the sigcheck directory (for example, run `cd c:\sigcheck`). |
| 90 | +1. For each of the drivers that the File Signature Verification Tool lists, run `sigcheck`. For example, run the following command for each driver: |
| 91 | + |
| 92 | + ```console |
| 93 | + sigcheck64 -i <DriverPath> |
| 94 | + ``` |
| 95 | + |
| 96 | + > [!NOTE] |
| 97 | + > |
| 98 | + > - In this command, \<DriverPath> is the driver path that the File Signature Verification Tool identified. |
| 99 | + > - If you run `sigcheck` on a 32-bit operating system, use `sigcheck -i` instead of `sigcheck64 -i`. |
| 100 | + > - Optionally, you can use the `driverquery` tool that's included in Windows to inspect drivers. For more information, see [Two Minute Drill: DriverQuery.exe](https://techcommunity.microsoft.com/t5/ask-the-performance-team/two-minute-drill-driverquery-exe/ba-p/374977). |
| 101 | +
|
| 102 | +If you find unsigned drivers, follow these steps to repair them: |
| 103 | + |
| 104 | +- Check for updated versions of the drivers, and install the updates. |
| 105 | +- Uninstall and then reinstall the drivers. |
| 106 | +- To restore a catalog file, reinstall the driver or copy the catalog file from another device. You might have to analyze another device to identify the catalog file that's associated with the unsigned driver. |
| 107 | + |
| 108 | +If none of these remedies succeed, uninstall the affected driver, and then try again to upgrade. |
| 109 | + |
| 110 | +### Step 7: Remove conflicting software |
| 111 | + |
| 112 | +1. Try to disable any third-party anti-virus and anti-malware applications |
| 113 | +1. Reconfigure or remove software that's known to cause conflicts, such as CrowdStrike. |
| 114 | +1. Try again to upgrade. |
| 115 | + |
| 116 | +### Step 8: Perform a clean restart |
| 117 | + |
| 118 | +When you start Windows by using a normal startup, several applications and services start automatically, and then run in the background. These programs include basic system processes, antivirus software, system utility applications, and other software. These applications and services can interfere with the update process. |
| 119 | + |
| 120 | +A clean restart, also known as a _clean boot_, starts Windows without these background applications and services. Follow these steps: |
| 121 | + |
| 122 | +1. Sign in to the affected computer as administrator. |
| 123 | +1. In the search box, type **msconfig**, and then select **System Configuration**. |
| 124 | +1. In System Configuration, select **Services** > **Hide all Microsoft services** > **Disable all**. |
| 125 | +1. Select **Startup** > **Open Task Manager**. |
| 126 | +1. Under **Startup** in Task Manager, select each startup item in turn, and then select **Disable**. |
| 127 | +1. Close Task Manager. |
| 128 | +1. In System Configuration, select **Startup** > **OK**. |
| 129 | +1. Restart the computer. |
| 130 | + |
| 131 | +After the computer restarts, try again to update or upgrade it. |
| 132 | + |
| 133 | +> [!IMPORTANT] |
| 134 | +> If you see the **Download and install updates** option during the installation process, make sure that you select it. |
| 135 | +
|
| 136 | +### Step 9: Remove all nonessential external hardware |
| 137 | + |
| 138 | +Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard, and display devices. Such devices include external storage devices and drives, docks, and other hardware that might be plugged into your device that isn't needed for basic functionality. Additionally, disconnect or disable any network adapters that you don't use for the upgrade. |
| 139 | + |
| 140 | +After you disconnect all nonessential hardware, try again to upgrade. |
| 141 | + |
| 142 | +> [!IMPORTANT] |
| 143 | +> To avoid potential driver conflicts for the disabled or removed devices, if you see the **Download and install updates** option during the installation process, make sure that it's disabled. |
| 144 | +
|
| 145 | +### Step 10: Check the number of local accounts |
| 146 | + |
| 147 | +To check the number of user accounts that are local to the computer, follow these steps: |
| 148 | + |
| 149 | +1. Open the Computer Management MMC snap-in (in the Search box, enter **compmgmt.msc**). |
| 150 | +1. Select **Computer Configuration** > **System Tools** > **Local Users and Groups** > **Users**. |
| 151 | +1. If any user accounts aren't used or are extraneous, remove them. |
| 152 | + |
| 153 | +### Step 11: Replace the computer |
| 154 | + |
| 155 | +If the issue persists, consider replacing the computer. |
| 156 | + |
| 157 | +## Collect data for advanced troubleshooting and support |
| 158 | + |
| 159 | +For troubleshooting assistance, contact Microsoft support. To provide supplemental information about your issue, collect the following information: |
| 160 | + |
| 161 | +- The contents of the CBS log folder (%windir%\Logs\CBS). |
| 162 | +- SetupAct.log and SetupErr.log (C:\Windows and C:$WINDOWS.~BT\Sources\Panther). |
| 163 | +- TroubleshootingScript (TSS) tool logs. For more information, see the ["Scenario: Installing or upgrading Windows"](../windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios.md#scenario-installing-or-upgrading-windows) section of "Collect data to analyze and troubleshoot Windows servicing, Updates, and Features on Demand scenarios." |
0 commit comments