"Failed in SECOND_BOOT phase ... error during MIGRATE_DATA operation" Get this message with every attempt to update from 10074 to 10122 or 10125

Hi,

The reason you see the error message can be found in below link provided. Check out the reply by Gabriel Aul replied on March 25, 2015.

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/eror-error-0xc1900101-0x4000d-when-i-instal/531001d5-dba5-4e13-b2c2-466665293850

Please follow the steps provided by Andre Da Costa replied on January 27, 2015 from the thread link provided and check if it helps.

 http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/couldnt-update-to-windows-10-technical-preview/e43b587d-bf67-4180-8585-9c65a0518fe3

If the issue persists please provide feedback through the feedback app. 

Hope this helps. 

 

Have now, finally, updated from 10174.  Suspects of success include:

building a thumb drive to boot an .ISO of the desired build

removing 130+ downloaded apps and data files,

uninstalling more than a half-dozen unused apps

uninstalling Charter Cable's anti-virus.  Earlier failed updates only had the tool turned off with Task Manager.  Turned on Windows Defender.

Innocent bystanders seem to include the wireless Logitech mouse and keyboard and maybe the AMD driver 15.200.1023.3 (dated 5/14/2015) working two displays with the 3rd working off the i5 Intel 4000 internal GPU.  Nothing was changed about those before the successful update.

However, those possible innocents could have been guilty, but MS may have rehabilitated them with downloaded fixes when this finally successful upgrade from 10074 asked to check for changes to download early in the update process.

Lum (wondering why he's so eager to descend into unknown sewer tunnels wearing respectable new shoes.  Ans:  crisis = opportunity.  The best MS OS is now running on this box)

Hi,

The reason you see the error message can be found in below link provided. Check out the reply by Gabriel Aul replied on March 25, 2015.

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/eror-error-0xc1900101-0x4000d-when-i-instal/531001d5-dba5-4e13-b2c2-466665293850

Please follow the steps provided by Andre Da Costa replied on January 27, 2015 from the thread link provided and check if it helps.

 http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/couldnt-update-to-windows-10-technical-preview/e43b587d-bf67-4180-8585-9c65a0518fe3

If the issue persists please provide feedback through the feedback app. 

Hope this helps. 

Neither of these suggestions worked for me and now my Microsoft mouse needs to be turned off and on every five minutes to get it working. Can you provide a step-by-step resolution to this error? Enough people are having this same issue that there should be a formal guide to correct the problem. Thank you.

1.  Remove every USB device you have plugged into your machine except for keyboard and mouse.

2.  Uninstall your anti virus software (don't just disable it, remove it - you can reinstall it later)

3.  Open MSCONFIG (start - run - msconfig)  then select the SERVICES tab, check the box HIDE ALL MICROSOFT SERVICES, then disabled (uncheck) all of the services that remain.  * In my case I left the Nvidia Driver service checked.  Next disable all startup programs on the STARTUP tab.

4.  If you have any windows 10 drivers for Display, I would suggest to install them prior to upgrade.  Everything else can be done post upgrade.

5.  Reboot the computer

6.  After reboot, login and start the Windows 10 upgrade process.  If you are using the windows update method wait until Windows downloads the installer and verifies it 100%.... Then unplug your network cable (disconnect from the internet) - leave it disconnected until you have successfully installed Windows 10.

If you are installing from the ISO/USB option, disconnect from the internet (pull your network cable out) and then start the upgrade.  Do not plug it back in until the upgrade is complete.

BE PATIENT - EXTREMELY PATIENT...  
In my case after the First Phase reboot the installer sat at about 19% for about 45 minutes.  In the Second Phase reboot, it finally got past 63% and after that it flew past the Third Phase reboot with no problems.  Once it booted into Windows 10, I made sure to wait until I had actually logged into the desktop before I reconnected to the internet and began the process of installing missing drivers (there will be a few most likely).  

If these steps do not allow the upgrade to finish....  Your only other option is to perform an upgrade without keeping your files, apps and settings (clean install).

Outside of the installation pains... Windows 10 so far is ALL IT'S BEEN ADVERTISED TO BE!  Great Job Microsoft - The OS is exactly what 8 SHOULD have been.  (Now fix the damn installer - I've got 6 more PC's to do this on.)

I followed these instructions but have yet to have any success.  I am about to give up.  Are there any other suggestions?

I struggled with this too for a few days. I tried all the drivers / BIOS update, clean boot, etc. with no success. Finally, I rooted cause the problem to the use of another HDD for Public and Document folders. I have small SSD for C: and a bigger HDD for all the documents. Somehow during the phase that Windows 10 is migrating user data, it does not like those folders being outside of C:. 

My solution was to change those folders back to their original location in C: (even if they're empty folders, that's fine too). Just right click on them, select Properties and then Location tab. After all "special" folders are dealt with, Windows 10 upgrade no problem at all. 

After finishing Windows upgrade, then you can change the locations of those folders back to another drive as in before the upgrade.

I hope this helps a few people in the same situation.

Wow! after trying for so long to sort out my Windows 10 upgrade fail with this message,  it all came done to Libraries being set to have other locations included that were on another drive. removing these back to default C locations only allowed the window 10 upgrade with no problem. thank you thank you NimNik1111 for your snipet of advice here. It worked a treat!!

notify setting

I struggled with this too for a few days. I tried all the drivers / BIOS update, clean boot, etc. with no success. Finally, I rooted cause the problem to the use of another HDD for Public and Document folders. I have small SSD for C: and a bigger HDD for all the documents. Somehow during the phase that Windows 10 is migrating user data, it does not like those folders being outside of C:. 

My solution was to change those folders back to their original location in C: (even if they're empty folders, that's fine too). Just right click on them, select Properties and then Location tab. After all "special" folders are dealt with, Windows 10 upgrade no problem at all. 

After finishing Windows upgrade, then you can change the locations of those folders back to another drive as in before the upgrade.

I hope this helps a few people in the same situation.

Hello,

would this include the pagefile.sys and swapfile.sys ? I have the same configuration, a SSD (C:\) with the OS and Apps and a HDD (D:\) with documents and files and I moved the pagefile.sys and swapfile.sys on the HDD.

I don't know if I have other folders (the one that Windows 10 thinks they should be on C:\). 

Is there a way to find out this ? how ? By tha way, i do not have a Location tab under Properties for folders in Windows Explorer. Oh, I have just descovered that for SOME folder on C:\ there is a Location tab.

thank you

I did have my videos and downloads folder redirected to my 2nd hard drive in my system and suspected this was my issue.  I defaulted them back to my C:\ Drive.  Rebooted, AV was off and tried again.  Failed in the exact same place at 75% but this time it just didn't give me the error about migrating data.  So I'm still stuck in the same place with no error message to go off of now?  Anybody?  I'd really like to get this update out of the way and I'm tired of spending an hour and half each attempt just for it to fail at the end AGAIN.