Windows 11 Update Fail

I'm stuck at 22H2. I tried the inplace upgrade using the windows ISO. It gets to about 92% complete and then barfs and reverts back to my original Windows.

Would upgrading to Windows Pro 11 resolve the issue? I've tried several suggestions, Windows Assist with the ISO. Running it under Admin rights privledge.

My computer came with Windows 11 and it meets all the windows 11 requirements for TPM, memory, processor and drive space.

dgjacquin said:

Would upgrading to Windows Pro 11 resolve the issue?

Click to expand...

Most likely, no.
Try this.
Disable any 3rd party antivirus software.
Make sure you have no corrupt system files that is causing this problem. Open a command prompt as administrator and type dism /online /cleanup-image /restorehealth
When complete, restart. Then open command prompt as admin again and run sfc /scannow
Pay attention to the scan results to see if SFC found anything it could not repair

Try the upgrade using the iso again. If it still fails,
You would need to look at the failure logs to see the cause of your failure. Depending on where in the install the failure occurs, the log can be in multiple places.

If no error message occurs, the following log files are created when an upgrade fails during installation before the computer restarts for the second time.
C:\$Windows.~BT\Sources\panther\setupact.log

C:\$Windows.~BT\Sources\panther\miglog.xml

C:\Windows\setupapi.log

[Windows 10:] C:\Windows\Logs\MoSetup\BlueBox.log

C:\Windows\inf\setupapi.app.log

C:\Windows\inf\setupapi.dev.log

C:\Windows\panther\PreGatherPnPList.log

C:\Windows\panther\PostApplyPnPList.log

C:\Windows\memory.dmp


The following log files are created when an upgrade fails, and then you restore the desktop:
C:\$Windows.~BT\Sources\panther\setupact.log

C:\$Windows.~BT\Sources\panther\miglog.xml

C:\$Windows.~BT\sources\panther\setupapi\setupapi.dev.log

C:\$Windows.~BT\sources\panther\setupapi\setupapi.app.log

C:\Windows\memory.dmp


The following log files are created when an upgrade fails, and the installation rollback is initiated:
C:\$Windows.~BT\Sources\Rollback\setupact.log

C:\$Windows.~BT\Sources\Rollback\setupact.err

Mine rolled back so I found my particular error in the last 2 logs.

If logfiles do not direct you to what caused the error, I advise anyone to not waste his time as you can chase your tail for days. Either stay where you are or bite the bullet, back up your data, and do a clean install.

I had the same thing happen on one of my laptops a while back. Tried everything and eventually gave up and downloaded the 25H2 iso and did a clean install.

If none of glasskuter's suggestions help, you may be relegated to the same fate.

