KB0047 - CPU Health check failed: Access to the registry key 'Global' is denied.

Scope

This article applies to PowerShell Universal  (Kestrel - MSI installer)  version 4.0.0 and above ^[1]  on Windows Server.

Problem

There is a failed CPU health check related to a 'Global' registry key.

(above figure shows the PowerShell Universal health checks log with a failure due to lack of access to the registry key 'Global')

Root cause

The service account or (application identity pool) does not have access to the Performance Monitors. ^[2]

Solution

1. Add the service account or application pool identity to the Performance Monitors ^[3] group.

2. Restart the PowerShell Universal service

3. Confirm from the health check logs that the CPU check is either passing or failing for a different reason

(above figure shows the PowerShell Universal health checks log is no longer failing due to lack of access to the registry key 'Global')

References

^{[1] See https://docs.powershelluniversal.com/changelogs/changelog#4.0.0-6-13-2023}

^{[2] See https://docs.powershelluniversal.com/config/running-as-a-service-account}

^{[3] See https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-security-groups#performance-monitor-users}

• Related Articles

• KB0080 - Failed to Locate Secret in Database or Vault

  Scope Users running PowerShell Universal 5.0.16 attempting to run a script as another user based on a new secret PSCredential variable. Problem When attempting to run the script as the user stored in the PSCredential secret, the application reports ...

• KB0023 - Unauthorized Access screen presented after upgrading to PowerShell Universal 3.7.1

  Affected Versions - PowerShell Universal 3.7.0 - PowerShell Universal 3.7.1 Issue A user attempts to access the admin console on a machine that was upgraded and are presented with a Not Authorized screen. Solution 1. Upgrade to PowerShell Universal ...

• KB0026 - Authentication failure when connecting to BitBucket using a HTTP Access Token

  Applicability This article applies to any version of PowerShell Universal with git sync enabled. Symptom When attempting to synchronize with a BitBucket git repository using a HTTP Access Token generated from the BitBucket repository, it fails to ...

• "[WARN] Call failed. An error occurred while sending the request." message in all jobs

  Version: Any Root Cause When PowerShell Universal starts a new job, it uses the Management API to retrieve job information from the server. It does this over HTTP and will generate a Read-Only app token for the identity of the user that started or ...

• KB0015 - Offline PSU server has slow dashboards

  Disclaimer Please be careful with changing any settings on your server around the Certificate Revocation List. You should only do this if you know what you are doing. Read the related Github articles (linked below) in their entirety. Symptom PSU ...