{"id":19854,"date":"2020-11-13T11:14:55","date_gmt":"2020-11-13T05:44:55","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=19854"},"modified":"2023-08-08T20:06:23","modified_gmt":"2023-08-08T14:36:23","slug":"error-0x800707e7-0x3000d-upgrade-windows-10","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/error-0x800707e7-0x3000d-upgrade-windows-10\/","title":{"rendered":"Error 0x800707E7 0x3000D during Windows Setup"},"content":{"rendered":"

When you upgrade from Windows 7 or Windows 8 to Windows 10 or 11 or do a repair installation, the error 0x800707E7 \u2013 0x3000D may occur and the setup is canceled automatically. The same error may occur when installing a Feature Update (e.g., upgrading from 21H2 to 22H2). Here is the full error message:<\/p>\n

We couldn't install Windows 10.\r\n\r\nWe've set your PC back to the way it was just before you started installing Windows 10.\r\n\r\n0x800707E7 - 0X3000D\r\n\r\nThe installation failed in the FIRST_BOOT phase with an error during MIGRATE_DATA operation.<\/pre>\n
<\/p>\n
Cause<\/h2>\n
The error ERROR_PROFILE_DOES_NOT_MATCH_DEVICE<\/code> (0x800707E7<\/code>) denotes\u00a0The specified profile is intended for a device of a different type than the specified device<\/strong><\/em>.<\/p>\n
The error occurs when the setup process attempts to migrate data from the old installation to the new. If the old installation has service user accounts (e.g. nVidia’s UpdatusUser<\/code> user account, SQL Server’s service account, etc.), the setup process fails when attempting to access the account and migrate its contents.<\/p>\n
The setuperr.log (C:\\$Windows.~BT\\Sources\\Panther\\setuperr.log<\/code>) would show these entries:<\/p>\n
Error SP User profile suffix mismatch, upgrade cannot continue.[gle=0x00000012]\r\n\r\nError 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 *)\r\n\r\nError SP Apply (first boot apply, online phase): Migration phase failed. Result: 4, specific error: 0x800707E7[gle=0x00000002]\r\n\r\nError SP Operation failed: First boot apply. Error: 0x800707E7[gle=0x000000b7]\r\n\r\nError SP Operation execution failed: 13. hr = 0x800707E7\r\n\r\nError SP ExecuteOperations: Failed execution phase Post First Boot. Error: 0x800707E7\r\n\r\nError SP Operation execution failed.\r\n\r\nError SP CSetupPlatformPrivate::Execute: Failed to deserialize\/execute post-FirstBoot operations. Error: 0x800707E7<\/pre>\n
And the following line is the most significant in the setupact.log<\/code> file:<\/p>\n
Warning SP User profile suffix mismatch: upgrade asked for \"UpdatusUser\", actual suffix is: \"UpdatusUser.000\"\r\nInfo SP Conflicting profile folder content (C:\\Users\\UpdatusUser)<\/pre>\n
Resolution<\/h2>\n
The UpdatusUser<\/code> is a special user account added by the Nvidia update<\/strong> program. This account runs the NVIDIA Update service for updating drivers and application profiles through the NVIDIA server. The service cannot be run without this account.\u00a0This account runs the NVIDIA Update service for updating application profiles through the NVIDIA server.<\/p>\n
It’s unclear why the Windows 10 Setup is encountering an error when accessing these kinds of special profiles.\u00a0To work around the issue, delete the UpdatusUser account.<\/p>\n
To remove the UpdatusUser account from desktop PCs, you must remove the NVIDIA Update software (and all its functionality) from your PC. To remove NVIDIA Update software, either:<\/p>\n
\u2022 Uninstall the NVIDIA Update software using Windows Programs and Features, or<\/p>\n
\"nvidia<\/p>\n
\u2022 Reinstall the NVIDIA driver but do not install (deselect) the NVIDIA Update software<\/p>\n
To remove the UpdatusUser account from Optimus notebooks, you must uninstall the entire NVIDIA graphics driver from the notebook. It is not possible to remove the UpdatusUser<\/code> account without uninstalling the driver.<\/p>\n
(via What is NVIDIA \u2019UpdatusUser\u2019? | NVIDIA<\/a>)<\/em><\/p>\n
After removing the UpdatusUser<\/code> service account, remove the C:\\Users\\UpdatusUser folder manually if required. The Windows 10 Setup should run correctly now.<\/p>\n
\n
Not UpdatusUser, but a regular account?<\/h3>\n
In some cases, the log may point to a regular user account instead of a service account like UpdatusUser.<\/p>\n
Example:<\/h4>\n
\r\nWarning    [0x0803ba] MIG    Found valid profile but can't get user credentials. User SID: S-1-5-21-4177050897-1459726966-2642812848-1002<\/strong>. Error: 0x00000534[gle=0x000000cb]\r\nWarning SP User profile suffix mismatch: upgrade asked for \"ramesh\", actual suffix is: \"ramesh.000\"\r\nInfo SP Conflicting profile folder content (C:\\Users\\ramesh):<\/pre>\n
Clean up the ProfileList registry key<\/h4>\n
Before beginning, note that troubleshooting the error 0x800707E7 is similar to troubleshooting the 0x8007001F error. These error codes have a common cause — i.e., duplicate user profiles. For more information, read the article Error 0x8007001F Installing Feature Update or Cumulative Update.<\/a><\/em><\/p>\n
Open the Registry Editor by running regedit.exe<\/code>.<\/p>\n
Go to the following key:<\/p>\n
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\ProfileList<\/pre>\n
Select the erroneous SID subkey (denoted in the log). In this example, the erroneous SID is S-1-5-21-4177050897-1459726966-2642812848-1002<\/strong>. Delete the SID from the ProfileList registry key below:<\/p>\n
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\ProfileList\\S-1-5-21-4177050897-1459726966-2642812848-1002<\/pre>\n
Important:<\/strong> Be sure to make registry hive backup<\/a> before modifying the ProfileList<\/code> registry entry. Incorrectly modifying the key will prevent you from logging in to your user account.<\/p>\n
\n
Event Tracing sessions running?<\/h3>\n
The error 0x800707E7 may also occur if some files in your profile folder is locked by some event tracing files. To see if a third-party app has enabled event tracing, inspect the Performance Monitor.<\/p>\n
    \n
  1. Open perfmon.msc<\/strong><\/code> and maximize the window.<\/li>\n
  2. Expand “Data collector sets”.<\/li>\n
  3. Inspect “Event Trace sessions” and “Startup Event Trace sessions” to see if a third-party event trace session is running. If so, stop\/disable it.\n
    For example, Zune app or Norton Security may have enabled an event tracing session.<\/p>\n
    \"Norton
    \nThe screenshot is from Windows 10 Polish language OS. Polish to English translation is below:<\/p>\n
    \"Dzia\u0142a\" means \"Working\"\r\n\"W\u0142\u0105czone\" means \"Enabled\"\r\n\"Wy\u0142\u0105czone\" means \"Disabled\"<\/pre>\n
    In this example, you can see Norton’s “NPETraceSession” entry is enabled.<\/li>\n
  4. See if Setupact.log mentions “NPETraceSession” as the reason for the migration failure. If so, disable the event trace.<\/li>\n
  5. In “Startup Event Trace sessions, double-click “NPETraceSession”<\/li>\n
  6. Select “Trace Session” tab, and uncheck “Enabled”<\/li>\n
  7. Click OK.<\/li>\n
  8. Restart Windows and try to update Windows.<\/li>\n<\/ol>\n
    \n
    Here is what some users said:<\/h3>\n
    This led me to discover HOMEGROUPS was enabled on this computer. I disabled HOMEGROUPS, the homegroups$ user was removed and upgraded successfully.<\/p><\/blockquote>\n
     <\/p>\n
    So the problem was indeed a wrong user, in my case it was the user “UpdatusUser”. It was tricky because it is a hidden user.
    \nAfter some research I found that this user is created by NVIDIA since version 270 on desktop computers (previous version on some laptop computer already used the “UpdatusUser”).<\/p><\/blockquote>\n
     <\/p>\n
    Upgrading from Win10 1511 to 1703. Same problem & codes as original question. Unlike below replies with solutions, only Microsoft AV was installed. Two steps to my solution.<\/p>\n
    1 – I found two profiles referencing the same user directory on the hard disk. I deleted the one I suspected was invalid. (Export\/Backup first!)<\/p>\n
    HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\ CurrentVersion\\ProfileList<\/p>\n
    2 – I switched from using a domain admin account to using the local PC admin account to perform the upgrade (run setup.exe).<\/p>\n
    Unsure which step or both was the key.<\/p><\/blockquote>\n
     <\/p>\n
    What did I do to solve this problem:<\/p>\n
    I moved my SQL Server Databases to another SQL Server Instance on another machine in my network (in fact a VM hosted on the same PC)
    \nI uninstalled SQL Server 2017 from the machine
    \nI removed all folders in C:\\Windows\\ServiceProfiles that seemed to belong to SQL Server respectively were mentioned in the log file (about 10 folders)
    \nThereafter I started the update again. And it ran through.<\/p>\n
    And maybe this will help someone else…<\/p>\n
    Michael<\/p><\/blockquote>\n
    I hope one of the above suggestions helped you fix the Windows 10\/11 Setup error 0x800707E7 0x3000D.<\/p>\n","protected":false},"excerpt":{"rendered":"
    When you upgrade from Windows 7 or Windows 8 to Windows 10 or 11 or do a repair installation, the error 0x800707E7 \u2013 0x3000D may occur and the setup is canceled automatically. The same error may occur when installing a Feature Update (e.g., upgrading from 21H2 to 22H2). Here is the full error message: We … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[8,869],"tags":[191,951,441,781],"class_list":["post-19854","post","type-post","status-publish","format-standard","hentry","category-windows-10","category-windows-11","tag-error-messages","tag-logs","tag-registry","tag-windows-setup"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":9422,"url":"https:\/\/www.winhelponline.com\/blog\/windows-10-feature-update-error-0xc1900101\/","url_meta":{"origin":19854,"position":0},"title":"Error 0xC1900101 Installing Windows 10 Feature Update","author":"Ramesh","date":"May 20, 2019","format":false,"excerpt":"When you install a Windows 10 feature update (eg., v1809 on a computer running v1803) via Windows Update, the error 0xC1900101 occurs and the installation fails. Error 0xC1900101 is a rollback code that indicates that an incompatible driver is present on the computer. Microsoft stated in its blog post that\u2026","rel":"","context":"In "Windows 10"","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"0xc1900101 windows 10 1809","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2019\/05\/0xc1900101-error.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2019\/05\/0xc1900101-error.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2019\/05\/0xc1900101-error.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2019\/05\/0xc1900101-error.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":19513,"url":"https:\/\/www.winhelponline.com\/blog\/windows-update-error-0xc19001e1-windows-10\/","url_meta":{"origin":19854,"position":1},"title":"[Fix] Windows Update Error 0XC19001E1 in Windows 10","author":"Ramesh","date":"October 25, 2020","format":false,"excerpt":"On some systems, the error 0XC19001E1 may occur when installing a Windows 10 feature update -- e.g., when upgrading from version 1903 to 2004, 2004 to 20H1, etc. The 0XC19001e1 error is one of the vaguest error messages of all the Windows Update errors. Feature update to Windows 10, version\u2026","rel":"","context":"In "Windows 10"","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"windows 10 inplace upgrade","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/10\/w10-inplace-upgrade.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/10\/w10-inplace-upgrade.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/10\/w10-inplace-upgrade.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/10\/w10-inplace-upgrade.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":80494,"url":"https:\/\/www.winhelponline.com\/blog\/feature-update-software-license-terms-error-encountered\/","url_meta":{"origin":19854,"position":2},"title":"Windows 11 Upgrade: Software License Terms – Error encountered","author":"Ramesh","date":"March 16, 2026","format":false,"excerpt":"When you install the latest Windows 11 Feature Update via Windows Update, the following error message may occur: Software License Terms Error encountered. The above error likely occurs because EULA.txt couldn't be opened due to a corrupt setup image. Resolution Option 1: Reset the Windows Update cache Resetting the Windows\u2026","rel":"","context":"In "Windows 11"","block_context":{"text":"Windows 11","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-11\/"},"img":{"alt_text":"Windows 11 Installation Assistant","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2026\/03\/windows_11_installation_assistant.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2026\/03\/windows_11_installation_assistant.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2026\/03\/windows_11_installation_assistant.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2026\/03\/windows_11_installation_assistant.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":6011,"url":"https:\/\/www.winhelponline.com\/blog\/dism-restorehealth-error-0x800f081f-windows-10\/","url_meta":{"origin":19854,"position":3},"title":"[Fix] DISM and .NET Framework 3.5 Error 0x800F081F","author":"Ramesh","date":"December 9, 2017","format":false,"excerpt":"When running the following DISM command, the error 0x800F081F may appear in some systems. The same error occurs when installing the .NET Framework in Windows 10. Dism \/Online \/Cleanup-Image \/RestoreHealth Error: 0x800f081f The source files could not be found. Use the \"Source\" option to specify the location of the files\u2026","rel":"","context":"In "Windows 10"","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"dism restorehealth wim success","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2017\/12\/dism-wim-success.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2017\/12\/dism-wim-success.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2017\/12\/dism-wim-success.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2017\/12\/dism-wim-success.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":10136,"url":"https:\/\/www.winhelponline.com\/blog\/fix-logilda-dll-error-at-startup-in-windows-10\/","url_meta":{"origin":19854,"position":4},"title":"Fix: LogiLDA.dll Error at Startup","author":"Ramesh","date":"July 3, 2019","format":false,"excerpt":"After upgrading to Windows 10, you may see one of the following errors when logging in to your user account: There was a problem starting C:\\Windows\\System32\\LogiLDA.dll The specified module could not be found Error in C:\\WINDOWS\\SYSTEM32\\LOGILDA.DLL - Missing entry: LOGIFETCH There was a problem starting C:\\Windows\\System32\\LogiLDA.dll. C:\\Windows\\System32\\LogiLDA.dll is not a\u2026","rel":"","context":"In "Windows"","block_context":{"text":"Windows","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/"},"img":{"alt_text":"logitech download assistant LogiLDA.dll error at startup - autoruns","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2019\/07\/logitech-download-assistant-autoruns.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2019\/07\/logitech-download-assistant-autoruns.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2019\/07\/logitech-download-assistant-autoruns.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2019\/07\/logitech-download-assistant-autoruns.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":27613,"url":"https:\/\/www.winhelponline.com\/blog\/vc-redist-setup-error-1935-assembly\/","url_meta":{"origin":19854,"position":5},"title":"VC++ Redist Error 1935: An error occurred during the installation of assembly","author":"Ramesh","date":"August 26, 2022","format":false,"excerpt":"When you run the Visual C++ Redistributable setup file or install a program that adds the VC++ redistributables, error 1935 may occur. The following is the full error message verbatim: Microsoft Visual C++ 2008 Redistributable Setup Error 1935.An error occurred during the installation of assembly 'Microsoft.VC90.ATL,version=\"9.0.30729.6161\",publicKeyToken=\"1fc8b3b9a1e18e3b\",processorArchitecture=\"x86\",type=\"win32\"'. Please refer to Help\u2026","rel":"","context":"In "Windows"","block_context":{"text":"Windows","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/"},"img":{"alt_text":"icacls installtemp - vc++ error 1935","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/08\/icacls-installtemp.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/08\/icacls-installtemp.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/08\/icacls-installtemp.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts\/19854","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/comments?post=19854"}],"version-history":[{"count":0,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts\/19854\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/media?parent=19854"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/categories?post=19854"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/tags?post=19854"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}