Windows 10: Error 0xC1900101 - 0x20017 When Upgrading to Build 10162 Solved

Page 1 of 2 12 LastLast
  1.    04 Jul 2015 #1

    Error 0xC1900101 - 0x20017 When Upgrading to Build 10162


    Hi,

    I'm running Windows 10 Pro Build 10159 and I can't upgrade to build 10162. I tried to update through Windows Update and through the ISO, but when I need to restart my PC, it boots to Recovery Mode (giving me 2 options: 1. Turn off my PC, 2. Troubleshoot my PC - cmd, start up repair, reset my PC and etc.). I tried anything I know and could - run dism /online /cleanup-image /restorehealth, sfc /scannow, disk cleanup, disable anti-virus software (including Windows Firewall/Defender and UAC), update my drivers, unplug unnecessarily USB(s), check Windows Update service and many other things. The only last option I can think of, and I really want to avoid it, is performing clean install.

    I also run chkdsk /f /r /x on my PC's disk, and the Windows found a few errors in my disk and fixed them, but yet, the installation is still failing the same way as before. Nothing changed.

    Important note: When I'm trying to install it using the ISO, I'm getting the following message (as seen below): "0xC1900101 - 0x20017 The installation failed in the SAFE_OS phase with an error during BOOT operation".

    Click image for larger version. 

