Windows 10: Win 10 Upgrade from 7 Fails and Rolls back- Failed in FIRST_BOOT etc

So I have tried (7) times to upgrade to Windows 10, including having Microsoft assist me remotely for (4) of them.
All Win 7 updates are in place...I've removed Norton Security...

The Win 10 upgrade makes it all the way to the big circle on monitor counting from 0% to 50% or so, then it fails and fully rolls itself back every time to Win 7 with this same exact error:

Error: 0x80070004-0x3000D
"Install failed in FIRST_BOOT phase with error during MIGRATE_DATA"

After a bunch of MSCONFIG turning stuff off, the last Microsoft tech came back and said he thinks I should install totally clean and give up all my software and reinstall. Easy for him to say, all the Adobe Creative Suite and so on would take such a long time to restore. I also have FSX and X-Plane with 100s of GBs of scenery and all... His assumption he said is that some of my 3rd party software is interfering with the data migration...he said it may be something that is integrated with the shell.

Anyway, I'd sure like to find a way to upgrade without doing a clean installation. Any thoughts? Am happy to post list of what I am running/programs etc.

Thanks for any help.

:)

 

Windows 10 upgrade failed and get an error code 0xC1900101-0x3000D

Installation failed in the FIRST_BOOT phase with an error during MIGRATE_DATA operation.

Are you upgrading from Windows 7 or Windows 8 or upgrading a build in Windows 10?

 

Getting error 0xC1900101 - 0x30018 when upgrading to Windows 10 1709

When I try to upgrade to Windows 10, the installation fails and rolls back to my previous operating system with the error:



We couldn’t install Windows 10.

We’ve set your PC back to the way it was right before you started installing Windows 10.



0xC1900101 - 0x30018

The installation failed in the FIRST_BOOT phase with an error during SYSPREP operation

Pls. Help

 

Hi and welcome to the forum! *Smile

There are a few other users with the same problem: 0x80070004-0x3000D "FIRST_BOOT phase" "MIGRATE_DATA" - Google Search I currently cannot tell, what exactly the problem might be for you, but the upgrade should leave upgrade log files in the Windows folder. Maybe they contain something helpful...

I know that installing those Adobe programs again (don't forget to deactivate them before!) would take a long time. You did not know that the upgrade would fail that way. However, if you had done a clean install directly, you most likely would have things installed again now. So maybe, looking at the time you have already invested and thinking that basically no one knows what is causing the problem, so: no one knows how much time this upgrade would still take if you tried again and again, taking this into account, installing from scratch could really be faster.

 

My FSX (Microsoft Flight Sim) folder alone is ~94GB of scenery and aircraft to reload....it would suck to clean install this machine.

 

Just a thought... Do you have over 50% hard drive space left free? My guess is that it is attempting to make a backup of all that data for rollback later and running out of space.

 

I have 248GB free of 948GB. I think if that was the case, it would have to be fairly widely known by now.

 

You would think so, but you aren't going to get an upgrade from what you have now. I would suggest a new hard drive, go through the process of getting a clean windows 10 install on it with the old hard drive disconnected. Then reconnect the old hard drive, set up dual booting, then slowly copy everything over.

When it's all done, you will have the added benefit of a backup of everything.

 

Thanks, but no thanks. I already have a backup of everything of mine in the cloud. I solved my problem that the Microsoft tech could not by reading the post at this link:

To anyone getting the 0x80070004 - 0x3000d on install - WIN10 OS Forum - The AVSIM Community

Deleting that one file made the upgrade go through without a hitch! *Cool

 

So deleting an ORBX file called "TODO" in the C:\Users\\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Orbx folder solved that issue.

 

Awesome! Glad it worked!