Trying to upgrade Windows 11 23H2 to 24H2 (or 25H2) always rolls back

Question

Trying to upgrade Windows 11 23H2 to 24H2 (or 25H2) always rolls back

Georg Rottensteiner 16

I've recently bought a new PC with Windows 11 Professional.

It came with 23H2 preinstalled. I've received the upgrade attempts to 24H2 several times, but it always fails and rolls back.

I see a bunch of errors in setuperr.log, but nothing I can make heads or tails of. If anybody could point me into the right direction I'd be really grateful!

These are the errors from the log:

2026-03-20 07:27:37, Error                 DU     DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
2026-03-20 07:34:12, Error                        WsmSendMessage: Failed FilterSendMessage, hr = 0x800701de
2026-03-20 07:34:12, Error                        WsmUpdateTrackingConfig: Failed to send PortMsgAddOrUpdateTrackedPath for D:\OneDrive; hr = 0x800701de
2026-03-20 07:34:12, Error                 SP     SETUPMON: Failed to update tracking configuration for the monitoring filter driver. Error: 0x800701DE
2026-03-20 07:34:12, Error                 SP     Failed to start the monitoring filter driver. Error: 0x800701DE
2026-03-20 07:34:16, Error                            WsmSendMessage: Failed FilterSendMessage, hr = 0x800701de
2026-03-20 07:34:16, Error                            WsmUpdateTrackingConfig: Failed to send PortMsgAddOrUpdateTrackedPath for D:\OneDrive; hr = 0x800701de
2026-03-20 07:34:16, Error                 SP         SETUPMON: Failed to update tracking configuration for the monitoring filter driver. Error: 0x800701DE
2026-03-20 07:34:16, Error                 SP         SETUPMON: Failed to start the monitoring filter driver. Error: 0x800701DE
2026-03-20 07:34:16, Error                 SP         pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
2026-03-20 07:34:43, Error      [0x080831] MIG        CSIAgent: Invalid xml format: FormatException: "script" attribute is mandatory. class Mig::CMXEMerge *__cdecl Mig::CMXEMigrationXml::LoadMerge(class UnBCL::XmlNode *,int,class Mig::CMXEMigrationXml *,class Mig::CMXEXmlComponent *)
2026-03-20 07:37:04, Error      [0x080813] MIG            CRegProcessingUnit::ProcessGather: Failed to get dataunit in POV enumeration for location("HKCU\Software\Classes\Applications\updater.exe")
2026-03-20 07:38:24, Error                        WsmSendMessage: Failed FilterSendMessage, hr = 0x800701de
2026-03-20 07:38:24, Error                        WsmUpdateTrackingConfig: Failed to send PortMsgAddOrUpdateTrackedPath for D:\OneDrive; hr = 0x800701de
2026-03-20 07:38:24, Error                 SP     SETUPMON: Failed to update tracking configuration for the monitoring filter driver. Error: 0x800701DE
2026-03-20 07:38:24, Error                 SP     Failed to start the monitoring filter driver. Error: 0x800701DE
2026-03-20 08:01:04, Error      [0x0808fe] MIG    Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!RemoveObsoleteCHSHKLMRegkey - fail to open regkey (software\Microsoft\CTF\TIP\{E429B25A-E5D3-4D1F-9BE3-0C608477E3A1}\LanguageProfile\0x00000804) = 2
2026-03-20 08:01:04, Error      [0x0808fe] MIG    Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!ApplySuccess() remove HKLM Registries error
2026-03-20 08:01:04, Error      [0x0808fe] MIG    Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: offline key (new) = '$OFFLINE_RW_810A4DCA$SYSTEM\Setup\Upgrade\Bridge'
2026-03-20 08:01:04, Error      [0x0808fe] MIG    Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: query bridge presence key failed 0x139f, bridge present = 0
2026-03-20 08:01:04, Error      [0x08038d] MIG            Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll", CLSID={43CCF250-2A74-48c6-9620-FC312EC475D6}, ThreadingModel=Apartment, ExceptionHandling=Default}. Error: 0x80070002
2026-03-20 08:01:04, Error                 SP             Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEXmlPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment,Default. Will return 2[gle=0x000000cb]
2026-03-20 08:01:05, Error      [0x0808fe] MIG    Plugin {8707fcd0-e62a-4451-b224-7707ffe1c286}: WinsockMig: Namespace catalog is not equal so integration is required

