Fix it now
The published half of this code is VDS_E_OBJECT_NOT_FOUND: the Virtual Disk Service could not find the object it asked for. That is what a stick which drops off the bus mid-write looks like from inside the tool. The 0xA001A extend code is not published by Microsoft, so judge the failure by what the tool was doing rather than by that number.
diskpart
list disk
select disk 2
clean
exit
- Use a different USB stick before anything else. Microsoft’s published requirement is a blank drive with at least 8 GB of space, and it notes that any content on the drive is deleted.
- Wipe the stick properly from an elevated prompt rather than right-clicking Format, using the block above with the correct disk number.
- Disconnect every other removable device, and close anything watching the drive – backup agents and endpoint products with device control are the usual culprits.
- Run the Media Creation Tool as administrator, from a normal interactive sign-in rather than through a remote tool, a service or a scheduled task.
- If it fails again, skip the tool: download the ISO directly and either write it with a media-writing utility or copy its contents onto a stick you have prepared yourself.
- Verify what you downloaded before you build anything on it:
Get-FileHash -Path .\Windows.iso -Algorithm SHA256and compare with the value published where you got it.
A half-written stick often still boots and then fails part way through Setup, which sends people off diagnosing a machine that was never the problem. Rebuild the media rather than retrying the install.
If the tool completes and the stick boots to the disk selection screen, you are done. If not, the next section separates the tool’s problems from the stick’s.
Why it happens
The Media Creation Tool does three things in sequence: download the payload, prepare the target drive, and write the installation files onto it. Failures at each stage look similar from the outside and are fixed in completely different places, so the useful first question is how far it got before it stopped.
The result half of the headline code has a published meaning. 0x80042405 is VDS_E_OBJECT_NOT_FOUND from the Virtual Disk Service error list, ‘The specified object was not found’. It is not a statement that partitioning or formatting failed; it is a statement that something the disk service asked for was not there. A flash drive that resets mid-operation, or one whose controller stops responding, disappears from under the service exactly like that.
The 0xA001A part is not published. Microsoft’s extend code tables document phases 0 to 5, and 0xA is outside them, so there is no phase or operation to decode. Treat it as an identifier for the failure the tool hit rather than as something with a meaning you can look up. The same applies to 0x8030002F, which returns nothing at all from Microsoft’s documentation.
0x8007025D deserves its own note because it is widely misdescribed, including in earlier versions of this article. It is Win32 605, ERROR_BAD_COMPRESSION_BUFFER: ‘The specified buffer contains ill-formed data.’ Not a failed read, not a mismatch against an expected value – a buffer whose contents are malformed. On a machine building or using installation media that usually means the source is corrupt, the write was bad, or memory is scrambling data in transit.
0x800704DD is Win32 1245, ERROR_NOT_LOGGED_ON: the operation was not performed because the user has not logged on to the network. The 0x90016 extend code paired with it is not published. The practical reading – run the tool from a proper interactive administrator session rather than from a service or a remote automation context – is sound advice, but it is inference from the result half rather than something Microsoft documents for the pairing.
The stick cannot be partitioned
You have this one if The failure comes early, before substantial download progress, and Disk Management struggles with the drive too.
- Clean and rebuild the partition table in diskpart using the block above.
- If
cleanitself fails, clear the read-only attribute on the selected disk and try again. - If it still fails, the stick is at the end of its life. Replace it rather than persevering.
Flash drives fail write-first. One that reads fine and refuses to be formatted is telling you something, and it does not get better.
The tool has no interactive context
You have this one if 0x800704DD accompanies the failure, or the tool was started through remote management, a service, a scheduled task or a session that can disconnect.
- Sign in to the machine interactively as an administrator and run the tool there.
- Right-click and choose Run as administrator rather than relying on the account being one.
- Do not run it in a context with no loaded user profile, and avoid a session that can drop mid-write.
Security software is intercepting the writes
You have this one if The tool fails at the same point every time on a managed machine and works on an unmanaged one.
- Check for device control or removable media policies in the endpoint product; blocking writes to USB storage outright is a common default.
- Pause real-time scanning for the duration if policy allows, or build the media on a machine outside that policy.
- Reinstate the policy afterwards.
There is no room for the temporary download
You have this one if The failure comes after a long download and the system drive has only a few gigabytes free.
- Free space with Disk Cleanup, using Clean up system files to include previous installations and delivery optimisation content.
- Clear the temporary folders under the user profile and under
C:\Windows\Temp. - Retry with several gigabytes free rather than just enough to fit the image.
The image will not fit the file system on the stick
You have this one if You are building media by hand on a FAT32 stick and the copy fails on the largest file under sources.
- Format the stick NTFS, which removes the single-file size limit. Most UEFI firmware boots NTFS media.
- Where the firmware insists on FAT32, split the image instead:
Dism /Split-Image /ImageFile:D:\sources\install.wim /SWMFile:E:\sources\install.swm /FileSize:3800. - Copy everything else from the ISO across as normal.
Full reference
What is published and what is not
| Code | Status |
|---|---|
0x80042405 |
VDS_E_OBJECT_NOT_FOUND: the specified object was not found |
0xA001A (extend half) |
Not published; outside Microsoft’s documented phase range |
0x8030002F |
Not published anywhere by Microsoft |
0x8007025D |
Win32 605, ERROR_BAD_COMPRESSION_BUFFER: the buffer contains ill-formed data |
0x800704DD |
Win32 1245, ERROR_NOT_LOGGED_ON: the user has not logged on to the network |
0x90016 (extend half) |
Not published |
Preparing a stick by hand
- Open an elevated Command Prompt and run
diskpart. - Run
list diskand identify the USB stick by size. Getting this wrong wipes an internal disk. - Select it, run
clean, then create a primary partition and format it. - NTFS avoids the FAT32 single-file limit; FAT32 is more widely bootable but needs the image split.
- Assign a drive letter, then copy the contents of the mounted ISO across, or let the Media Creation Tool write to the prepared stick.
Splitting the image for FAT32
Dism /Split-Image /ImageFile:<install.wim> /SWMFile:<install.swm> /FileSize:<MB> divides the image into chunks below the size you name. Note the documented behaviour: if a single file inside the image is larger than the value you give, one of the resulting .swm files will be larger too, in order to accommodate it. Add /CheckIntegrity if you want DISM to detect corruption while it works.
Verifying before you trust the media
| Check | What it proves |
|---|---|
Get-FileHash -Algorithm SHA256 on the ISO |
The download is intact before any hardware is involved |
The sources folder exists on the stick with a plausibly sized image file |
The write completed rather than stopping quietly |
| The stick boots a test machine to the disk selection screen | The media is bootable on that firmware |
| A second machine boots it too | The media rather than one machine’s USB implementation |
When the tool is not the answer
Microsoft publishes the ISO as well as the tool, and for virtual machines it recommends creating an ISO rather than a USB drive. If the tool keeps failing on a machine you do not control – a managed laptop with device control policies, say – downloading the ISO and building the stick elsewhere is faster than negotiating an exception. The ISO is also what you want for an in-place upgrade, since mounting it skips the removable media path entirely.
When a licence is the actual fix
Building media costs nothing: Microsoft publishes both the tool and the ISO, and a working USB stick is the only outlay. The licence sits separately from the media. The same ISO installs Home, Pro and the volume editions, and what decides which one a machine ends up running is the key or the digital entitlement attached to it, not the stick. So there are only two reasons to buy anything in this article. One is a replacement USB stick, because a drive that fails to format is finished. The other is an edition change: if you are building media in order to move a machine from Home to Pro, that is a Windows 11 Pro upgrade licence, and it is a decision about capability made before you build the stick rather than a fix for the tool failing. Buy neither on the strength of a failed media build alone.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80042405 - 0xA001A |
The result half is VDS_E_OBJECT_NOT_FOUND, the specified object was not found; the 0xA001A extend half is not published | Microsoft Learn |
0x8030002F |
Seen during Setup and media creation; no acceptable source publishes a meaning | not published by the vendor |
0x8007025D |
Win32 605, ERROR_BAD_COMPRESSION_BUFFER: the specified buffer contains ill-formed data | Microsoft Learn |
0x800704DD - 0x90016 |
The result half is Win32 1245, ERROR_NOT_LOGGED_ON, the user has not logged on to the network; the 0x90016 extend half is not published | Microsoft Learn |
Confirm the fix worked
- The finished stick has a
sourcesfolder containing an image file of a plausible size. - The ISO hash matches the value published where you downloaded it.
- A test machine boots from the stick and reaches the disk selection screen.
- The installation copies files past the point where the previous media failed.
- The same stick works on a second machine, which distinguishes bad media from one fussy USB controller.
Questions people ask about this
Is a third-party writing tool acceptable?
For writing an ISO you downloaded from Microsoft, yes – the resulting media contains Microsoft’s files. Verify the ISO hash first, because a writing tool faithfully reproduces a corrupt download.
Do I need a licence to download the ISO?
No. The media is free to obtain and installs any edition it contains. The entitlement is separate, and it is what decides which edition a machine may run.
NTFS or FAT32 for the stick?
NTFS unless the firmware refuses to boot it, because it removes the single-file size limit that trips up the image file. Where FAT32 is required, split the image with DISM rather than looking for a smaller build.
Why does the stick boot but fail later in Setup?
Because a partial write still produces a bootable stick. Setup gets far enough to start and then cannot read a file it needs. That is why the fix is to rebuild the media rather than to retry the installation.
What does the 0xA001A part actually mean?
Nothing published. Microsoft’s extend code tables cover phases 0 to 5 and 0xA is outside them, so there is nothing to decode. The half that does have a meaning is 0x80042405, and it says an object was not found.