Found this:
2026-02-13 16:25:08, Info UI Determining whether we should run ConX or legacy setup
2026-02-13 16:25:08, Info UI Legacy setup.exe doesn't exist. Continue to run ConX setup
2026-02-13 16:25:08, Info UI Initializing Media class driver for audio support
2026-02-13 16:25:08, Info UI Initializing media class driver status: 126
2026-02-13 16:25:08, Info UI Launching ConX setup experience
2026-02-13 16:25:08, Info UI Inspecting ConX Setup Cmdline
2026-02-13 16:25:08, Info UI Launching C:\$GetCurrent\media\Sources\SetupPrep.exe /migchoice upgrade /showoobe none /quiet /Compat IgnoreWarning /eula accept /noreboot /postoobe C:\$GetCurrent\SafeOS\SetupComplete.cmd /CorrelationVector ZrKxiJup10i1Cjk+.999 /ClientId Win10UA:VNL:URL::<1.4.19041.6448>:<1>:{5F2DE210-CC67-402D-8194-E97E51F8A146}:[10.0.22621]:[2] /DynamicUpdate Enable /telemetry enable /UpdateMedia Decline /SkipSummary
2026-02-13 16:37:24, Info MIG MigHost started with command line: {763ED68E-D4FC-429F-8370-E1B4D99AEF6B} /InitDoneEvent:MigHost.{763ED68E-D4FC-429F-8370-E1B4D99AEF6B}.Event /ParentPID:12560
2026-02-13 16:37:24, Info MIG MigHost: CMigPluginSurrogate::Init: Successfully initialized surrogate.
2026-02-13 16:37:24, Info MIG MigHost: Initialized successfully with CLSID[{763ED68E-D4FC-429F-8370-E1B4D99AEF6B}] and LogDir=[]
2026-02-13 16:37:24, 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=[1].
2026-02-13 16:37:24, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID=[0x5b0c], Server=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[1], ExceptionPolicy=[1]
2026-02-13 16:37:24, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Loaded server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)
2026-02-13 16:37:24, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Successfully loaded and registered server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)
2026-02-13 16:37:24, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() succeeded.
2026-02-13 16:37:24, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer finished: Result=[0x0].
2026-02-13 16:37:24, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: Exiting ThreadID=[0x5b0c].
2026-02-13 16:37:24, Info MIG MigHost: Exiting process.
2026-02-13 16:53:54, Info MIG MigHost started with command line: {6E39F1DD-76A9-4659-8153-C6887CD1B50A} /InitDoneEvent:MigHost.{6E39F1DD-76A9-4659-8153-C6887CD1B50A}.Event /ParentPID:12560
2026-02-13 16:53:54, Info MIG MigHost: CMigPluginSurrogate::Init: Successfully initialized surrogate.
2026-02-13 16:53:54, Info MIG MigHost: Initialized successfully with CLSID[{6E39F1DD-76A9-4659-8153-C6887CD1B50A}] and LogDir=[]
2026-02-13 16:53:54, 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=[1].
2026-02-13 16:53:54, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID=[0x399c], Server=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[1], ExceptionPolicy=[1]
2026-02-13 16:53:54, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Loaded server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)
2026-02-13 16:53:54, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Successfully loaded and registered server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)
2026-02-13 16:53:54, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() succeeded.
2026-02-13 16:53:54, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer finished: Result=[0x0].
2026-02-13 16:53:54, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: Exiting ThreadID=[0x399c].
2026-02-13 16:53:54, Info MIG MigHost: Exiting process.

All greek to me...

My last error code was 0X8007007f.

My windows version is 22H2 which says it's not supported any longer.

I had co-pilot scan the logfile you posted. Here's what it said. Co-pilot answer is in regular text, my comments are in italics.

What 0x8007007f Actually Means
Error 0x8007007f = ERROR_PROC_NOT_FOUND In plain English: Setup tried to load a DLL or driver during the upgrade, and a required function was missing.

This almost always points to one of these:

1. A broken or mismatched migration plugin
Your logs show repeated loading of: RasMigPlugin.dll>
This is the Remote Access Service migration plugin.If it’s corrupted, mismatched, or replaced by OEM software, the upgrade fails.

2. Damaged or incomplete replacement manifests The logs show Setup loading from: C:\$WINDOWS.~BT\Sources\ReplacementManifests\

3. Component Store (WinSxS) corruption
The logs show Setup loading from: C:\$WINDOWS.~BT\Sources\ReplacementManifests\
If any manifest is missing or corrupted, the upgrade fails late in the process (90–97%).

4. Third‑party drivers hooking networking or VPN components
Anything that touches RAS (VPN clients, virtual adapters, old OEM networking utilities) can break the migration plugin.
(Note: If you have such components you can uninstall such components and try agrain if you wish. (VPN clients, virtual adapters, Killer/Intel networking suites, old motherboarlan utilities)

The Fix — Based on Your Log and Symptoms​

You’re on 22H2, which is now out of support, so Windows is trying to perform a FULL FEATURE UPGRADE, not a small patch. That makes the system more sensitive to corruption. Co -pilot agreed with me on my suggestion of running DISM and SFC which you have already done..

If it still fails at 90–97%
Then your logs are telling us the truth:The RAS migration plugin is corrupted beyond repair, and the component store is likely damaged.

At that point, you have two realistic options:

Option A — In‑place repair using a 22H2 ISO This rebuilds WinSxS and the manifests without wiping apps
There is always a possibility that it will also fail

Option B — Clean install of 25H2 This is the nuclear option, but it ALWAYS works. This was my original suggestion.

I'd do a clean install

1) Please add WMIC:





