[0x8007042B - 0x2000D] In Place Repair Failed in Attempt To Recover Windows 11 Home

Question

I've encountered a crash without warning while I was looking through my images, my monitor first went dark and than restarted, and it crashed again. After awhile of waiting, the login screen reappeared but I wasn't able to connect to the Internet again, after resetting, restarting my router, plug and unplugging my ethernet cable, none worked. I realized that I could be a corrupted system executables and libraries and i decided to run SFC and DISM. SFC showed up with "no integrity violation found" and DISM completed successfully. I restarted it, it did not work so I turned to in place repair. I took my laptop and downloaded the latest Multi-edition ISO from the official site for Windows 11 and transferred the ISO to my desktop using USB. I made sure I've uninstalled all of the external anti-viruses and VPNs before anything, killed off unnecessary processes. In the in place repair options, I chose not to update drivers and windows since I had no internet access. Kept all my programs and files and let it do its job. After the blue phase of the repair is done and restarted my device, the percentage went up to 23% then restarted again, and then "Undoing changes made to your computer" showed up and brought me back to the login screen along with phantom typing on my keyboard, managed to partially fixed it and later after logging into my account "We couldn't install Windows 11 - We've set your PC back to the way it was right before you started installing Windows 11 - 0x8007042B - 0x2000D The installation failed in the SAFE-OS phase with an error during MIGRATE_DATA operation", I found out that there was a error icon within the device manager for the Intel ethernet driver so I reinstalled it and it had not helped. I did managed to get some logs. (setuperr.log) My only hope is to preserve my 10 Terabyte archive along with my programs. I do not have enough things to fully backup everything.
Thank you all very much for helping me!

Notes: System is in C: drive with 2 Terabytes with partial archives scattered around, A: drive includes most of the archives and files.

Device Specs:
OS: Windows 11 Home
RAM: 128GB DDR4 3600MHZ
CPU: Intel I7 12700K
GPU: Nvidia RTX 3070 Ti
Storage: 12 Terabytes.

Answer 1

Alright, we made progress. There is a new error.

2026-02-15 15:19:22, Info                  MIG            V2VArbitrate: Source migration unit <System>\Microsoft-Windows-TPM-Driver-WMI (CCSIAgent) is not supported on the destination machine and it will not be restored

To take care of the issue, this article should help-

https://www.yourwindowsguide.com/2025/12/25h2-repair-install-failed.html

I’m eager to hear back and work together to find a solution.

A Windows MVP writes content on the above website, so it is safe. However, do watch out for the ads. It should translate into your Browser language automatically.

Answer 2

I would request you to ask MSI forums for any ideas they can provide, since it is more of a hardware problem I am afraid, Bic.

Answer 3

Hi,

It is the same error :(

Please supply the following Information.

Right-click the Start button and Choose the Run option

Type in msinfo32

Press enter.

Take a screenshot of the System Summary window and post it in the next reply.

I look forward to your response and am eager to collaborate until we find a solution.

Answer 4

Hi, It appears that the BCD is corrupt.2026-02-07 22:08:34, Error SP Cannot revert execution of operation 101 (Add boot entry for D:$WINDOWS.~BT\NewOS\WINDOWS. Locale = en-US). Execution queue is now compromised.[gle=0x00000002]

1. Open Command Prompt as Administrator.
2. Run bcdedit.
3. In the same elevated Command Prompt, run the following commands one after the other (C: is the Windows 11 drive):
   • bcdedit /export C:\BCD.bak
   • bcdedit /set {bootmgr} device partition=C:
4. Close Command Prompt and restart Windows.
5. Some systems had BCD issues where the device parameter existed but contained invalid additional entries. These needed to be removed using:
   • bcdedit /delete {ID}
6. Example:
   • bcdedit /delete {b2d1a263-cc33-11e9-a476-ec8e4d5eb847}
7. {ID} refers to the invalid or extra BCD entry causing the issue.

I hope this information helps. If you have any more questions, don't hesitate to reach out.

Otherwise, please take a moment to rate the answer. Wishing you good luck!

Answer 5

Hi,

Could you also share setupact.log file? I think I have a fix for you which should work?

I’m eager to hear back and work together to find a solution.