[Issue] Scripts run into "Failed to open the registry" and "The network path was not found" when Remote Registry is not running

Describe the issue
The issue is not clear to the admin running the script to know that the problem is related to Remote Registry not running on the server. This causes various issues with both Health Checker and Exchange Extended Protection Management script plus I am sure all other scripts that use this function.

Expected behavior
Have a better handling of this error that will bubble up the correct information to the client to provide what is wrong.

Additional context
Repro Steps:
Stop the Remote Registry Service. Health Checker only appears to be affected when running remotely. Otherwise, the other script shows a problem when running locally as well.