Media Creation Tool Error 0x80042405 0xA001B

Anonymous
2019-05-22T02:24:49+00:00

I must be doing something wrong because I always have the update fail with some BS error like this. What are the proper steps to run this tool?

I download the tool to the desktop. I'm on an Admin account. I insert a 16GB thumb drive. I format it. I start the tool. I point it to the thumb drive. During the phase where the files are copied to the USB, I get some stupid error like this:

Why are my steps not good enough? Where is the hole in my logic? Or is this tool just written poorly. I'd like to use stronger language here as I used to have to start it all over again and burn bandwidth trying this failed endeavor over and over.

I've heard people make it work by running the tool FROM the USB. Why would that matter? I've tried to write files to the thumb drive just after the format and before running the tool to make sure I have successful writes. Doesn't help. 

As a workaround today, I left the error up for a bit. Tried to access the thumb drive and it said it needed to be formatted AGAIN! So I did. Then I just opened the C:$Windows.~WS\Sources\Windows and copied the files to the drive by hand. Made the dang thing myself! WHO WRITES THIS STUFF??

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 No comments
Answer accepted by question author
Kapil Arya 38,446 Reputation points Volunteer Moderator
2019-10-23T10:23:40+00:00

Hello,

I would suggest you to create latest media. Download the Media Creation Tool using this link:

https://go.microsoft.com/fwlink/?LinkId=691209

Hope this helps!

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments

227 additional answers

Sort by: Newest
  1. Anonymous
    2019-09-14T21:57:48+00:00

    All these desktops. One is an HP core i5 3rd gen, one dell core i7 4th, 4th gen clone i7 devil's canyon, laptop of specs unknown. Most recent one succeeded on HP 6th gen i5 but I had MCT on the USB.

    Never seen any sleeping USB issues on any but not ruling it out yet. Very plausible.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-09-14T20:50:02+00:00

    If you have the 64 bit installed you do not need to install the 32 bit on the same computer as the 64 bit system will read all of the 32 bit software.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-09-14T20:11:10+00:00

    I have been following this topic since I posted to it on July 8th, more than 2 months ago.

    It is obvious to me that this error "code" is a catch all for any and all failures that occur when making the MCT tool.

    It is too bad that microsoft won't acknowledge what the problem is or at least put out meaningful error codes.

    It only took them 25 years to get to a stable and useful release of Windows.  I am not looking for any meaningful progress on this problem.

    JelloZ, 

    Yes it is a catch all, you can get the same error message if you pull out the USB device before MCT tries to format it. It gets to 50% of the progress and then it tries to access the USB device which is no longer available.

    So anything that causes the USB device to become not accessible, after the selection at the beginning of the process,  will end up with the same error message when MCT tries to write to the device.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-09-14T19:57:24+00:00

    Roy, 

    I just tried again on the Lenovo laptop, without power cable, just on batteries.

    The whole operation of download, verify and copy to the USB device took less than 20 Minutes without any error.

    This was with only the 64 Bit version. 

    I assume it may take twice as long if I download both 32 and 64 bit.

    Like you I don't want to waste my bandwidth on these tests, I already did this too many times without error.

    Again I cannot get this thing to fail. :(

    Was this answer helpful?

    0 comments No comments