Support

When i click the child job button it goes to a white screen. This is still an issue on 2026.2.5 I didnt see any errors in the console.

Running version: 5.5.2 I have git sync enabled, TwoWay, using the external client. This works well to keep the main server up to date, but I find that my apps often restart when there is a git sync, even when the app files are not updated, and the app has the Auto Deploy disabled. The apps restart even if there are no changes to pull from git. Here are some screenshots showing the app details, as well as the restart times related to the git pull. There are a number of other git commands at the same time, so possibly it's one of those, but I just used the git pull as the reference event to correlate times. Dates are in UK format. The git sync is set to every 10 mins, but the restart of the apps doesn't happen that often - sometimes every 25 mins, sometimes there is an hour between restarts. Is there a way to disable the app restart when git runs? Or is there a way to disable the automatic git sync and then I can trigger it manually at a time that the server is unused? [image] [image] [image] [image] [image] [image] [image]

I just wanted to let you know we have issues with PSU and SentinelOne (security platform) on 2026.2.4 Issues started when introducing a continouos schedule workflow (every 10 minutes) After a few hours the PSU service stopped every time, and we also saw Sentinelctl.exe crashes in eventlog just before the timestamp. We tried excluding PSU in SentinelOne but that didn't work. Problem was resolved when completely uninstalling SentinelOne. So I think we can conclude it was indeed related.

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

When viewing the jobs table admin/automation/jobs and clicking on the column selector here [image] it throws an error. [image]

we are pretty new customers and I do not have a ton of experience yet with this product. installed on Windows Server 2025 I was writing some scripts and running tests yesterday fine. I did install August Microsoft monthly updates yesterday afternoon. Now today when i'm in the portal trying to work it keeps locking up and I find the service is stopped. I have tried restarting the service / restarting the server with no improvement. I do see the following log on the server. ...... Faulting application name: Universal.Server.exe, version: 1.0.0.0, time stamp: 0x69970000 Faulting module name: coreclr.dll, version: 9.0.1426.11910, time stamp: 0x699753ca Exception code: 0xc00000fd Fault offset: 0x0000000000047037 Faulting process id: 0xC0C Faulting application start time: 0x1DD35886A7A1D32 Faulting application path: C:\Program Files (x86)\Universal\Universal.Server.exe Faulting module path: C:\Program Files (x86)\Universal\coreclr.dll Report Id: 68b019eb-342e-4a82-82b0-a9cd8a2623eb Faulting package full name: Faulting package-relative application ID: and since I got back into the portal and tried to work with it I have received this log about 15 times on the server.... The PowerShell Universal service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Anyone else seeing this after Microsoft Patching this month? It may not be that but it's the only thing that has changed since it seemed to work fine.

nothing will run in production i am on 2026.2.5.0, there is nothing that i can do to get into the /hangfile site also, it is access denied.

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

I was wondering if anyone had any experience using -Properties param when calling the Write-PSULog command? I cant seem to view the values that i've added to the properties hash. Not getting any errors or anything, just cant figure out how to actually use it. Or are the property hash key / values not available to be used in the -Message param?

Hello! our Powershell Universal Installation is on Version 2026.2.3. Im having a issue with scheduled scripts on Environment Powershell 5.1 After every Script-Run the Script creates a Folder with the current date. Inside theres a transcript file (which i cant provide because of sensetive information). If needed, i can edit it [image] [image] Thanks in advance for your help!

hi, I am trying to use Autocomplete so that users may also enter parts of an entry. e.g. the Autocomplete options are "super duper" and "mega giga" What I am looking for is that a user may enter "sup dup" and still get the option "super duper" displayed. Is this possible at all? KR G.

After the update we have been experiencing very long query times on MSSQL HA Cluster resulting the Service not do Start due to timeouts. For git settings its was something like 25-35 seconds. After restoring the DB from yesterday and restarting the software it workes again now.

I am working on a new development instance of powershell universal that's on a separate domain from my current production version. When I run the Powershell Universal service as local system the site loads and works, but when I switch over to the service account I created on the new domain the service starts but the site never loads. I have given the account local admin, full permissions for all the folders PSU is located in, and I have given it the permissions listed in the " Running as a Service Account " help page. Any advice would be appreciated.

For awareness: Looks like the formatting's broken on the page - New-UDChartJS | Devolutions PowerShell Universal | Product guides & reference [image] EDIT: Also on New-UDChartJSDataset

Hi, PSU version: 2026.2.2 (Windows, licensed, ZIP Installation) What we're trying to do: Enable the "Auto-reload" toggle (Settings -> Files -> Configuration Changes) programmatically from a code-first script (.universal/settings.ps1), so a freshly provisioned local dev instance or automatically newly deployed instances doesn't need a manual click every time. Steps to reproduce: 1. Fresh instance, new/empty database (GitSyncBehavior is not OneWay, so the toggle is available, not greyed out). 2. In .universal/settings.ps1 (a script PSU re-evaluates on every server start), call: Set-PSUSetting -DisableAutoReload:$false -Integrated (also tested without -Integrated) 3. Restart the server (reusing the same database, no DB reset) several times. Expected: Settings -> Files -> Configuration Changes -> "Auto-reload" toggle shows enabled. Actual: Toggle stays off across every restart, no matter how many times the script runs with -DisableAutoReload:$false. Isolating the cause: - Manually flipping the same toggle ON once via the admin console persists correctly across subsequent restarts (as long as the DB isn't recreated) - so DB persistence of the setting itself works fine. - This suggests Set-PSUSetting -Integrated either doesn't write DisableAutoReload to the database at all, or writes it but the running process doesn't pick it up, while the admin console's toggle goes through a different code path that applies it live. - Also tried the DisableCodeFirst alias - same result. Questions: 1. Is this a known bug, or is DisableAutoReload intentionally not settable via -Integrated or code directly? 2. Is there any supported code-first / startup-time way (appsettings.json key, cmdlet, CLI flag) to enable Auto-reload on a fresh instance without a manual admin console click? 3. If not, could this be added as a feature - i.e. Set-PSUSetting actually applying DisableAutoReload live, matching the admin console's behavior? Happy to provide logs or run further tests if useful. [image] Thanks, René

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?

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?

i have to down grade, and i did not find anything in the logs to really identify what was going on, it just hangs on startup never letting me into the admin site. 2026.2.1.0 seems to work better and start up like normal

Dear team, I experienced some behavior which I can't tell if the feature works as expected and it's just not documented or if it's a possible bug. Findings According to the official docs the file system watcher is activated by default and from what I saw in the UI you can either chose to enable / disable " Auto-reload ". With the "auto-reload" and file system watcher enabled, my understanding would be that if I make some changes through an editor on the file itself and save the changes, my changes should applied automatically. To test this, I added a new endpoint to the default endpoints.ps1 file (no custom path) by simply editing and saving the file on the local instance through VSCode. Regardless if the "auto-reload " feature is enabled or disabled while I do see the changes in the history tab: [image] Before config the reload: Get-PSUEndpoint -UseDefaultCredentials | Select-Object -Property Url Url --- /VSCodeExtensionTest/defaultEndpointsFile /VSCodeExtensionTest/customEndpointsFile /FileWatcherTest/defaultEndpointsFile /FileWatcherTest/newEndpointAgain After the config reload: Get-PSUEndpoint -UseDefaultCredentials | Select-Object -Property Url Url --- /VSCodeExtensionTest/defaultEndpointsFile /VSCodeExtensionTest/customEndpointsFile /FileWatcherTest/defaultEndpointsFile /FileWatcherTest/newEndpointAgain /FileWatcherTest/newEndpointPSModuleCheck # <-- manually added endpoint However, the newly added endpoint doesn't show up in the APIs->Endpoints section (neither in the PSU Admin UI nor if I check it through the PSU PowerShell module) until I explicitly reload the endpoints configuration: [image] If I check the endpoints.ps1 in the UIs Settings->Files section though, I see the changes I made previously even before the config reload so assume that it isn't a permission issue or a user error. Setup PSU Version: Version 2026.2.4 Developer License (although issue seems to be identical on our productive server) Windows Server Version 24H2 (OS Build 26100.33158) VSCode Version: 1.134.0 Questions Since I couldn't find further details in the official docs it raises some questions for me: Does this feature work as expected? If so, what exactly does the "auto-reload" feature / explicit "Pending Reload" actually apply / change? Could you point me out where I can find more detailed infos in the official docs? If it's not and a bug: Is it already a known issue and if so is there an ETA for the fix? Please let me know if you need any further infos and thank you in advance for your efforts. Best regards, Viktor

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?

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?

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?

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

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?

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