Share via

Windows 11 in-place upgrade encountered error 0x8007042b - 0x2000d.

Mika 20 Reputation points
2025-08-16T02:30:34.27+00:00

I am an IT professional. I have thoroughly studied the content on this website "https://learn.microsoft.com/zh-cn/windows/deployment/upgrade/resolve-windows-upgrade-errors", but I still cannot solve this problem. The error occurred when I was performing an in-place upgrade using the official Windows 11 ISO image file provided by Microsoft. The failure manifested in the SafeOS stage of the upgrade process.

Will submit the following diagnostic files for analysis:

  1. Windows Setup log files (setuperr.log) setuperr.log
  2. SetupDiag output (SetupDiagResults.xml) setupdiagresults.xml

I have performed the following system operations:

  1. I have uninstalled all third-party antivirus and system optimization software from the device.
  2. I have executed the following system repair commands: Dism & sfc ("Dism /Online /Cleanup-Image /ScanHealth" "Dism /Online /Cleanup-Image /CheckHealth" "DISM /Online /Cleanup-image /RestoreHealth" "sfc /SCANNOW")
  3. I have disconnected all non-essential USB peripheral devices from the system.
  4. I have renamed the following Windows update components folders: SoftwareDistribution & Catroot2

I will present my analysis results below:

I can see intuitively in "SetupDiagResults. xml". The error is related to data migration

In "setuperr.log", I suspect that this problem may be related to "adamigrate. dll". So I replaced the "adamigrate. dll" in Windows PE with the "adamigrate. dll" of the local computer, but the problem still cannot be solved.

I have tried all the methods that can be searched on the network, including microsoft and third-party websites. So I hope senior technicians can analyze my log and help me solve this problem.

The size of the "setupact. log" file is too large to upload. If you need the file content, please let me know in a timely manner, and I will extract the required content and upload it

Windows for business | Windows Client for IT Pros | Devices and deployment | Install Windows updates, features, or roles
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Harry Phan 1,225 Reputation points Independent Advisor
    2025-08-18T07:56:11.4066667+00:00

    Dear Mika,

    Based on your description, the upgrade failure occurred during the SafeOS phase, and your analysis points to a potential issue with data migration, possibly involving adamigrate.dll. You've already taken commendable steps, including:

    • Removing third-party antivirus and optimization software
    • Running DISM and SFC repair commands
    • Disconnecting non-essential peripherals
    • Renaming update-related folders
    • Reviewing SetupDiagResults.xml and setuperr.log

    The SafeOS phase errors—especially those involving adamigrate.dll—are often linked to:

    Corrupted or incompatible drivers, particularly storage or migration-related components

    Residual system files or registry entries from third-party utilities

    Safeguard holds that block upgrades due to known compatibility issues2

    Hardware inconsistencies, such as faulty RAM or storage sectors

    Replacing adamigrate.dll manually may not resolve the issue if the root cause lies in system-level migration logic or driver conflicts.

    1. Run SetupDiag with Latest Definitions Ensure you're using the latest version of SetupDiag to capture updated diagnostics.
    2. Check for Safeguard Holds Use PowerShell to verify if a safeguard hold is active: Get-WindowsUpdateLog You may also consider temporarily disabling safeguard holds via Group Policy or registry if applicable.
    3. Perform Clean Boot Upgrade Boot into a clean environment using msconfig to disable all non-Microsoft services. Retry the upgrade using the official ISO.
    4. Review Storage Drivers Ensure that your storage controller drivers (e.g., Intel RST, NVMe) are up to date and compatible with Windows 11.
    5. Submit Full Setup Logs Please upload the relevant portions of setupact.log as mentioned. This file often contains critical context for SafeOS failures.

    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated. Best regards,

    Harry Phan

    You found this answer helpful.
  2. Mika 20 Reputation points
    2025-08-19T03:55:01.1466667+00:00
    0 comments
  3. Mika 20 Reputation points
    2025-08-29T11:00:52.0833333+00:00

    My issue has been resolved. The reason is that this version of Windows has a problem and cannot be installed with the same version number. Therefore, I updated to the dev version and successfully installed Windows.

    0 comments

Your answer

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