다음을 통해 공유


Windows 10 Troubleshooting: Error 0xC1900101 - 020017 - installation failed in SAFE_OS phase with error during BOOT operation

Scenario

This time we are dealing with windows 10 upgrade issue. There is an online article available which discuss about error messages that one can encounter while upgrading current windows to windows 10. Please check the link here. Issue could become really complex if windows logging is not able to capture the problem in logs for windows upgrade. Please check the link here to check with logs for windows upgrade issue.

One of the scenario where windows may not be able to capture this information is because of hardware compliant issue with windows 10. For that I would really recommend to check with respective vendor of the workstation to confirm if their drivers support windows 10 or not.

This is one of the case where I was encountering with this error message "The installation failed in the SAFE_OS phase with an error during BOOT operation" Error "0xC1900101 - 020017", while upgrading windows 7 to windows 10.

Symptoms

  1.  While upgrading, windows takes first reboot at 83 % and directly boot into recovery environment.

  2.  During this time if we hard reboot the windows, it will roll back to windows 7.

  3.  Logs, setuperr.log and setupact.log available at c:\windows~BT, reveals no information about the issue.

  4. Setupmem.dmp file is missing or doesn't get created at location, $WINDOWS.~BT\Sources\Panther\Setupmem.dmp

  5. While using err.exe to resolve first parameter in "0xC1900101 - 020017" we see below information.

    # err.exe 0xC1900101
    
    # as an HRESULT: Severity: FAILURE (1), Facility: 0x190, Code 0x101
    
    # for hex 0x101 / decimal 257 :
    
    CLOCK_WATCHDOG_TIMEOUT            bugcodes.h
    
    # A clock interrupt was not received on a secondary processor
    
    # within the allocated time interval.
    
    MMIOERR_FILENOTFOUND              mmsystem.h
    
    MCIERR_INVALID_DEVICE_ID          mmsystem.h
    
    STATUS_ALERTED                    ntstatus.h
    
    SQL_257_severity_16               sql_err
    
    # Implicit conversion from data type %ls to %ls is not
    
    # allowed. Use the CONVERT function to run this query.
    
    # 5 matches found for "0xC1900101"
    
  6. Hardware information

    • OS Name Microsoft Windows 7 Professional
    • Version 6.1.7601 Service Pack 1 Build 7601
    • Other OS Description  Not Available
    • OS Manufacturer Microsoft Corporation
    • System Name ###########
    • System Manufacturer Dell Inc.
    • System Model Precision T3600

Some insights about this hardware, Dell Precision T3600 model has two storage controllers which are embedded on motherboard itself.

  1. One is SAS RAID controller
  2. Second is SATA AHCI controller.

Above all symptoms will match if OS drive is connected to RAID controller because driver for this controller has to be provided by vendor and it is not available natively on windows 10.

Resolution

  1. Move OS drive from RAID controller to SATA AHCI controller.
  2. Upgrade the windows 7 to windows 10.
  3. Update RAID controller driver from dell website "https://downloadcenter.intel.com/download/25393/Intel-RSTe-AHCI-SCU-Software-RAID-driver-for-Windows-"
  4. Switch back the controllers for OS drive.

Or, we can inject the raid driver in install.wim, in advance, check  here for procedure.

See also

Same symptoms are observed here on this article as well.

https://blogs.msdn.microsoft.com/arvindsh/2015/07/07/error-0xc1900101-0x20017-upgrading-to-windows-10-build-10162/ 

Windows 10 upgrade errors GUIDE
https://technet.microsoft.com/en-us/itpro/windows/deploy/resolve-windows-10-upgrade-errors