Windows 10: Error when upgrading Windows 10 PRO 1803 to 1903: 0xC1900101 – 0x30018

Discus and support Error when upgrading Windows 10 PRO 1803 to 1903: 0xC1900101 – 0x30018 in Windows 10 Installation and Upgrade to solve the problem; I am getting following error: 0xC1900101 - 0x30018 The installation failed in the FIRST_BOOT phase with an error during SYSPREP operation... Discussion in 'Windows 10 Installation and Upgrade' started by SteveDemcak, Oct 12, 2019.

  1. Error when upgrading Windows 10 PRO 1803 to 1903: 0xC1900101 – 0x30018


    I am getting following error:

    0xC1900101 - 0x30018

    The installation failed in the FIRST_BOOT phase with an error during SYSPREP operation

    ------------------------------------------

    I have tried all the items suggested:

    • Troubleshooting in Settings / Update
    • Disabling Bitdefender antivirus software
    • Have the USB Media Creation Tool that I made -- tried this 3x
    • ran from CMD Admin -- sfc /scannow
    • ran from CMD Admin -- Reset your Windows Update Components

    I think I have tried everything I could find online for this. I did NOT have trouble updating to version 1803. The cummulative updates are working for 1803.

    I do have the following directories which I can also send if I know what/how to do so:

    $Windows.~BT\sources\Panther
    $Windows.~BT\sources\Rollback


    I also ran msinfo32.exe and some of the information is below:

    BELOW ARE SOME OF THE ERRORS FROM THE MSINFO32


    8.0

    10/13/19 00:27:08

    OS Name -- Microsoft Windows 10 Pro

    Version -- 10.0.17134 Build 17134

    Other OS Description -- Not Available

    OS Manufacturer -- Microsoft Corporation

    System Name -- STEVE-HP

    System Manufacturer -- Hewlett-Packard

    System Model -- HP ProBook 450 G2

    System Type -- x64-based PC

    System SKU -- J8V34UT#ABA

    Processor -- Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 2601 Mhz, 2 Core(s), 4 Logical Processor(s)

    BIOS Version/Date -- Hewlett-Packard M74 Ver. 01.52, 8/29/2019

    SMBIOS Version -- 2.7

    Embedded Controller Version -- 103.37

    BIOS Mode -- Legacy

    BaseBoard Manufacturer -- Hewlett-Packard

    BaseBoard Model -- Not Available

    BaseBoard Name -- Base Board

    Platform Role -- Mobile

    Secure Boot State -- Unsupported

    PCR7 Configuration -- Binding Not Possible

    Windows Directory -- C:\WINDOWS

    System Directory -- C:\WINDOWS\system32

    Boot Device -- \Device\HarddiskVolume1

    Locale - United States

    Hardware Abstraction Layer -- Version = "10.0.17134.1006"

    User Name -- Steve-HP\SteveD

    Time Zone -- Central Daylight Time

    Installed Physical Memory (RAM) -- 16.0 GB

    Total Physical Memory -- 15.9 GB

    Available Physical Memory -- 10.7 GB

    Total Virtual Memory -- 70.6 GB

    Available Virtual Memory -- 65.6 GB

    Page File Space -- 54.7 GB

    Page File -- C:\pagefile.sys

    Kernel DMA Protection -- Off

    Virtualization-based security -- Not enabled



    Device Encryption Support

    Reasons for failed automatic device encryption: PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, Disabled by policy





    Hyper-V - VM Monitor Mode Extensions

    Yes



    Hyper-V - Second Level Address Translation Extensions

    Yes



    Hyper-V - Virtualization Enabled in Firmware

    No



    Hyper-V - Data Execution Protection

    Yes


    APPLICATION ERRORS:


    10/12/2019 11:46 PM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0x1144
Faulting application start time: 0x01d5815727edcac1
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: 70498955-a66e-4210-a5e2-35bf1db384ea
Faulting package full name: 
Faulting package-relative application ID:





    10/12/2019 8:38 PM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0xf40
Faulting application start time: 0x01d5813cefe756c5
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: 57bc6c24-d087-437c-a1fa-87014a2d5732
Faulting package full name: 
Faulting package-relative application ID:





    10/12/2019 7:56 PM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0xca0
Faulting application start time: 0x01d58137093472af
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: d1086de6-ff36-4b6f-bc41-13dbdbc01de8
Faulting package full name: 
Faulting package-relative application ID:





    10/12/2019 6:44 PM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0x2ad4
Faulting application start time: 0x01d5812d13240c4a
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: 77526611-e9d4-49ac-acee-2dc22ab5c812
Faulting package full name: 
Faulting package-relative application ID:





    10/12/2019 2:09 AM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0xee8
Faulting application start time: 0x01d580a217f8f6eb
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: 94da057e-ef68-4090-81c1-6a4b5b01e1ad
Faulting package full name: 
Faulting package-relative application ID:





    10/12/2019 1:57 AM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0xc0c
