Share via

Windows 11 update from 23H2 to 25H2 fails (0x8007042B - 0x2000D)

Richard Brunner 5 Reputation points
2025-12-08T09:31:37.5933333+00:00

Dear ladies and gentlemen,

we have 39 PCs running Windows 11 Pro on our network, 6 of them refuse to update from Win 11 23H2 to 25H2.

After installing version 25h2 and rebooting, windows is rolling back to 23H2 and I get the following error messge:

0x8007042B - 0x2000D

The installation failed in the SAFE_OS phase with an error during MIGRATE_DATA operation

Setupdiaglog.txt

https://drive.google.com/file/d/15BdFg6YrdVoFD9a6idRU-O9h2Mq2uSBw/view?usp=sharing

setuperr.log

https://drive.google.com/file/d/1u2EfWdProAp5U5NREWCAZyDACWKFAoL7/view?usp=sharing

I´ve already done the following steps:

  1. sfc /scannow
  2. dism /online /cleanup-image /restorehealth
  3. dism /online /cleanup-image /startcomponentcleanup
  4. chkdsk c: /scan
  5. net stop bits, net stop wuauserv, net stop appidsvc, net stop cryptsvc

deleting c:\windows\SoftwareDistribution and c:\windows\Migration Folder and c:\windows\system32\catroot2

restarting the services above

  1. win + r -> "cleanmgr" -> Clean all (mainly Delivery Optimization Files)
  2. we only use Windows defender as AV solution
  3. do a "clean reboot" (s

8a) msconfig -> deactivate all NON-Microsoft services + reboot

8b) taskmanager -> deactivate all autostart services

  1. do an "in place upgrade" using the Win11-25h2 ISO from the microsoft homepage -> mount it -> start "setup.exe" with and without "Download and Install updates"
  2. install windows using the Microsoft Installation Assistant
  3. successfully checking that the PC is applicable for running Win11 using the MS PC health tool
  4. disk space is > 700GB
  5. updating drivers (network card, motherboard, ...)

I´d be very greatful if you could assist me in this matter.

Best regards,

Richard

