Windows 7 upgrade to 10 error during MIGRATE_DATA: 0x8007001F-0x3000D

I have a complex development setup on a Windows 7 Build 7601 Service Pack 1 desktop machine. Since replicating it after a clean install would take me more than a week, I am trying a version upgrade to keep all my apps and user data. I have already succeeded in migrating a Dell laptop with a similar configuration. However, when attempting the Win 10 upgrade on the desktop computer I am getting this error:

Error: 0x800701F-0x300D
Install failed in the FIRST_BOOT phase with an error during MIGRATE_DATA operation.

The SetupDiag tool is unable to find the cause of the error:

Code:

SetupDiag was unable to match to any known failure signatures.
System Information:
	Machine Name = NEBO
	Manufacturer = ASUSTeK COMPUTER INC.
	Model = Z9PE-D8 WS
	HostOSArchitecture = x64
	FirmwareType = PCAT
	BiosReleaseDate = 
	BiosVendor = BIOS Date: 01/07/15 21:37:45 Ver: 04.06.05
	BiosVersion = 5701
	HostOSVersion = 
	HostOSBuildString = 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707
	TargetOSBuildString = 10.0.19041.621 (vb_release_svc_prod1.201014-1758)
	HostOSLanguageId = 
	HostOSEdition = Enterprise
	RegisteredAV = Microsoft Security Essentials
	FilterDrivers = FileInfo
	UpgradeStartTime = 4/5/2021 3:00:34 PM
	UpgradeEndTime = 4/5/2021 4:52:33 PM
	UpgradeElapsedTime = 01:51:59
	CV = 
	ReportId = 2a43d53f-8188-4bd2-bd42-38455285876c

I have checked and there is enough space in the C:\ system drive



I tried installing several times following the advice posted for similar problems on other threads: disconnecting the Ethernet cable, deleting unused profiles, disabling unrecognized devices in device manager, but the error persists. Can someone give me a hint on how to solve the issue? I am totally lost here.

Here is the link to the setupact.log and setuperr.log files under C:\$WINDOWS.~BT\Sources\Panther. I have compressed them with 7zip because they are rather large:

Transfer - Dropbox

- - - Updated - - -

These are the last entries in setuperr.log:

Code:

