Fix: 0xC1900101 – 0x20017 Anniversary Update error
The Anniversary Update installation process can be plagued by various errors, preventing users from getting their hands on Microsoft’s latest OS. One of the most common errors encountered by users is the 0xC1900101 – 0x20017 error code, which briefly informs them that the installation process failed in the SAFE_OS phase with an error during the BOOT operation.
This error is extremely frustrating because it appears when the Anniversary Update installation reaches 100%, and the computer enters the final restart phase. Luckily there are a few workarounds available to fix this issue.
The 0xC1900101 – 0x20017 error prevents users from installing the Anniversary Update
When I try to update to the newest version of Windows 10, during the reboot phase it takes me to a screen asking about the layout of my keyboard. After I make a selection, I can go back to Windows, but I get this error [0xC1900101 – 0x20017 ] regarding the installation failure. My hard drive is actually four 30GB SSD’s in RAID 0. I am wondering if this could be the problem? It hasn’t been an issue for any of the previous versions.
How to fix 0xC1900101 – 0x20017 Anniversary Update errors
Solution 1 – Uninstall Broadcom Bluetooth and Wireless drivers (for Windows 7, 8.1)
This error usually occurs because of a driver bug check fail. For Windows 7 and 8.1 PC owners, the culprits are the Bluetooth and Wireless Network drivers, which are not compatible with Windows 10. If you’re upgrading from these OS versions, first uninstall the two drivers and then try again to install the Anniversary Update.
- Open the Device Manager.
- Find your Bluetooth driver on the list.
- Right click the driver > select Uninstall.
- Repeat the process for the wireless network driver.
If uninstalling the two drivers didn’t solve the issue, disable them from BIOS:
- Restart your computer.
- Enter BIOS during the boot sequence.
- Go the Advanced Tab > Wireless >hit Enter.
- The options Internal Bluetooth and Internal Wlan shoould be visible.
- Disable them > press Esc to go back to the main screen > save the changes.
Solution 2 – update or uninstall the corrupted drivers
If you’re upgrading from Windows 10 to the Anniversary Update, follow these steps to locate all the problematic drivers:
- Go to Local Disk C: > Windows
- Scroll down to the Panther folder > Open it
3. Open the Setuperr.log and Setupact.log to locate the problematic drivers.
4. Uninstall the corrupted drivers.
5. If the issue is caused by an outdated driver we recommend this third-party tool (100% safe and tested by us) to automatically download all the outdated drivers on your PC.
Solution 3- unplug all peripherals
Some users have confirmed they managed to install the Anniversary Update after unplugging all peripherals from their computers. Although this may sound like a third-grade solution, you should try it out as it has proven to be useful for some users.
Solution 4- Remove additional RAM or your Network card
Sometimes the 0XC190010 – 0x20017 error is caused by extra RAM, so you can also try to remove one RAM module and make another attempt at installing the Anniversary Update. There are also users who have reported that removing their network card also fixes the issue.
If you’re still having issues on your PC or you simply want to avoid them for the future, we recommend you to download this tool to fix various PC problems, such as file loss, malware and hardware failure. It will also optimize your PC for maximum performance.
You should use this fix only if you’re good at computers. If your computer’s warranty is still valid, then you should contact a professional and have them do this for you.
RELATED STORIES YOU NEED TO CHECK OUT:
- Something went wrong error blocks Anniversary Update install
- Fix: Not Enough Disk Space for Anniversary Update
- Anniversary Update doesn’t detect the second monitor
Microsoft is all set to launch its next big update, Windows 10 version 1809 in October. While that should be a nice piece of news […]
The Windows 10 October 2018 Update (otherwise 18H2) rollout might now be two to three weeks away. For the last few months, new build previews […]