[German]Some users are receiving error 0xC1900101-0×20017 or 0xC1900101-0×30017 during upgrading a Windows 7/Windows 8.1 machine to Windows 10. Here are a few hints, to overcome this show stopper.
Users are observing these errors during upgrade from previous Windows versions to Windows 10.
Try a log file analysis
To find out, what causes this error code, try to analyze the log files created during setup. All log files are collected in hidden folders:
Folder Panther contains *.log files, whilst folder Rollback contains *.txt files. Just copy these *.log files via explorer to desktop and open it in Windows editor notepad. Then search for the error code. In some cases, some additional hints may be found.
Troubleshooting Upgrade error 0xC1900101-0×20017
If a log file analysis doesn’t provide any clue about the root cause, you can process the following checks to prevent show stoppers:
- Convert your hard disk into a GPT partition scheme (only on UEFI systems) – see the remark from my MVP colleague Andre da Costa within for this US-Wiki.
- If you’ve use Truecrypt, encrypt your whole disk and try upgrade again.
- As mentioned in my old (German) Windows 8.1 blog post, remove unused 2nd hard disks.
- Here jwbecker mentioned, that SSDs connected to a RAID or other storage controller was the root cause. Plugging it to a SATA controller solved the issue. Also a storage controller O2Micro was found as a show stopper.
- Here is a hint, that this is a hardware specific issue affecting a few Samsung models which are expecting a specific IOCTL to be set on boot. There is no fix for such machines afaik.
- I’ve seen also reports, where Paragon’s Migrate OS to SSD 4.0 was supposed to be the root cause (see).
- Here somebody mentioned, that a disabled UEFI boot on a Samsung notebook was the cause.
- Disable netword and Wifi adapters (and use an ISO file created via Media Creation Tool) for upgrade. Here I found a suggestion to remove a Broadcom WiFi module.
- Here some guys have to upgrade the BIOS (to disable overclocking, see ASRock-forum). See also this MS Anwers thread. It seems that it hits also Intel Pentium G3258 – in this case, disabling one core could solve the issue.
- On some systems with Intel CPU, it seems that KB3064209 (an Intel Microcode update issued in June 2015) caused the issue. This update changes C:\Windows\system32\mcupdate_genuineintel.dl. See this MS Answers thread to get a workaround for this issue.
- Sometimes resetting the BIOS to optimized defaults worked. I’ve seen also incidents, where tools like IOBit driver booster or Tuning tools are the root cause for this update error.
If the tips given above won’t fix the problem, refresh your previous Windows copy and try upgrade again. Also a clean install solved the problem (but there is the activation problem for Upgrade solutions).
Troubleshooting Upgrade error 0xC1900101-0×20017/0xC1900101-0×30017
Microsoft supporters told me: This is a failure to boot into Windows 10 immediately after the WinRE phase. It’s typically due to a boot critical 3rd party driver. Unfortunately, there is nothing very actionable for those hitting this error. About all you can do externally is to make sure all your drivers are up to date, and remove any drivers not absolutely needed. Here a few hint’s what I’ve observed in German MS Anwers forum as show stoppers:
- Uninstall your security software (firewall, antivirus software, protect software) and try to run also a clean tool provided by software vendor (to clean remaining filter drivers).
- Uninstall TuneUp, virtual drive software and similar tools – undo all “changes” made by tuning tools.
- Remove all unused devices and deactivate drivers/devices in device manager.
- Some users are reporting non compatible graphics driver causing this error message. If possible, uninstall your graphic adapter driver and try VGA driver during upgrade.
- Also take care, that the disks are not encrypted (TrueCrypt) and also in proper NTFS-MBR/GPT-Format.
Have also a look into this US MS Answers-Wiki (German edition Windows 10: Installations- und Upgrade-Troubleshooting).
But at the end of the day, some users are stuck with their machines at the old Windows version, because the system isn’t ready for Windows 10 upgrade.