sodcalculator

10 Tech How-To

Windows Installation Error 0xe0000100: Fixes

Guide 10-32136 · Updated · Step by step

Windows installation error 0xe0000100 stops setup with a generic “Windows cannot install required files” message, and it is almost always caused by a corrupted installation source, a faulty USB drive, or failing RAM. The fix is to recreate your installation media, test your memory, and ensure your hard drive has a healthy connection before retrying the install.

What Error 0xe0000100 Actually Means

Error code 0xe0000100 is a hexadecimal representation of a Windows Setup failure. Unlike errors that pinpoint a specific driver or partition problem, this code is a catch-all for “unexpected error” during the file-copying phase of installation. Microsoft’s own documentation categorizes it under setup errors that occur when Windows cannot read or write the files it needs to complete the installation.

In practical terms, the error appears in one of two places:

  • During the initial “Copying Windows files” stage, often at a specific percentage (like 30% or 60%).
  • During the “Expanding Windows files” stage, after the PC has rebooted from the USB drive.

The error message itself is usually displayed in a dialog box with an “OK” button, and clicking it returns you to the beginning of setup. If you see this error repeatedly at the same point, the cause is likely consistent, not random.

Most Common Causes and How to Diagnose Them

Because the error is generic, you need to work through the likely culprits in order of probability. The three most common causes are:

  1. Corrupted installation media – The ISO file you downloaded was incomplete, or the USB drive has bad sectors. This is the single most frequent cause.
  2. Faulty RAM – A bad memory module can corrupt files as they are copied from the USB drive to the hard drive. This often shows up as the error occurring at a different percentage each time.
  3. Unstable storage connection – A loose SATA cable, a failing SSD, or a hard drive with bad sectors can cause read/write failures during the copy phase.

To diagnose which one you have, try the simplest test first: attempt the installation again. If the error appears at a different point each time, strongly suspect RAM. If it appears at the exact same point, suspect the media or the drive.

Step-by-Step Fixes to Try

Work through these fixes in order. Each one addresses a specific cause, and you should test the installation after each step rather than doing them all at once.

1. Recreate the Installation Media

This is the first thing to try because it is the most common fix and takes about 15 minutes.

  1. Download the official Windows 10 Media Creation Tool from Microsoft’s website. Do not use a third-party ISO download site.
  2. Use a different USB drive if you have one. A drive that is older or has been used for other purposes may have failing sectors.
  3. When the tool asks, select “Create installation media for another PC” and choose the correct language, edition, and architecture (64-bit is standard).
  4. Let the tool finish completely. Do not unplug the USB drive during the process.
  5. If you already have an ISO file, you can also try burning it to a DVD instead of using USB, as this bypasses USB controller issues entirely.

2. Test Your RAM

If recreating the media does not help, test your memory. Windows has a built-in tool, but you need to run it from outside the installation environment.

  1. Boot from your Windows installation USB drive.
  2. On the first screen, press Shift+F10 to open a command prompt.
  3. Type mdsched.exe and press Enter. This launches the Windows Memory Diagnostic tool.
  4. Choose “Restart now and check for problems.” The PC will reboot and run the test, which can take 20-60 minutes.
  5. If the tool reports errors, replace the faulty RAM module. If it reports no errors, move to the next step.

An alternative is to use MemTest86, a free third-party tool that you boot from a separate USB drive. It is more thorough than the Windows tool and is the standard for memory testing.

3. Check the Hard Drive Connection and Health

A loose or failing drive can cause this error. If you are comfortable opening your PC case:

  1. Power down the PC and unplug it.
  2. Reseat the SATA data cable and power cable on both the drive and the motherboard. If you have a spare SATA cable, swap it in.
  3. For NVMe SSDs, remove and reinsert the drive in its M.2 slot, ensuring the retaining screw is tight.
  4. Boot from the installation media again and press Shift+F10 to open a command prompt.
  5. Type diskpart, then list disk. Note the disk number for your target drive.
  6. Type select disk X (replace X with your drive number), then clean, then exit.
  7. Restart the installation. If the error persists, the drive itself may be failing. Try installing to a different drive if you have one.

