What else could cause "Access Denied" errors when trying to encrypt folders?

[Jeff7]

Googling suggests that I make sure the files are not set to hidden or read only. These files have no attributes set.
I have full permissions to the entire drive and all files on it, as well as ownership.
I have encrypted files on other drives just fine.
The files on this drive will not encrypt, either with Explorer or cipher.exe.
The files on the drive are not currently open either.

What other things could cause Access Denied errors when trying to encrypt files?

Fixed: The System Volume Information folder didn't have the System:F permission set.


Except now cipher.exe keeps giving me Delayed Write Failed errors on the temp files it creates for large files. 🙁
Dammit all, chkdsk just gave the bad news:
Bad sectors.
Bad sectors on my backup drive. Lovely.
Edit: Good news. Drive is still under warranty.🙂

 

[corkyg]

Any file that is hooked for use by the system will do that.

 

[bsobel]

Originally posted by: Jeff7
Googling suggests that I make sure the files are not set to hidden or read only. These files have no attributes set.
I have full permissions to the entire drive and all files on it, as well as ownership.
I have encrypted files on other drives just fine.
The files on this drive will not encrypt, either with Explorer or cipher.exe.
The files on the drive are not currently open either.

What other things could cause Access Denied errors when trying to encrypt files?

Have to ask, this drive is indeed NTFS and not FAT32 right?

 

[Jeff7]

It is indeed NTFS, and the files on it have been encrypted in the past. I dencryped them when my system started acting funny, in anticipation of the impending format and reinstall. They are confirmed to all be decryped.

I don't know why any files on this drive would need to be in use. It's a backup drive in a removable bay if that makes a difference, which I wouldn't think it should, since it was removable the last time these files were encrypted.
I might also note that it first errors out when just trying to encrypt the folders themselves. But I also tried to encrypt a single file on the drive - no luck.


If that's it though, if Windows thinks that I can't encrypt files on a removable drive, then I guess I'll have to use a 3rd party encryption program.

 

[Mark R]

Anything in the event log?

EFS sometimes puts useful error messages in there when denying access to a file.

 

[Jeff7]

Ah, indeed there is. Not a lot of info though:
Source: EFS
Event ID: 6022
Description: Cannot Create\Open System Volume Information directory.


Clicking the link in the description for details yields, "We're sorry
There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time. You can use the links in the Support area to determine whether any additional information might be available elsewhere. "


Fixed: Keyphrase there is System Volume Information. I added "System" and gave it full permissions for the SVI folder. Boom, it works. Thank you. 🙂