EFS Error 0X0000177E: Partition Doesn't Support Encryption
This pops up when you try to encrypt files on a drive that doesn't support EFS. Usually a FAT32 partition, a network drive, or a RAW volume. Quick fix: check the file system first.
The 30-Second Fix: Check the File System
This error is almost always caused by the drive being formatted with FAT32 or exFAT instead of NTFS. The Encrypting File System (EFS) only works on NTFS volumes. I've seen this a dozen times — small business owners plugging in a new external drive that's FAT32 out of the box, then trying to encrypt a client contract. Doesn't work.
Open File Explorer, right-click the drive that's giving the error, and select Properties. Look at the File system line. If it says FAT32 or exFAT, that's your problem. If it says NTFS, move to the next section.
If it's FAT32, you have two choices: reformat the drive to NTFS (wipes all data) or convert it without data loss. More on that in a second.
The 5-Minute Fix: Convert FAT32 to NTFS (No Data Loss)
Don't want to lose your files? You can convert the partition without reformatting. Windows has a built-in command that takes under a minute. I used this last week on a client's backup drive that had years of QuickBooks files — zero issues.
Step 1: Open Command Prompt as Administrator. Hit Win+X, select Terminal (Admin) or Command Prompt (Admin).
Step 2: Type this command and press Enter:
convert E: /fs:ntfsReplace E: with your actual drive letter. You'll get a prompt asking for a volume label — just type it in (the one you saw in Properties). The conversion takes maybe 30 seconds for a 500GB drive. No data wiped, no drama.
Once it finishes, retry the encryption. Should work now. If it still gives the error, you've got something else going on.
Quick tip: If the drive is your system partition (C:), you'll need to reboot and the conversion will happen before Windows loads. Don't interrupt it.
The 15+ Minute Fix: What to Check When NTFS Doesn't Work
If the drive is already NTFS and you're still getting 0X0000177E, you've got a different problem. Here's what I've seen cause this:
1. The Partition Is RAW or Corrupted
Sometimes the file system gets flagged as RAW — Windows can't read it properly. Open Disk Management (right-click Start > Disk Management). If your partition shows as RAW, run chkdsk to fix it.
Open an admin command prompt and run:
chkdsk E: /f /rThat scans for bad sectors and fixes file system errors. Takes a while on big drives. I had a client last month whose external drive got corrupted after a power surge — chkdsk brought it back, and EFS worked again.
2. The Drive Is a Network Share or Removable Media
EFS does NOT work on network drives by default. If you're trying to encrypt files on a mapped network drive, you'll get this error every time. The fix: copy the file locally, encrypt it, then move it back. Or set up BitLocker for network storage instead — different technology, same result.
USB drives also sometimes fail with EFS if Windows sees them as removable. I keep a USB stick specifically for testing — had one that wouldn't encrypt until I reformatted it with NTFS in Disk Management instead of the quick format option.
3. Group Policy Blocks EFS on Removable Drives
This one's rare but I've seen it in corporate environments. If you're on a business network, your admin might have disabled EFS for removable drives via Group Policy. Run gpedit.msc (Pro/Enterprise only) and check under Computer Configuration > Administrative Templates > System > Removable Storage Access. Look for a policy that says "Removable Disks: Deny write access" or specifically about EFS. If it's enabled, talk to your IT person.
For home users on Windows 10/11 Home, this policy doesn't exist, so skip it.
4. The EFS Service Isn't Running
Press Win+R, type services.msc, find Encrypting File System (EFS). It should be set to Manual and started. If it's disabled, double-click it, change the startup type to Manual, then click Start. Had one client whose antivirus had killed this service — a quick re-enable fixed the whole thing.
When to Give Up on EFS
Honestly? EFS is finicky. It's tied to your user account and if you reinstall Windows without backing up the certificate, your files become unrecoverable. BitLocker is more reliable for whole drives. If this error keeps popping up on the same drive even after converting to NTFS, consider switching to BitLocker or a third-party encryption tool like VeraCrypt.
Had a client lose three years of financial records because they reimaged their laptop and never exported their EFS certificate. Don't be that guy.
Was this solution helpful?