The above fix worked for me. I ran the Tool directly from the USB and it created it successfully.
Windows 10 Media Creation Tool Error: 0x80042405 - 0xA001A
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
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.
322 answers
Sort by: Newest
-
Anonymous
2018-07-05T15:16:06+00:00 -
Anonymous
2018-07-04T14:08:03+00:00 I am still facing the same issue though I have tried the method above.
It still showing the same error.
-
Anonymous
2018-07-03T10:41:45+00:00 How has this issue not been fixed yet in 2018...
Don't expect people to pay for a license and then having to fix this crap on their own.
Absolutely agree....i sometimes wonder how MS got to where they are with such poor software.
-
Anonymous
2018-07-02T23:58:19+00:00 It's silly but it works (FOR ME). and after careful observation of my magic hamster ball. it appears the drive does not get properly reformatted if the executable is not present. the process will un-partition the drive but never successfully re-partitions the drive when the file is missing. (failed runs have a nuked un-partitioned Thumbelina drive). looks like a MS Dev made a minor mistake in the build of the detecting code.
Your Mileage may vary , contents of this message may have shifted or settled during transport, offer not valid in 9 out of 10 realities . This statement should not be considered legal advice. Its been a long long day and I really need to go home.
-
Anonymous
2018-06-29T15:52:50+00:00 Thank you , it work for me,best regard, Luis