WinRAR says not enough space on disk when there is: the causes
When the drive you extract to has room, check where WinRAR actually writes. Dragging files out of the WinRAR window, or opening a file from inside an archive, unpacks it to the Windows temporary folder first, normally on C:. A FAT32 USB drive cannot hold a file of 4 GiB or more. Use Extract To, and check the drive's file system.
By Yash Bavadiya, maker of HatchZip. Updated .
What do "Not enough disk space" and "There is not enough space on the disk" mean?
Both mean that a write failed because a drive was full or would not take the file. It is not always the drive you picked.
WinRAR's own messages for this include "Not enough disk space for" followed by a file name, and "Write error in the file" (both are in WinRAR 7.13). "There is not enough space on the disk." is Windows' text for system error 112, as Microsoft lists it. If the message shows a path, look at which drive it is on: that is the drive to check.
Why does WinRAR fill up C: when I extract to another drive?
Because drag and drop, and opening files from inside an archive, go through the Windows temporary folder. WinRAR's help says so in its list of frequent questions, about the temporary files it leaves behind: "It happens when you use drag and drop to extract files or open archived files with an external viewer."
So when you drag a large folder from the WinRAR window onto drive D:, the drive that holds the temporary folder needs room for it first. To see where that is, type %TEMP% into the Explorer address bar. On a standard Windows setup it is inside your user folder on C:. WinRAR's temporary folders there have names starting with Rar$.
WinRAR does not delete them right away. Its help says that the next time WinRAR starts, it deletes temporary files more than an hour old. After a failed drag, a large Rar$ folder can still be using space on C: until then.
The fix: Extract To
Select the files in WinRAR, click Extract To (or press Alt+E), and choose the destination folder. Or right-click the archive in Explorer and use one of WinRAR's Extract items. WinRAR's help names Extract To, in the window or in the right-click menu, as the way to keep the temporary folder out of it entirely.
The setting: folder for temporary files
WinRAR also has a setting under Options, Settings, Paths, called Folder for temporary files. Its help page describes it as the folder WinRAR uses to create temporary files; the folder must already exist, and typing %temp% sets it back to the Windows default. The help does not list which commands use it, so if C: still fills up after changing it, use Extract To.
Can a FAT32 USB drive cause the error?
Yes. FAT32 cannot hold a single file of 4 GiB or more, however much free space the drive has. Microsoft's file system comparison lists 4 GiB as FAT32's maximum file size, against 264 bytes minus 1 for exFAT and NTFS.
Current WinRAR has messages for this case: WinRAR 7.13 includes "FAT32 file system does not support 4 GB or larger files". Other programs may show a plain space error instead; a July 2026 question on Microsoft's community forum reports exactly that when copying a large file to a USB drive.
To check, right-click the drive in Explorer, choose Properties, and read File system. To fix it, copy anything you need off the drive, then format it as exFAT or NTFS: right-click the drive, choose Format, and pick the file system. Formatting erases the drive.
Could a disk quota or a full C: drive be the cause?
Yes, in two situations.
- A disk quota. On a PC managed by an employer or a school, an administrator can limit how much of an NTFS drive each account may use. Microsoft's documentation of GetDiskFreeSpaceEx notes that with per-user quotas, the free space available to you "may be less than the total number of free bytes on a disk". Ask whoever manages the PC.
- A full C: drive. If C: is nearly full, every drag out of WinRAR can fail, wherever you drop the files, because of the temporary folder above. Use Extract To, or free up space on C:.
What if the archive and the files really don't fit?
Then WinRAR is right: the drive has to hold the archive and every extracted file until the extraction ends. Add up the Size column in WinRAR's file list to see how much it will write; the Packed column is what the archive already takes.
The fixes are to extract to another drive, to free up space, or to extract in place. The guide to extracting without enough disk space covers each one, with a test on a nearly full disk.
Where HatchZip fits, and where it doesn't
HatchZip helps with the last cause only. It extracts RAR 5 and RAR 4 archives, single files and volume sets such as .part1.rar, in place: it frees the archive file by file and deletes each volume once it is empty, so the drive needs room for the extracted files rather than for the files and the archive together. Download HatchZip; RAR support is included in the downloads from this site.
It does not help with:
- The temporary folder. That is how WinRAR hands files to Explorer, not a lack of space on your target drive. Use Extract To.
- FAT32. HatchZip cannot write a file of 4 GiB or more to a FAT32 drive either. Format the drive as exFAT or NTFS.
- A disk quota that leaves your account less space than the files need.
- A solid RAR. It decodes from front to back in one pass, so HatchZip extracts it only while keeping the archive, which needs as much space as WinRAR does.
- RAR archives with encrypted file names or links. HatchZip refuses them before changing anything.
- Keeping the archive. In-place extraction uses it up.
Sources
Checked 2026-10-25.
- WinRAR 7.13 help file (
WinRAR.chm, from the installer on rarlab.com): the frequently asked question "Why WinRAR does not delete its temporary files in the Windows temporary folder?" and the Paths settings topic. An online copy of an older version is at documentation.help; it is not run by the makers of WinRAR. - WinRAR 7.13 program file (
WinRAR.exe): the message texts quoted above. - win-rar.com: Does WinRAR leave artifacts in temp folders, on unpacking files to the temp folder when they are opened in other apps.
- Microsoft: File system functionality comparison, System error codes 0 to 499, GetDiskFreeSpaceEx.