Update management
953 TopicsWindows 11 23H2 → 25H2 in-place upgrade fails in SAFE_OS / MIGRATE_DATA
I'm trying to in-place upgrade a Windows 11 23H2 system to 25H2 and consistently get a rollback in the SAFE_OS / MIGRATE_DATA phase with 0x8007042B – 0x2000D. After a lot of analysis (Panther logs, SetupDiag, DISM, etc.), the failure always points to migration problems around Microsoft-Windows-TPM-Driver-WMI (CCSIAgent) and, secondarily, Microsoft-Windows-DirectoryServices-ADAM-Client (adammigrate.dll). I'd like to confirm whether this is a known 25H2 migration issue (especially on Education) and if there is any supported workaround short of a clean install. --- ENVIRONMENT - OS: Windows 11 Education 23H2, Build 22631.6276 - Edition: Education (confirmed via winver and Settings → System → About) - Target: Windows 11 25H2 (26200.6584, "2025 Update") - Upgrade method tried: - Windows Update feature enablement - Windows 11 Installation Assistant - Official 25H2 ISO (26200.6584.250915-1905.25h2_ge_release_svc_refresh_CLIENT_CONSUMER_x64FRE_en-us.iso) mounted locally → setup.exe - Hardware: - Motherboard: Gigabyte Z690 AORUS PRO (BIOS F31) - SSD: WD_BLACK SN770 NVMe (firmware 731130WD, WD Dashboard reports "Healthy", no errors) - TPM 2.0: Intel PTT (firmware TPM) enabled - Secure Boot: Enabled - BitLocker on C: OFF (fully decrypted) --- SYMPTOM Every full in-place upgrade attempt (23H2 → 25H2) behaves as follows: 1. Setup runs, copies files, reboots to SAFE_OS phase. 2. During MIGRATE_DATA, setup fails and rolls back to 23H2. 3. Message on screen: "0x8007042B – 0x2000D The installation failed in the SAFE_OS phase with an error during MIGRATE_DATA operation" In C:\$WINDOWS.~BT\Sources\Panther\setuperr.log / setupact.log, the failure is always in SAFE_OS / MIGRATE_DATA and includes: 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 Apply (machine-independent apply, offline phase): Migration phase failed. Result: 44 ExecuteOperations: Failed execution phase Safe OS. Error: 0x8007042B On some runs, just before the TPM arbitration failure, there are also errors related to DirectoryServices-ADAM-Client: Failure while calling IPostApply->ApplySuccess for Plugin="Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll"… Error: 0x80070002 Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEXmlPlugin, C:\$WINDOWS.~BT\Sources\ReplacementManifests, Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll… However, the ADAM plugin errors are logged as "ignore" in some traces, while the actual rollback is always tied to the critical TPM-Driver-WMI migration unit. --- WHAT I HAVE ALREADY TRIED I've tried to rule out all the usual suspects and a bit more: 1. Health checks & storage - sfc /scannow → no integrity violations - DISM /Online /Cleanup-Image /ScanHealth / CheckHealth / RestoreHealth → clean - chkdsk C: /scan → no file system / bad sector issues - WD Dashboard extended test → drive healthy, no SMART warnings 2. Drivers, TPM, AV, services - TPM: - Device: "Trusted Platform Module 2.0" (ACPI\MSFT0101\1) - Driver provider: Microsoft (inbox TPM driver), no OEM TPM drivers - pnputil /enum-drivers | findstr /i tpm shows only Microsoft TPM entries; any OEM/TMP-related oem*.inf were removed. - Legacy / problematic drivers: - Removed old Intel CougarPoint USB driver (oem25.inf) via pnputil /delete-driver oem25.inf /uninstall /force. - Antivirus / security: - McAfee WebAdvisor fully uninstalled. - Kaspersky products uninstalled via standard uninstallers and then cleaned with Kaspersky's kavremover in Safe Mode. - No Kaspersky services, drivers, files, or uninstall entries remain. - Currently only Microsoft Defender is active. - Telemetry: - Connected User Experiences and Telemetry (DiagTrack) service set to Manual and Running to avoid telemetry-related cancellation (0x800704C7). 3. Upgrade artefacts / component cleanup - Deleted: - C:\$WINDOWS.~BT - C:\$GetCurrent - C:\$WINDOWS.~WS - C:\Windows\SoftwareDistribution\Download - Ran: - DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase - Then again DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow 4. ISO & media verification - 23H2 ISO: Win11_23H2_English_x64.iso (official multi-edition ISO, SHA-256 verified). - 25H2 ISO: 26200.6584.250915-1905.25h2_ge_release_svc_refresh_CLIENT_CONSUMER_x64FRE_en-us.iso (official 25H2 ISO, SHA-256 verified). - Both mounted locally; upgrade run via setup.exe from the ISO (no third-party media tools). - Tried with Dynamic Update enabled and disabled (/DynamicUpdate Disable). 5. Compatibility scan vs full upgrade behavior - Running from 25H2 ISO: setup.exe /Compat ScanOnly /DynamicUpdate Disable → completes WITHOUT logging the earlier TPM-Driver-WMI / MIGRATE_DATA critical failures. - However, when running a FULL in-place upgrade (same ISO, same environment, DynamicUpdate disabled, "Keep personal files and apps"), the upgrade still fails in SAFE_OS / MIGRATE_DATA with the same TPM-Driver-WMI critical arbitration error and rollback. So, compatibility scan looks clean, but the real SAFE_OS/MIGRATE_DATA phase still hits the TPM-Driver-WMI migration problem. 6. ADAM / DirectoryServices-ADAM-Client state - DISM shows DirectoryServices-ADAM-Client feature as Disabled. - The ADAM migration plugin (adammigrate.dll) logs 0x80070002 during IPostApply->ApplySuccess on some runs. - As suggested in other cases, I have tried: - dism /online /enable-feature /featurename:DirectoryServices-ADAM-Client /norestart → reboot - dism /online /disable-feature /featurename:DirectoryServices-ADAM-Client /norestart → reboot - The ADAM error sometimes disappears or is logged as "ignored", but the TPM-Driver-WMI critical arbitration error persists and still causes rollback. 7. Attempt to repair TPM-Driver-WMI as a package (failed) Following the idea that TPM-Driver-WMI might be a partially removed servicing package, I: - Ran: DISM /Online /Get-Packages | findstr /i "TPM-Driver-WMI" → NO ENTRIES. There is no Microsoft-Windows-TPM-Driver-WMI-Package~… installed as a standalone package. - Mounted Win11_23H2_English_x64.iso as G: and searched for *TPM-Driver-WMI*.cab: → No such cab found anywhere in the ISO. - Mounted install.wim (index 4, Education) read-only and inspected Windows\servicing\Packages, and ran offline DISM /Image:... /Get-Packages | findstr TPM: → No Microsoft-Windows-TPM-Driver-WMI package or mum/cab. Only the component payload exists in WinSxS (amd64_microsoft-windows-tpm-driver-wmi_31bf3856ad364e35_10.0.22621.1...), but there is no installable package to feed into DISM /Add-Package. So there is NO STANDALONE TPM-Driver-WMI package that I can re-add or repair via DISM; it appears baked into the base image. --- CURRENT SITUATION - TPM driver: Microsoft inbox, no OEM TPM drivers. - AV: only Defender. - Component store: DISM /RestoreHealth and sfc /scannow are clean. - Storage: healthy. - Telemetry service: running. - ADAM client: "enable → disable" cycle tried. - 25H2 compatibility scan: now passes without TPM migration errors. - Full upgrade: still fails in SAFE_OS / MIGRATE_DATA with: - Source migration unit <System>\Microsoft-Windows-TPM-Driver-WMI (CCSIAgent) is not supported on the destination machine and it will not be restored - 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 At this point, the only remaining options I can see are: - In-place repair install of 23H2 using the 23H2 ISO (setup.exe → keep apps & data), to rebuild the whole servicing/migration stack, and then retry 25H2; - Or clean install 25H2 from scratch. Before I go down that path, I'd like to know: --- QUESTIONS 1. Is this a known migration issue in Windows 11 25H2 (especially for Education) involving Microsoft-Windows-TPM-Driver-WMI (CCSIAgent)? In other words, is the "not supported on the destination machine" for this migration unit an expected symptom of a current 25H2 bug or a misconfiguration on my side? 2. Is there any supported way to reset/repair/ignore the TPM-Driver-WMI migration unit on the source side, given that: - there is no standalone Microsoft-Windows-TPM-Driver-WMI-Package~*.cab in the 23H2 ISO, and - DISM /Get-Packages does not list such a package? 3. Is an in-place repair install of 23H2 the recommended next step in this scenario, or is the official guidance to perform a clean install of 25H2 when SAFE_OS / MIGRATE_DATA fails on a critical migration unit like this? 4. Is there any known difference between consumer vs Education/volume 25H2 media that could affect whether the TPM-Driver-WMI migration manifest is present on the target image? Any official guidance or confirmation (e.g., "this is a known issue; wait for an updated 25H2 image or cumulative update" vs "your 23H2 install is irreparably corrupted, clean install recommended") would be very helpful before I commit to a wipe-and-reinstall. Thank you in advance.303Views1like4CommentsWindows Defender is blocking true performance of my AMD Ryzen 5950x unacceptable.
I was using PBO Tuner to fine tune my processor yesterday and now Windows Defender blocked it for no reason and its not letting me restore the file.If anybody can help me with this i would appreciate it.71Views1like0CommentsSave the date: Windows Office Hours - December 18, 2025
Join us for the next Windows Office Hours on December 18, from 8:00–9:00 AM PT! We’ll have a broad group of product experts, servicing specialists, and engineers ready to connect with you in real time. Topics include Windows, Microsoft Intune, Configuration Manager, Windows 365, Windows Autopilot, security, public sector, FastTrack, and more. Our experts will be available in chat to share guidance, discuss strategies, and answer your questions. For details on how Windows Office Hours works, visit the Windows IT Pro Blog. Can’t join live? Post your questions on the Windows Office Hours: December 18th event page up to 48 hours in advance.26Views0likes0Commentssince KB5065426 or KB5064081 my old 32 bit app doesn't launch
hi, on windows 11, after one of the two KBs installation (in the title), my exe 32 bits files from 2001 doesn't launch anymore. i don't know where to look for explanation. there is nothing in the event observer. the exe just quits. if i remove the KB, everything is working fine . but sometimes i just can remove them anymore. Has anyone had a similar problem? how to investigate further Thank you in advance for your insights David38Views0likes1CommentHow to remove the default folders from the left pane of File Explorer in Windows11
The left navigation pane of File Explorer displays default folders such as 3D Objects, Desktop, Documents, Downloads, Music, Pictures, and Videos. I wish to completely hide or remove these entries. Please advise on the procedure.526Views0likes2CommentsFeedback on Windows 11
I've been a Windows customer since the beginning. I was doing computing back on the TSR-80, when we still saved information on audio tape. However, with the changes in the last few versions of Windows; I feel I can on longer use a Windows product. I've been using a Windows 11 system for several months now, and I've hated every time I had to use it. With the increase in non-optional "optional" and non-removable features; I've decided that it's time to move onto a Linux based system. Sincerely, a former Microsoft customer.12KViews13likes50CommentsCan I still upgrade to windows 11 from windows 7? Dell Latitude E6430
Bought a refurbished business laptop (Dell Latitude E6430) and it comes with a Windows 7 OS. For me, it is a still decent device and want to work with it at daily basic. However, many of the modern apps does not support Windows 7 so I decided to upgrade this Dell laptop to Windows 11 if possible. I heard there are some tricks I can apply to install Windows 11 on un supported PC but don't know how to do this myself. If, pls kindly let me know how to upgrade to Windows 11 from Windows 7 for this laptop, which is powered by Intel Core i5 3rd Gen 3320M CPU, 8GB RAM and 256GB SSD. Thank you685Views0likes9Commentswindows 11 crashes all office365-apps
windows 11 crashes all office365-apps, without MS-Access , and chrome browser e.g. Are there any experience with this, update was Build Wimndows 11 24H2 (Build 26120.6772) Cumulative Update for Windows 11 Insider Preview (KB5065797) (26120.6772) vom 07.10.2025 thanks kind regards43Views0likes1CommentWindows 11 24H2 breaks the .exe and .com file associations
Hello world, Recently updated to 24H2 feature update on my Dell Latitude 7450 laptop. Update took hours to complete. However, after login in, we found all the exe and com file extensions are broken. From notepad, task manager to Command prompt are not working. Tried all possible ways to restore the file associations thorough the recovery startup page, but did not help, until completely uninstall all quality and feature updates. 24H2 is still matured till this day, i believe. Please let me know if there is a workaround on this issue or a patch is available addressing this issue. Thank you.2KViews0likes4CommentsUnable to remove or hide failed Powershell updates in WU
Failed updates such as PowerShell v7.4.6 (x64) appear in Windows Update history and Reliability Monitor even though PowerShell 7 is not serviced through Windows Update. These entries look like genuine failures and cause unnecessary stress and confusion for users. Currently, there is no way to hide or remove these entries, which makes troubleshooting harder and leaves the system looking unhealthy when it is actually fine. I strongly request that Microsoft reintroduce the ability to hide or remove updates from the Windows Update history. At minimum, users should be able to mark failed updates as “ignored” or “hidden” so they no longer appear as ongoing problems. This feature existed in earlier versions of Windows (“Show or Hide Updates” troubleshooter) and was very useful. Bringing it back would reduce confusion, improve user confidence, and save time when dealing with harmless update failures.43Views0likes1Comment