Can Windows 10 finish an automatic rollback when the system drive lacks sufficient free space?

Direct Answer

No. Windows 10 cannot complete an automatic rollback when the system drive lacks sufficient free space. The servicing stack performs a space check at the moment rollback is triggered—whether user‑initiated or automatic after repeated boot failures—and aborts the operation if the check fails.

How the Space Check Works

• Timing: Windows does not verify free space when the 10‑day rollback window opens. It validates only when rollback actually starts.
• Threshold: There is no fixed byte count. The requirement scales with the size of the previous Windows installation stored in $WINDOWS.~BT\Windows. A practical rule of thumb is roughly 2× that folder size (commonly 8–20 GB).
• Abort behavior: If free space is below the threshold, the rollback is skipped, Event ID 19001 is written to the Setup Operational log, and a "Not enough disk space" notification appears in Action Center.

What Happens If Space Runs Out Mid‑Rollback

If the check passes but free space drops below the required level during the operation (e.g., due to concurrent writes), the rollback halts partway through. The OS is left in a partially reverted state, and the next boot enters the Windows Recovery Environment so the user can free space manually.

Prerequisite: Intact $WINDOWS.~BT Folder

Even with ample free space, rollback is impossible if $WINDOWS.~BT is missing, corrupted, or has been removed by Disk Cleanup, Storage Sense, or third‑party tools. The folder must contain the previous build's payload.

Verification Steps Before the Rollback Window

1. Check free space with the authoritative command:
   

   fsutil volume diskfree C:

2. Confirm a rollback target exists:
   

   dism /online /get-targeteditions

   
   Absence of output means $WINDOWS.~BT is gone.
3. If the folder exists, compare its size to free space:
   

   dir /s C:\$WINDOWS.~BT\Windows

4. Review Setup logs for prior low‑space events:
   

   wevtutil qe Microsoft-Windows-Setup/Operational /f:text /q:"*[System[EventID=19001]]"

One Diagnostic Detail Needed

Which exact Windows 10 build (e.g., 1909, 21H2, 22H2) is installed? The servicing stack was updated across versions, and the precise space‑check logic and error messaging can differ.