Skip to content

Commit 74d9940

Browse files
authored
Update upgrade-fails-with-error-0xc1900101-0x20017.md
1 parent 6dff506 commit 74d9940

File tree

1 file changed

+26
-26
lines changed

1 file changed

+26
-26
lines changed

support/windows-client/setup-upgrade-and-drivers/upgrade-fails-with-error-0xc1900101-0x20017.md

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -13,24 +13,24 @@ appliesto:
1313
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
1414
- ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
1515
---
16-
# Upgrade fails and generates error code 0xC1900101-0x20017
16+
# Upgrade fails and generates error code "0xC1900101-0x20017"
1717

18-
This article describes how to resolve Windows upgrade failures that generate error code 0xC1900101-0x20017. This error can affect both Windows Client and Windows Server editions.
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.
1919

2020
## Symptoms
2121

22-
When you try to upgrade Windows, you see either of the following behaviors:
22+
When you try to upgrade Windows, you see either of the following behaviors occur:
2323

24-
- The Windows upgrade process fails during the SAFE_OS or BOOT phases, or wile cleaning up external drivers. Windows rolls back to the previous version.
25-
- The Windows upgrade appears to finish. However, the computer fails to restart.
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.
2626

27-
Additionally, you might see other error codes such as 0x00000005.
27+
Additionally, you might see other error codes get returned, such as 0x00000005.
2828

2929
## Cause
3030

31-
This error typically results from driver or hardware configuration issues, or conflicts with third-party software. Such causes include the following issues:
31+
This error typically results from driver or hardware configuration issues, or conflicts with third-party software. Such issues include the following examples:
3232

33-
- Outdated or incompatible drivers, especially drivers for network cards, storage controllers, or external devices. For example, PVSCSI controllers are known to cause this issue.
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.
3434
- Conflicts with third-party software, including antivirus programs and security tools such as CrowdStrike.
3535
- Incorrect driver settings, such as CSagent altitude configurations in CrowdStrike.
3636
- Hardware configurations or dynamic update settings that interfere with the upgrade process.
@@ -49,9 +49,9 @@ To verify that your computer meets the requirements for Windows or Windows Serve
4949

5050
### Step 2: Review event logs
5151

52-
Use Event Viewer to review the System logs. In particular, look for any events that might be related to driver or hardware issues.
52+
Use Event Viewer to review the system logs. In particular, look for any events that might be related to driver or hardware issues.
5353

54-
If you identify an issue that you can fix, fix that issue and then try to upgrade again.
54+
If you identify an issue that you can fix, fix that issue and then try again to upgrade.
5555

5656
### Step 3: Make sure that Windows and third-party drivers are up to date
5757

@@ -65,27 +65,27 @@ If you identify an issue that you can fix, fix that issue and then try to upgrad
6565
> [!NOTE]
6666
> You might have to select each category to expand the list of devices.
6767
68-
1. To repair a driver error, right-click the marked device and then select either **Update Driver Software** or **Uninstall**.
68+
1. To repair a driver error, right-click the marked device, and then select either **Update Driver Software** or **Uninstall**.
6969

70-
After you address all the errors in Device Manager, try to upgrade again.
70+
After you resolve all the errors in Device Manager, try to upgrade again.
7171

7272
### Step 5: Check the BIOS
7373

74-
Make sure that the BIOS and firmware for the device is up to date. If needed, check the device manufacturer's website.
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.
7575

7676
### Step 6: Repair or remove unsigned drivers
7777

7878
Check for any unsigned drivers, and repair or remove them. Drivers might not be properly signed in the following circumstances:
7979

8080
- 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 corrupt or missing. If a catalog file is corrupt or missing, the driver appears to be unsigned, even though it should be signed.
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.
8282

8383
To check your system for unsigned drivers, follow these steps:
8484

85-
1. Open an administrative Command Prompt window and run the `sigverif` command.
85+
1. Open an administrative Command Prompt window, and run the `sigverif` command.
8686
1. In the File signature Verification tool, select **Start**.
8787
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. The next step is to check that 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.
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.
8989
1. At the command prompt, change to the sigcheck directory (for example, run `cd c:\sigcheck`).
9090
1. For each of the drivers that the File Signature Verification Tool lists, run `sigcheck`. For example, run the following command for each driver:
9191

@@ -97,47 +97,47 @@ To check your system for unsigned drivers, follow these steps:
9797
>
9898
> - In this command, \<DriverPath> is the driver path that the File Signature Verification Tool identified.
9999
> - 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 is 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).
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).
101101
102102
If you find unsigned drivers, follow these steps to repair them:
103103

104104
- Check for updated versions of the drivers, and install the updates.
105105
- 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 need to analyze another device to identify the catalog file that is associated with the unsigned driver.
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.
107107

108-
If none of these remedies succeed, uninstall the affected driver, and then try to upgrade again.
108+
If none of these remedies succeed, uninstall the affected driver, and then try again to upgrade.
109109

110110
### Step 7: Remove conflicting software
111111

112112
1. Try to disable any third-party anti-virus and anti-malware applications
113113
1. Reconfigure or remove software that's known to cause conflicts, such as CrowdStrike.
114-
1. Try to upgrade again.
114+
1. Try again to upgrade.
115115

116116
### Step 8: Perform a clean restart
117117

118118
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.
119119

120-
A clean restart, also known as a clean boot, starts Windows without these background applications and services. Follow these steps:
120+
A clean restart, also known as a _clean boot_, starts Windows without these background applications and services. Follow these steps:
121121

122122
1. Sign in to the affected computer as administrator.
123-
1. In the search box, type **msconfig** and then select **System Configuration**.
123+
1. In the search box, type **msconfig**, and then select **System Configuration**.
124124
1. In System Configuration, select **Services** > **Hide all Microsoft services** > **Disable all**.
125125
1. Select **Startup** > **Open Task Manager**.
126-
1. Under **Startup** in Task Manager, for each startup item, select the item and then select **Disable**.
126+
1. Under **Startup** in Task Manager, select each startup item in turn, and then select **Disable**.
127127
1. Close Task Manager.
128128
1. In System Configuration, select **Startup** > **OK**.
129129
1. Restart the computer.
130130

131-
After the computer restarts, try to update or upgrade it again.
131+
After the computer restarts, try again to update or upgrade it.
132132

133133
> [!IMPORTANT]
134134
> If you see the **Download and install updates** option during the installation process, make sure that you select it.
135135
136136
### Step 9: Remove all nonessential external hardware
137137

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 you might have plugged into your device that isn't needed for basic functionality. Additionally, disconnect or disable any network cards that you're not using for the upgrade.
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 you might have plugged into your device that isn't needed for basic functionality. Additionally, disconnect or disable any network adapters that you're not using for the upgrade.
139139

140-
After you disconnect all nonessential hardware, try to upgrade again.
140+
After you disconnect all nonessential hardware, try again to upgrade.
141141

142142
> [!IMPORTANT]
143143
> 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.

0 commit comments

Comments
 (0)