Fix ERROR_COMPRESSION_DISABLED 0x00000301 on NTFS Volumes

Cause #1: The volume's compression attribute is simply off

Most of the time, 0x00000301 shows up because you're trying to compress a file or folder on a volume that has compression disabled at the drive level. Windows lets you turn on compression for an entire NTFS drive, but if that toggle is off, any attempt to compress individual items throws this error. I saw this last month at a dental clinic — their server admin had turned off compression on the E: drive to speed up backups, then forgot. When the staff tried to compress a folder of old X-rays, boom.

Here's the fix — open an admin command prompt and run:

fsutil behavior set disablecompression 0

That command re-enables compression globally on all NTFS volumes. If it still fails, check if the volume itself has compression disabled:

fsutil volume compressionstate C:

If it reports anything other than “Enabled,” you'll need to enable compression on that volume. That's not always a direct command, but you can right-click the drive in Explorer, go to Properties > General tab, and check “Compress this drive to save disk space.” Apply that, and it'll enable compression for future operations.

Cause #2: The volume is formatted with a filesystem that doesn't support compression

Here's the trap: compression only works on NTFS. If the volume is FAT32, exFAT, or ReFS, you'll get 0x00000301 no matter what you do. I've had two clients swear their drive was NTFS when it was actually exFAT — one had formatted it that way for Mac compatibility. Real pain.

Check the filesystem with:

fsutil fsinfo volumeinfo C:

Look for the “File System Name” line. If it says anything but NTFS, you've got two options:

• Convert the volume to NTFS (only if you don't need Mac compatibility): convert C: /fs:ntfs
• Or just skip compression entirely and use Windows' built-in file compression alternatives like compact OS or just buy more storage. Honestly, if it's an external drive used with Macs, exFAT is the right call — don't force it.

Cause #3: Corrupted or dirty volume causing compression to fail

Sometimes the volume is NTFS and compression is enabled, but there's file system corruption that stops the operation. This is the sneaky one because the error message doesn't hint at corruption.

A client's accounting machine hit this after a sudden power loss. The drive had bad sectors and the NTFS metadata was a mess. Running chkdsk fixed it:

chkdsk C: /f /r

You'll need to reboot for the system drive. After that, compression worked fine. Also check if the volume is marked dirty with:

fsutil dirty query C:

If it says 'Dirty,' reboot and let chkdsk run.

Quick reference

Start with the first fix — it's the most common and takes ten seconds. If that doesn't cut it, move down the list. And if you're on a ReFS volume, don't bother; compression isn't supported there at all.