Faulting application start time: 0x01d580a0556db2f2
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: b5fe2528-e293-454f-9ca1-306326808c1f
Faulting package full name: 
Faulting package-relative application ID:





    10/11/2019 8:27 PM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0x2c28
Faulting application start time: 0x01d580725bb3ca90
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: e012ad09-25dc-41c3-a593-dabe76807d7c
Faulting package full name: 
Faulting package-relative application ID:





    10/11/2019 7:00 PM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0x36c0
Faulting application start time: 0x01d5806624145572
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: 8a30f91a-f104-4376-a071-8b2fb1dad05d
Faulting package full name: 
Faulting package-relative application ID:



    10/11/2019 1:11 AM


    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0x2060
Faulting application start time: 0x01d57fd0ca9c53cf
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: ec764945-75d7-4ce4-b898-da7673d955fb
Faulting package full name: 
Faulting package-relative application ID:



    10/10/2019 11:10 PM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0xe38
Faulting application start time: 0x01d57fbfd158182d
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: 68a2785c-17d7-44c1-b925-02c5a938574e
Faulting package full name: 
Faulting package-relative application ID:




    10/10/2019 10:06 PM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0x31d8
Faulting application start time: 0x01d57fb705aff39f
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: 628a5386-e22a-442f-af33-7d3a5df7f892
Faulting package full name: 
Faulting package-relative application ID:





    10/10/2019 9:11 PM

    Application Error

    Faulting application name: WLANExt.exe, version: 10.0.17134.1, time stamp: 0x37c688c7
Faulting module name: Rtlihvs.dll, version: 704.10.727.2017, time stamp: 0x597edaff
Exception code: 0xc0000005
Fault offset: 0x0000000000079db2
Faulting process id: 0xd68
Faulting application start time: 0x01d57faf3696acd4
Faulting application path: C:\WINDOWS\system32\WLANExt.exe
Faulting module path: C:\WINDOWS\system32\Rtlihvs.dll
Report Id: 877940bb-9d00-4299-b241-01c7bb1f6753
Faulting package full name: 
Faulting package-relative application ID:





    10/10/2019 3:06 PM

    Application Error

    Faulting application name: nordvpn-service.exe, version: 6.23.11.0, time stamp: 0x5d4cfa7b
Faulting module name: KERNELBASE.dll, version: 10.0.17134.1067, time stamp: 0xe94e2b6e
Exception code: 0xe0434352
Fault offset: 0x00114592
Faulting process id: 0xa38
Faulting application start time: 0x01d57f7c3b57f4b5
Faulting application path: C:\Program Files (x86)\NordVPN\nordvpn-service.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 26e97be4-0cad-4d99-898a-395c3daa2065
Faulting package full name: 
Faulting package-relative application ID:





    10/9/2019 5:10 PM

    Application Error

    Faulting application name: Explorer.EXE, version: 10.0.17134.1038, time stamp: 0x41d35672
Faulting module name: atom.dll, version: 1.0.20.31528, time stamp: 0x587e230f
Exception code: 0xc0000005
Fault offset: 0x000000000000682f
Faulting process id: 0xfb8
Faulting application start time: 0x01d57ec3717bc215
Faulting application path: C:\WINDOWS\Explorer.EXE
Faulting module path: C:\Program Files\PDFescape Desktop\atom.dll
Report Id: b7c3554a-1a8d-419a-a2c4-6ca7f05427f9
Faulting package full name: 
Faulting package-relative application ID:


    -----------------

    Please help.


    Steve

    :)
     
    SteveDemcak, Oct 12, 2019
    #1
  2. Bree Win User

    0xC1900101 - 0x30018 Error Upgrading to Windows 10


    Some suggestions from Microsoft for 0x30018....

    and...

    Microsoft | Resolve Windows 10 upgrade errors : Technical information for IT Pros
     
  3. Rose Ter Win User
    Error when upgrading to Windows 10: 0xC1900101 – 0x30018

    Hi Peter,

    There are multiple factors that we need to consider why you’re getting the error “0xC1900101 - 0x30018” when upgrading to Windows 10 Pro 1703. For us to isolate the issue, we will need to ask you a few questions:

    • Have you tried all the troubleshooting steps that were provided on this thread?
    • Since when have you been experiencing this issue?
    Regards.
     
    Rose Ter, Oct 12, 2019
    #3
  4. PeteVfi Win User

    Error when upgrading Windows 10 PRO 1803 to 1903: 0xC1900101 – 0x30018

    Windows 10 Anniversary Upgrade error 0xc1900101 - 0x30018 referring to SYSPREP

    OK, please, following you have an updated one step ahead question regarding my first question post on the title.

    The question now is, how possibly get some info or tracing/debug on, which possible reason is leading to this error referring to SYSPREP.

    In the net I found several posts for this, and the following link do have quite exact instructions what to look at and try, and I have also been following most of them, except maybe one-two, which I now will still follow on a next Upgrade trial in few hours.

    -> Windows 10 Upgrade First_Boot Failure with Error 0xC1900101 - 0x30018 - Tech Journey

    Here you have a summary of the background info for this case:

    • Windows 10 Anniversary Upgrade is stuck at ab. 32% done, in a minute after the second (despite named as FIRST_BOOT) restart at 30%, during the actual final update process phase, with blank grey display and power-on
    • after an emergency power-off in a quarter or so, the Upgrade trial will got reversed and following error splash window will pop-up:

    • the laptop is some 7yrs old with dual-core AMD 1.9GHz 32-bit, memory 3GB, and has been working great with Windows 10 Pro (updated from 8.1) since 9 months
    • I know there is outdatings with e.g. display driver, now run with the basic MS one, and Wi-Fi driver etc., but several of the risky devices and also software have been disabled during the Upgrade trials

    I hope someone could help me some step ahead on this.
     
    PeteVfi, Oct 12, 2019
    #4
