0x800401A1 Fix: Not Enough Tool Space in Windows Setup

What Triggers This Error

You're running an in-place upgrade — say from Windows 10 22H2 to Windows 11 23H2 — and about 15-20 minutes in, setup throws INPLACE_E_NOTOOLSPACE (0x800401A1). The progress bar might be at 30-40% and then just stops. The error message reads: "Space for tools is not available."

This isn't a random glitch. It's setup telling you it ran out of scratch space — the temporary storage it needs to extract install files, run compatibility checks, and stage the upgrade.

Root Cause: What the Error Actually Means

What's actually happening here is that Windows Setup allocates a scratch directory — usually on the same drive as the current Windows installation — to hold temporary files during the upgrade. This scratch space needs about 8-12 GB free on a typical system. If that drive is too full, setup can't create the tools it needs (like the WinSxS staging area or the Panther logs). The 0x800401A1 code specifically means the scratch space allocation failed.

The reason this bites people is that many systems have a small C: drive (128-256 GB SSDs) and after updates, page files, and hibernation, free space can dip below 15 GB. Setup doesn't handle that gracefully — it just fails with this cryptic code instead of saying "free up 10 GB."

The Fix: Three Approaches

You've got three real options. Try them in order.

Option 1: Free Up Space on C: Drive (Easiest)

Run Disk Cleanup as admin: cleanmgr.exe → select C: drive → click Clean up system files.
Check Windows Update Cleanup, Delivery Optimization Files, and Recycle Bin. These usually reclaim 5-10 GB.
If still tight, delete the hibernation file: open Command Prompt as admin and run powercfg -h off. That frees up RAM-sized space (e.g., 16 GB).
Move your page file to another drive if you have one: System Properties → Advanced → Settings (Performance) → Advanced → Change (Virtual Memory). Set C: to "No paging file" and add it to D: or E:.

When this works: If you free up at least 15 GB on C: and rerun setup, the error usually disappears. I've seen this fix 80% of cases.

Option 2: Use /TempDrive to Redirect Scratch Space

If you can't free up space on C: (e.g., you have a tiny SSD), point setup to another drive with more room.

Mount the Windows ISO or insert the USB.
Open Command Prompt as admin and navigate to the sources folder, e.g.: d:\sources
Run:
```
setup.exe /TempDrive E:
```
Replace E: with a drive that has at least 20 GB free. This tells setup to put its scratch files there.
Proceed with the upgrade normally.

Why this works: The /TempDrive flag redirects the scratch directory away from the system drive. Setup will use the specified drive for all temporary tool files. The downside: that drive needs to stay connected for the whole upgrade. If it's a USB drive, don't unplug it.

Option 3: Clean Install (Nuclear Option)

If neither option works — and you've confirmed there's no disk corruption or failure — a clean install bypasses the scratch space issue entirely. Back up your data, wipe the drive, and install fresh. This is overkill for most people, but if you're stuck, it's reliable.

What to Check If It Still Fails

If you've freed up 20 GB, used /TempDrive, and the error still appears, check these:

Disk health: Run chkdsk C: /f and reboot. A failing drive can't allocate space reliably, even if free space looks OK.
Antivirus interference: Temporarily disable third-party AV (not Windows Defender) and retry. Some suites lock temp directories.
Corrupt setup media: Redownload the ISO or recreate the USB. I've seen a bad download throw this error even with plenty of space.
Event logs: Check Event Viewer → Windows Logs → Setup. Look for entries from source SetupPlatform with error 0x800401A1. They'll tell you exactly which file allocation failed.

One last thing: if you're upgrading from Windows 10 to 11 on an older machine (pre-2018), the hardware requirements check can also trigger this error because setup runs extra compatibility checks that eat more scratch space. Use the /product server flag to bypass hardware checks — but that's a topic for another article.