Name:	Screenshot (17).png 
Views:	2744 
Size:	14.2 KB 
ID:	23303

    I'm adding the setuperr log from the setup files ($Windows.~BT\Sources\Panther) hopefully someone can read it and help me figure out how to fix this (see attachments).

    Let me know if you need more logs/information. Thanks.
    Error 0xC1900101 - 0x20017 When Upgrading to Build 10162 Attached Files
      My ComputerSystem Spec

  2.    04 Jul 2015 #2

    I've got the same thing - The installer logo shows up but instantly reboots. The only difference is that none of the recent builds (10158, 10159, 10162) work for me, and I'm stuck on 10130. I've tried everything - Windows Update, exe installer, bootable USB, unplugging all peripherals... It just doesn't like something about my hardware. Only thing to do is wait and hope for a build that isn't borked.
      My ComputerSystem Spec

  3.    05 Jul 2015 #3

    So somehow, I successfully upgraded to build 10162. If you want the short version of this, read the TL;DR part.

    Here's what I did. First, I ran chkdsk /f /r /x on my whole disk (disk error check; you can run it on Command Prompt with Administrator privileges that way: "chkdsk X:\ /f /r /x" without the quotes, while 'X' is the driver letter), which apparently found some errors on my disk and fixed them, but that haven't solved the problem. Well, maybe it did, but the installation still failed on the first try.

    Then I read another thread (not on this site, and I'm not adding link because it may count as advertisement), which helped me understand that the problem might be because "too many device INFs are being migrated and hitting an internal limit.", and the solution for it is "remove unnecessary peripherals and remove them from Device Manager and trying the upgrade again." So I opened the Device Manager and checked under View menu "Show hidden devices", and in storage volume section, I found 4-6 (I don't remember exactly the number) "Roxio Saib" devices. I have no idea what is it, how and from where it popped up on my PC, but I know I don't have any device or software that is associated with it. I actually occurred it when I plugged my flash drive for the first time in this build (10159), and my PC identify it as Roxio Saib for some reason. Either way, I deleted all the Roxio Saib drivers, a few other drivers that looked duplicated (I kept only one of a kind) and some unnecessary drivers that if I will need them in the future, I can easily reinstall them anyway.

    There's also one last thing I did before I tried to upgrade again. I check the log again, and I saw this: "Failed to get inf path SYSTEM\CurrentControlSet\Control\Network\{4d36e975-e325-11ce-bfc1-08002be10318}\{58474950-424f-0058-cfe8-aba2187557f2}". I entered the Registry Editor and checked the path. I found a folder that contained data of the driver for Xbox controller without an INF data (other folders in the had "InfPath" string key in them, while this one didn't had it). Since I'm not using an Xbox controller a lot, I deleted the folder. In the new log (after I succeed installing build 10162), this specifically error wasn't existing. Though, the reset of the errors from the original log did exist in the new log, but it still succeed. Weird.


    TL;DR: The source of the problem is the driver(s) in the PC. It may not be the same driver my PC had issues with, but it's probably one or more of the drivers in the PC. The best way to figure out which driver is causing the problem, is by reading the setuperr.log located in C:\$Windows.~BT\Sources\Panther. Another possible solution, "is to use Disk Cleanup to clean up system files and choose Device driver packages, Previous Windows installations and Temporary Windows installation files."

    Important note: Unless you know and sure about what you're doing, it is very recommended and important to backup your files/drivers/registry keys or create a restore point. Deleting the wrong driver or registry key may damage your PC and may not be reversible without a backup.
      My ComputerSystem Spec


  4. Posts : 10
    Windows 10 build 10130
       05 Jul 2015 #4

    10162 update and iso install total fail 0xC1900101 - 0x20017
    G3258,***AsRock h97m Pro4 latest Bios ver 1.9***, 8gb ram, Samsung 850 SSD
    I can reinstall and use 10130 with zero issues (using same and different 3.0 usb drives tried, with Win 7 Usb tool)
    - but starting with 10158, and especially 10162, 100% boot crash at startup, even if I install 10130 1st, then 10162 iso, same crash once any of kind of re-booting starts. Updating via Windows update, same thing. I have other PC and Laptops that I have used the SAME usb drive with the 10162 on, they installed with no problems.
    I pulled the SSD and put it in ANOTHER build I have with a i5 4690 core and a AsRock h97 Extreme 3 board, no problems with SSD, fired up 10162 it installed on drive with no problem, so its not the SSD. But, not sure still even I put a standard (new) HD drive back on the ***Pro4 build***, exact same problem.
    Logic says the new 10162 hates the ***AsRock h97m Pro4*** board, or something on it.


    NO EXECUTE MEMORY PROTECTION is ENABLED...

    I would L O V E to solve this problem just because, but at this point I am ready to give up and hope MS is tweaking the builds still to irritate systems such as mine. Odd though as 10130 drops on this board like it was made for it. Fire up 10162, and you would swear something broke between the time reaching for the USB install. Odd indeed

      My ComputerSystem Spec

  5.    05 Jul 2015 #5

    Doesn't seem to be a driver issue in my case - I even wiped the HDD with Derik's Boot and Nuke and no luck.

    My PC:
    Gigabyte GA-B85M Gaming 3
    Pentium G3258
    8GB RAM

    Edit: Must be the G3258 it's failing on... This guy claims it's because his is overclocked, but mine isn't and it still crashes.
    Windows 10 - new builds wont boot
      My ComputerSystem Spec


  6. Posts : 21
    Windows 7 Professional
       05 Jul 2015 #6

    The download happened and yes the error did too. Rebooted and it did run its Upgrade setup very nicely with no errors thus far. MS has changed the graphics of the startup page along with other nice tweaks. I did seeit loading itself and programs faster without using a deframenter. I think it is getting close to the release version. I cannot comment about Cortana or Edge as I don't use either.
      My ComputerSystem Spec


  7. Posts : 10
    Windows 10 build 10130
       05 Jul 2015 #7

    tenuser said: View Post
    Doesn't seem to be a driver issue in my case - I even wiped the HDD with Derik's Boot and Nuke and no luck.

    My PC:
    Gigabyte GA-B85M Gaming 3
    Pentium G3258
    8GB RAM

    Edit: Must be the G3258 it's failing on... This guy claims it's because his is overclocked, but mine isn't and it still crashes.
    Windows 10 - new builds wont boot
    Umm, Your not referring to me are you?? Mines not OC'd btw.

    My system is just extra retarded as I can install 10130 from iso with NO problems. Updating to 10162 from windows update or installing 10162 from iso from within 10130, OR from a boot/fresh install starts the death loop from h*ll with anything 10162
      My ComputerSystem Spec


  8. Posts : 10
    Windows 10 build 10130
       08 Jul 2015 #8

    Londo said: View Post
    Umm, Your not referring to me are you?? Mines not OC'd btw.

    My system is just extra retarded as I can install 10130 from iso with NO problems. Updating to 10162 from windows update or installing 10162 from iso from within 10130, OR from a boot/fresh install starts the death loop from h*ll with anything 10162
    Anyway, here my setuperr file:


    2015-07-07 17:19:55, Error CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-07 17:20:01, Error SP CSetupPlatform::ResurrectNewSystem: Failure: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat: The system cannot find the file specified. [0x00000002] __cdecl UnBCL::FileStream::FileStream(const class UnBCL::String *,enum UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)[gle=0x00000002]
    2015-07-07 17:21:29, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010001)
    2015-07-07 17:21:32, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010001)
    2015-07-07 17:22:00, Error CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-07 17:22:01, Error CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-07 17:22:03, Error CDiagnosticsHelper::SetDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
    2015-07-07 17:22:03, Error CDiagnosticsHelper::SetDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
    2015-07-07 17:22:12, Error CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-07 17:22:12, Error CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-07 17:22:20, Error CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-07 17:22:21, Error CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-07 17:22:45, Error CDiagnosticsHelper::SetDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
    2015-07-07 17:22:54, Error CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-07 17:22:58, Error CONX Failed to initialize net class data 80070002


    2015-07-07 17:23:10, Error CONX Failed to get inf path SYSTEM\CurrentControlSet\Control\Network\{4d36e975-e325-11ce-bfc1-08002be10318}\{58474950-424f-0058-cfe8-aba2187557f2}


    2015-07-07 17:23:10, Error CONX Failed to add net component 80070002


    2015-07-07 17:23:10, Error CONX Failed to open inf key SYSTEM\CurrentControlSet\Control\Network\{6bdd1fc5-810f-11d0-bec7-08002be2092f}\{a1252922-f77d-4de4-a7f2-7291974c379f}


    2015-07-07 17:23:10, Error CONX Failed to add net component 80070002


    2015-07-07 17:24:01, Error [SetupHost.Exe] ReAgentXMLParser::ParseConfigFile (xml file: C:\$WINDOWS.~BT\Sources\SafeOS\ReAgent.xml) returning 0X2
    2015-07-07 17:24:06, Error SP CInstallDUUpdatesOffline::FindOperation: No info found in section DynamicUpdate.Drivers of file C:\$Windows.~BT\Updates\Critical\SetupPlatform.ini[gle=0x00000002]
    2015-07-07 17:24:06, Error SP CInstallDUUpdatesOffline::FindOperation: No info found in section DynamicUpdate.GDRs of file C:\$Windows.~BT\Updates\Critical\SetupPlatform.ini[gle=0x00000002]
    2015-07-07 17:24:06, Error SP CInstallDUUpdatesOffline::FindOperation: No info found in section DynamicUpdate.Langpacks of file C:\$Windows.~BT\Updates\Critical\SetupPlatform.ini[gle=0x00000002]
    2015-07-07 17:24:06, Error SP CInstallDUUpdatesOffline::FindOperation: No info found in section DynamicUpdate.FeaturesOnDemand of file C:\$Windows.~BT\Updates\Critical\SetupPlatform.ini[gle=0x00000002]
    2015-07-08 13:30:12, Error SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
    2015-07-08 13:30:19, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: "id" attribute is mandatory. void __cdecl Mig::CMXEMigrationXml::LoadSupportedComponent(class UnBCL::XmlNode *,int,class Mig::CMXEMigrationXml *,class Mig::CMXEXmlComponent *)
    2015-07-08 13:30:21, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{39CC25F3-AF21-4C42-854D-0524249F02CE} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
    2015-07-08 13:30:40, Error [0x0808fe] MIG Plugin {65cbf70b-1d78-4cac-8400-9acd65ced94a}: CreateProcess(s) failed. GLE = d
    2015-07-08 13:31:32, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] Failed to get preferred homegroup with hr=0x80070490
    2015-07-08 13:31:32, Error [0x0808fe] MIG Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: CBrgUnattend::CollectBridgeSettings failed: 0x1, 0
    2015-07-08 13:31:38, Error [0x0808fe] MIG Plugin {D12A3141-A1FF-4DAD-BF67-1B664DE1CBD6}: WSLicensing: Failed to read machine binding, hr=0x80070002
    2015-07-08 13:31:38, Error [0x0808fe] MIG Plugin {D12A3141-A1FF-4DAD-BF67-1B664DE1CBD6}: WSLicensing: Error reading Server Info hr=0x80070490
    2015-07-08 13:31:41, Error CSetupAutomation::Resurrect: File not found: C:\$Windows.~BT\Sources\Panther\automation.dat[gle=0x00000002]
    2015-07-08 13:31:41, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
    2015-07-08 13:32:03, Error MOUPG CSetupHost::ReportEventW(1618): Result = 0x8024F005
    2015-07-08 13:32:03, Error MOUPG SetupHost: Reporting pending reboot event failed: hr = [0x8024F005]
    2015-07-08 13:32:03, Error MOUPG CDlpManager::AsyncSerializeDisable(471): Result = 0x80070216

      My ComputerSystem Spec

  9.    09 Jul 2015 #9

    Can you try 10166 that's on Windows Update?
      My ComputerSystem Spec


  10. Posts : 10
    Windows 10 build 10130
       11 Jul 2015 #10

    tenuser said: View Post
    Can you try 10166 that's on Windows Update?
    Same crash - I just read on another thread I posted looking for here that there may be something that started on the 10158 builds that was to fix AMD CPU's that my G3258 is specific does not work well with and my potentially be the cause on this problem.

    Not confirmed but its the best lead I've had so far, and it makes sense somewhat...I guess...
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
Solved Windows 10 Error code 0xc1900101-0x30018 in Installation and Upgrade
Upgrading a Windows 8.1 installation and it stuck at getting devices ready at 2%. No BSOD. Has to be specific to 8.1 as I have already installed 10 on a clean partition with no issues on this machine. All drivers up to date. Did try removing Avast....
Hi, I am trying to upgrade one of my desktops from Windows 8.1 to Windows 10 build 10240, but I am always receiving the error that Windows 10 Installation has failed. I tried to upgrade my ultrabook and my other desktop and everything went fine. I...
I successfully installed build 10159 when it came out (the prior builds were also successfully installed); however, when I tried to download 10162, the download appeared to be successful, but the install step failed, giving me the 0x800705b4 error...
I've tried restarting the wuauserv service, no luck. But, if this is a problem I can't fix, can I upgrade from the ISO? I don't want to do a clean install.
Don't know what program/driver/windows update is causing it. This could be an issue for upgrading. There is one other method I haven't tried. See, Microsoft wants you to upgrade to the free version. Looks more like I will be sticking...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 16:39.
Find Us