2026-03-20 08:01:05, Error      [0x0808fe] MIG    Plugin {8707fcd0-e62a-4451-b224-7707ffe1c286}: WinsockMig: Upgrade of NSPs is now disabled when in offline mode

2026-03-20 08:02:30, Error      [0x0808fe] MIG    Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!RemoveObsoleteCHSHKLMRegkey - fail to open regkey (software\Microsoft\CTF\TIP\{E429B25A-E5D3-4D1F-9BE3-0C608477E3A1}\LanguageProfile\0x00000804) = 2
2026-03-20 08:02:30, Error      [0x0808fe] MIG    Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!ApplySuccess() remove HKLM Registries error
2026-03-20 08:22:40, Error                        WsmSendMessage: Failed FilterSendMessage, hr = 0x800701de
2026-03-20 08:22:40, Error                        WsmUpdateTrackingConfig: Failed to send PortMsgAddOrUpdateTrackedPath for D:\OneDrive; hr = 0x800701de
2026-03-20 08:22:40, Error                 SP     SETUPMON: Failed to update tracking configuration for the monitoring filter driver. Error: 0x800701DE
2026-03-20 08:22:40, Error                 SP     Failed to start the monitoring filter driver. Error: 0x800701DE
2026-03-20 08:22:54, Error                 SP         pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
2026-03-20 08:23:58, Error                 SP         BFSVC: Failed to check UEFI DB variable. Error code = 0xcb
2026-03-20 08:23:58, Error                 SP         BFSVC: ShouldUseExFiles check failed: cb, defaulting to 2011 binaries 1
2026-03-20 08:23:59, Error                 SP         BFSVC: AddBootmgrLast and PreserveBootOrder options are ignored when custom volume is specified
2026-03-20 08:24:54, Error                 SP         BFSVC: AddBootmgrLast and PreserveBootOrder options are ignored when custom volume is specified
2026-03-20 08:25:31, Error                            [SetupPlatform.exe] System disks found
2026-03-20 08:26:20, Error                 CBS    Failed to enumerate packages for capability: %ws: E_INVALIDARG
2026-03-20 08:26:20, Error                 CBS    Failed to enumerate store capabilities for FOD inventory.: E_INVALIDARG
2026-03-20 08:26:20, Error                 CBS    Failed to generate FOD inventory hash: E_INVALIDARG
2026-03-20 08:28:00, Error      [0x08038d] MIG            Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="%windir%\system32\IasMigPlugin.dll", CLSID={6df2d9df-1294-4637-82d3-d53761ca2c11}, ThreadingModel=Apartment, ExceptionHandling=Default}. Error: 0x80010105
2026-03-20 08:28:00, Error                 SP             Error READ, 0x80010105 while gathering/applying object: apply-success, Action,CMXEXmlPlugin,C:\$WINDOWS.~BT\Work\MachineIndependent\Working\agentmgr\CCSIAgent,%windir%\system32\IasMigPlugin.dll,{6df2d9df-1294-4637-82d3-d53761ca2c11},Apartment,Default. Will return 2[gle=0x000000cb]
2026-03-20 08:29:11, Error                        WsmSendMessage: Failed FilterSendMessage, hr = 0x800701de
2026-03-20 08:29:11, Error                        WsmUpdateTrackingConfig: Failed to send PortMsgAddOrUpdateTrackedPath for D:\OneDrive; hr = 0x800701de
2026-03-20 08:29:11, Error                 SP     SETUPMON: Failed to update tracking configuration for the monitoring filter driver. Error: 0x800701DE
2026-03-20 08:29:11, Error                 SP     SETUPMON: Failure while removing protection for monitored folder. Error: 0x800701DE

