Fix it now
0xC0000102 is STATUS_FILE_CORRUPT_ERROR. Microsoft publishes two causes: the file named in the error message is corrupt, or the disk structure has become corrupt and unreadable. Its documented remedies are to run chkdsk on that volume and to replace the named file from the component store – not to rebuild your installation media first.
diskpart
list volume
exit
chkdsk X: /f
dir <binary-name> /s
- Write down the file named on the error screen. Everything below depends on it, and it is the only specific information the code carries.
- Find the Windows volume with
diskpartandlist volume, then runchkdsk X: /fagainst it. That is Microsoft’s first documented action for this code. - If the named file is a system binary, look for a good copy:
dir <binary-name> /sfrom the root of the Windows volume finds the versions held under WinSxS. - Rename the damaged file to
<name>.sys.old, then copy the newest WinSxS copy intoX:\Windows\System32\Drivers, and restart. - Only if the code appears during setup from removable media does the media itself come into it: verify the ISO with
Get-FileHashagainst the published value and rewrite the stick.
If the drive is already suspect, image it before running chkdsk. A repair pass writes to the disk, and writing to failing media is how a recoverable problem becomes an unrecoverable one.
If the machine starts and the operation that failed now completes, you are done. If the same file fails again, or a different file each time, the next section explains what that pattern means.
Why it happens
0xC0000102 is a structural complaint. Windows read something, checked its internal consistency, and the contents did not add up. Microsoft publishes it as STATUS_FILE_CORRUPT_ERROR and gives two causes: the file displayed in the error message is corrupt, or the disk structure has become corrupt and unreadable. Both of those are about the machine in front of you, which is why the documented remedies are chkdsk and file replacement rather than anything to do with downloads.
That distinction matters because of where people usually meet this code. It appears during installations and repairs more than during ordinary use, and the natural conclusion is that the installation source is bad. Sometimes it is. But setup also reads several gigabytes as fast as the hardware allows, which is precisely the workload that exposes a marginal memory module, a USB stick that writes unreliably, or a drive with a few weak sectors that ordinary use never touches. Rebuilding the media first tests the least likely of those.
0xC0000032 is the second of Microsoft’s two causes stated in its own right: STATUS_DISK_CORRUPT_ERROR, the file system structure on the disk is corrupt and unusable, run the Chkdsk utility on the volume. If you see that alongside, the volume is the problem and no amount of re-downloading helps until the file system is repaired or the disk replaced.
The other two companions belong to the servicing stack rather than to the file system. 0x8007000D is ERROR_INVALID_DATA, the data is invalid – the same complaint in the servicing stack’s vocabulary. 0x80070490 is ERROR_NOT_FOUND, element not found, which during servicing usually means a manifest referenced something the component store no longer holds. Both point at the component store rather than at the disk.
The named file is corrupt
You have this one if The error screen names a specific file, and the same file is named every time.
- Run
chkdsk X: /fagainst the volume holding it. Microsoft’s documented sequence starts here. - Locate a replacement:
dir <binary-name> /sfrom the root of the Windows volume lists the copies WinSxS holds. - Rename the damaged file rather than deleting it, then copy the newest WinSxS copy into place.
- If Windows starts afterwards, run
sfc /scannowanddism /Online /Cleanup-Image /RestoreHealthto catch anything else in the same state.
The disk structure is corrupt
You have this one if 0xC0000032 appears, chkdsk reports problems, or installing to a different disk in the same machine succeeds.
- Image the drive first if the data matters, then run
chkdsk X: /ffrom the recovery environment. - Check drive health with the manufacturer’s utility once the machine starts.
- For a clean installation on a suspect disk, delete and recreate the partitions rather than installing over the existing structure.
- If the drive is failing, recover from the image rather than the original.
Memory is faulty or overclocked
You have this one if The failure happens at a different point each attempt, or a different file is named each time, and the machine is also unstable under other heavy workloads.
- Disable XMP, EXPO or any manual memory timings in firmware and retry at the board default speed.
- Run a full memory test.
mdsched.exeschedules the built-in test at the next restart; server firmware usually has a more thorough one. - If errors appear, test one module at a time, and on a server read the management controller log for correctable error counts.
Microsoft names faulty RAM and a corrupted page file alongside disk errors as causes of image and checksum corruption. A file that is different every attempt is the signature of memory rather than media.
The installation media is unreliable
You have this one if The code appears only during setup from a USB stick, at the same point every time, and the same stick fails on more than one machine.
- Verify the ISO:
Get-FileHash C:\path\to\windows.iso -Algorithm SHA256compared with the published value. Where none is published, download twice and confirm the two files hash identically. - Write to a different stick, ideally from a different batch, and let the writer finish rather than pulling the stick early.
- Plug into a port directly on the machine, avoiding hubs, docks and front-panel headers.
- On a server, mount the ISO through the management controller’s virtual media instead of using a stick at all.
Full reference
Isolating the source from the pattern
| Observation | What it points at |
|---|---|
| The same file is named every time | That file. Replace it from WinSxS after a chkdsk |
| A different file each attempt | Memory, or a marginal connection |
| 0xC0000032 alongside | The volume structure. Repair it before anything else |
| Installation works on another disk in the same machine | The target drive |
| The same USB stick fails on more than one machine | The stick, or the image written to it |
| 0x80070490 during an in-place repair rather than a clean install | The existing component store, not the media |
Replacing a system binary from the component store
This is Microsoft’s own documented procedure and it takes a few minutes. From a command prompt with access to the Windows volume, run dir <binary-name> /s from the root of that volume. WinSxS holds one or more copies of most system binaries, in directories named after the component and version. Pick the most recent, rename the damaged file in Windows\System32\Drivers to .old, and copy the WinSxS version into its place.
chkdsk X: /f
X:
cd \
dir mydriver.sys /s
ren X:\Windows\System32\Drivers\mydriver.sys mydriver.sys.old
copy X:\Windows\WinSxS\<directory>\mydriver.sys X:\Windows\System32\Drivers\
Do not do this with a file you cannot identify. If the name on the screen belongs to a third-party product rather than to Windows, the right copy comes from that vendor’s installer, not from WinSxS.
The four codes, and which layer each belongs to
| Code | Published as | Layer |
|---|---|---|
0xC0000102 |
STATUS_FILE_CORRUPT_ERROR: a corrupted file is preventing the machine starting | The file, or the disk structure under it |
0x8007000D |
ERROR_INVALID_DATA (13): the data is invalid | The servicing stack |
0x80070490 |
ERROR_NOT_FOUND (1168): element not found | The component store |
0xC0000032 |
STATUS_DISK_CORRUPT_ERROR: the file system structure on the disk is corrupt and unusable | The volume |
If the code appears during an in-place repair upgrade rather than a clean installation, the existing component store is the more likely source. Repair it first with dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:E:\sources\install.wim:<index> /LimitAccess, run sfc /scannow, and then retry setup.
A clean installation destroys everything on the target volume. Copy your data off, confirm you can open the copies from another machine, and only then start. If the drive is already suspect, image it before running chkdsk or any repair tool.
Verifying an image when no hash is published
Download it twice, to different filenames, and compare the two hashes with Get-FileHash. If they match, the download is at least internally consistent and was not truncated. It is weaker than comparing against a published value, but it catches the common failure – and it costs nothing but time you would otherwise spend reinstalling.
When a licence is the actual fix
Getting back from this usually costs nothing. Microsoft states that a device with a digital licence can have the same edition of Windows reinstalled without entering a product key, and that it activates automatically once the installation completes and the machine is online. A key is genuinely needed where the device never had an activated copy of Windows, where you are moving to a different edition – Home to Pro, say – or where the motherboard has been replaced so the hardware the licence was recorded against has changed. One thing to settle before you order: Windows 10 reached end of support on 14 October 2025, so a machine being rebuilt now should come back on Windows 11 unless something specific prevents it. Where a Windows 10 machine genuinely has to stay where it is, the consumer Extended Security Updates programme is the supported way to keep it patched, and Microsoft publishes its end date as 12 October 2027. Arco supplies Windows 11 Pro keys with an invoice and a traceable channel. Send us what slmgr /dli reported before the rebuild and we will tell you whether you need one at all.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC0000102 |
STATUS_FILE_CORRUPT_ERROR: a corrupted file is preventing the machine starting. Microsoft’s two documented causes are the file named in the error being corrupt, or the disk structure being corrupt and unreadable | Microsoft Learn |
0x8007000D |
ERROR_INVALID_DATA (13): the data is invalid – the same complaint expressed by the servicing stack | Microsoft Learn |
0x80070490 |
ERROR_NOT_FOUND (1168): element not found. During servicing, a manifest referenced something the component store no longer holds | Microsoft Learn |
0xC0000032 |
STATUS_DISK_CORRUPT_ERROR: the file system structure on the disk is corrupt and unusable. Microsoft’s stated action is to run the Chkdsk utility on the volume | Microsoft Learn |
Confirm the fix worked
chkdsk X: /scanon the affected volume reports no problems.- The installation, repair or start that originally failed now completes without returning the same code.
sfc /scannowon the finished installation reports no integrity violations.- If memory was suspected, a full diagnostic pass completes without errors at the board default speed.
- Drive health shows no reallocated or pending sectors, and no growth in them a week later.
Questions people ask about this
Is a corrupt file always the media’s fault?
No, and assuming so wastes time. Microsoft’s documented causes for this code are the named file being corrupt and the disk structure being corrupt – both on the machine in front of you. Memory faults produce the same result, because setup reads huge amounts of data through RAM and a single flipped bit fails a check.
Why does Microsoft say to run chkdsk when the problem is one file?
Because a corrupt file and a corrupt file system are the two things the code distinguishes between, and chkdsk answers that question. If the volume is sound, replacing the file is quick and safe. If it is not, replacing the file just puts a good copy on bad structure.
How do I check an ISO when no hash is published?
Download it twice, to different filenames, and compare the hashes with Get-FileHash. If they match, the download is at least internally consistent and was not truncated. It is weaker than a published value but it catches the common failure.
Can I reuse my licence after replacing the disk?
Yes. Replacing a drive does not change the machine’s hardware identity for licensing, so a rebuild on a new disk in the same machine reactivates from the existing digital licence. Replacing the motherboard is the change that breaks an OEM licence.
Should I rebuild on Windows 10 to keep things familiar?
Not unless something specific forces it. Windows 10 reached end of support on 14 October 2025, so a rebuild onto it puts you on an operating system that no longer receives updates. If a machine genuinely has to stay on Windows 10, the consumer Extended Security Updates programme runs to 12 October 2027 and is the supported way to keep it patched.
