Share via

Win 10 upgrade error: User profile suffix mismatch, 0x800707E7 - 0x3000D

Anonymous
2020-01-23T17:47:03+00:00

I have been trying to upgrade my Win 7 Ultimate (SP1) to Windows 10 for the past two weeks, and keep having the same problem.

When the upgrade gets to 56%, the system reboots again, Restores to Windows 7 and shows the following error:

0x800707E7 - 0X3000D

The installation failed in the First Boot phase with an error during Migrate Data operation.

I have tried dozens of way to fix this, disabling and removing devices, disconnect the LAN cable so it wont download updates, going into MSCONFIG and Disable the Services and Startup items, going into Regedit and removing the OLE.

I am doing up upgrade with a boot DVD from the ISO file, but also tried directly from the HDD.

People have said to look in the Panther dir and look for errors in the setuperr.log file. This is what is at the very end:

2020-01-23 12:00:57, Error                 SP     pSPExecuteApply: Migration phase caught exception: Win32Exception: User profile suffix mismatch, upgrade cannot continue: The specified profile is intended for a device of a different type than the specified device. [0x000007E7] enum MIGSTATUS __cdecl pSPExecuteApply(enum SetupPlatform::SP_MIG_SCOPE,class UnBCL::String *,int,int,int,class UnBCL::ArrayList<class UnBCL::String *> *,class UnBCL::String *,class UnBCL::String *,class UnBCL::ArrayList<class UnBCL::DictionaryEntry<class UnBCL::String *,class UnBCL::String *> *> *,class UnBCL::String *,int,int,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::ArrayList<class CWIMBootData *> *,class UnBCL::String *,int *,class CSPTelemetryData *,struct ISPMigProgress *,long *)

2020-01-23 12:00:57, Error                 SP     Apply (first boot apply, online phase): Migration phase failed. Result: 4, specific error: 0x800707E7[gle=0x00000002]

2020-01-23 12:00:57, Error                 SP     Operation failed: First boot apply. Error: 0x800707E7[gle=0x000000b7]

2020-01-23 12:00:57, Error                 SP     Operation execution failed: 13. hr = 0x800707E7

2020-01-23 12:00:57, Error                 SP     ExecuteOperations: Failed execution phase Post First Boot. Error: 0x800707E7

2020-01-23 12:00:57, Error                 SP     Operation execution failed.

2020-01-23 12:00:57, Error                 SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute post-FirstBoot operations. Error: 0x800707E7

2020-01-23 12:00:57, Error                 SP     Apply (first boot apply, online phase): Migration phase failed. Result: 4, specific error: 0x800707E7[gle=0x00000002]

2020-01-23 12:00:57, Info                  SP     SetupPlatform: Global progress: 71, Phase progress: 93

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
  1. Anonymous
    2020-09-28T08:43:15+00:00

    I have had the same problem and because of the "User profile suffix mismatch", I went into the registry and checked

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    I noticed that there were two user accounts with the same username and home directory (one local account, one domain account).

    I don't know how this had happened. I'm quite sure someone had reinstalled windows 10 on said machine and set that username as "registered owner" of the machine. I guess this is how that happened.

    Anyways, I simply removed the registry key that seemed to be the local account and this has solved the problem for me.

    10+ people found this answer helpful.
    0 comments No comments
Answer accepted by question author
  1. Anonymous
    2020-05-01T01:34:20+00:00

    I encountered this as well.  In my case it was actually related to this issue I had a different machine just doing Windows Update to 1903.

    The issue in both cases is that my user profile had some files locked.  That meant when it tries to upgrade the user profile, it ended up with a ".000" suffix because the original folder had the locked files.  You can see this in the setupact.log, it said something like "expected profile 'Bob' but profile is 'Bob.000'".

    I had the Zune software still installed (from when I was developing software for Windows Phone), and that has a trace that needed to be disabled (or you can uninstall the Zune software).  See the details here:

    https://superuser.com/questions/1318983/windows-10-update-1803-renamed-the-user-account-folder-with-000-suffix/1519965#comment2352352\_1519965

    Once I handled that, the upgrade worked perfectly.

    2 people found this answer helpful.
    0 comments No comments

26 additional answers

Sort by: Most helpful
  1. Anonymous
    2020-02-01T17:43:44+00:00

    So I was able to fix this problem. Going into NETPLWIZ showed a bunch of "Unknown User" listed. After I deleted them, I was able to have the Win 10 upgrade complete installation.

    6 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-06-10T20:56:01+00:00

    I met the similar problem. (I upgraded my PC from win10 1909 to win 10 2004. After two days of experiments, the upgrade was finally successful)

    I use SetupDiag.exe(About SetupDiag)to collect log files(It seems to have a more detailed error messages)

    run SetupDiag.exe after the win10 update failed, you will find it generate a zip file "Logs.zip". Unzip it, there will be a file called setupact.log.

    At the end of the file:

    2020-06-10 02:25:01, Warning               SP     User profile suffix mismatch: upgrade asked for "krysl", actual suffix is: "krysl.000"

    2020-06-10 02:25:01, Info                  SP     Conflicting profile folder content (C:\Users\krysl):

    2020-06-10 02:25:01, Info                  SP     C:\Users\krysl [NTUSER.DAT]

    2020-06-10 02:25:01, Info                  SP     C:\Users\krysl [ntuser.dat.LOG1]

    2020-06-10 02:25:01, Info                  SP     C:\Users\krysl [ntuser.dat.LOG2]

    2020-06-10 02:25:01, Info                  SP     C:\Users\krysl [NTUSER.DAT{53b39e88-18c4-11ea-a811-000d3aa4692b}.TM.blf]

    2020-06-10 02:25:01, Info                  SP     C:\Users\krysl [NTUSER.DAT{53b39e88-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000001.regtrans-ms]

    2020-06-10 02:25:01, Info                  SP     C:\Users\krysl [NTUSER.DAT{53b39e88-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000002.regtrans-ms]

    2020-06-10 02:25:01, Info                  SP     C:\Users\krysl\AppData

    (ignore about 100 lines)

    2020-06-10 02:25:01, Info                  SP     C:\Users\krysl\SendTo

    2020-06-10 02:25:01, Info                  MIG    VERBOSEENUM: Will not enumerate reparse point C:\Users\krysl\SendTo

    2020-06-10 02:25:01, Info                  MIG    VERBOSEENUM: Will not enumerate reparse point C:\Users\krysl\SendTo

    2020-06-10 02:25:01, Info                  SP     C:\Users\krysl\Templates

    2020-06-10 02:25:01, Info                  MIG    VERBOSEENUM: Will not enumerate reparse point C:\Users\krysl\Templates

    2020-06-10 02:25:01, Info                  MIG    VERBOSEENUM: Will not enumerate reparse point C:\Users\krysl\Templates

    2020-06-10 02:25:01, Info                  SP     C:\Users\krysl\「开始」菜单

    2020-06-10 02:25:01, Info                  MIG    VERBOSEENUM: Will not enumerate reparse point C:\Users\krysl\「开始」菜单

    2020-06-10 02:25:01, Info                  MIG    VERBOSEENUM: Will not enumerate reparse point C:\Users\krysl\「开始」菜单

    2020-06-10 02:25:01, Error                 SP     User profile suffix mismatch, upgrade cannot continue.[gle=0x00000012]

    2020-06-10 02:25:01, Info                         Entering MigCloseCurrentStore method

    2020-06-10 02:25:01, Info       [0x0801dc] MIG    Closing catalog file

    2020-06-10 02:25:01, Info       [0x0801dd] MIG    Deleting catalog file at C:$WINDOWS.~BT\Work\MachineSpecific\Temp\tmpF608.tmp

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKLM\ELAM

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKLM\ELAM

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKLM\SYSTEM\CurrentControlSet

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKLM\SYSTEM\CurrentControlSet

    2020-06-10 02:25:02, Info       [0x0803e5] MIG    Not unmapping HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide; it is not mapped

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKLM\SOFTWARE\Wow6432Node\Classes

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKLM\SOFTWARE\Wow6432Node\Classes

    2020-06-10 02:25:02, Info       [0x0803e5] MIG    Not unmapping HKLM\SOFTWARE\WowAA32Node\Classes; it is not mapped

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKR

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKR

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKU.DEFAULT

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKU.DEFAULT

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKLM\SYSTEM

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKLM\SYSTEM

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKLM\COMPONENTS

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKLM\COMPONENTS

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKLM\SOFTWARE

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKLM\SOFTWARE

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKLM\SECURITY

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKLM\SECURITY

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKLM\SAM

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKLM\SAM

    2020-06-10 02:25:02, Info       [0x080487] MIG    Destroying OS analysis service

    2020-06-10 02:25:02, Info       [0x080488] MIG    Destroyed OS analysis service

    2020-06-10 02:25:02, Info                         Leaving MigCloseCurrentStore method

    2020-06-10 02:25:02, Info                         Entering MigShutdown method

    2020-06-10 02:25:02, Info                  MIG    COutOfProcPluginFactory::FreeSurrogateHost: Shutdown in progress.

    2020-06-10 02:25:02, Info                  MIG    MigHost: Exiting process.

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKLM\ELAM

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKLM\ELAM

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKLM

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKLM

    2020-06-10 02:25:02, Info       [0x0803e6] MIG    Removing mapping for HKU

    2020-06-10 02:25:02, Info       [0x0803e7] MIG    Successfully unmapped HKU

    2020-06-10 02:25:02, Info                  MIG    AdjustPrivilege: Privilege SeTakeOwnershipPrivilege will be Disabled

    2020-06-10 02:25:02, Info                  MIG    Privilege has been disabled

    2020-06-10 02:25:02, Info                  MIG    AdjustPrivilege: Privilege SeSecurityPrivilege will be Disabled

    2020-06-10 02:25:02, Info                  MIG    Privilege has been disabled

    2020-06-10 02:25:02, Info       [0x080487] MIG    Destroying OS analysis service

    2020-06-10 02:25:02, Info       [0x080488] MIG    Destroyed OS analysis service

    2020-06-10 02:25:02, Info                         Leaving MigShutdown method

    2020-06-10 02:25:02, Error                 SP     pSPExecuteApply: Migration phase caught exception: Win32Exception: User profile suffix mismatch, upgrade cannot continue: 指定的配置文件预期用于与指定设备的类型不同的设备。 [0x000007E7] enum MIGSTATUS __cdecl pSPExecuteApply(enum SetupPlatform::SP_MIG_SCOPE,class UnBCL::String *,int,int,int,class UnBCL::ArrayList<class UnBCL::String *> *,class UnBCL::String *,class UnBCL::String *,class UnBCL::ArrayList<class UnBCL::DictionaryEntry<class UnBCL::String *,class UnBCL::String *> *> *,class UnBCL::String *,int,int,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::ArrayList<class CWIMBootData *> *,class UnBCL::String *,int *,class CSPTelemetryData *,struct ISPMigProgress *,long *)

    2020-06-10 02:25:02, Info                  SP     SPExecuteFirstBootApply: End run. Result: 0x00000004

    2020-06-10 02:25:02, Error                 SP     Apply (first boot apply, online phase): Migration phase failed. Result: 4, specific error: 0x800707E7[gle=0x00000002]

    2020-06-10 02:25:02, Info                  SP     SetupPlatform: Global progress: 71, Phase progress: 93

    2020-06-10 02:25:02, Info                  SP     SETUPPLATFORMEXE: Sending progress message: Phase: First Boot, Operation: Migrate data, Percentage: 93%

    2020-06-10 02:25:02, Info                  SP     SETUPPLATFORMCOMM: Progress message received: Phase: First Boot, Operation: Migrate data, Percentage: 93%

    2020-06-10 02:25:02, Error                 SP     Operation failed: First boot apply. Error: 0x800707E7[gle=0x000000b7]

    2020-06-10 02:25:02, Error                 SP     Operation execution failed: 13. hr = 0x800707E7

    2020-06-10 02:25:02, Error                 SP     ExecuteOperations: Failed execution phase Post First Boot. Error: 0x800707E7

    2020-06-10 02:25:02, Error                 SP     Operation execution failed.

    2020-06-10 02:25:02, Error                 SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute post-FirstBoot operations. Error: 0x800707E7

    2020-06-10 02:25:02, Info                         Persisting diagnostics data to C:$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat

    2020-06-10 02:25:02, Info                         Diagnostics data saved successfully

    2020-06-10 02:25:02, Info                  SP     Execution phase [Post SysPrep] exiting with HRESULT [0x800707E7]

    2020-06-10 02:25:02, Info                  SP     SETUPPLATFORMCOMM: Progress message received: Phase: First Boot, Operation: Migrate data, Percentage: 93%

    2020-06-10 02:25:02, Info                  SP     WINDEPLOY error code is 0x80071501. Will not attempt uninstall

    2020-06-10 02:25:02, Info                  CBS    Trusted Installer signaled for shutdown, going to exit.

    2020-06-10 02:25:02, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_NOTIFICATION:PRESHUTDOWN

    2020-06-10 02:25:02, Info                  CBS    Ending the TrustedInstaller main loop.

    2020-06-10 02:25:02, Info                  CBS    Starting TrustedInstaller finalization.

    2020-06-10 02:25:02, Info                  CBS    Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6

    2020-06-10 02:25:02, Info                  CBS    Ending TrustedInstaller finalization.

    The first error occurs after C:\Users\krysl\「开始」菜单

    I found that is a broken junction, it links to a folder that does not exist:

    C:\Users\krysl>dir /A | grep JUNCTION

    2019/05/04 周六  01:27    <JUNCTION>     Application Data [C:\Users\XXXX\AppData\Roaming]

    2019/05/04 周六  01:27    <JUNCTION>     Cookies [C:\Users\XXXX\AppData\Local\Microsoft\Windows\INetCookies]

    2019/05/04 周六  01:27    <JUNCTION>     Local Settings [C:\Users\XXXX\AppData\Local]

    2019/05/04 周六  01:27    <JUNCTION>     My Documents [C:\Users\XXXX\Documents]

    2019/05/04 周六  01:27    <JUNCTION>     NetHood [C:\Users\XXXX\AppData\Roaming\Microsoft\Windows\Network Shortcuts]

    2019/05/04 周六  01:27    <JUNCTION>     PrintHood [C:\Users\XXXX\AppData\Roaming\Microsoft\Windows\Printer Shortcuts]

    2019/05/04 周六  01:27    <JUNCTION>     Recent [C:\Users\XXXX\AppData\Roaming\Microsoft\Windows\Recent]

    2019/05/04 周六  01:27    <JUNCTION>     SendTo [C:\Users\XXXX\AppData\Roaming\Microsoft\Windows\SendTo]

    2019/05/04 周六  01:27    <JUNCTION>     Start Menu [C:\Users\XXXX\AppData\Roaming\Microsoft\Windows\Start Menu]

    2019/05/04 周六  01:27    <JUNCTION>     Templates [C:\Users\XXXX\AppData\Roaming\Microsoft\Windows\Templates]

    2018/10/05 周五  14:11    <JUNCTION>     「开始」菜单 [C:\Users\XXXX\AppData\Roaming\Microsoft\Windows\Start Menu]

    XXXX in C:\Users\XXXX is the account nameI used before. years agoI changed my account name from "XXXX" to "krysl" using the method similar to the one mentioned in this article "How to Change Your Account Name on Windows 10".

    I use command line (find -type l -print0 | xargs -0 -IR ls -l R | grep XXXX) to find out all the broken junction, and fix them. (I should have written a script to automatically perform all those operations, but I wasted an hour and found no suitable solution. Maybe someone can do this)

    Fortunately, the number is not much.

    Do the following for each broken junction:

    rmdir "C:\Users\krysl\「开始」菜单"

    mklink /j "C:\Users\krysl\「开始」菜单" "C:\Users\krysl\AppData\Roaming\Microsoft\Windows\Start Menu"

    After completing these, still can't upgrade win10 successfully.

    I fix almost all "C:\Users\XXXX" to "C:\Users\krysl" in the Windows Registry. (I installed RegistryWorkshop to batch replace the values, because I can find hundreds of search results matching “Users\XXXX”.)

    Then, I was able to successfully upgrade win10. (It is strongly recommended to use "Backup and Restore (Windows 7)" to back up the entire system before using these operations to avoid serious unrecoverable errors.)

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-01-23T19:07:34+00:00

    Hi, FAUguy

    My name is Jeffrey and I am an Independent Advisor. I would be happy to help you today.

    If you have problems updating Windows, follow these steps:

    If you have a third-party antivirus, you must disable or uninstall it.

    You can do it manually by downloading the Windows ISO. This also applies to version 1909.

    When updating with the ISO, disconnect the Internet.

    https://www.microsoft.com/en-us/software-downlo...

    https://answers.microsoft.com/en-us/windows/for...

    2 people found this answer helpful.
    0 comments No comments