0 comments

3 answers

Your answer

Answer 1

The log snippets alone do not map to a specific, documented Windows 11 upgrade error in the provided material. However, there are supported, end‑to‑end approaches that reliably fix repeated rollback issues when upgrading from Windows 11 23H2 to 24H2/25H2.

Use the following supported paths, in order of preference:

Upgrade using the latest Windows 11 ISO (in‑place upgrade)
This is the same method recommended when Windows Update–based upgrades or LCUs repeatedly fail.
1. From a working 23H2 desktop, download the latest Windows 11 ISO (multi‑edition, x64) using the official software download page.
2. Right‑click the ISO and select Mount, then run Setup.exe from the mounted drive.
3. In the first screen, clear any option like Help make the installation of Windows better, then choose Change how Setup downloads updates and select Not right now.
4. Accept the license terms.
5. On the Ready to install screen, select Change what to keep and choose Keep personal files and apps so that data, apps, and settings are preserved.
6. Start the installation and let it complete; the PC will restart several times.
This in‑place upgrade path is the same approach recommended in similar rollback scenarios for Windows 11 25H2 and for failed cumulative updates when normal servicing paths fail.
Use the built‑in “Reinstall” (repair install) option on 23H2, then update
If the in‑place upgrade still rolls back, repair the current 23H2 installation first, then try upgrading again:
1. Go to Settings → System → Recovery.
2. Use the Reinstall (repair install) option that reinstalls the current Windows 11 version without removing apps or data.
3. After reinstall completes and the system is stable, run Windows Update again to move to 24H2/25H2, or repeat step 1 with the latest ISO.
This repair‑install approach is explicitly recommended for Windows 11 25H2 install errors such as 0x800f081f and other update failures.
If upgrading specifically to 23H2/24H2 from Windows 10 (for other readers)
For devices still on Windows 10 that hit rollback issues or cryptographic errors (0x80092003 / 0x000000c1) due to the Secure Boot/UEFI CA 2023 bootloader, the supported resolutions are:
- Upgrade directly to Windows 11 24H2 or later using Windows Update or media created after February 11, 2025; or
- Use the latest Windows 11 23H2 media created after that date; or
- Allow the device to connect to Windows Update during setup so it can download and install KB5052424 Safe OS Dynamic Update, or slipstream KB5052424 into custom media.
These steps ensure the bootloader in the media is at least as new as the one on the device, preventing rollback in the SafeOS/WinRE phase.
If repeated failures persist even with ISO and repair install
When both a repair reinstall and an ISO‑based in‑place upgrade fail, the supported next step is a full reinstall of Windows 11 using current media, backing up data first. This is the same resolution used in other documented cases where CBS/servicing errors persist and even in‑place upgrades fail.

References:

Answer 2

Clary-N 15,730 Microsoft External Staff Moderator

Hi Georg Rottensteiner,

I understand how concerning this experience has been, especially on a new PC where the Windows feature upgrade keeps rolling back without a clear on‑screen explanation. Thank you for your patience and for sharing the setup logs, that information is very helpful.

From the logs, it appears the upgrade is stopping because Windows is unable to safely monitor file changes during the upgrade process. This may happen when certain folders (such as OneDrive or known folders like Desktop, Documents, or Pictures) are redirected to another drive, or when security or backup software is actively protecting those locations. When Windows can’t complete this monitoring step, it will automatically roll back to protect your data.

Based on what we’re seeing, the most reliable way to move forward in this situation is to perform an in‑place upgrade using the official Windows installation media. This method refreshes the Windows system components while keeping your personal files, installed apps, and settings intact, and it often succeeds where repeated Windows Update attempts continue to roll back.

I recommend downloading the official Windows 11 ISO from Microsoft, mounting it, and running setup.exe from within Windows. When prompted, choose the option to keep personal files and apps and allow the upgrade to complete.

