Windows 10: Windows update to 1903 from 1803 fails at 60%

Discus and support Windows update to 1903 from 1803 fails at 60% in Windows 10 Installation and Upgrade to solve the problem; I've try various option to update my window 10 1803 build to latest update. I've unplugged all the USB device ran delete softwaredistribution file... Discussion in 'Windows 10 Installation and Upgrade' started by kenji815, Feb 13, 2020.

  1. KENJI815
    kenji815 Win User

    Windows update to 1903 from 1803 fails at 60%


    I've try various option to update my window 10 1803 build to latest update.


    I've unplugged all the USB device

    ran delete softwaredistribution file

    updated driver



    setupact.log


    2020-02-12 23:46:18, Info UI Determining whether we should run ConX or legacy setup

    2020-02-12 23:46:18, Info UI Will launch ConX setup experience

    2020-02-12 23:46:18, Info UI Initializing Media class driver for audio support

    2020-02-12 23:46:18, Info UI Initializing media class driver status: 126

    2020-02-12 23:46:18, Info UI Launching ConX setup experience

    2020-02-12 23:46:18, Info UI Inspecting ConX Setup Cmdline

    2020-02-12 23:46:18, Info UI Launching C:\ESD\Windows\Sources\SetupPrep.exe /DynamicUpdate Enable /Telemetry Enable /CorrelationVector zosLfBI8+U+ydtXQ.3

    2020-02-12 23:56:10, Info MIG MigHost started with command line: {A48378B4-E8B8-46A4-AA63-2C29063F0436} /InitDoneEvent:MigHost.{A48378B4-E8B8-46A4-AA63-2C29063F0436}.Event /ParentPID:14364

    2020-02-12 23:56:10, Info MIG MigHost: CMigPluginSurrogate::Init: Successfully initialized surrogate.

    2020-02-12 23:56:10, Info MIG MigHost: Initialized successfully with CLSID[{A48378B4-E8B8-46A4-AA63-2C29063F0436}] and LogDir=[]

    2020-02-12 23:56:10, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer in progress: BinaryPath=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[0].

    2020-02-12 23:56:10, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID=[0x3740], Server=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[0]

    2020-02-12 23:56:10, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Loaded serverC:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll

    2020-02-12 23:56:10, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Successfully loaded and registered serverC:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll

    2020-02-12 23:56:10, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext succeeded.

    2020-02-12 23:56:10, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer finished: Result=[0x0].

    2020-02-12 23:56:10, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: Exiting ThreadID=[0x3740].

    2020-02-12 23:56:10, Info MIG MigHost: Exiting process.

    2020-02-12 23:59:39, Info MIG MigHost started with command line: {0C4028EF-5735-492F-B6A3-0BDCEC423F1B} /InitDoneEvent:MigHost.{0C4028EF-5735-492F-B6A3-0BDCEC423F1B}.Event /ParentPID:14364

    2020-02-12 23:59:39, Info MIG MigHost: CMigPluginSurrogate::Init: Successfully initialized surrogate.

    2020-02-12 23:59:39, Info MIG MigHost: Initialized successfully with CLSID[{0C4028EF-5735-492F-B6A3-0BDCEC423F1B}] and LogDir=[]

    2020-02-12 23:59:39, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer in progress: BinaryPath=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[0].

    2020-02-12 23:59:39, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID=[0x10f8], Server=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[0]

    2020-02-12 23:59:39, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Loaded serverC:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll

    2020-02-12 23:59:39, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Successfully loaded and registered serverC:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll

    2020-02-12 23:59:39, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext succeeded.

    2020-02-12 23:59:39, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer finished: Result=[0x0].

    2020-02-12 23:59:39, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: Exiting ThreadID=[0x10f8].

    2020-02-12 23:59:39, Info MIG MigHost: Exiting process.

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo15/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo15/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo17/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo17/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo15/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo15/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo17/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo17/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo15/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo15/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo14/00010001

    AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo17/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0071&subsys_38423978&rev_1001#5&341c1cc2&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo17/00010001

    :)
     
    kenji815, Feb 13, 2020
    #1
  2. STUCKAT50
    Stuckat50 Win User

    Win 10 1803 to 1903 failed at 60% everytime

    Some progress I believe.

    I was able to recover a small system partition. I believe it's "partition 5" in diskpart, and "F" in minitool.


    Windows update to 1903 from 1803 fails at 60% [​IMG]



    Windows update to 1903 from 1803 fails at 60% [​IMG]


    What should my next step be?
     
    Stuckat50, Feb 13, 2020
    #2
  3. STUCKAT50
    Stuckat50 Win User
    Win 10 1803 to 1903 failed at 60% everytime

    Windows update to 1903 from 1803 fails at 60% [​IMG]


    I also attempted another update this am and it failed again. I was hoping it was the avast uninstaller that would have fixed it but I guess not.
     
    Stuckat50, Feb 13, 2020
    #3
  4. STUCKAT50
    Stuckat50 Win User

    Windows update to 1903 from 1803 fails at 60%

    Win 10 1803 to 1903 failed at 60% everytime

    Windows update to 1903 from 1803 fails at 60% [​IMG]


    These are my partitions

    - - - Updated - - -

    I attached some panther logs
     
    Stuckat50, Feb 13, 2020
    #4
