要解决此问题，您需要确保用于配置 Release Management 服务器的凭据在 C:\ProgramData\Microsoft\Crypto\ 上具有修改权限RSA\机器密钥.您可能必须先获得该文件夹中某些文件的所有权，然后才能授予自己修改权限.

To fix the problem, you need to make sure that the credentials used to configure the Release Management server has modify permissions on C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys. You might have to take ownership of some of the files within that folder before you can grant yourself modify permissions.

它对我有用

大家好，快速更新我找到了问题的解决方案.它与 C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys 中的加密文件有关.您需要在 MachineKeys 中专门选择 Release Management 使用的文件，并将完全权限应用于用于 RM 的帐户的该文件.如果您在文件夹级别执行此操作，即使您也告诉它，它也不会递归地应用权限.相信 SYSTEM 帐户对 MachineKeys 中的文件没有权限，因此当您尝试更改文件夹级别的权限时，它无法在此过程中访问这些文件，除非您单独手动覆盖文件的安全设置.希望这对某人有所帮助，因为这让我发疯了！

Hi everyone, A quick update I found the solution to the problem. Its to do with the encryption files in the C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys. You need to specifically select the file that is used by Release Management within MachineKeys and apply full permissions to that file for the account thats being used for RM. If you do this at the folder level it doesn't recursively apply the permissions even if you tell it too. Believe that the SYSTEM account doesn't have permissions to the files in MachineKeys so when you try to change the permissions at the folder level it can't access those files during the process unless you manually override the security settings on the files individually. Hope this helps someone cause this has been driving me nuts!