2) Run tuneup_plus_log.bat > post a share link






3) Run upgrade_failure_info.bat > post a share link






4) Run the V2 log collector > post a share link




5) Open administrative command prompt and type or copy and paste:

fltmc

Post a share link



6) Search for: c:\windows\logs\cbs > post a share link

glasskuter said:

I had co-pilot scan the logfile you posted. Here's what it said. Co-pilot answer is in regular text, my comments are in italics.

What 0x8007007f Actually Means
Error 0x8007007f = ERROR_PROC_NOT_FOUND In plain English: Setup tried to load a DLL or driver during the upgrade, and a required function was missing.

This almost always points to one of these:

1. A broken or mismatched migration plugin
Your logs show repeated loading of: RasMigPlugin.dll>
This is the Remote Access Service migration plugin.If it’s corrupted, mismatched, or replaced by OEM software, the upgrade fails.

2. Damaged or incomplete replacement manifests The logs show Setup loading from: C:\$WINDOWS.~BT\Sources\ReplacementManifests\

3. Component Store (WinSxS) corruption
The logs show Setup loading from: C:\$WINDOWS.~BT\Sources\ReplacementManifests\
If any manifest is missing or corrupted, the upgrade fails late in the process (90–97%).

4. Third‑party drivers hooking networking or VPN components
Anything that touches RAS (VPN clients, virtual adapters, old OEM networking utilities) can break the migration plugin.
(Note: If you have such components you can uninstall such components and try agrain if you wish. (VPN clients, virtual adapters, Killer/Intel networking suites, old motherboarlan utilities)

The Fix — Based on Your Log and Symptoms​

You’re on 22H2, which is now out of support, so Windows is trying to perform a FULL FEATURE UPGRADE, not a small patch. That makes the system more sensitive to corruption. Co -pilot agreed with me on my suggestion of running DISM and SFC which you have already done..

If it still fails at 90–97%
Then your logs are telling us the truth:The RAS migration plugin is corrupted beyond repair, and the component store is likely damaged.

At that point, you have two realistic options:

Option A — In‑place repair using a 22H2 ISO This rebuilds WinSxS and the manifests without wiping apps
There is always a possibility that it will also fail

Option B — Clean install of 25H2 This is the nuclear option, but it ALWAYS works. This was my original suggestion.

Click to expand...

Thank you for your time in reviewing this. Looks like it will be a reinstall.

I feel your pain. It's not fun. Remove all drives from the computer except the system drive before installing.
Read and follow this carefully.

dgjacquin said:

Thank you for your time in reviewing this. Looks like it will be a reinstall.

Click to expand...

There are other options.

glasskuter said:

I feel your pain. It's not fun. Remove all drives from the computer except the system drive before installing.
Read and follow this carefully.

Clean Install Windows 11

This tutorial will show you step by step on how to clean install Windows 11 at boot on your PC with or without an Internet connection and setup with a local account or Microsoft account. Windows 11 has all the power and security of Windows 10 with a redesigned and refreshed look. It also comes...

www.elevenforum.com

Click to expand...

Thank you so much for your help with this. Great Support !!!

dgjacquin said:

I'm stuck at 22H2. I tried the inplace upgrade using the windows ISO. It gets to about 92% complete and then barfs and reverts back to my original Windows.

Would upgrading to Windows Pro 11 resolve the issue? I've tried several suggestions, Windows Assist with the ISO. Running it under Admin rights privledge.

My computer came with Windows 11 and it meets all the windows 11 requirements for TPM, memory, processor and drive space.

Click to expand...

This problem was on my part solved by a new update from MS, thankful for that. This was aprrox two - three weeks ago.