Windows 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.Besoin d’aide pour une mise à niveau windows 11 sur un PC de bureau ancien
Bonjour à tous, j’utilise actuellement Windows 10 sur un PC de bureau âgé d’environ 7 ans et je me demande s’il est possible de passer à Windows 11 sans trop de complications. J’ai lu que certains matériels plus anciens peuvent poser problème, notamment au niveau du processeur ou du TPM, et je ne sais pas si une mise à niveau windows 11 est réaliste dans mon cas. Avant de me lancer, j’aimerais avoir vos retours d’expérience et vos conseils sur les méthodes possibles, les risques à connaître et les points à vérifier. Pensez-vous qu’une mise à niveau windows 11 soit recommandée pour un PC de cet âge, ou vaut-il mieux rester sur Windows 10 pour le moment ? Merci d’avance pour votre aide.
Bluetooth driver disappears after every restart/sleep on Windows 11
Dear Support Team, I am writing this complaint out of sheer frustration after enduring a critical Bluetooth driver issue on my Windows 11 laptop for an unreasonably long time. Every single time I restart my system or wake it up from sleep, the Bluetooth driver completely disappears from the system. It is not just disabled — it is gone. Bluetooth vanishes from Device Manager, settings, and system controls as if the hardware itself never existed. The only way to restore Bluetooth functionality is to reinstall the driver manually every time. This issue occurs: After every restart After waking the system from sleep Randomly during normal usage The frequency is so high that I have been forced to keep a Bluetooth driver installer shortcut permanently on my desktop — something that feels absolutely absurd for a modern operating system in 2025. Let me be very clear: This is not a user error This is not a one-off bug This is not acceptable behaviour for a premium Windows device I have tried: Reinstalling drivers multiple times Using official OEM drivers Updating Windows fully Disabling power management options Troubleshooting through Device Manager Running system diagnostics None of these provides a permanent fix. The core issue is painfully obvious: Windows 11 (or its driver/power management stack) is failing to reliably retain or initialise the Bluetooth driver across restarts and sleep cycles. This is a basic OS-level responsibility. As a long-time Windows user, I find it shocking that in a system where I spent a considerable amount, I am dealing with an issue that feels more appropriate for an unstable experimental build, not a consumer-ready operating system. To be completely honest, this experience has pushed me to the point where I am seriously considering abandoning Windows altogether and switching to macOS, despite having used Windows on my personal machines for years. The idea of paying that amount again just to escape such basic reliability problems is becoming more appealing than continuing to fight my own laptop daily. This is not just a “bug report” — this is a usability failure that affects: Work productivity Meetings Audio devices Input devices Everyday usability I expect: A clear acknowledgement of the issue A concrete explanation of why this happens A permanent fix, not temporary workarounds Or an official statement admitting the limitation I am documenting this issue publicly and will be sharing it across relevant forums and feedback channels unless a meaningful resolution is provided. Windows users should not have to reinstall core drivers every day to use basic hardware features. I look forward to a serious response. Sincerely, A very frustrated but still hopeful Windows user
Excessive ram usage in Windows 11
Hi there Since installing the Windows 11 1/2026 update, my PC has been using an excessive amount of ram. My Desktop has 32 Gigs of ram and while sitting idle, just looking at the desktop without having anything running and only some programs running in the background, the ram usage is about 25 gigs constant. Before the update the average usage while using my PC was around 15 to 20 gigs and that's while actively using it and having multiple programs running, including heavier things like CAD and stuff. Tried rolling back the update by booting into the recovery menu and uninstalling the update, but it didn't help. Any Ideas on how to fix it?
Installation Failure of KB5074109 on Windows 11 25H2 Multi-Session – Error 0x80073712
We are experiencing persistent issues installing the latest Windows update, KB5074109, on Windows 11 25H2 Multi-Session running in Azure. The installation fails on multiple machines with error code 0x80073712. We have tried the following troubleshooting steps, but still the same issue: sfc /scannow DISM.exe /Online /Cleanup-Image /RestoreHealth Windows Update Troubleshooter (Settings → System) Manual download and installation of the update Has anyone else run into this, or does anyone have ideas on how to fix it? Could the update itself be the problem?
Windows Subsystem for Linux doesn't work after the reinstallation of Windows 11 version 24H2.
I am not able to use Windows Subsystem for Linux after I reinstalled Windows 11 Home version 24H2 after resetting my Dell Inspiron 5410 laptop. The same occurred with my friend on a Windows 11 Pro laptop. Before the reset, the Windows Subsystem for Linux was working fine on both of our laptops. I tried following these steps to fix the issues. 1. I tried "Turn Windows features on or off," in which I enabled Windows Subsystem for Linux, which should make me use Ubuntu on my Windows PC after upgrading to version 2 using a kernel update. when I tried to update the WSL kernel By downloading and installing the latest WSL 2 kernel from Microsoft’s WSL Kernel Update. https://learn.microsoft.com/en-us/windows/wsl/install-manual Step 4 It says, "This update is applicable to machines with the Windows subsystem for Linux." and does not install updates WSL allows the following features: Ubuntu terminal environment in minutes with Windows Subsystem for Linux (WSL). Develop cross-platform applications, improve your data science or web development workflows, and manage IT infrastructure without leaving Windows. Key features: - Efficient command line utilities, including bash, ssh, git, apt, npm, pip, and many more - Manage Docker containers with improved performance and startup times - Leverage GPU acceleration for AI/ML workloads with NVIDIA CUDA - A consistent development-to-deployment workflow when using Ubuntu in the cloud But "Turn Windows features on or off" did not help. 2. Then, I tried installing WSL manually with the following codes: https://learn.microsoft.com/en-us/windows/wsl/install-manual Step 1 - Enable the Windows Subsystem for Linux Step 3 - Enable Virtual Machine feature PS C:\WINDOWS\system32> .exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart >> Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.2605 Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. PS C:\WINDOWS\system32> .exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart >> Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.2605 Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. Although it ran, it was not helpful even after 100 percent installation, but it did not help. 3. I tried following codes in PowerShell as Administrator: wsl.exe --install wsl --install wsl.exe --update PS C:\WINDOWS\system32> wsl.exe --install Class not registered Error code: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG PS C:\WINDOWS\system32> wsl --install Class not registered Error code: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG none of these codes helped. 4. When I tried running the command Bash in PowerShell as Administrator. C:\Windows\System32>bash Class not registered Error code: Bash/CallMsi/Install/REGDB_E_CLASSNOTREG It did not run. 5. I verified virtualization is enabled in BIOS. Restart your computer and access the BIOS/UEFI (usually by pressing F2, Del, or a similar key during boot). Look for settings like Intel Virtualization Technology (VT-x) or AMD-V and ensure they are enabled. Save changes and reboot into Windows. 6. Another error was given Error: 1168 Error code 1168 usually translates to "Element not found" in Windows. This error indicates that some required files, registry entries, or features are missing or improperly configured. In the context of WSL installation. 7. I even tried reinstalling Windows, which did not help. 8. I installed Windows 11 (multi-edition ISO for x64 devices). https://www.microsoft.com/en-us/software-download/windows11 But this also does not fix my issue. 9. Even the Windows customer support team was not able to help. I guess this is the issue with most of the system. Please help me fix it. and there may be a bug in Windows 11.Possible to bypass Windows 11 cpu check with rufus?
When I run the Windows 11 setup.exe from mounted ISO file, an error message shows: This processor isn't supported for this version of Windows. The CPU is an Intel Core 6700K. It seems this old PC doesn't meet the official CPU and TPM requirements. Could someone please confirm the exact steps to bypass Windows 11 cpu check with rufus? I want to make sure I select the correct settings to skip the compatibility checks during installation without causing any other issues. Any additional tips would be greatly appreciated.
Windows 11 Recovery Logic and BitLocker Default Issues Causing Boot and Reset Failure
I recently submitted critical feedback through the Windows Feedback Hub regarding a recovery failure scenario that blocked a system reset and was compounded by BitLocker being enabled by default without clear consent. After a normal shutdown, the system failed to boot. A reset attempt was blocked by Windows and required file deletion. At the same time, the system could not boot, making file deletion impossible. This forced a clean install in order to recover functionality. BitLocker was enabled by default, with the recovery key tied to a Microsoft account that was not actively managed. No documentation or guidance was provided to explain this circular recovery logic. I did eventually find a workaround, but a recovery process should never require undocumented steps or technical workarounds simply to regain access to one’s own machine. This represents a design failure, not user error. I submitted this issue as high severity under Install and Update, Backup and Restore, with the problem classified as Inability to use my PC. Feedback Hub link: https://aka.ms/AAzbsvg My key concerns are that boot and reset should not be blocked by opaque security defaults, BitLocker should be opt in and clearly explained during setup, recovery logic must be logically consistent and accessible, and a consumer operating system should not require undocumented workarounds to restore functionality. I also raised broader platform concerns including Windows 11 cost and value compared to macOS annual free operating system updates, ongoing install and uninstall friction caused by legacy registry behavior, and Apple’s predictable recovery process and system reliability. This is not bias. It is professional experience based on decades of use, certification, and paying customer history. I am sharing this here to increase visibility and open discussion, with the hope that engineers and other users can engage with the severity of this real-world failure mode.