4. Disable Overclocking and XMP

Memory overclocking profiles (XMP for Intel, DOCP for AMD) can cause instability during installation, even if the system runs fine in Windows. Enter your BIOS/UEFI setup (usually by pressing Del or F2 during boot) and set the memory to its default JEDEC speed (often 2133 MHz or 2400 MHz). Also disable any CPU overclocking. Save and exit, then retry the installation.

5. Try a Different Installation Method

If USB installation keeps failing, consider these alternatives:

  • Install from within Windows – If you have a working Windows installation, mount the ISO file (right-click > Mount) and run setup.exe from inside Windows. This performs an in-place upgrade or repair install.
  • Use a DVD – Burning the ISO to a DVD and booting from that can bypass USB controller or USB drive issues.
  • Use a different USB port – Try a USB 2.0 port instead of USB 3.0, or vice versa. Some older systems have flaky USB 3.0 drivers during setup.

What Not to Do

There are a few common mistakes people make when dealing with this error that waste time or make things worse:

  • Do not skip the RAM test – Many people assume RAM is fine because the system boots normally. RAM errors can be intermittent and only appear under heavy load.
  • Do not keep using the same USB drive – If the drive has failed once, it will likely fail again. Use a brand new or known-good drive.
  • Do not download ISOs from random websites – A corrupted or modified ISO is a common source of this exact error. Always use Microsoft’s official tool.
  • Do not format the drive before testing – If you format the target drive and the error is caused by RAM, you have lost your data for nothing.

Less Common Causes Worth Knowing

If the above fixes do not work, there are a few rarer causes that have been reported in forums and Microsoft support threads:

  • BIOS/UEFI settings – Secure Boot and TPM settings can sometimes interfere with installation. Try disabling Secure Boot temporarily, and if your system uses Intel Rapid Storage Technology (RST), switch the SATA mode from RAID to AHCI in the BIOS.
  • Power supply instability – A failing or undersized power supply can cause random failures during the high-load phases of installation. This is rare but possible.
  • Antivirus software – If you are upgrading from within Windows, third-party antivirus software can interfere with file operations. Uninstall it before attempting the upgrade.
  • Corrupted Windows image on the drive – If you are using a recovery partition or a system image instead of a fresh ISO, the image itself may be corrupted. Recreate it.

Frequently Asked Questions

Will I lose my files if I retry the installation?

If you are doing a clean install, yes, the target partition will be wiped. If you are doing an upgrade (running setup.exe from within Windows), your files and apps are preserved. Back up important data to an external drive before any installation attempt, regardless of the method.

Can this error be caused by a bad hard drive?

Yes. A failing hard drive with bad sectors can cause the installation to fail at the file-copy stage. Run a disk health check using the manufacturer’s tool or a free utility like CrystalDiskInfo (if you can boot into Windows) to check the drive’s SMART status.

Why does the error happen at a different percentage each time?

This is a strong indicator of RAM problems. When memory is faulty, the data corruption occurs at unpredictable points, so the installation fails at different stages. If the error always happens at the exact same percentage, the cause is more likely the media or the target drive.

Is error 0xe0000100 the same as 0x80070017?

No, but they are related. Error 0x80070017 is a CRC (cyclic redundancy check) error, which specifically indicates corrupted data during file copy. Error 0xe0000100 is more generic. However, the causes and fixes for both are largely the same: bad media, bad RAM, or a failing drive.

Can I install Windows 10 from a phone or external SSD?

Yes, but it is not recommended. The installation media must be bootable, and most phones do not present themselves as bootable USB drives. An external SSD works, but it must be formatted correctly (FAT32 for UEFI systems) and the boot files placed correctly. The Media Creation Tool only supports USB drives and DVDs, so manual setup is complex and error-prone.

Should I update my BIOS before retrying?

Updating the BIOS can help if you are experiencing other instability issues, but it is not a first-line fix for this error. Only update the BIOS if you have a specific reason to believe it is the cause, such as a known compatibility issue between your hardware and Windows 10. An incorrect BIOS update can brick your motherboard, so treat this as a last resort.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →