danielkrauss

Thanks for the explanation and the helpful suggestions!

Adding ::1 and [::1] to NO_PROXY resolved my issue.

I initially still had permission errors when using Invoke-PSUEndpoint -Integrated and other cmdlets with -Integrated. I worked around this in my application by enabling -GrantAppToken and switching to token-based API calls.

My first PSU application is now working as expected.

Thanks again for your support!

Hello everyone,

I'm currently evaluating PowerShell Universal 2026.3.4 for potential use in our environment. I have used PSU in the past and am now considering using it again.

I installed PSU locally on a Windows 11 machine using the MSI installer, running it as a Windows service under `LocalSystem`.

Unfortunately, neither the default PowerShell 7 environment nor an additional custom PowerShell 7 environment works. Even simple test scripts fail to execute. The `Integrated` environment generally works.

The PSU logs show:

[WRN] Job process exited before handshake was received.

PowerShell process 2724 exited before responding

to the job handshake.

The host logs contain:

[ERR] Failed to start server.

Grpc.Core.RpcException:

StatusCode="Unavailable"

Detail="failed to connect to all addresses"

at IJobAgent.SetAgentInformation(...)

at UniversalAutomation.Host.GrpcProtocol.SetClientPort(...)

Additionally, commands such as `Get-PSUApp -Integrated` and `Get-PSUEndpoint -Integrated` fail in the built-in PSU console. Both take quite some time before returning the same gRPC error:

StatusCode="Unavailable"

Detail="failed to connect to all addresses"

So far, I have checked the following:

• Tested the PSU service under both `LocalSystem` and an AD service account, with no difference.

• Verified that the internal gRPC client port is reachable locally over both IPv4 and IPv6.

• Checked proxy/NO_PROXY settings and Kestrel endpoints.

• Reviewed `PSModulePath` without finding any obviously invalid directory paths.

• Found no related application crash events in the Windows Event Log.

Some host logs also contain:

[ERR] Error checking module path

System.ArgumentException:

The path is not of a legal form.

at UniversalHost.AgentService.Initialize(...)

My question: Am I missing a basic configuration step or prerequisite for a standard MSI installation running as a Windows service? Or is this a known issue with PSU 2026.3.4?

Since both external PowerShell 7 environments and internal PSU cmdlets are affected, I suspect the issues might be related to PSU's internal gRPC communication.

Any suggestions would be greatly appreciated.

Thanks in advance!