Windows for business | Windows Client for IT Pros | Devices and deployment | Install Windows updates, features, or roles
0 comments
Answer accepted by question author
  1. VPHAN 10,565 Reputation points Independent Advisor
    2025-12-12T07:54:05.08+00:00

    Hi Richard Brunner,

    Thank you for sharing the detailed "nuclear" cleanup procedure that finally cleared the blockage on those 6 remaining PCs. It is excellent news that you were able to resolve it and get the entire fleet upgraded to 25H2.

    To clarify why your final approach worked when the logs specifically pointed to adammigrate.dll (ADAM/AD LDS), I think even though the RSAT tools were not explicitly "installed" in the visible UI, the presence of the adammigrate.dll error in the logs confirms that orphaned components or stale registry pointers from a past configuration (or a base image) were triggering the migration engine to look for files that didn't exist. By performing step 2b (Remove ALL Optional Features except .NET), you effectively purged the hidden or corrupted remnants that dism and sfc were previously unable to unlink on their own. This "scorched earth" removal of optional components is a powerful technique for these exact "ghost" migration errors.

    If you have a moment, please consider accepting the answer. While my specific pointer to RSAT was the catalyst, your rigorous execution of the optional feature removal was the cure, and marking this thread as resolved helps document this "clean sweep" strategy for other administrators fighting persistent 0x8007042B migration errors. Thank you, have a nice day!

    VPHAN

    0 comments

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-12-08T09:31:55.43+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error code 0x8007042B - 0x2000D during the Windows 11 update typically indicates an issue during the migration of data, specifically in the SAFE_OS phase. Since you've already performed several troubleshooting steps, here are a few additional suggestions that may help resolve the issue:

    1. Check for Corrupted User Profiles: Sometimes, user profile corruption can cause update failures. Try creating a new local user account and see if the update works under that account.
    2. Review Setup Logs: Since you have the setuperr.log and setupdiaglog.txt, check these logs for any specific errors that might indicate what is causing the rollback. Look for lines that mention "error" or "failed".
    3. Disable Third-Party Software: Even though you performed a clean boot, ensure that any third-party software, especially security software, is completely disabled or uninstalled temporarily during the update process.
    4. Update BIOS/Firmware: Make sure that the BIOS or firmware of the affected PCs is up to date. Sometimes, outdated firmware can lead to compatibility issues during major updates.
    5. Check Disk for Errors: Although you ran chkdsk, it might be worth running it again with the /f option to fix any errors found on the disk. Use the command chkdsk c: /f and restart the PC.
    6. Use Windows Update Troubleshooter: Run the built-in Windows Update Troubleshooter. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update.
    7. Reset Windows Update Components: You can try resetting the Windows Update components manually. This involves stopping the Windows Update services, renaming the SoftwareDistribution and catroot2 folders, and then restarting the services.
    8. Perform a Repair Install: If all else fails, consider performing a repair install of Windows 11 using the installation media. This will keep your files and applications while reinstalling the OS.

    If these steps do not resolve the issue, you may need to consider reaching out to Microsoft Support for more detailed assistance specific to your environment.

    References:

  2. VPHAN 10,565 Reputation points Independent Advisor
    2025-12-08T10:12:03.7433333+00:00

    Hi Richard Brunner,

    The error 0x8007042B - 0x2000D specifically means "The migration driver crashed while trying to move data (apps, registry, or user profiles) to the new OS structure."

    Since you have already done the "clean boot" and standard repairs (SFC/DISM), the issue is almost certainly a corrupted registry key or a broken user profile that survives a reboot. The standard Microsoft "clean up" commands won't fix this because they don't see third-party registry keys as "errors", but the migration engine chokes on them.

    Here are some of my suggestions:

    1. The "WINEVT" Registry Fix (Most Common Cause)

    This is the #1 cause of this specific error code in corporate environments. Third-party apps (especially older VPNs, monitoring agents, or database tools) often leave "garbage" entries in the Windows Event Log registry keys. The migration tool tries to copy these, hits an invalid character, and crashes.

    Open Regedit as Administrator =>Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels

    Export this key (save it as channels_backup.reg) just in case.

    Look through the list of sub-keys. You are looking for anything that looks "weird", not a standard Microsoft path.

    Examples of bad keys: entries with bizarre characters, or orphaned entries from software you uninstalled years ago.

    Radical Test: If you can't spot a specific bad one, you can delete the entire Channels key (after backing up!). Windows will regenerate the default channels on reboot.

    Try the update again.

    2. The "New Local Admin" Bypass

    If a specific user's NTUSER.DAT (user profile registry) is corrupted, the migration will fail every time you run the setup from that user's session.

    Create a new, fresh Local Administrator account on the machine (e.g., UpdateAdmin) =>Log out of your current domain/user account =>Log in as UpdateAdmin =>Run the Windows 11 25H2 ISO Setup.exe from this new account.

    The migration engine processes the current user differently than the stored users. Being logged into a fresh, clean profile often allows the engine to successfully package the "broken" old profiles as passive data rather than active settings.

    3. Check for "Junction Points" or Symlinks

    The MIGRATE_DATA phase often fails if you have redirected user folders (e.g., you moved C:\Users\Name\Downloads to D:\Downloads using a symlink or registry hack).

    If you have moved any user libraries to a different partition, move them back to their default location (C:) before updating.

    4. How to read your own setuperr.log

    Since I couldn't access external Google Drive links, I will give you some instructions on how to find the culprit in the file you already have.

    Open C:$WINDOWS.~BT\Sources\Panther\setuperr.log (or the one you uploaded).

    Scroll to the very bottom of the file.

    Look for the last entry that mentions a File Path or a Registry Key right before the "Fatal Error" or "0x8007042B".

    Example: If the last line mentions C:\Program Files\SomeApp, uninstall that app. If it mentions a printer driver, delete that printer.

    Often, it's a specific driver like oem#.inf. If you see a driver mentioned, use pnputil /delete-driver oem#.inf /uninstall /force to kill it.

    Okay, I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer then. Should you have more questions, feel free to leave a message. Have a nice day!

    VPHAN

  3. VPHAN 10,565 Reputation points Independent Advisor
    2025-12-08T15:04:27.4733333+00:00

    Hi Richard Brunner,

    Thanks for the log file, which pinpoints the exact component that is killing your upgrade. You can stop guessing about user profiles or generic corruption. The culprit is the Active Directory Lightweight Directory Services (AD LDS) component (formerly known as ADAM).

    From the critical block in your log:

    2025-12-07 15:08:34, Error [0x08038d] MIG Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll" ... Error: 0x80070002

    => It means the migration engine is trying to migrate the "ADAM Client" (Active Directory tools), but the migration plugin (adammigrate.dll) crashed because it couldn't find a specific file (Error: 0x80070002 = File Not Found).

    The result is the system flags this as a "Critical migration unit" failure (MIG V2VArbitrate: Source migration unit is critical) and aborts the entire OS upgrade to protect the system.

    => Solution: Remove the RSAT/AD LDS Feature

    You likely have the RSAT (Remote Server Administration Tools) or the Active Directory Lightweight Directory Services feature installed on these 6 PCs, and it is in a corrupted state. You must remove it to allow the upgrade to proceed. Here are the steps:

    Step 1: Uninstall the Feature Since these are Win 11 Pro PCs, this is likely an "Optional Feature."

    Open Settings > System > Optional features.

    Search for "RSAT: Active Directory Domain Services and Lightweight Directory Services Tools".

    Uninstall it.

    If it's not there, check Control Panel > Programs and Features > Turn Windows features on or off. Look for "Active Directory Lightweight Directory Services" and uncheck it.

    Step 2: Clean the Winsock Catalog (Secondary Error) Your log also shows a Winsock error:

    WinsockMig: Namespace catalog is not equal so integration is required

    This often happens if a third-party VPN or Security client (like a legacy Cisco AnyConnect or older Antivirus filter) is installed.

    Open CMD as Administrator => Run: netsh winsock reset => Run: netsh int ip reset

    Step 3: Reboot and Retry

    Restart the computer => Attempt the Windows 11 25H2 upgrade again.

    (Optional) You can reinstall the RSAT tools after the upgrade is finished if you still need them.

    VP

    0 comments
  4. VPHAN 10,565 Reputation points Independent Advisor
    2025-12-09T20:47:22.3733333+00:00

    Hi there,

    I am checking in to see if removing the RSAT/Active Directory components allowed you to get those 6 machines past the SAFE_OS rollback. If the log analysis provided the breakthrough you needed to clear the 0x8007042B error and finalize the deployment, please consider accepting the answer. This helps verify the solution for other administrators facing similar migration failures on workstations with RSAT tools installed.

    VP

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.