Share via

Windows 11 Education 23H2 to 25H2 upgrade fails - TPM-Driver-WMI migration error 0x8007042B

panagiotis Drakatos 0 Reputation points
2025-12-06T18:59:14.5166667+00:00

SUMMARY

In-place upgrade from Windows 11 Education 23H2 (Build 22631.6276) to 25H2 (Build 26200.6584) consistently fails during SAFE_OS / MIGRATE_DATA phase with error 0x8007042B – 0x2000D.

Panther logs show critical failure in Microsoft-Windows-TPM-Driver-WMI (CCSIAgent) migration unit with message: "Source migration unit is not supported on the destination machine and it will not be restored"

Looking for confirmation if this is a known 25H2 issue or if there's a supported workaround.

ENVIRONMENT

OS: Windows 11 Education 23H2, Build 22631.6276

Target: Windows 11 25H2, Build 26200.6584

Hardware: Gigabyte Z690 AORUS PRO, WD_BLACK SN770 NVMe, Intel PTT (TPM 2.0), Secure Boot enabled

BitLocker: Off (fully decrypted)

Upgrade methods attempted:

  • Windows Update feature enablement
  • Windows 11 Installation Assistant
  • Official 25H2 ISO mounted locally via setup.exe

ERROR DETAILS

Setup reaches SAFE_OS phase, then fails during MIGRATE_DATA and rolls back.

From setuperr.log and setupact.log:

V2VArbitrate: Source migration unit System Microsoft-Windows-TPM-Driver-WMI (CCSIAgent) is not supported on the destination machine and it will not be restored

V2VArbitrate: Source migration unit is critical, arbitration will fail

V2V Arbitration failed. Last error: 0x00000032

pSPExecuteApply: Apply operation failed. Error: 0x0000002C

ExecuteOperations: Failed execution phase Safe OS. Error: 0x8007042B

Secondary errors (sometimes present):

DirectoryServices-ADAM-Client adammigrate.dll plugin fails with 0x80070002 during IPostApply ApplySuccess, but these are often logged as "ignore" - the actual rollback trigger is always the TPM-Driver-WMI critical migration failure.

TROUBLESHOOTING COMPLETED

System Health:

  • sfc /scannow - clean
  • DISM RestoreHealth - clean
  • chkdsk - no errors
  • WD Dashboard - drive healthy

TPM and Drivers:

  • TPM 2.0 device present (ACPI MSFT0101)
  • Using Microsoft inbox TPM driver only
  • Removed all OEM TPM drivers via pnputil
  • Removed legacy problematic drivers (Intel CougarPoint USB)

Security Software:

  • McAfee WebAdvisor uninstalled
  • Kaspersky completely removed (standard uninstall + kavremover in Safe Mode)
  • Only Windows Defender active

Services:

  • DiagTrack service set to Manual and Running

Cleanup:

  • Deleted all upgrade folders (WINDOWS.~BT, GetCurrent, WINDOWS.~WS, SoftwareDistribution Download)
  • DISM StartComponentCleanup ResetBase completed
  • Re-ran RestoreHealth and sfc after cleanup

Media Verification:

  • Both 23H2 and 25H2 official ISOs SHA-256 verified
  • Mounted locally, no third-party tools
  • Tried with Dynamic Update enabled and disabled

Compatibility Testing:

  • setup.exe /Compat ScanOnly /DynamicUpdate Disable completes WITHOUT errors
  • Full upgrade with same parameters FAILS in SAFE_OS with TPM-Driver-WMI error

ADAM Feature:

  • DirectoryServices-ADAM-Client currently disabled in DISM
  • Tried enable-disable cycle with reboots
  • ADAM errors sometimes disappear but TPM-Driver-WMI error persists

Component Investigation:

  • DISM Get-Packages shows NO Microsoft-Windows-TPM-Driver-WMI package
  • No TPM-Driver-WMI cab found in 23H2 ISO
  • Component exists in WinSxS but not as installable package
  • Cannot repair via DISM Add-Package (no package available)

CURRENT STATUS

Compatibility scan: PASSES

