Windows 10: Issues Upgrading from Windows 10 1803 to 1903

So I am having issues with upgrading to 1903. I have tried installing from the an ISO. I disabled my network adapters and turned off my third party antivirus and malware programs. I get to 60 percent, after multiple restarts, and get the error "Windows could not configure one or more systems...". "The installation failed during the FIRST_BOOT phase with an error during SYSPREP_SPECIALIZE operation."


I have read through others questions and nothing has worked. I'm guessing it is a outdated driver that is messing with the installation. I'm trying to refrain from having to do a fresh install but decided to post my setupact.log first in hopes that someone can help. Thanks for any of your assistance in advance!



2019-09-21 15:16:57, Info UI Determining whether we should run ConX or legacy setup

2019-09-21 15:16:57, Info UI Will launch ConX setup experience

2019-09-21 15:16:57, Info UI Initializing Media class driver for audio support

2019-09-21 15:16:57, Info UI Initializing media class driver status: 126

2019-09-21 15:16:57, Info UI Launching ConX setup experience

2019-09-21 15:16:57, Info UI Inspecting ConX Setup Cmdline

2019-09-21 15:16:57, Info UI Launching D:\Sources\SetupPrep.exe

2019-09-21 15:21:52, Info MIG MigHost started with command line: {B251A2F9-B2C5-4B73-B342-3747E09E8E83} /InitDoneEvent:MigHost.{B251A2F9-B2C5-4B73-B342-3747E09E8E83}.Event /ParentPID:19992

2019-09-21 15:21:52, Info MIG MigHost: CMigPluginSurrogate::Init: Successfully initialized surrogate.

2019-09-21 15:21:52, Info MIG MigHost: Initialized successfully with CLSID[{B251A2F9-B2C5-4B73-B342-3747E09E8E83}] and LogDir=[]

2019-09-21 15:21:52, 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].

2019-09-21 15:21:52, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID=[0x2f60], Server=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[0]

2019-09-21 15:21:52, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Loaded server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)

2019-09-21 15:21:52, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Successfully loaded and registered server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)

2019-09-21 15:21:52, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() succeeded.

2019-09-21 15:21:52, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer finished: Result=[0x0].

2019-09-21 15:21:52, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: Exiting ThreadID=[0x2f60].

2019-09-21 15:21:52, Info MIG MigHost: Exiting process.

2019-09-21 15:25:47, Info MIG MigHost started with command line: {3AE275EA-B501-4D64-93AE-AC3AB40CFC0E} /InitDoneEvent:MigHost.{3AE275EA-B501-4D64-93AE-AC3AB40CFC0E}.Event /ParentPID:19992

2019-09-21 15:25:47, Info MIG MigHost: CMigPluginSurrogate::Init: Successfully initialized surrogate.

2019-09-21 15:25:47, Info MIG MigHost: Initialized successfully with CLSID[{3AE275EA-B501-4D64-93AE-AC3AB40CFC0E}] and LogDir=[]

2019-09-21 15:25:47, 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].

2019-09-21 15:25:47, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID=[0x521c], Server=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[0]

2019-09-21 15:25:47, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Loaded server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)

2019-09-21 15:25:47, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Successfully loaded and registered server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)

2019-09-21 15:25:47, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() succeeded.

2019-09-21 15:25:47, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer finished: Result=[0x0].

2019-09-21 15:25:47, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: Exiting ThreadID=[0x521c].

2019-09-21 15:25:47, Info MIG MigHost: Exiting process.

AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0083&subsys_38426286&rev_1001#5&2705e4eb&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo08/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0083&subsys_38426286&rev_1001#5&2705e4eb&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo08/00010001

AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0083&subsys_38426286&rev_1001#5&2705e4eb&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo08/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0083&subsys_38426286&rev_1001#5&2705e4eb&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo08/00010001

AudMig: Device Ids match - {2}.\\?\hdaudio#func_01&ven_10de&dev_0083&subsys_38426286&rev_1001#5&2705e4eb&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo08/00010001 {2}.\\?\hdaudio#func_01&ven_10de&dev_0083&subsys_38426286&rev_1001#5&2705e4eb&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\topo08/00010001

:)

 

Local profile issue after upgrading to 1903


Hi roblinb

Not listed in the Known.

Known issues for Windows 10 May 2019 Update version 1903


As far as Wifi any chance it is Qualcom inside USB adapter, if Qualcom then yes known issue.


I might create another user (Local) and when if try again see if this issue occurs on both users.

Would also suggest you run the first 5 steps in this tutorial to see if you have any corruption with current build.

Use DISM to Repair Windows 10 Image


Ken

 

Windows 10 upgrade problem, no input accepted

I really hate having to come here and ask for help, but I really am stumped. It hurts my geek pride. I have a PC with fairly modern hardware in it. It has a p8p67 pro in it. I have tried upgrading windows 10 on it twice now. Both times I have had the same result.

After windows finishes upgrading it goes to the log in/set up screen. I can't do anything. No keyboard or mouse input is accepted.

I will list some, or hopefully all, of the troubleshooting steps I have tried:

• Move keyboard and mouse to different USB ports.
• Try different keyboard or mouse.
• Restart computer, repeatedly.
• Google for related issues.
• Update Bios, because why not.
• Create boot media and revert to windows 7.

The windows 10 system restore boot media works fine with keyboard and mouse. All USB ports work in windows 7. I don't know what is wrong. I suspect that windows 10 is lacking a driver of some sort, but since the computer accepts no input I have no way of checking for which driver let alone installing it.

Please help me figure this out. If I have to revert back to windows 7 again, I am not going to get it upgraded to windows 10. Thank you in advanced.

 

Windows 10 1803 doesn't play nice with some Intel SSDs

Legit Reviews is reporting that Windows 10 1803 has issues with some Intel SSDs, specifically their 600p series: "When attempting to upgrade to Window 10 April 2018 Update select devices with certain Intel SSDs may enter a UEFI screen reboot or crash repeatedly." Microsoft and/or Intel are working on a fix.