*Disclaimer: Let’s try performing an in-place install or in-place upgrade which will refresh your Windows files and operating system without removing files or applications. That being said, we always recommend that if you have important data, you should back it up before making large system changes. If you want to back up your data first, please do so.

This approach does not erase your data and is commonly used to resolve upgrade rollback issues like the one you’re encountering.

Please let me know how it goes or if you have any questions before proceeding. I’m happy to help further.

If you have any further questions about this answer, please click "Comment".

Note: If you would like to receive email notifications on this topic, please follow the steps in our documentation to enable email notifications.

Georg Rottensteiner 16 Reputation points

2026-03-21T08:48:50.58+00:00

I've already tried that too. I'm trying a full reinstall from an USB stick freshly created with the Media Tool as a last resort now.
Seems that something that came pre installed is making problems. Teaches me to always do a complete fresh install after getting a new PC.
Georg Rottensteiner 16 Reputation points

2026-03-21T18:42:47.94+00:00

Doing a full install from an USB stick worked (without keeping Apps and Data, as that didn't work as well), went directly to 25H2.
Unfortunately the previously activated Windows now says it can't activate my PC with the key I've read from the registry prior. But that's a different story altogether. Looks like the shop I've bought it from used a digital key which didn't register. I'll clarify with them.

Note: I could reinstall without keeping apps and data because I always use a second partition for my real data.
All I had to do was to copy the content on the desktop to a backup folder, and nothing much else was lost.
All that got lost were the tabs in Edge (I can see them in history though).

TL;DR: ALWAYS WIPE AND REINSTALL A CLEAN WINDOWS WHEN YOU BUY IT PRE-INSTALLED.
Clary-N 15,730 Reputation points Microsoft External Staff Moderator

2026-03-24T07:28:00.0033333+00:00
Hi Georg Rottensteiner,

Thanks for the update. I’m glad to hear the clean USB reinstall resolved the issue and that the system is now running properly on 25H2.

Preinstalled software or OEM configurations can sometimes cause unexpected behavior, and a clean install is a reliable way to rule that out. It’s also great that having your data on a separate partition made the process smooth.

Regarding activation, if the device was originally using an OEM digital license, Windows should normally reactivate automatically. Since that didn’t happen, please try the following:

Make sure the edition matches: Confirm that the installed Windows edition matches what the PC originally came with (for example, Home vs Pro). An OEM Home license will not activate Pro.

Run the Activation Troubleshooter: Go to Settings > System > Activation > Troubleshoot. If prompted, sign in with your Microsoft account if the license was previously linked.

If activation still doesn’t work after this, checking with the retailer is the right next step to confirm the license and assist with reactivation. Microsoft Support can also help once the purchase details are confirmed.

Please let me know if you need any further assistance.
Clary-N 15,730 Reputation points Microsoft External Staff Moderator

2026-03-25T08:09:44.69+00:00

Hi Georg Rottensteiner,

Please let me know if there is anything I can help by leaving your comment down here.
Georg Rottensteiner 16 Reputation points

2026-03-25T08:57:35.9633333+00:00

I've contacted my retailer regarding the key. From by POV this issue can be closed.
Clary-N 15,730 Reputation points Microsoft External Staff Moderator

2026-03-26T00:11:10.9666667+00:00

Hi Georg Rottensteiner,

Thank you for the update. Please reach out if you need anything else.

Have a great day!

Answer 3

TK 0

This is caused by different locations for specific folders (like Documents, Downloads, OneDrive, Music), which most probably target to different drive (like D:/Downloads, D:/Music etc.). I'm not sure if a system repair can fix this. But the quick 'n dirty solution is to restore original locations before the upgrade and specify different locations again after the upgrade. Do not copy folder contents, just restore/respecify folder locations.

Clary-N 15,730 Reputation points Microsoft External Staff Moderator

2026-09-04T07:25:00.0333333+00:00

Thanks for sharing this information.
Georg Rottensteiner 16 Reputation points

2026-09-04T07:26:37.43+00:00

In this case I didn't change the location of the special folders, I chose to just not use them.