Windows 10: 1703 to 1709 fails in SECOND_BOOT phase, error during MIGRATE_DATA

Hi all, please bear with me.

I have the following drives: (see attachment)
My C drive, a 120GB SSD
My D drive (Music), E drive (More Programs), F drive (Steam Library) all on a 4TB drive
My G drive (Video), my K drive (email) on a 2TB drive
My H drive (Games) a 240GB SSD I put certain games on
My I Drive (Disks), a 2TB drive that I use as a backup for things like Pictures and some of my music software disks

18th August this year I did a clean install of 1703.

I have my C drive for windows
My D drive has the folders as shown in the last attached pic.

For all my own documents, Pictures, Saved Games etc, I simply right clicked in C:\Users\me on each of them and selected Location and moved it to the D drive (downloads and Video moved to my E drive)

I moved the Public directory to the D drive by doing:

robocopy /MIR %SYSTEMDRIVE%\Users\Public D:\Public
rmdir /s /q %SYSTEMDRIVE%\Users\Public
then booting into safe mode and doing
mklink /J %SYSTEMDRIVE%\Users\Public D:\Public

I uninstalled all apps that let me uninstall through the settings pages

I installed my motherboards chipset, lan, USB, SATA drivers etc.

I finally installed my MS Office 2007 edition (Word and excel) to my G (More Programs) drive

I then made an image copy of my C and G drive.

Then I installed all the non game/music software I use, Thunderbird, VLC, Photoshop etc to my G drive and made another system image of C and G

Then I installed the programming software I'm playing around with (Unity, Visual Studio) and made another system Image of C and G.

Finally I installed all my music software (that takes literally hours and some of it insists on putting the huge sample libraries in the Public/Documents directory (hence why I moved it after the fresh install) and made a final system image of C and G

And I have all of the above images on my I drive.

I then install my games but don't do a system image of it.

Then, whenever there's a major update of my music software , I spend a few mins loading the C and G image, run all windows updates and other software updates, update the music software, then make another disk image of C and G and once verified, I delete the old one. I probably do this between 1 and 3 times a year. This means all my documents, music saves etc are on a different drive that doesn't get overwritten (but obviously is backed up) , then if I have a problem, it takes 5 mins to load the disk images and I'm ready to go. OK I have to re-install Steam, but the games are all on a separate drive so don't have to be downloaded.

So that's the history of this system, sorry for the length.

As a major windows update is out, I thought I would go back a bit, hence reloaded my disk image at the point before all my music software was installed, as it's effectively a fresh 1703 install with my non music software installed. I thought with this being a major update that I would re-install my music software after.

First I tried using windows update for 1709

This seemed to be going fine, but during the reboots as it installed, it sudden;y re-installed previous version

I reloaded the disk image

I then tried the Windows 10 update assistant

Exactly the same problem happened.

I reloaded the disk image

I downloaded the ISO do a USB pen and tried installing from that

Same problem but at least I had an error message now.

0x8007042B_0x4000D
Installation failed in SECOND_BOOT phase with an error during MIGRATE_DATA operation

I reloaded the disk image, removed all USB devices and software licensing dongles (music software not installed yet anyway) except for mouse and keyboard and tried again

Same problem, same error message.

I reloaded the disk image, powered down the PC and unplugged all disks except Disk 0 (D, E and F drive) and Disk 2 (windows disk) and tried again.

Same problem, same error message.

I installed the system image one earlier than the one I had been using (containing all my non music software but not Unity and Visual Studio), I left the other drives unplugged and tried again.

Same problem, same error.

Finally I went back to my original system, image I first made after moving the folders etc and tried again.

Same problem, same error.

To check there wasn't some weird problem with my download, I tried a fresh install of 1709 and this worked 100% fine, but I don't really want to go this route as there's a huge amount of work involved in setting up things lime my Unity software etc. I have now reloaded the image before my music software and given one last try, and of course same error.

Anyone got any ideas or am I screwed and need a fresh install?

Sorry for the length but wanted to try to explain it all properly.

PC Specs:
Corsair Neutron GTX SSD 240GB
Corsair Force GT SSD 120GB
Seegate Sata3 2TB
Toshiba Sata3 2TB
Toshiiba HDWE140 4TB

XFX RADEON RX480 Black Edition OC

Utech MMO Gaming Mouse
Logitech G510 Keyboard

Dell U2713HM monitor running at 2560 x 1440 (main)
HannsG HW191D monitor running at 1440 x 900

Intel Core i7 3820 a2011
Asus P9X79 Socket 2011 ATX Motherboard
32GB Corsair Vengance DDR3 RAM

Focusright Saffire Pro 24 firewire external Audio interface/sound card

Corsair 750 Watt HX750i Fully Modular ATX PSU/Power Supply

Archon SB-E X2 CPU Cooler
Antec 1200 Case

:)

 

Recuring Error 80072002C-4000D when upgrading to Win10 on a Surface Pro 3

The install failed in the SECOND_BOOT phase with error during MIGRATE_DATA operation.

What's next?

 

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

 

Sorry I lied, I stupidly presumed that it would fail with the same error but have just discovered it has in fact worked.

I gave the update assistant another go (with all drives re-attached) and while it was downloading the update I typed the above post, I stupidly presumed as I had re-installed my disk image that failed every time before, it would fail this time too, but it worked fine.

So at a guess one of two things happened.

Either me reformatting my system SSD and doing a complete install of 1709 before re-installing mu disk image and re-trying the upgrade did something that fixed it

or

MS changed something with their download version. version now says 1709, build 16299.64