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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-12T02:02:23+00:00

    NTFS vs FAT32 should not affect anything.

    The usual cause of this (other than a lack of administrator privileges) is some kind of security software that sees a program trying to write to a different drive in the manner that the Windows 10 Media Creator Tool does as malware (or a virus, what-have-you). The reason that copying the file directly to the drive and running it from that drive solves the problem in these situations is that it removes this suspicious cross-drive behavior. This is also the reason why many users report temporarily disabling their security software as a solution to the problem.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-10T18:39:35+00:00

    I think the error comes to the USB is NTF .

    but the correct way is FAT32, then only instal the boot

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-10T15:31:27+00:00

    This worked for me. Bizarre but true.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Anonymous
    2018-01-09T22:34:23+00:00

    Copying the file to the usb drive didn't work for me.  And also formatting to ntfs didn't.

    What worked was to delete the usb partition and recreate it as mentioned in one of the comments here:

    "

    Copying the Media Creation Tool to the USB drive worked for me but I was curious to try a few things.

    It appears that running the Simple Volume Wizard fixes the problem without having to copy the Media Creation Tool to the USB drive.

    This can be accessed in Computer Management > Disk Management.

    Right click on the USB drive in the lower (graphical) part of the window and select Delete Volume.

    Click Yes to the warning. If there are any volumes remaining, delete those also.

    The entire USB drive should now show as Unallocated.

    Right click on it again and select New Simple Volume.

    Click through all the windows in the wizard using the default settings, selecting NTFS as the file system.

    A new volume will be created.

    Now run the Media Creation Tool without copying it to the USB drive.

    "

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments