Like they used to say in cartoons, "It's crazy enough, it just might work."
Sure enough, it worked.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Greetings,
Recently, I have seen many people inquiring about this error regarding the Media Creation Tool. I myself got this error when I try to create a bootable USB drive (aka Create an Installable Media).
Here's what I tried:
Reformatting USB drive to FAT32
Deleting files
Tried to locate and run Setupprep.exe (I couldn't find this file in C:\$Windows.~BT\Sources or anywhere)
Change Startup Type of Update-Related Services (Startup Type: Manual -> Automatic)
Uninstalled and Reinstall Windows 10 Media Creation Tool
Made sure my USB is above 8Gb as instructed by the tool (it is 15Gb)
The Fix (for me at least):
1. Downloadthe Windows 10 Media Creation Tool directlyinto the USB drive that you want to use as a bootable device (meaning you download the Tool into the same USB you chose to use as an Installation Media). If you already downloaded the tool on your PC's Desktop, copy it into your USB.
2. Run the Tool directly from your USB, meaning you open File Explorer, locate the MediaCreationTool.exe in your USB and double-click to run it.
The installer should then create an Installation Media/Bootable USB.
Hope this helps!
Cheers,
Tom
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.
Like they used to say in cartoons, "It's crazy enough, it just might work."
Sure enough, it worked.
NTFS + Setup file on USB + Admin Previleges Worked for me !! All other combinations failed for obviously unknown reasons... Magics can only be experienced not explained. Thanks TOM !!
Worked perfectly for me.
Thank you.
I had the same issue.
Each time it fails it would formatting my USB, and I left the USB's display name blank.
The last time I change the USB's display name as "X", it solved the problem.
After successfully installed, it changed the name to "ESD-USB".
Thanks Tom!
Can't believe such a buggy Microsoft product isn't fixed quickly, but your workaround worked for me!