![powershell microsoft.win32.registrykey openremotebasekey credentials powershell microsoft.win32.registrykey openremotebasekey credentials](https://i1.wp.com/www.jaapbrasser.com/wp-content/uploads/2016/05/InstallModuleDiskCleanup.png)
![powershell microsoft.win32.registrykey openremotebasekey credentials powershell microsoft.win32.registrykey openremotebasekey credentials](https://theitbros.com/wp-content/uploads/2020/06/word-image-38.png)
The sensor message is UnauthorizedAccess when trying a 64-bit PowerShell. Note: Executing the PowerShell script with PowerShell (x86) will not work with this sensor.Open a PowerShell (32 bit) with admin privileges and execute the command (and confirm it):.
#Powershell microsoft.win32.registrykey openremotebasekey credentials windows
Please follow these steps to create a custom Windows registry sensor: If the value is empty or the key does not exist, the sensor will also show an error.The sensor does have a verbose option which you can set to true for debugging output.Both options can either be simple strings or regular expressions and can be used together.-mustnotcontain sets the sensor to an error if the result contains this string.-mustcontain sets the sensor to an error if the result does not contain this string.You have a -mustcontain and a -mustnotcontain option:.
![powershell microsoft.win32.registrykey openremotebasekey credentials powershell microsoft.win32.registrykey openremotebasekey credentials](https://devblogs.microsoft.com/wp-content/uploads/sites/29/2019/02/8463.hsg-5-18-12-5.png)
You can copy the subkey that you want to monitor from the registry editor and provide it in the sensor settings (like in the deprecated registry sensor).It provides the following monitoring options: To make this alternative more comfortable for you we provide a PowerShell script that you can use to monitor the Windows registry. However, it is still possible for you to continue (or even to start) monitoring your Windows registry with an EXE/Script sensor. You cannot add it as of PRTG version 16.x.23 and running registry sensors are removed from PRTG with version 16.x.25. This means you cannot monitor your Windows registry anymore with a sensor that is available out of the box in PRTG. The Windows Registry sensor is one of the sensor types that we remove in context of The PRTG Sensor Cleanup. This article applies to PRTG Network Monitor 16.x.23 or later Monitoring the Windows Registry