Share via

Windows 10 Update Fails with error: 0x800707E7 - 0x3000D

Anonymous
2020-06-09T08:48:15+00:00

I've been having this issue for a few months now, but I'm finally determined to fix it. The thing is I'm stuck at windows 10 version 10240, and everytime I try to update windows, it will restart and get to about 70ish percent when an error occurs and it undoes all changes made to my PC. I've tried multiple suggestions I've seen online such as turning off any anti-virus/malware, unplugging all external devices other than mouse + keyboard, and clearing enough space on my main SSD. All resulted the same way.

I've also tried using the windows update assistant, found here: https://www.microsoft.com/en-us/software-download/windows10. And this did not work either. I then tried using the media creation tool found in the same link, and that didn't work either but at least it provided me with the following error message: "0x800707E7

  • 0x3000D The installation failed in the FIRST_BOOT phase with an error during MIGRATE_DATA operation".

I looked this up and I found that it may have something to do with corrupted windows profiles and I found advice suggesting to delete any unused profiles through regedit. I did find data for one profile that I had deleted a while back but I guess it still had data in ProfileList, so I deleted that too hoping it would help, but I'm still getting the same problem when I try to update. Let me know if more info is needed.

Also I'm not sure if this is relevant or not, but sometime last year my main SSD got corrupted and I had to format it and reinstall windows. It has worked fine since then other than this issue.

Windows for home | Windows 10 | Windows update

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

Sumit D - IA 170.4K Reputation points Independent Advisor
2020-06-11T05:01:31+00:00

Delete the one ending with .bak and check.

Was this answer helpful?

10 people found this answer helpful.
0 comments No comments

10 additional answers

Sort by: Most helpful
  1. Sumit D - IA 170.4K Reputation points Independent Advisor
    2020-06-10T04:50:51+00:00

    Alright, how about deleting the user profile from this address?

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

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  2. Sumit D - IA 170.4K Reputation points Independent Advisor
    2020-06-11T08:42:51+00:00

    Your welcome, thank you for letting us know!

    If you have no other questions feel free to mark the thread as answered and choose an appropriate rating. Have a good rest of the week.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-06-10T03:44:15+00:00

    HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/ProfileList

    and the profile folder I deleted from there was I believe called S-1-5-21-2221823218-2232689269-2096485173-1002

    I also checked the netplwiz prior to deleting the profile in regedit and there was no second profile in netplwiz, only in regedit.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. Sumit D - IA 170.4K Reputation points Independent Advisor
    2020-06-09T08:52:42+00:00

    Hi Ved,

    I am Sumit, an Independent Advisor and a 3 year Windows Insider MVP here to help.

    ERROR_PROFILE_DOES_NOT_MATCH_DEVICE winerror.h

    The specified profile is intended for a device of a

    different type than the specified device.

    Let us check the Installation log to find why the update failed. Please share the following logs:

    The Panther logs. Files named Setupact.log and Setuperr.log from the following path C:$Windows.~BT\Sources\Panther

    The Rollback logs: These usually are created if Windows Update rolls back. Files named Setupact.log and Setuperr.log from the following path C:$Windows.~BT\Sources\Rollback

    [Only if the error code is 0xC1900101-0x30018] The Device Install Log from C:/$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log

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

    To upload files here, see the following article. You must copy the logs to the desktop first and then upload.

    How to share diagnostic files/logs on Microsoft community

    https://answers.microsoft.com/en-us/feedback/fo...

    As the log size might be large consider zipping everything before uploading.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments