Fix STATUS_NT_CROSS_ENCRYPTION_REQUIRED (0XC000015D) Error

What’s This Error and Why Does It Happen?

You’re copying or opening a file and Windows throws STATUS_NT_CROSS_ENCRYPTION_REQUIRED (0XC000015D). It means the file you’re trying to access is encrypted with one method (like EFS or BitLocker) but the destination—or your current user account—can’t decrypt it. This often happens when you move files from a BitLocker-protected drive to an unencrypted one, or when your EFS certificate is missing or corrupted. I’ve seen it most with users migrating old Windows accounts to new PCs.

Don’t panic. You’ve got three routes to fix this. Start with the quick one—it works more often than you’d think.

Fix 1: The 30-Second Check – Decrypt the File and Re-encrypt

This is the fastest fix and you can do it without admin rights. The idea is simple: remove encryption from the file, then let Windows re-encrypt it to match the current environment.

1. Right-click the file or folder giving you the error.
2. Select Properties.
3. Click the General tab, then click Advanced.
4. Uncheck Encrypt contents to secure data.
5. Click OK, then Apply. After clicking Apply you should see a dialog asking if you want to apply changes to this folder only or all subfolders and files. Choose Apply changes to this folder only if it’s a single file, or to this folder, subfolders and files if it’s a whole directory.
6. Click OK to close Properties.

Now the file should be decrypted. Try opening or copying it again. If the error’s gone, you’re done. If you still get 0XC000015D, the decryption itself failed because your user account doesn’t have the right certificate. Move to Fix 2.

Fix 2: The 5-Minute Fix – Restore Your EFS Certificate

This error often means your Encrypting File System (EFS) certificate is missing or expired. You need to get it back or create a new one.

Step A: Check if you have a backup certificate

1. Press Windows Key + R, type certmgr.msc, and press Enter.
2. In the left pane, expand Personal and click Certificates.
3. Look for a certificate under Intended Purposes that says Encrypting File System. If you see one, right-click it, choose All Tasks > Export, and follow the wizard to save a .pfx file (include the private key). After exporting, double-click the .pfx file to re-import it into your current user store. You should then be able to access the file.

Step B: If no certificate exists, create a new one

1. Open a Command Prompt as administrator (right-click Start, choose Command Prompt (Admin) or Windows PowerShell (Admin)).
2. Type this command and press Enter:

   cipher /k

   This generates a new EFS certificate for your user account. After running it, you’ll see “New EFS certificate has been created.”
3. Close the command prompt, then try opening the file again. If the error persists, the file was encrypted with a certificate from another user or system. You’ll need Fix 3.

Fix 3: The 15+ Minute Fix – Decrypt Using the Original Certificate or Recovery Key

This is the nuclear option. You need the original encryption key—either the EFS certificate from the old user account or the BitLocker recovery key.

If it’s an EFS-encrypted file from another user:

1. Log into the original user account on the old computer (or find the backup .pfx file).
2. On that machine, open certmgr.msc, export the EFS certificate with the private key as a .pfx file.
3. Copy the .pfx file to your current computer via USB drive or network.
4. Double-click the .pfx file, follow the wizard to import it into Personal store for your user account.
5. Now right-click the problem file, go to Properties > Advanced, uncheck encryption, and click OK. The decryption should succeed this time.

If the file is on a BitLocker-encrypted drive:

1. Open Control Panel > System and Security > BitLocker Drive Encryption.
2. Click Suspend protection next to the drive (this decrypts temporarily without needing the recovery key). After suspending, you’ll see a warning—ignore it for now.
3. Try copying or opening the file again.
4. When done, resume protection by clicking Resume protection in the same place.

If you don’t have the original certificate or the recovery key, you’re stuck. The file is effectively locked forever—there’s no backdoor on EFS or BitLocker. Your only option is to restore from a backup made before the encryption.

Pro tip: Always back up your EFS certificate and BitLocker recovery key when you first set up encryption. Write the key down or save it to a USB stick. It’s a pain to recover without it.

When to Call It Quits and Reinstall

If you’ve tried all three fixes and still see 0XC000015D, the encryption chain is completely broken. You might have a corrupt user profile or a system file issue. Back up your data (skip any encrypted files you can’t open), then do a clean install of Windows. I know that sounds drastic, but it’s faster than hunting for ghost certificates.