The first problem with EFS came when I was hired to review some CAD drawings for a part number inventory. I ran out of time during the day so decided to experiment setting up an Offline Folder so I could review the drawings at home. My win2000ProSP1 machine went through the process of copying the network folder locally. Then before I left, I decided that I had better encrypt the folder on my hard drive in case my laptop was stolen. My machine finished encrypting the folder on my hard drive, then I went home. I got a panicked call about 8:30 the next morning. Apparently no one in the office could read any of the files that I had copied to my hard drive; they were all encrypted on the server!
I rushed into their office, and the very first thing I did before connecting to the network was to copy all the files in my local offline folder to my local Win32 partition to remove the encryption. ALWAYS BACKUP AT THE FIRST POINT OF FAILURE! Good thing, because when I reconnected to the network and tried to remove the encryption from the files, all I got was permission errors. My computer did what looked like some synching, and then even I couldn't read either my own offline folder or the network folder's files!
I recovered from the situation only by deleting my offline folder, and then copying the files on my win32 partition back to the server. If I had not have removed the encryption before I reconnected to the network, then all would have been lost. Some very major Windows bug here, I think!
I lost some files another time when I enabled some UDMA66 service on my UDMA33 computer and my hard drive went flaky. I reinstalled the OS to recover and lost the ability to access all the encrypted files because I didn't back up the unencryption key first.
I have never used EFS again!