Thema:

Windows update to 1903 from 1803 fails at 60%

Loading...

  1. Windows update to 1903 from 1803 fails at 60% - Similar Threads - update 1903 1803

  2. Windows 10 version 1803 to update to 1903 or 1909 fails at 60%

    in Windows 10 Installation and Upgrade
    Windows 10 version 1803 to update to 1903 or 1909 fails at 60%: Hello, I have tried so many different suggestions clean boot, RestoreHealth, SFC scan, check disk, driver updates, etc to resolve the updates that keep failing at 60% and nothing has worked. I do have a log file from using SetupDiag that has a couple different text log...

  3. windows 1803 update to 1903 failed

    in Windows 10 Installation and Upgrade
    windows 1803 update to 1903 failed: I've updated for several times. It always stuck at first screen after rebooting. I try lots of command like: Dism /Online /Cleanup-Image /CheckHealth Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /RestoreHealth sfc /scannow No matter I use...

  4. Win 10 1803 to 1903 failed at 60% everytime

    in Windows 10 Installation and Upgrade
    Win 10 1803 to 1903 failed at 60% everytime: Hi Guys. Normally I am able to figure these things out myself but I'm at wits end. I've been unable to update for months. Every time I initiate an update, or it does it automatically, it stops at 60% with the message that one of windows components couldn't be installed. It...

  5. Windows 10 update 1903 failing at 60%

    in Windows 10 Installation and Upgrade
    Windows 10 update 1903 failing at 60%: Hi, I've been trying to update to Windows 10 1903 but for the past week every time I try it fails at 60%. I have googled and tried many ways: manually updating with Windows 10 Update Assistant, turning off antivirus, disabling IIS ... but nothing worked I include here...

  6. Windows 10 update 1903 failing at 60%

    in Windows 10 Installation and Upgrade
    Windows 10 update 1903 failing at 60%: Hi, I've been trying to update to Windows 10 1903 so I can install the Game Pass PC beta but for the past two days every time I try it fails at 60%. I've tried everything on the below page with no luck https://zillowtech.com/windows-10-failed-to-install.html Any...

  7. Failed update windows 10 from 1803 to 1903

    in Windows 10 Installation and Upgrade
    Failed update windows 10 from 1803 to 1903: Hello everyone,I got a problem when I update my windows 10 from 1803 to 1903,I had tried the update two times,first time is last month,and second time is yesterday；but the problem is the same: the update progress stuck at a reboot ,the black screen,and with the spinning...

  8. 1903 update from 1803 consistently fails

    in Windows 10 Installation and Upgrade
    1903 update from 1803 consistently fails: The update seems to complete normally up until the first restart. Upon restart, I have a black screen. I have tried the following steps to resolve it: - Control-alt-delete at the black screen (allegedly a Microsoft recommended fix). - control-shift-alt-windows-b to...

  9. Windows update to 1903 from 1803 fails at 60%

    in Windows 10 Installation and Upgrade
    Windows update to 1903 from 1803 fails at 60%: I've run the update twice, the second time using the media creation version (usb), with antivirus totally switched off. Both times it halted at 60% and told me it could not update a component. I can't see anything in the logs though I may be looking in the wrong place....

  10. Updating from 1803 to 1903 failed

    in Windows 10 Installation and Upgrade
    Updating from 1803 to 1903 failed: Hi, I'm trying to apply 1903 update (from 1803) to my system and I'm getting this error: 0xC1900101 - 0x30018 The installation failed in the FIRST_BOOT phase with an error during SYSPREP_SPECIALIZE operation At 60% of the updating progress this error appears: "Windows...