Support

We are using Windows SSO Sign-in setup as explained in Windows SSO | Devolutions PowerShell Universal | Product guides & reference (Kestrel) We have a role for each AD-Group with the Default groups (Administrator, User, ...) defined as nested group. [image] E.g. for the Admins: [image] So far this was working fine as we did not have "deeper" permissions other than the admins and the "All" group. (The "All" group basically has access to a single App accessible via the Portal). The App is assigned using the "Security" tab: [image] Now we tried giving permissions to the "execute" group (bottom of the screenprint) to some of the scripts, in order for users to manually start these scripts from the Portal. But so far it does not work - the scripts are not displayed in the portal, only the app accessible to all users. [image] Assignment of the script to the Role: [image] Also assigning the permissions using the "Permissions" page does not work. [image] I suspect that PSU evaluates the AD groups based on the order defined in permissions.ps1 and only the first group matching is applied and as "Domain Users" is member of the "All" group, everything after the "All" group never is evaluated... Maybe someone can confirm this and if this is the case - how can we achieve the desired result?

Hi, We recently installed PSU, and when testing scheduled scripts they are all failing immediately with the following error: Cannot convert '' to the type 'System.Collections.Generic.ICollection`1[System.String]' required by parameter 'Collection'. Specified method is not supported. This happens with all scripts tested so far, including all execution environments (PS 5.1, 7, and integrated). Any help would be much appreciated. Thanks

Version 2026.2.4 I've got a cached variable, and am able to retrieve data from it. It's persisted in the DB as I'm running an HA pair. However, if I try and pull the cache detail, I get no metadata back. i.e.: AbsoluteExpiration : AbsoluteExpirationRelativeToNow : SlidingExpiration : Persist : False Roles : SecurityContextId : 00000000-0000-0000-0000-000000000000 LastRead : 1/1/0001 12:00:00 AM Created : 1/1/0001 12:00:00 AM Updated : 1/1/0001 12:00:00 AM Id : 0 However, I DO get the cached data in the Value property. This is the same whether I try and get this detail via web console or add detail to a Card in an app. But if I view the cache in the web ui, the information's there: [image] Any ideas?

We have some secret variables that contain tokens or keys for sensitive systems. We assigned a new role to them, but it seems like the only way to access the variables is by assigning the script to this role. If we update the script "Execution Role" to our custom role everything works great. But... we don't want anyone to just be able to assign this new role. For example: Author A can write scripts and access all variables Author B can write scripts, but we don't want them to access Secret1 Author B simply writes a script and assigns it to the "Secret1 Access" role and then just outputs the value to the terminal. Now they know the value. I want to be able to say "Only authors in Secret1 Access role can assign scripts to the Secret1 Access role". How can I do that?

In the API Endpoints i get no log, its just emtpy. Anyone else had this problem before? [image] Version 2026.2.3 running on Windows Server with integrated Webserver

Hi. We have our PSU git connection set up to manual commits, so if we haven't first klicked the "Edit" button we can't edit scripts but just view them. This is perfectly fine, the problem is that when I'm viewing a script and then click "Edit" I still can't edit the script without first leaving the script and then going back to it. Is this intended behaviour or just a glitch? The buttons on the top row changes, so I can for example edit script properties, but not the code itself, it still says "Cannot edit in read-only editor". This is on version 2026.2.3

We have several scripts that are using the -ContentTypeHTML in the Convoke-PSUScript cmdlet which sends the 'true' value. This was working previously. We just upgraded to 2026.2.3 and we're now getting this error: A positional parameter cannot be found that accepts argument 'True'. at , : line 1 I can see that before the update it was also sending that value and was being accepted. So this functionality appears to be broken right now. I tried removing the -ContentTypeHTML switch from a script, and the child script does successfully run but of course the resulting text is not being interpreted as HTML anymore.

Hi, I used to work with VSCode and the PowerShell Universal Extension version 5.6.2. My PSU Server meanwhile is on 2026.2.2 The old extension still somewhat works. I can edit APP code and pages. I can add a page. I can restart the APP. Same for Scripts and Apis. Now I have tried the new extension 2026.2.2 It is all different, but ok. The problem is that I can't edit scripts or API (Endpoints). I can't add app pages. And it happened that a saved some faulty code by accident, that lead to my page being still on disk, but no longer shown. I could neither delete, nor update. All in all the new version is not usable for me so I am back to 5.6.2 which does what I need for now. Anybody else with similar or other experience on that?