Thema:

Error when upgrading Windows 10 PRO 1803 to 1903: 0xC1900101 – 0x30018

Loading...
  1. Error when upgrading Windows 10 PRO 1803 to 1903: 0xC1900101 – 0x30018 - Similar Threads - Error upgrading PRO

  2. Error when upgrading to Windows 10: 0xC1900101 – 0x30018

    in Windows 10 Installation and Upgrade
    Error when upgrading to Windows 10: 0xC1900101 – 0x30018: When I try to upgrade to Windows 10, the installation fails and rolls back to my previous operating system with the error: We couldn’t install Windows 10.We’ve set your PC back to the way it was right before you started installing Windows 10. 0xC1900101 - 0x30018The...
  3. Error when upgrading to Windows 10: 0xC1900101 – 0x30018

    in Windows 10 Installation and Upgrade
    Error when upgrading to Windows 10: 0xC1900101 – 0x30018: When I Want Upgrade To Windows 10 I Get Error.It rolls me back To My Previus System Windows 7 . Error:We couldn’t install Windows 10. We’ve set your PC back to the way it was right before you started installing Windows 10. 0xC1900101 - 0x30018 The installation failed in the...
  4. DESESPERATED!!! 0xC1900101 - 0x30018 error when upgrading to build 1903

    in Windows 10 Installation and Upgrade
    DESESPERATED!!! 0xC1900101 - 0x30018 error when upgrading to build 1903: I am getting 0xC1900101 - 0x30018 errors when attempting to upgrade from 1809 (10.0.17134.829) to 1903. The installation failed in the FIRST_BOOT phase with the error during SYSPREP operation. I have tried to upgrade via Windows Update, Media Creation Tool...
  5. 0xC1900101 - 0x30018 error when upgrading from 1803 to 1903 (as well as to 1809)

    in Windows 10 Installation and Upgrade
    0xC1900101 - 0x30018 error when upgrading from 1803 to 1903 (as well as to 1809): I have tried to upgrade via Windows Update, Media Creation Tool (https://www.microsoft.com/en-us/software-download/windows10) - both upgrade and via ISO ... same error. I have tried troubleshooting with: 1. All 9 steps per:...
  6. Error Upgrading Windows 10 to 1903 - Stuck at 60% with error 0xC1900101 - 0x30018

    in Windows 10 Installation and Upgrade
    Error Upgrading Windows 10 to 1903 - Stuck at 60% with error 0xC1900101 - 0x30018: The installation failed in the FIRST_BOOT phase with an error during SYSPREP_SPECIALIZE operation. Which log files can I send to you, where do I find them and where do I send them? I've tried everything I can find on the forums but cannot fix it myself and now have no more...
  7. 0xC1900101 - 0x30018 error when upgrading to build 1903

    in Windows 10 Installation and Upgrade
    0xC1900101 - 0x30018 error when upgrading to build 1903: Hello, this is now the third time trying to install the upgrade from my current version: Build 17134.rs4-release 18041-1804. I did the last try with all Antivirus disabled ...with the same result. Since the process takes forever, I who like a bit of guidance... I read...
  8. Cannot upgrade to Windows 10 1903 0xc1900101 - 0x30018

    in Windows 10 Installation and Upgrade
    Cannot upgrade to Windows 10 1903 0xc1900101 - 0x30018: Split from this thread. Im also getting the error 0xc1900101 - 0x30018 and have tried everything possible with no luck, always stuck in 48% and have to force shutdown and it rollsback, the last driver to be tried is always Microsoft Wi-Fi Direct Virtual Adapter which i...
  9. 0xC1900101 - 0x30018 error when upgrading to build 1903

    in Windows 10 Installation and Upgrade
    0xC1900101 - 0x30018 error when upgrading to build 1903: Per https://support.microsoft.com/en-us/help/10587/windows-10-get-help-with-upgrade-installation-errors, I am getting 0xC1900101 - 0x30018 errors when attempting to upgrade from 1809 (10.0.17134.829) to 1903. I have tried to upgrade via Windows Update, Media Creation Tool...
  10. Windows 10 upgrade error 0xc1900101-0x30018 is back.

    in Windows 10 Installation and Upgrade
    Windows 10 upgrade error 0xc1900101-0x30018 is back.: 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 with the windows 7. If you can't use it,...
Tags: