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: Oldest
  1. Anonymous
    2019-07-14T07:52:14+00:00

    OK, I see your numbers. Too, too bad I hastily deleted mine.

    (1) Ah, right, it was $Windows.~BT inside Windows.old (not the other way around I said).

    (2) Ah, that's right, "Previous Windows installation(s)" (not what I said).

    (3) I see yours is a Legacy install:     System Reserved, Windows (C:), Recovery;

        not the UEFI install that I've got:  EFI, MSR, Windows (C:), Recovery.

    Here are my thoughts...

    (a) Maybe MSFT continues to do it the old-fashioned way for Legacy installations.

    (b) Maybe my eye cataracts have blocked out most of my Windows.old.

    Anyway - I'll make pictures after the next feature update (new Windows version) & post them into this thread. I'll be flabbergasted, if it looks like yours.

    Edit: And here are my partitions. The upgrade didn't add the Recovery (WinRE 1903), because it was already there & large enough. But it did update it, because Shift+Restart gets to a 175 Command Prompt - just as you promised in that other thread. 

    Note: Disk Management doesn't show the 16 MB MSR partition. That's normal.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-07-14T08:27:33+00:00

    PCR, 

    As for your # 3) ,

    I have 5 systems 3 are legacy and 2 are UEFI, the logic is the same,

    Windows.old was over 23GB on my UEFi machines too.

    The only difference on the UEFI it did not need to add a recovery partition because the existing one was big enough. It may add an extra one or expand the existing one if there is not enough space.

    Also Disk Management does not show all the partitions, there is a 16MB of type other that you don't see on disk management, but you will see it with diskpart  -> list partition.

    See below.

    DISKPART> list disk

      Disk ###  Status         Size     Free     Dyn  Gpt

      --------  -------------  -------  -------  ---  ---

      Disk 0    Online          476 GB      0 B        *

      Disk 1    Online         1863 GB      0 B

      Disk 2    No Media           0 B      0 B

      Disk 3    No Media           0 B      0 B

      Disk 4    No Media           0 B      0 B

      Disk 5    No Media           0 B      0 B

    DISKPART> select disk 0

    Disk 0 is now the selected disk.

    DISKPART> list partition

      Partition ###  Type              Size     Offset

      -------------  ----------------  -------  -------

      Partition 1    Recovery           499 MB  1024 KB

      Partition 2    System             100 MB   500 MB

      Partition 3    Reserved            16 MB   600 MB

      Partition 4    Primary            476 GB   616 MB

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-07-14T15:38:57+00:00

    OK. I await the next upgrade, & chances are good I'll be flabbergasted to see it gives me a full sized Windows.old. Did you actually see your user folders (Documents, Downloads, Pictures, etc.) inside your Windows.old? I definitively recall mine were absent.

    That's right, the MSR (Microsoft System Reserved) shows up in DiskPart & in 3rd-party partitioning tools like AOMEI Partition Assistant...

    That MSR is a strange one. It doesn't show up as a separate entity in a Windows system image backup, either. But I discovered it is within the .vhdx of the Windows partition. But I can't recall how I made the discovery or how to repeat it.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-07-14T18:10:52+00:00

    PCR, 

    If you go in the  Windows.old 'Users' folder you should find all that stuff  needed for the various users to go back.

    The files may not be in the windows.old folders if they were already moved in the new folders, they save the structure and the folders, they don't need to save the same stuff twice as long as it is available on the C: volume one place or the other, they can go back to the previous version and move the files where they belong, the option to go back is only good for 10 days anyway... 

    Here is the same disk cleanup on a UEFI system, you can see 25.3GB for the previous windows Installation

    Was this answer helpful?

    0 comments No comments