Editing an API endpoint using VS Code and PSU Extension doesn't work. When creating an API endpoint I tried supplying a Path: testendpoint.ps1. However in vs code the file it seems to be editing is not the file live on powershell universal. How is this supposed to work?

Ever since our latest upgrade to PowerShell Universal (PSU), anytime we modify something in VSCode, it's taking a noticeably long time to save/write those changes to PSU. We see a spinning wheel at the bottom and it takes anywhere from 5-20 seconds to actually make the change. Is there a configuration we can change to make this instantaneous like it was before or is this just the new way of saving with the upgrade VSCode extension + PSU? [image]

Hi i have created 2 PSU Servers with a SQL Database backend ¨we have put a netscaler in front for LB and what to use the url https://MYURL/api/v1/status to check if the servers is up and running but its always gives me a return code 503 and if i browses the api site i gets this "One or more endpoints are not healthy." i cant see whats wrong im running version 2026.2.4 and its hosted on windows with a IIS

Hello, we are experiencing an issue with the Universal module when running it on a server behind an HTTP proxy. ( https://www.powershellgallery.com/packages/Universal/ ) We use the module to connect to our PowerShell Universal server, for example with Connect-PSUServer. The server has a system-wide proxy configuration that includes exceptions/bypass rules for certain hosts. I observed that the module appears to retrieve the system's proxy settings, but does not honor the configured proxy exceptions. As a result, Connect-PSUServer attempts to connect to our PSU server through the proxy, even though the PSU server is configured as a proxy exception. Is this expected behavior, or is there currently a workaround for this? If the proxy exceptions cannot be honored automatically, it would also be useful to have an option such as -NoProxy on the relevant cmdlets to explicitly bypass the proxy. Universal module version : 2026.2.3 Thank you!

We are running PSU version 2026.1.1 Ran into an issue where on macOS, enabling Dark Mode in any browser caused it to not finish rendering the page? Has anyone else experienced this? [image]

Hi, we are monitoring error logs and are seeing daily error log entries like this. They usually come in pairs as show below. C:\ProgramData\PowerShellUniversal\Logs\System\systemLog20260810.txt:49256:2026-08-10 11:27:56.904 +02:00 [ERR][UniversalDashboard.DashboardHub] Client disconnected: Client hasn't sent a message/ping within the configured ClientTimeoutInterval. C:\ProgramData\PowerShellUniversal\Logs\System\systemLog20260810.txt:49257:2026-08-10 11:27:56.904 +02:00 [ERR][UniversalDashboard.DashboardHub] Not removing connection in case of reconnect. Is it possible to exclude these from the error log? It doesn't seem like an actual error to worry about but just users keeping the tab open in the background. More like informational. Best regards Frederic

I am attempting to upgrade PSU from v5.5.0 to v26.2.3.0, both initial install and upgrade are being done via MSI. The v26 MSI upgrade process itself completes successfully without error. However, post upgrade when first trying to start the PSU service the below error throws and the service will not start. I don't recall ever doing anything unique/special with this PSU installation, but as of now I am unable to get past it. Are there intermediate version(s) I need to step through instead of a straight jump to 26.2.3.0? [FTL] Fatal error starting PowerShell Universal as a Windows service. Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'duplicate column name: DebugPreference'. at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db) at Microsoft.Data.Sqlite.SqliteCommand.PrepareAndEnumerateStatements()+MoveNext() at Microsoft.Data.Sqlite.SqliteCommand.GetStatements()+MoveNext() at Microsoft.Data.Sqlite.SqliteDataReader.NextResult() at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader() at Microsoft.Data.Sqlite.SqliteCommand.ExecuteNonQuery() at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteNonQuery(RelationalCommandParameterObject parameterObject) at Microsoft.EntityFrameworkCore.Migrations.MigrationCommand.ExecuteNonQuery(IRelationalConnection connection, IReadOnlyDictionary2 parameterValues) at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.Execute(IReadOnlyList1 migrationCommands, IRelationalConnection connection, MigrationExecutionState executionState, Boolean beginTransaction, Boolean commitTransaction, Nullable1 isolationLevel) at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.<>c.<ExecuteNonQuery>b__3_1(DbContext _, ValueTuple6 s) at Microsoft.EntityFrameworkCore.Storage.NonRetryingExecutionStrategy.ExecuteTState,TResult at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.ExecuteNonQuery(IReadOnlyList1 migrationCommands, IRelationalConnection connection, MigrationExecutionState executionState, Boolean commitTransaction, Nullable1 isolationLevel) at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.MigrateImplementation(DbContext context, String targetMigration, MigrationExecutionState state, Boolean useTransaction) at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.<>c.<Migrate>b__20_1(DbContext c, ValueTuple4 s) at Microsoft.EntityFrameworkCore.Storage.NonRetryingExecutionStrategy.Execute[TState,TResult](TState state, Func3 operation, Func3 verifySucceeded) at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration) at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.Migrate(DatabaseFacade databaseFacade) at PowerShellUniversal.SQLite.DatabaseFeature.InitializeDatabase(IConfiguration configuration, ILogger logger) in D:\a\powershell-universal\powershell-universal\src\PowerShellUniversal.SQLite\Plugin.cs:line 72 at Universal.Server.Services.SystemPluginService.InitializeDatabase(IConfiguration configuration) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Services\SystemPluginService.cs:line 58 at Universal.Server.Startup.InitializeDatabase(ISystemPluginService systemPluginService) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Startup.cs:line 340 at Universal.Server.Startup.ConfigureServices(IServiceCollection services) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Startup.cs:line 82 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span1 copyOfArgs, BindingFlags invokeAttr) at System.Reflection.MethodBaseInvoker.InvokeWithOneArg(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Microsoft.AspNetCore.Hosting.ConfigureServicesBuilder.InvokeCore(Object instance, IServiceCollection services) at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.UseStartup(Type startupType, HostBuilderContext context, IServiceCollection services, Object instance) at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.<>c__DisplayClass7_0.<UseStartup>b__0(HostBuilderContext context, IServiceCollection services) at Microsoft.Extensions.Hosting.HostBuilder.InitializeServiceProvider() at Microsoft.Extensions.Hosting.HostBuilder.Build() at Universal.Server.PowerShellUniversalWindowsService.StartHostAsync(CancellationToken cancellationToken) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\PowerShellUniversalWindowsService.cs:line 61

Hello! I am evaluating the PSU software and see it support OIDC via secret, but curious if it can also support OIDC via certificate? And if not, might it be on the near term roadmap? much thanks!

Hello! I'm wondering if someone can point me in the right direction. Script consists of: Param([string[]]$Text) foreach($Item in @($Text)) { [pscustomobject]@{ Text = $Item } } If I then use the following (after creating the endpoint): https://PSU.server.address/EndpointName?Text=sometext&Text=somemoretext it seems to be joining both strings into a single string, delimited by a comma: [ { "Text": "sometext,somemoretext" } ] Is this known behaviour, or am I doing something wrong?

After upgrading PowerShell Universal from 2026.1.7.0 to 2026.2.1.0 , the functions used by our endpoints and apps are no longer being recognized. For some context, the environments used by our endpoints and apps are configured to run a script at runspace startup that dot-sources all of our functions. This setup has worked correctly in all previous versions, but it stopped working immediately after the upgrade. Has anyone else experienced the same issue or found a workaround?

Hello, since a few weeks I sporadically encounter the following Error, when I open an App (also includes Portal and Admin page) or call an Endpoint: [image] (I added the inner exception as attachment) After some time (with refreshing and cookie delete) it works again. I already tried the following: Service / Server Restart (solved the issue for a few hours) Changed the Security Environment from "Integrated" to "Powershell 7" Fiddled a bit with my Saml Configuration (enabled, disabled "Load metadata" and recreated the whole Authentication Method Updated from 2026.2.2.0 to 2026.2.3.0 My Saml2 Method looks like this: [image] Do you have a suggestion how I can get this fixed? Thank you.

I have many scheduled jobs that run smoothly without any issues but I am noticing that two of them randomly get dropped from the scheduler. The fix is that I just have to reload the configuration file from the File tab (so no changes to the files). Then rinse and repeat like a week later. I don't catch these until users tell me that they are not getting some of the expected reports. Has anyone encountered this and found a fix? Thanks

Are variable and secrets supposed to be available to tests as we have built tests that require these but are all failing?

Hi, We are currently using PSU for our "internal" IT Automation, which runs great. By now we are thinking to extend this also for our Employees, to handle specific tasks like guided updating the Members of a Distribution Group in Active Directory. I have some concerns regarding security, if we let our employees access the PSU, which runs on our Automation Windows Server. What is the recommended setup here? Thanks for any answer!

I'm running Powershell Universal version 5.6.9. is it possible to upgrade directly to 2026.2.3.0?

Product: PowerShell Universal Version: 5.4.1 IIS Install/SQL Express AppPool ID: LocalSystem Greetings, first post here! I am struggling through the initial learning curve of PSU and trying to use a gMSA to run a script. I’m experienced in the ways of gMSA, so it’s been properly created and the local machine has rights to retrieve the password. The account has both “Log on as a batch job” and “Log on as a service” rights. I’ve registered the gMSA as a PSCredential variable (DOMAIN\user$), and checked the box for “Password not required”. No test can be performed on the credential, as for standard accounts. I assume this is a limitation of gMSAs. I can select the credential in the script properties. All good. But when running the script, I get: Error executing job: Failed to login user (1326). System.ComponentModel.Win32Exception (1326): The user name or password is incorrect. In the Windows Security Log, I see confirmation that IIS is initiating the logon, but finding “Unknown user name or bad password”: Subject: Security ID: SYSTEM Account Name: MYCOMPUTER$ Account Domain: MYDOMAIN Logon ID: 0x3E7 Logon Type: 4 Account For Which Logon Failed: Security ID: NULL SID Account Name: svc_gMSA$ Account Domain: MYDOMAIN Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xC000006D Sub Status: 0xC000006A Process Information: Caller Process ID: 0x1048 Caller Process Name: C:\Windows\System32\inetsrv\w3wp.exe The IIS app pool is running under LocalSystem. From the docs I am understanding that if I were to run it under a custom service account, then I could not use alternate credentials. How does one get this working? Thank you! Just to cover a few additional bases: forwardWindowsAuthToken is set to “true” Using a standard AD account as alternate credentials works fine Tried granting additional User Rights in Local Security Policy: Impersonate a client after authentication, Replace a process level token, Obtain an impersonation token for another user in the same session

Hi, I've had this solution working on a previous version but after migrating to the latest I'm getting an error and I've not been to resolve it and I'm running out of ideas. So any help will be appreciated. I have an API endpoint that I use to refresh a dashboard component. The dashboard is running in the Integrated environment as is the endpoint. New-PSUEndpoint -Url "/refresh" -Description "Refresh" -Method @('GET') -Endpoint { try { Sync-PSUComponent -Integrated -Id "Import" -Broadcast "[Dashboard Refreshed]" } catch { "[Dashboard Refresh Failed]" $_ } } -Environment "Integrated" When I call the API Endpoint I get an error with this exception TargetSite : @{Name=IPublicClient.SyncComponent; DeclaringType=; ReflectedType=; MemberType=8; MetadataToken=100664704; Module=; IsSecurityCritical=True; IsSecuritySafeCritical=False; IsSecurityTransparent=False; MethodHandle=; Attributes=481; CallingConvention=33; ReturnType=; ReturnTypeCustomAttributes=; ReturnParameter=; IsCollectible=True; IsGenericMethod=False; IsGenericMethodDefinition=False; ContainsGenericParameters=False; MethodImplementationFlags=0; IsAbstract=False; IsConstructor=False; IsFinal=True; IsHideBySig=True; IsSpecialName=False; IsStatic=False; IsVirtual=True; IsAssembly=False; IsFamily=False; IsFamilyAndAssembly=False; IsFamilyOrAssembly=False; IsPrivate=True; IsPublic=False; IsConstructedGenericMethod=False; CustomAttributes=System.Object[]} Message : Specified method is not supported. Data : InnerException : HelpLink : Source : ProtoBuf.Grpc.Internal.Proxies HResult : -2146233067 StackTrace : at ProtoBuf.Grpc.Internal.Proxies.ClientBase.IPublicClient_Proxy_51.IPublicClient.SyncComponent(StringRequest, Boolean) at Universal.SyncComponentCommand.ProcessRecord() in D:\a\powershell-universal\powershell-universal\src\Cmdlets\Apps\SyncComponentCommand.cs:line 17 at System.Management.Automation.CommandProcessor.ProcessRecord()