Windows Media Creation Tool error 0x80072F76-0x20017

Anonymous
2017-10-29T07:49:05+00:00

Hello, 

I want to reinstall my windows 10 64 bit into a new SSD I bought.

I am trying to create a USB flash drive using windows media creation tool but I am getting this error every time. I have tried it on 4 laptops and 1 desktop, and with 3 different pendrives. 

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
Answer accepted by question author
Anonymous
2017-10-29T11:10:43+00:00

Hi Divyank,

The error code 0x80072F76-0x20017 means that the tool doesn't have permission for it to run. For us to assist you, we suggest that you follow the simple steps listed below:

  1. Right-click on the Media Creation Tool.exe.
  2. Press Properties.
  3. Click on General.
  4. At the bottom, click on Unblock.
  5. Press Apply, and then OK.

Let us know how it goes and if you need further assistance, feel free to post back.

Was this answer helpful?

100+ people found this answer helpful.
0 comments

146 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-12-05T04:29:01+00:00

    Thats because that is the work around.  The actual solution is the compatibility mode.  Yes, the DNS change works because it bypasses the version checker on the server, but running it in compatibility mode is the actual way it

    was designed.

    That is A workaround, not THE workaround, as, again, that solution works about as well as all of the others, meaning it does for some, and only sometimes.  

    The problem is NOT compatibility.  If it were, the tool wouldn't work for ANYONE with Windows 10 who didn't use the compatibility mode.  It works just fine for me without it.  It may not tomorrow.  It may again the next day.  When it works it works on both of my Windows 10 computers.  When it doesn't it doesn't work on either one.  When it works again it works on both.

    Whatever the problem is, it lies with Microsoft's servers, not compatibility.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-12-05T03:45:54+00:00

    Because when you select a version, it should be ran with the compatibility mode troubleshooter.  Most of the time it will be the Windows 8 compatibility mode, but obviously if you are on a version previous to that then you wont be able to run it in Windows 8 compatibility mode.  It would most likely be the version previous to the one you are using currently.  If your Windows 8 or 10, then Win 8 mode, Windows 7, then 7 or previous.  Easiest way is to use the Compatibility Mode version troubleshooter, if 8 doesn't work for you.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-12-05T03:42:07+00:00

    Thats because that is the work around.  The actual solution is the compatibility mode.  Yes, the DNS change works because it bypasses the version checker on the server, but running it in compatibility mode is the actual way it was designed.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-12-05T03:40:43+00:00

    Huh? I have no idea what you just said.

    Was this answer helpful?

    0 comments