Custom Environments not working after upgrade to 2026.3.3

Published 2 days ago

After i updated to 2026.3.3 my custom Environments are not working anymore.
Apps are not starting and scripts are not running.

When i changed the Environment to the ones PSU brings in the App Starts:

2026-10-15 07:30:58.777 +02:00 [ERR][Universal.Server.Services.DashboardManager] App process running but did not response after 30 seconds. Terminating process.
2026-10-15 07:32:57.851 +02:00 [ERR][] Failed to get dashboard. Status(StatusCode="Unavailable", Detail="failed to connect to all addresses", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1792042377.845000000","description":"Failed to pick subchannel","file":"..\..\..\src\core\ext\filters\client_channel\client_channel.cc","file_line":3218,"referenced_errors":[{"created":"@1792042377.845000000","description":"failed to connect to all addresses","file":"..\..\..\src\core\lib\transport\error_utils.cc","file_line":165,"grpc_status":14}]}") Grpc.Core.RpcException
2026-10-15 07:32:57.990 +02:00 [ERR][] at ProtoBuf.Grpc.Internal.Reshape.UnaryTaskAsyncImpl[TRequest,TResponse](AsyncUnaryCall`1 call, MetadataContext metadata, CancellationToken cancellationToken) in /_/src/protobuf-net.Grpc/Internal/Reshape.cs:line 554
at PowerShellUniversal.ClientServiceRedirect.IsDebuggerAttachedAsync() in D:\a\powershell-universal\powershell-universal\src\Host\GrpcUniversalClient.cs:line 42
at Nito.AsyncEx.Synchronous.TaskExtensions.WaitAndUnwrapException[TResult](Task`1 task)
at Nito.AsyncEx.AsyncContext.<>c__DisplayClass16_0`1.<Run>b__0(Task`1 t)
at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Nito.AsyncEx.Synchronous.TaskExtensions.WaitAndUnwrapException[TResult](Task`1 task)
at Nito.AsyncEx.AsyncContext.Run[TResult](Func`1 action)
at PowerShellUniversal.ValueTaskExtensions.ToResult[T](ValueTask`1 valueTask) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal\ValueTaskExtensions.cs:line 49
--- End of stack trace from previous location ---
at PowerShellUniversal.ValueTaskExtensions.HandleException[TResult](RpcException e) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal\ValueTaskExtensions.cs:line 130
at PowerShellUniversal.ValueTaskExtensions.ToResult[T](ValueTask`1 valueTask) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal\ValueTaskExtensions.cs:line 53
at UniversalDashboard.Services.UDRunspaceFactory.CreateRunspace() in D:\a\powershell-universal\powershell-universal\src\UniversalDashboard\Services\UDRunspaceFactory.cs:line 499
at UniversalDashboard.Services.UDRunspaceFactory.Create() in D:\a\powershell-universal\powershell-universal\src\UniversalDashboard\Services\UDRunspaceFactory.cs:line 677
at Microsoft.Extensions.ObjectPool.DefaultObjectPool`1.Get()
at UniversalDashboard.Services.UDRunspaceFactory.GetRunspaceReference(Boolean sendSaturationWarning) in D:\a\powershell-universal\powershell-universal\src\UniversalDashboard\Services\UDRunspaceFactory.cs:line 112
at UniversalDashboard.Services.UDRunspaceFactory.GetRunspaceAsync() in D:\a\powershell-universal\powershell-universal\src\UniversalDashboard\Services\UDRunspaceFactory.cs:line 78
at UniversalAutomation.Host.UniversalDashboardService.StartDashboard() in D:\a\powershell-universal\powershell-universal\src\Host\DashboardService.cs:line 213
2026-10-15 07:32:57.990 +02:00 [ERR][] Inner Exception: Grpc.Core.Internal.CoreErrorDetailException
2026-10-15 07:33:24.841 +02:00 [ERR][] Failed to get dashboard. Status(StatusCode="Unavailable", Detail="failed to connect to all addresses", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1792042404.837000000","description":"Failed to pick subchannel","file":"..\..\..\src\core\ext\filters\client_channel\client_channel.cc","file_line":3218,"referenced_errors":[{"created":"@1792042404.837000000","description":"failed to connect to all addresses","file":"..\..\..\src\core\lib\transport\error_utils.cc","file_line":165,"grpc_status":14}]}") Grpc.Core.RpcException
2026-10-15 07:33:24.855 +02:00 [ERR][] at ProtoBuf.Grpc.Internal.Reshape.UnaryTaskAsyncImpl[TRequest,TResponse](AsyncUnaryCall`1 call, MetadataContext metadata, CancellationToken cancellationToken) in /_/src/protobuf-net.Grpc/Internal/Reshape.cs:line 554
at PowerShellUniversal.ClientServiceRedirect.IsDebuggerAttachedAsync() in D:\a\powershell-universal\powershell-universal\src\Host\GrpcUniversalClient.cs:line 42
at Nito.AsyncEx.Synchronous.TaskExtensions.WaitAndUnwrapException[TResult](Task`1 task)
at Nito.AsyncEx.AsyncContext.<>c__DisplayClass16_0`1.<Run>b__0(Task`1 t)
at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Nito.AsyncEx.Synchronous.TaskExtensions.WaitAndUnwrapException[TResult](Task`1 task)
at Nito.AsyncEx.AsyncContext.Run[TResult](Func`1 action)
at PowerShellUniversal.ValueTaskExtensions.ToResult[T](ValueTask`1 valueTask) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal\ValueTaskExtensions.cs:line 49
--- End of stack trace from previous location ---
at PowerShellUniversal.ValueTaskExtensions.HandleException[TResult](RpcException e) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal\ValueTaskExtensions.cs:line 130
at PowerShellUniversal.ValueTaskExtensions.ToResult[T](ValueTask`1 valueTask) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal\ValueTaskExtensions.cs:line 53
at UniversalDashboard.Services.UDRunspaceFactory.CreateRunspace() in D:\a\powershell-universal\powershell-universal\src\UniversalDashboard\Services\UDRunspaceFactory.cs:line 499
at UniversalDashboard.Services.UDRunspaceFactory.Create() in D:\a\powershell-universal\powershell-universal\src\UniversalDashboard\Services\UDRunspaceFactory.cs:line 677
at Microsoft.Extensions.ObjectPool.DefaultObjectPool`1.Get()
at UniversalDashboard.Services.UDRunspaceFactory.GetRunspaceReference(Boolean sendSaturationWarning) in D:\a\powershell-universal\powershell-universal\src\UniversalDashboard\Services\UDRunspaceFactory.cs:line 112
at UniversalDashboard.Services.UDRunspaceFactory.GetRunspaceAsync() in D:\a\powershell-universal\powershell-universal\src\UniversalDashboard\Services\UDRunspaceFactory.cs:line 78
at UniversalAutomation.Host.UniversalDashboardService.StartDashboard() in D:\a\powershell-universal\powershell-universal\src\Host\DashboardService.cs:line 213
2026-10-15 07:33:24.856 +02:00 [ERR][] Inner Exception: Grpc.Core.Internal.CoreErrorDetailException
2026-10-15 07:33:41.240 +02:00 [ERR][Universal.Server.Services.DashboardManager] App process running but did not response after 30 seconds. Terminating process.

I took a snapshot, after the upgrade last time also did not work, and after i reverted back to 2026.2.3 everything is working again

All Comments (3)

Michel Audi

Published a day ago

Hello nikopieper,

Thank you for the log, and for testing with the built-in environments before rolling back.

What the log shows: on some starts, the app's process starts, but when it creates its first runspace, one of its connections back to the PowerShell Universal server fails ("failed to connect to all addresses", in IsDebuggerAttachedAsync). On other starts, the app process did not report back to the server within 30 seconds, and the server terminated it: "App process running but did not response after 30 seconds. Terminating process."

To find what your environments do differently from the built-in ones, we want to run your exact definitions on 2026.3.3 in our lab, with an app and a script. Could you send us:

1. The New-PSUEnvironment lines of your custom environments, from .universal\environments.ps1 in your repository folder (by default %ProgramData%\UniversalAutomation\Repository: https://docs.devolutions.net/powershell-universal/config/repository/). You can copy them from your current 2026.2.3 installation; no upgrade is needed. If that file does not list them, a screenshot of each environment under Manage > Environments > Environments works too.
2. The operating system, and how PowerShell Universal runs: Windows service, IIS, Linux or Docker.
3. Whether the failing apps or scripts use a Run As credential.

One note while you stay on 2026.2.3: if your instance uses a Microsoft SQL Server database, it is affected by security advisory DEVO-2026-0031 (low severity), which applies to 2026.2.5 and earlier and is fixed in 2026.3.0: https://devolutions.net/security/advisories/DEVO-2026-0031/

Best regards,

Michel

Michel Audi

nikopieper

Published 17 hours ago

Hello,

PSUs runs on Windows Server 2022 with the integrated Webserver and the apps are not using a Run As Credential.
I also tried creating a new env in 3.3 but this had the same error.
these are our environments, I changed the Names to numbers, but there are no special characters in the regular name:
$Parameters = @{
Name = '1'
Path = 'C:\Program Files\PowerShell\7\pwsh.exe'
Modules = @('*')
Variables = @('*')
PersistentRunspace = $true
}
New-PSUEnvironment @Parameters
$Parameters = @{
Name = '2'
Variables = @('*')
PersistentRunspace = $true
Type = 'PowerShell7'
}
New-PSUEnvironment @Parameters
$Parameters = @{
Name = 'Integrated'
Path = 'Universal.Server'
Variables = @('*')
Description = 'An environment for running scripts directly in the PowerShell Universal server.'
}
New-PSUEnvironment @Parameters
$Parameters = @{
Name = '3'
Path = 'C:\Program Files\PowerShell\7\pwsh.exe'
Modules = @('activedirectory','hdi.credmod','hdi.psutools')
Variables = @('*')
PersistentRunspace = $true
}
New-PSUEnvironment @Parameters
$Parameters = @{
Name = 'PowerShell 7'
Variables = @('*')
Description = 'The PowerShell 7 version included with PowerShell Universal.'
Type = 'PowerShell7'
}
New-PSUEnvironment @Parameters
$Parameters = @{
Name = 'PowerShell 7.4.12
'
Path = 'C:\Program Files\PowerShell\7\pwsh.exe'
Variables = @('*')
}
New-PSUEnvironment @Parameters
$Parameters = @{
Name = '4'
Path = 'C:\Program Files\PowerShell\7\pwsh.exe'
Modules = @('*')
Variables = @('*')
PersistentRunspace = $true
}
New-PSUEnvironment @Parameters
$Parameters = @{
Name = 'test'
Path = 'C:\Program Files\PowerShell\7\pwsh.exe'
PersistentRunspace = $true
}
New-PSUEnvironment @Parameters
$Parameters = @{
Name = 'Windows PowerShell 5.1'
Variables = @('*')
Description = 'Windows PowerShell 5.1'
Type = 'WindowsPowerShell'
}
New-PSUEnvironment @Parameters

Michel Audi

Published 4 hours ago

Hello nikopieper,

Thank you for your environment definitions.

We made four clean test installations of PowerShell Universal 2026.3.3 in our lab, as a Windows service, with PowerShell 7.4.12 as the Path of your environments that point at pwsh.exe (in two of the four installed at C:\Program Files\PowerShell\7), and ran one app and one script in six of your environments (without your hdi modules).

On the first start, in two of the four installations, some apps failed with one of the errors in your log, which starts with:
Failed to get dashboard. Status(StatusCode="Unavailable", Detail="failed to connect to all addresses" It came from IsDebuggerAttachedAsync, as in your log, and those apps did not recover within the next few minutes. This happened in your environments test and 2 and in the built-in PowerShell 7. After each of our two service restarts, all apps started. Your script failures and your 30-second error did not occur in these runs.

Could you tell us:

1. After your upgrade to 2026.3.3, did you restart PowerShell Universal (its service, if it runs as one) or the server before reverting?

2. If you can repeat the upgrade on a snapshot: first check your apps and scripts and note which environments fail, then save a zip of %ProgramData%\PowerShellUniversal\Logs (with its PowerShellHost and System subfolders). Then restart PowerShell Universal once, check again, and send us both results and the zip before you revert.

Best regards,

Michel

Michel Audi