Windows 10 Media Creation Tool Error: 0x80042405 - 0xA001A

Anonymous
2017-11-16T13:39:26+00:00

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.

0 comments

322 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-05-10T15:36:20+00:00

    It is errors like this that just make me smack my head and think "how can you get something so simple and obvious, so fundamentally wrong MS?"

    I shake my head at you, the top software company in the world cannot even get this right. And we use their OS.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-05-10T16:02:24+00:00

    Well this fix worked for me. Hang your collective heads in shame MS, this is just pathetically poor.....

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-05-10T16:05:35+00:00

    This worked for me when other steps did not. I'm wondering if it's either due to formatting in NTFS (I was originally using FAT32) or creating a partition for the size of the entire drive (was just doing 32 GB before and it's a 64 GB drive). Either way, thanks!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-05-10T19:08:52+00:00

    This also worked for me! Thanks

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2018-05-11T19:28:11+00:00

    That has only gone a blooming worked.  What an odd fix!

    Was this answer helpful?

    0 comments