2021-04-05 16:41:07, Error                 MIG    CoCreateInstance(CoClassIdentityStore) failed. hr = 0x800401F0[gle=0x00000534]
2021-04-05 16:41:07, Error      [0x080a7b] MIG    Failed to build the connected providers mappings[gle=0x00000534]
2021-04-05 16:41:14, Error                 MIG    CoCreateInstance(CoClassIdentityStore) failed. hr = 0x800401F0[gle=0x00000534]
2021-04-05 16:41:14, Error      [0x080a7b] MIG    Failed to build the connected providers mappings[gle=0x00000534]
2021-04-05 16:41:17, Error                 MIG    Error creating E:\Users\Default User: class Mig::TargetExistsException: (no exception message provided) void __cdecl Mig::CFileDataStore::Create(class Mig::CDataUnit *)
2021-04-05 16:41:17, Error                 MIG    Error creating F:\Documents and Settings: class Mig::TargetExistsException: (no exception message provided) void __cdecl Mig::CFileDataStore::Create(class Mig::CDataUnit *)
2021-04-05 16:48:44, Error                 CBS    Failed to load Session:3064_1075593 [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-04-05 16:49:19, Error                 MIG    Ignoring replacement manifest with no settingsVersionRange or versionRange attribute in migration element: Microsoft-Windows-Container-Manager
2021-04-05 16:49:46, Error      [0x080831] MIG    CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2021-04-05 16:52:32, Error                        Mig::CUpgradeTransportPlatform::SetUserContext: Store platform failed to find the user with ID: USER00000009, SID: S-1-0-0
2021-04-05 16:52:32, Error                 MIG    Mig::CKnowledgeManager::BeginProcessingContext: Source platform failed to set the user context USER00000009

2021-04-05 16:52:32, Error                 SP     pSPExecuteApply: Apply operation failed. Error: 0x00000004
2021-04-05 16:52:33, Error                 SP     Apply (first boot apply, online phase): Migration phase failed. Result: 4, no specific error[gle=0x00000002]
2021-04-05 16:52:33, Error                 SP     Operation failed: First boot apply. Error: 0x8007001F[gle=0x000000b7]
2021-04-05 16:52:33, Error                 SP     Operation execution failed: 13. hr = 0x8007001F
2021-04-05 16:52:33, Error                 SP     ExecuteOperations: Failed execution phase Post First Boot. Error: 0x8007001F
2021-04-05 16:52:33, Error                 SP     Operation execution failed.
2021-04-05 16:52:33, Error                 SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute post-FirstBoot operations. Error: 0x8007001F

Could this log entry point to the cause of the installation failure? What does it mean?

2021-04-05 16:52:32, Error MigApply caught exception: Win32Exception: Can't switch to requested user context: USER00000009.: A device attached to the system is not functioning. [0x0000001F] int __cdecl Mig::CKnowledgeManager::Apply(class Mig::CPlatform *,class Mig::CPlatform *,class Mig::CPlatform *,class Mig::CUserMappingList *,class UnBCL::Hashtable<class UnBCL::String *,class UnBCL::String *> *,class Mig::CAgentManager *,class Mig::CMigrationLogger *,int *,struct IMigExecuteProgress *)

I cannot look at the log files at the moment.

Could it be that you moved your User Profile folder to another hard drive or partition?

Probably due to changes in the registry?

If so, undo it.

Windows Upgrade does not support the routine.



Friendly greetings

Sorry for any mistakes. English is not my native language.

Thanks for your answer!

Could it be that you moved your User Profile folder to another hard drive or partition?

Probably due to changes in the registry?

Yes, I moved the profiles folder from C:\Users to to D:\Users to preserve the life of my SSD drive. However, I did the same in my laptop and I succeeded in migrating it to W10.

This is a snapshot of the ProfileList registry key in my W7 desktop PC



And this is the same registry key in the laptop that was successfully upgraded to W10



What about the "A device attached to the system is not functioning" error in the log file? Is there a way to know which device the installer was complaining about?

Windows Upgrade cannot access the user path during the migration, which is why the error: "A device attached to the system is not functioning" occurs.

2021-04-05 16:52:32, Error Mig::CUpgradeTransportPlatform::SetUserContext: Store platform failed to find the user with ID: USER00000009, SID: S-1-0-0

2021-04-05 16:52:32, Error MIG Mig::CKnowledgeManager::BeginProcessingContext: Source platform failed to set the user context USER00000009

2021-04-05 16:52:32, Error MigApply caught exception: Win32Exception: Can't switch to requested user context: USER00000009.: A device attached to the system is not functioning. [0x0000001F] int __cdecl Mig::CKnowledgeManager::Apply(class Mig::CPlatform *,class Mig::CPlatform *,class Mig::CPlatform *,class Mig::CUserMappingList *,class UnBCL::Hashtable<class UnBCL::String *,class UnBCL::String *> *,class Mig::CAgentManager *,class Mig::CMigrationLogger *,int *,struct IMigExecuteProgress *)

As already written, undo the change temporarily and after the upgrade change the path back again.


Friendly greetings

Thanks for your help.

As already written, undo the change temporarily and after the upgrade change the path back again.

How can I undo the change temporarily and ensure that all users are correctly migrated? Changing the ProfilesDirectory key back to %SystemDrive%\users would suffice? The entries in ProfileList corresponding to each user also contain a ProfileImagePath key that points to the d:\users folder. Should they be changed too?

What about the profile folders in d:\users? Should I copy them to c:\users? I observe that here are many directory shortcuts/junctions there that cannot be moved. Could I alternatively create junctions from c:\users to d:\users and keep the actual content in d:\users

Finally, why the installer did not complain when migrating my laptop? I also had the ProfilesDirectory entry redirected to d:\users there. The only difference I can see is that in my laptop I also changed the Default entry from %SystemDrive%\users\default to d:\users\default.

Thanks again for your time.

costello said:

How can I undo the change temporarily and ensure that all users are correctly migrated? Changing the ProfilesDirectory key back to %SystemDrive%\users would suffice? The entries in ProfileList corresponding to each user also contain a ProfileImagePath key that points to the d:\users folder. Should they be changed too?

What about the profile folders in d:\users? Should I copy them to c:\users? I observe that here are many directory shortcuts/junctions there that cannot be moved. Could I alternatively create junctions from c:\users to d:\users and keep the actual content in d:\users

Finally, why the installer did not complain when migrating my laptop? I also had the ProfilesDirectory entry redirected to d:\users there. The only difference I can see is that in my laptop I also changed the Default entry from %SystemDrive%\users\default to d:\users\default.

Thanks again for your time.

You would of course have to put the entries in the registry and the profiles folder back in the position where they belong.

Alternatively, you can try whether the upgrade goes through if the Default Profile folder is also moved.

But you have to know that yourself and I don't advise it.


Basically, it should be possible to move the profile folder, as @Kari described there:
Move Users Folder Location in Windows 10 | Tutorials (tenforums.com)

but I don't usually do it.

The problem I see with this is when the hard drive to which the User Profile folder has been moved, for whatever reason, in the "First Boot Phase" not available is, the upgrade process fails.

Mission accomplished. Thank you very much for your help!

I did as you suggested, but without copying the profiles to C:\Users because I didn't know how to move the junctions. I managed to complete the migration, and then I spent a day copying the application data from the old folders to the newly created ones. Of course, this is much better than wasting more than a week reinstalling everything.

All the best!

I'm glad to hear that it has now worked.

And thank you for your feedback.

You´re welcome.

Stay safe and take care!