Fixing User Profile or Private Key are not Accessible

RECOMMENDED: Click here to fix Windows errors and optimize system performance

The SSL (Secure Sockets Layer) protocol is a standard security technology for establishing an encrypted connection between a server and a client. It is not easy to manipulate and can usually result in error messages if not executed correctly.

A good example is trying to import an SSL certificate file with a private key into the personal certificate store on the local computer.

Fortunately, there are solutions to these problems, and we have listed them below step by step.

Reason for this error:

This behavior occurs when one or more of the following conditions are met:

  • You do not have sufficient permissions to access the DriveLetter folder: \Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys on the computer.
  • There is a third-party registry subkey that prevents IIS from accessing the cryptographic service provider.
  • You are connected to the computer remotely via a Terminal Services session, and the user profile is not stored locally on the server where Terminal Services is enabled.

September 2020 Update:

We now recommend using this tool for your error. Additionally, this tool fixes common computer errors, protects you against file loss, malware, hardware failures and optimizes your PC for maximum performance. You can fix your PC problems quickly and prevent others from happening with this software:

  • Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
  • Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
  • Step 3 : Click “Repair All” to fix all issues.


Resetting permissions in the MachineKeys folder

  • Right-click on the MachineKeys folder
  • On the Security tab, click Advanced.
  • Click View/Edit
  • Select the Reset permissions for all child objects and allow the propagation of inherited permissions check box.

Save the User Profile for the Terminal Services Session Locally

If this appears to be the case, ask your IT administrator to simply move the user profile to the server where terminal services are enabled. You can also use roaming profiles.

RECOMMENDED: Click here to troubleshoot Windows errors and optimize system performance