Menu
- Windows 10 Upgrade Fails To Install
- Windows 10 Failed To Install Updates
- Windows 10 Failed To Install Safe_os
Some users are receiving error 0xC1900101 – 0x20004 during upgrade from Windows 7/8.1 to Windows 10 (GA). Here are a few tips and workarounds to overcome this error.
Advertising
: We couldn’t install Windows 10 0x8007001f - 0x2006 The installation failed in the SAFEOS phase. Unanswered 4 Replies 2877 Views Created by Daryl LFP - Friday, November 8, 2019 11:49 PM Last reply by Kiki Shi - Thursday, December 5, 2019 8:03 AM. Windows 10, Version 2004 update failed to install. So, I've tried installing this update two times now without success. I've ran the Update Troubleshooter & tried reinstalling.still getting 'Last failed attempt on 9/28/2020 - 0xc1900101'. For more info, see Free up drive space in Windows 10. Run Windows Update a few times. Download and install any available updates in Windows Update, including software updates, hardware updates, and some third-party drivers. Use the troubleshooter for Windows 10 to fix Windows Update errors. Check third-party drivers and download any updates.
The error description
The error has been reported during upgrading Windows 7 or Windows 8.1 to Windows 10 (final and Preview Builds). The users are observing that install progress stall at 25%. This is the step, where install files are copied to the destination partition. The copy process stops at 84% and setup drops error code 0xC1900101 – 0x20004. The error message reported is:
Error 0xC1900101 – 0x20004
The installation failed in SAFE_OS phase with an error during INSTALL_RECOVERY_ENVIRONMENT operation.
INSTALL_RECOVERY_ENVIRONMENT is the environment used by Windows 10, to process a rollback to the previous Windows install, if an non recoverable error occurs. The error has been reported also during Upgrade to Windows 8.1 and indicates, that something went wrong exchanging/copying.
Try a log file analysis
Windows 10 setup creates log files located in the hidden folders:
$Windows.~BTsourcesPanther
$Windows.~BTsourcesRollback
$Windows.~BTsourcesRollback
In folder Panther are *.log files, while folder Rollback contains *.txt files. We need to copy the *.log files via context menu to the desktop. Then it’s possible to open the log-files in Windows editor. This Technet-thread contains parts of a setuperr.log with indications that something went wrong during WLAN driver init. In some cases, the analysis shows which driver are causing the error.
Advertising
Workaround #1: Uninstall your Antivirus/Internet Security Suites
I’ve mentioned in my German Windows 10 Upgrade-Troubleshooting FAQ – Teil 1: During upgrade to Windows 10, third party system tools like AV programs, Internet Security Suites or other system tools (virtual discs) can be a show stopper. Therefore uninstall these tools before upgrading. In case of AV software, it’s mandatory to execute also a clean tool provided by AV vendors, to clean the system from filter drivers and left over installation files/settings.
Workaround #2: Remove all unused SATA devices
There has been several reports, that DVD drives and other SATA drives are conflicting with Install Recovery Environment. Here and here users are reporting, that removing SATA DVD drive and removing SATA cables from unused devices has fixed the install issue.
Windows 10 Upgrade Fails To Install
There is a simple cause for this issue: Some main boards are using SATA controllers that doesn’t support AHCI mode – which is required during setup. In this case exchanging the SATA driver is a show stopper.
Workaround #3: Convert dynamic discs to basic disks
A user comment in my German blog article indicates another show stopper for Windows 10 upgrade:
I had a simlare problem, installation aborted among 25% with the INSTALL_RECOVERY_ENVIRONMENT error
The problem was my dynamic disk, windows cannot create a recovery partition on this type of disk.
You have to revert back to basic disk with third party tools like partition wizard
The problem was my dynamic disk, windows cannot create a recovery partition on this type of disk.
You have to revert back to basic disk with third party tools like partition wizard
Workaround #4: Remove all unused devices and drivers
If the recommendations given above doesn’t help, try to process the following check list – because there has been several hints, that incompatible drivers or hardware acts as a show stopper. https://midwestnew968.weebly.com/teamviewer-11-download-for-windows-xp.html.
- There has been a German MS Answers forum post from user “der Grieche” reporting, that removing “wrong” WWAN miniport entries in device manager has solved the upgrade issue.
- In this Technet posting an incompatible WLAN network chip was the root cause for setup conflicts. Deactivating the WLAN chip solved the issue.
- Here (user arik5405) reports that deinstalling all unused drivers was the cure for the upgrade issue.
- Remove all unused USB devices.
- Also an overclocked system can be the cause for clock_watch_timeout error.
Workaround #5: Update your drivers and BIOS
A User posts in MS Answers forum another solution for his problem on a HP Pavilion G6-2244ca. First he received error 0xc1900101-0x2000c. Then he decided to download the iso and getting the error 0xc1900101-0x20004 during upgrade.
His solution: He downloaded all drivers and bios from HP site – completed all updates – and then did the upgrade without any issue.
Another user was able to upgrade from Windows 7 after executing Windows Update-troubleshooter (click). Hope it helps to fix the issue.
Recommended Articles
Windows 10: Upgrade-Error 80240020
Windows 10: Dropping App Store Error 0x803F7003
Windows 10-Updates KB3074686; KB3074679 for Build 10240
Windows 10 Build 10130 stalls with error 0x80246017
Update fixes Windows 8.1 WinHlp32 problem (KB917607)
KB3050267 blocks Office 2013 Updates in SCCM 2012 R2 CU4
Surface Pro 3: Fix Miracast issue with Microsoft Wireless Display Adapter
Windows 7: Sidebar weather gadget “service not available”
Windows 10: Upgrade-Error 80240020
Windows 10: Dropping App Store Error 0x803F7003
Windows 10-Updates KB3074686; KB3074679 for Build 10240
Windows 10 Build 10130 stalls with error 0x80246017
Update fixes Windows 8.1 WinHlp32 problem (KB917607)
KB3050267 blocks Office 2013 Updates in SCCM 2012 R2 CU4
Surface Pro 3: Fix Miracast issue with Microsoft Wireless Display Adapter
Windows 7: Sidebar weather gadget “service not available”
Windows 10: Upgrade error 80240020
Windows 10: Upgrade error 0x80200013
Windows 10: Upgrade error 0xC1900101 – 0x20004
Windows 10: Upgrade error 0xC1900101-0x2000A
Windows 10: Upgrade error 0x80200013
Windows 10: Upgrade error 0xC1900101 – 0x20004
Windows 10: Upgrade error 0xC1900101-0x2000A
Cookies helps to fund this blog: Cookie settings
Advertising
Advertising
Windows 10 Failed To Install Updates
In my previous post, I showed you how to solve a Windows 10 Upgrade error 0x8007001F – 0x20006.
But just after overcoming this error, the Windows 10 upgrade process continues over phase 02. But the setup was stuck again at phase 4 when processing the OOBE (Out Of the Box Experience) and failed with the following message:
But just after overcoming this error, the Windows 10 upgrade process continues over phase 02. But the setup was stuck again at phase 4 when processing the OOBE (Out Of the Box Experience) and failed with the following message:
0xC1900101 – 0x4001E: The installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation.
If you don’t know it, the out of the box experience is the step when Cortana starts talking and ask you for your language preferences, Keyboard selection, Network connection…etc.
The Troubleshooting
First, let’s examine the error code 0xC1900101– 0x4001E.
The error code is a combination of two parts; The “result” code and the “extended” code.
The error code is a combination of two parts; The “result” code and the “extended” code.
Part 1: The resulting code (0xC1900101)
The 0xC1900101 is the result code. 0xC1900101 is a generic code that indicates that a rollback has occurred. Knowing that a rollback has occurred is not a big deal since I know that already. So I need to interpret the extended code 0x4001E to understand what caused the rollback.
Part 2: The extended code (0x4001E)
The extended code contains information about both the phase in which the error occurred and the operation performed when the error occurred.
By examining the code, I can deduct that the error occurred in phase 4.
By examining the code, I can deduct that the error occurred in phase 4.
Phase 4, is when the system boots for the second time and performs the following tasks:
- Migrate user settings;
- Migrate user data;
- Start OOBE (Out Of the Box Experience);
The 1E code part indicates that the error occurred during the Pre-OOBE operation ( SP_EXECUTION_OP_PRE_OOBE ).
Knowing this information can help me to search for clues in the log files.
Here are the last lines of the setupact.log under C:$WINDOWS.~BT SourcesPanther path;
Here are the last lines of the setupact.log under C:$WINDOWS.~BT SourcesPanther path;
I started reading the log file from the button up to the top, searching for keywords like error, fatal, failed…etc.
And in a short time, I found this line “FatalError [0x090001] PANTHR Exception (code 0xC0000005: ACCESS_VIOLATION) occurred at 0x00007FFFB4C75087 in C:WindowsSystem32provengine.dll…“
it seems that the setup program faced a memory access violation caused by running code loaded from the DLL provengine.dll and it generated a memory dump file.
And in a short time, I found this line “FatalError [0x090001] PANTHR Exception (code 0xC0000005: ACCESS_VIOLATION) occurred at 0x00007FFFB4C75087 in C:WindowsSystem32provengine.dll…“
it seems that the setup program faced a memory access violation caused by running code loaded from the DLL provengine.dll and it generated a memory dump file.
I then tried to analyze the dump file in windbg, by issuing the command “!analyze -v”
The result didn’t guide me toward a clear clue. So I took the instruction at the top of the call stack (provengine!TraceLoggingCorrelationVector::ToString) and put it in google search engine.
Why the instruction on the top of the stack?
Because it was the instruction that caused the memory access violation.
So, with a bit of luck, someone else has gone through the same problem and found the fix.
Because it was the instruction that caused the memory access violation.
So, with a bit of luck, someone else has gone through the same problem and found the fix.
And sure enough, I found an article, talking about the same error and delivering the solution to fix that problem.
Windows 10 Failed To Install Safe_os
The solution:
At a glance to solve the Windows 10 upgrade 0xC1900101– 0x4001E error code, you have to:
- Rename the “HKEY_LOCAL_MACHINESOFTWAREMicrosoftProvisioning ” registry key to “HKEY_LOCAL_MACHINESOFTWAREMicrosoftProvisioning.old “
- Rename the C:WindowsProvisiong folder to C:WindowsProvisiong.old
- Restart your computer;
- Run the setup again.
You can read the step by step solution here.
Do You Need Assistance?
Buy My Gig:
Please leave a comment below and share this article on your preferred social media platform, so that other persons can benefit.