Digitally sign your PowerShell scripts used by the Remote Diagnostics Toolkit

PowerShell scripts executed by the ScreenConnect Remote Diagnostics Toolkit should be digitally signed by ConnectWise. 

The Remote Diagnostics Toolkit currently executes PowerShell scripts from the ScreenConnect installation directory (for example, under C:\Windows\SystemTemp\ScreenConnect\...). These scripts are not digitally signed.

On systems where PowerShell execution policies require signed scripts (such as AllSigned), the toolkit cannot execute these scripts, resulting in errors similar to:

The file cannot be loaded because it is not digitally signed.

This prevents the Remote Diagnostics Toolkit from collecting diagnostic information such as processes, event logs, services, updates, and users.

Requiring customers to relax their PowerShell execution policy in order to use built-in ScreenConnect functionality is not an appropriate workaround, particularly in environments that intentionally enforce signed scripts as part of their security baseline.

Disabling the Remote Diagnostics Toolkit also removes useful functionality rather than addressing the underlying issue.