Full upgrade: FAILS at same point every time with TPM-Driver-WMI critical migration error

The system appears healthy by all diagnostic measures, but the upgrade process cannot migrate this specific component.

QUESTIONS

  1. Is Microsoft-Windows-TPM-Driver-WMI (CCSIAgent) migration failure a known issue in Windows 11 25H2 upgrades, particularly for Education edition?
  2. Is there a supported method to repair or reset the TPM-Driver-WMI migration unit on the source system when no standalone package exists?
  3. What is the recommended resolution path:
    • In-place repair install of 23H2 first, then retry 25H2 upgrade?
    • Direct clean install of 25H2?
    • Wait for updated 25H2 media or cumulative update?
  4. Are there known differences between Consumer and Education 25H2 media regarding TPM-Driver-WMI migration manifests?

Any official guidance would be appreciated before proceeding with a clean install.

Thank you.

Windows for home | Windows 11 | Windows update
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lucus-V 7,915 Reputation points Microsoft External Staff Moderator
    2025-12-09T06:29:06.9133333+00:00

    Hi panagiotis Drakatos,
    Welcome to Microsoft Q&A forum. I'm happy to help.

    Please take following steps:

    1. Update BIOS and drivers
    2. Clear TPM
      • Enter your BIOS to clear TPM
      • Run tpm.msc > Click Clear TPM
    3. Reboot your computer and try updating again

    If above steps cannot help, you should consider performing a clean install.

    Disclaimer: At this point, we have exhausted all troubleshooting and I recommend that we try to perform a clean install to get your computer back into a working condition. Please ensure that you backup any important data, including Documents, Pictures, Videos, and more. Windows 11 Clean Installation Process

    If you have any further questions, please feel free to let me know.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    1 person found this answer helpful.
  2. Sumit 43,801 Reputation points Volunteer Moderator
    2025-12-29T12:42:10.6433333+00:00

    https://www.yourwindowsguide.com/2025/12/25h2-repair-install-failed.html#gsc.tab=0- Open the ISO file and navigate to the Path – sources\Replacementmanifests folder. In that, delete the file \sources\replacementmanifests\tpmdriverwmi-replacement.man from the Windows installation media.

    • On the affected system, we would instruct Windows not to try replacing the manifest from 25H2 ISO file. Concurrently, the file handling the manifest is \Windows\WinSxS\migration.xml. Take Ownership of the file as Step 1 (Steps are here if you need).
    • Open the file using Notepad. The file would have a lot of <file></file> tags.
    • Search for microsoft-windows-tpm-driver-wmi. There would be 2 entries. Delete both of them, as per the GIF.
    • Clear the upgrade cache by deleting the $WINDOWS.~BT folder in Windows C drive.
    • Disconnect the system from the internet to keep the upgrade environment offline.
    • Restart the upgrade process and proceed with the repair install again.

    Was this answer helpful?

    0 comments

  3. AI answer

    2025-12-06T18:59:26.9266667+00:00
    1. The migration failure related to the Microsoft-Windows-TPM-Driver-WMI (CCSIAgent) during the upgrade from Windows 11 Education 23H2 to 25H2 is a known issue. It indicates that the source migration unit is not supported on the destination machine, which can lead to the upgrade failing during the SAFE_OS phase.
    2. Currently, there is no standalone package available to repair or reset the TPM-Driver-WMI migration unit. This issue typically requires addressing the underlying compatibility or driver issues that are causing the migration failure.
    3. The recommended resolution paths include:
      • Performing an in-place repair install of 23H2 first, which may help reset the system components before attempting the 25H2 upgrade again.
      • If the in-place repair does not resolve the issue, a direct clean install of 25H2 may be necessary.
      • Alternatively, waiting for updated 25H2 media or a cumulative update from Microsoft could also be a viable option.
    4. There may be differences between Consumer and Education 25H2 media regarding the TPM-Driver-WMI migration manifests, but specific details on these differences are not provided in the context. It is advisable to check for any updates or documentation from Microsoft regarding these differences.

    Before proceeding with a clean install, it is recommended to explore the in-place repair option and monitor for any updates from Microsoft that may address this issue.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.