Windows 10: Windows Update Error 0xC1900101 - 0x4000D The installation failed in the SECOND_BOOT phase...

Hi,

I've been attempting to apply the latest feature update October 2020 for months now with no success.

The machine it's on is a fairly complex Windows install. I'm a hobbiest programmer, not someone who just loads stock Windows and browses the internet. I have all kinds of little utilities installed - most of which I've probably forgotten about but solved some particular problem, god knows where all the product keys are, and I've done numerous registry fixes over the years.

I'd almost rather shoot myself than "do a fresh install", likely spend days getting the machine to work the way I want it, and then tripping over "things that don't work any more" intermittently for months on end as I run into something I only use intermittently where I once spent hours researching ways to implement a fix.

I'm running Windows 10 Pro, version 1909, OS build 18363.1256

I've been following the instructions on this page - https://answers.microsoft.com/en-us/windows/forum/all/troubleshoot-feature-update-install-failures/eaf4ff24-64d6-4c72-824c-3ba3df716fc3 largely, but have also tried a few things on other pages that are not listed here.

In addition to the bullet points listed here I've uninstalled Net Framework 3.5, I've run CHKDSK, DISM, and SFC.

The latest attempt was done by disconnecting everything, disabling all non-MSFT services and all startup programs, running CHKDSK, DISM, and SFC all successful, using MediaCreationTool20H2.exe to download the latest WindowsUpgrade9252.exe and running that.

Overnight run ended with 7 or so hours later stuck at 91%.


I've also attempted doing this by downloading a Windows ISO, mounting that, and running Setup.exe from there.

Same result, stuck at 91%.

The system it is on runs apparently flawlessly in all other respects. I can find nothing wrong. Every bit of software I use works, every device connected works, Device Manager reports no errors.

I'd be fine simply skipping this update - I doubt there's anything in there I need - but I can't just exclude it from Windows Update without pausing all updates, and that pause only works for a certain period of time, after which it automatically re-enables.

Then the system "updates and restarts", takes HOURS to get to the "stuck" point, I restart the machine, the rollback itself takes some time, after which I can finally get back to work.

Here's a link to the most recent logs, after last night's final attempt to update.

https://1drv.ms/u/s!Am6XYMMy2utii4ZrSVxUHpcaezfo-Q?e=Xl7T7v

Boy do I wish Windows could just tell me what's wrong so I could fix it!

I've looked at the logs myself but unfortunately I just can't see anything obvious to me.

Thanks,

Todd

:)

 

0xC1900101 - 0x4000D Setup failed in SECOND_BOOT phase with an error during MIGRATE_DATA operation

• 0xC1900101 - 0x4000D
• Setup failed in SECOND_BOOT phase with an error during MIGRATE_DATA operation

 

0xC1900101 - 0x4000D Setup failed in SECOND_BOOT phase with an error during MIGRATE_DATA operation

Hi Marcusvan,

The error message "0xC1900101 - 0x4000D Setup failed in SECOND_BOOT phase with an error during MIGRATE_DATA operation" may have something to do with incompatible drivers or with the software installed on the computer. With that said, we will be performing
some troubleshooting steps to isolate the cause of this issue. Before we proceed, kindly answer the following:

• What troubleshooting steps have you tried so far?
• Can you send us a screenshot of the error message you are getting? Make sure that you remove all personal information.
• Is this the first time that you encountered this concern?
• Do you have any antivirus program installed on your PC? If so, did you disable it before you update your computer?

 

Installation of Windows creator's update Error 0xC1900101 - 0x4000D: HELP!!!

Hi Pierre,

This error code 0xC1900101-0x4000D means that the installation failed at the second_boot phase with an error during MIGRATE_DATA operation. For us to troubleshoot your concern, we suggest that you check the post provided by Andre Da Costa on this

link that tackles the same error message that you receive on your device.

Let us know if you need further assistance.