daniel2

Hi.

We often need to find all scripts containing a specific word or phrase, for example all scripts that do "import-module module-x" or that uses "$secret:whatevercredentials". We haven't found any way to do this in PSU, so our current workaround is to start a NP++ directly on the server and do a "Find in files" on the repository folder. This works well, but being able to do this directly in the PSU interface of course would be much better. Would that be possible to implement?

/Daniel

Yep, sounds good!

The icing on the cake should be information straight on the start page, a list of all unhandled failed jobs.

We use the manual git push mode, so when we click "Commit Changes" in the top menu we get to the page where we choose which files to commit. This page is very good to see all changes, but has one little problem: The right hand side of the page (the part actually showing the changes) doesn't reflect which files are actually marked for commit in the left hand panel. It would be extremely useful if I could mark only the files I actually want to commit and then only those changes would be displayed.

On a side note: The ordering of files in the views (ie the files to change and the view showing the actual changes) doesn't really match, so sometimes it's hard to find which file in the right hand side matches a specific file in the left hand side. I don't know if this is a bug or intended behaviour.

I'm currently on 2026.3.0.

/Daniel

Can you print PSModulePath from a job the runs in the PS 7 environment with and without a credential?

Ok, tried now.

Without credential I get this:

C:\Program Files (x86)\Universal\Modules;C:\Users\svcpsuldaps\Documents\PowerShell\Modules;C:\Program Files\PowerShell\Modules;c:\program files (x86)\universal\hosts\7.5\Modules;C:\ProgramData\UniversalAutomation\Repository\Modules;C:\ProgramData\UniversalAutomation\Repository\Modules;C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules;C:\Program Files\WindowsPowerShell\Modules;

With credential I get this:

C:\Users\svcscoadmgt\Documents\PowerShell\Modules;C:\Program Files\PowerShell\Modules;c:\program files (x86)\universal\hosts\7.5\Modules;C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules;C:\Program Files (x86)\Universal\Modules

@daniel2 Are both PSFramework and TOPdeskPS installed in the WindowsPowerShell modules directory? I ask because we specifically disable Windows PowerShell Compatibility in certain circumstances and this would cause exactly what you are seeing.

about_Windows_PowerShell_Compatibility - PowerShell | Microsoft Learn

We ship a powershell.config.json file that can do this.

about_PowerShell_Config - PowerShell | Microsoft Learn

I'm unaware of any changes in 2026.3.0+ vs 2026.2.5 that changed this behavior but it's worth investigating. Are you primarily seeing this in scripts\jobs?

@Adam Driscoll

Yes, both TOPdeskPS and PSFramework are installed under:

C:\Program Files\WindowsPowerShell\Modules

I am seeing this in Automation scripts/jobs. More specifically, it occurs when a job uses the built-in PowerShell 7 environment together with an alternate AD execution credential.

The same script and modules work when using Windows PowerShell 5.1 or when PowerShell 7 is run without that alternate credential.

I understand that disabling implicit Windows PowerShell Compatibility could prevent modules in Windows PowerShell locations from being discovered. However, both modules load and work directly in PowerShell 7 when I import PSFramework and then TOPdeskPS using their full paths. They do not appear to require a WinPSCompatSession in this case.

Adding the following path to the PSU PowerShell 7 environment resolves module discovery for all affected jobs:

C:\Program Files\WindowsPowerShell\Modules

This worked without an explicit PSModulePath before upgrading from 2026.2.3.0 to 2026.3.0.0. I did not install the intermediate 2026.2.4 or 2026.2.5 releases, so I cannot determine exactly where the behavior changed.

Is excluding C:\Program Files\WindowsPowerShell\Modules from PSModulePath an intentional consequence when implicit WinCompat is disabled, even for modules that can load natively in PowerShell 7? Or should native-compatible modules in that directory still be discoverable?

I can also provide PSModulePath and powershell.config.json output from the affected job if useful.

Hi.

I mentioned this in the 2026.3.0 update thread, but I reckon that is the wrong place, so I'll copy the same text over here instead:

After upgrading an existing PowerShell Universal installation from 2026.2.3.0 to 2026.3.0.0, I encountered what appears to be a regression involving module discovery when combining the built-in PowerShell 7 environment with an alternate execution credential.

Configuration

The affected scripts use:

• Environment: PowerShell 7, configured with -Type "PowerShell7"

• Execution → Credential: an AD service account

• Modules installed under the standard machine-wide Windows module directories

The original environment configuration was:

New-PSUEnvironment -Name "PowerShell 7" -Variables @('*') -Description "The PowerShell 7 version included with PowerShell Universal." -Type "PowerShell7"

Actual behavior

When a script runs in PowerShell 7 using the AD service-account credential, modules installed in the standard module directories cannot be discovered.

For example:

Import-Module TOPdeskPS

fails with:

The specified module 'topdeskps' was not loaded because no valid module file was found in any module directory.

Importing TOPdeskPS by its full path causes its dependency to fail instead:

Import-Module 'C:\Program Files\WindowsPowerShell\Modules\TOPdeskPS\0.1.6\TOPdeskPS.psd1'

Result:

The required module 'PSFramework' is not loaded. Load the module or remove the module from 'RequiredModules' in the file 'C:\Program Files\WindowsPowerShell\Modules\TOPdeskPS\0.1.6\TOPdeskPS.psd1'.

If I import both PSFramework and TOPdeskPS using their complete paths, they load successfully. This confirms that the modules themselves work in this host, but automatic module discovery does not.

The problem only occurs with the combination:

PowerShell 7 + AD service-account execution credential

The same modules load successfully when using Windows PowerShell 5.1 or when running with another execution account.

Workaround

Adding the standard module directories explicitly to the PowerShell 7 environment resolves the issue:

New-PSUEnvironment -Name "PowerShell 7" -Variables @('*') -Description "The PowerShell 7 version included with PowerShell Universal." -Type "PowerShell7" -PSModulePath @(

'C:\Program Files\PowerShell\Modules'

'C:\Program Files\WindowsPowerShell\Modules'

'C:\Windows\System32\WindowsPowerShell\v1.0\Modules'

)

After applying this configuration, I tested several affected scripts using the AD service account and they all completed successfully without any script-specific workarounds.

Expected behavior

The normal machine-wide PowerShell module directories should remain available when a PowerShell 7 job is started using an alternate execution credential, without requiring them to be added explicitly to every environment.

Could you confirm whether this is a known regression in 2026.3.0.0, possibly related to the changes around PowerShell versions or process hosting?

I can provide sanitized PSModulePath output or relevant logs if needed.

Hey there,

I just saw the post and wanted to implement the option right away, and while doing so I noticed a bug in Dark Mode.

@Marco

Yep, I can confirm this one. Just haven't got around reporting it.

I think you missed that you already can... Open your user setttings (by clicking the icon at the top right corner) and check the "Menu" section!

Hi.

I just got an idea... Every day me and my collegues go through failed jobs in PSU and it's always hard to keep track on which jobs have been looked at and not. Would it be possible to add functionality to somehow "check off" jobs? Or maybe write a comment in them, like "Problem was that provider X was temporarily unreachable, will work again at next run" or "Problem was bug in script, corrected at line Y"? This would be immensely useful for me and my team!

/Daniel

Hi,

After upgrading an existing PowerShell Universal installation from 2026.2.3.0 to 2026.3.0.0, I encountered what appears to be a regression involving module discovery when combining the built-in PowerShell 7 environment with an alternate execution credential.

Configuration

The affected scripts use:

• Environment: PowerShell 7, configured with -Type "PowerShell7"

• Execution → Credential: an AD service account

• Modules installed under the standard machine-wide Windows module directories

The original environment configuration was:

New-PSUEnvironment -Name "PowerShell 7" -Variables @('*') -Description "The PowerShell 7 version included with PowerShell Universal." -Type "PowerShell7"

Actual behavior

When a script runs in PowerShell 7 using the AD service-account credential, modules installed in the standard module directories cannot be discovered.

For example:

Import-Module TOPdeskPS

fails with:

The specified module 'topdeskps' was not loaded because no valid module file was found in any module directory.

Importing TOPdeskPS by its full path causes its dependency to fail instead:

Import-Module 'C:\Program Files\WindowsPowerShell\Modules\TOPdeskPS\0.1.6\TOPdeskPS.psd1'

Result:

The required module 'PSFramework' is not loaded. Load the module or remove the module from 'RequiredModules' in the file 'C:\Program Files\WindowsPowerShell\Modules\TOPdeskPS\0.1.6\TOPdeskPS.psd1'.

If I import both PSFramework and TOPdeskPS using their complete paths, they load successfully. This confirms that the modules themselves work in this host, but automatic module discovery does not.

The problem only occurs with the combination:

PowerShell 7 + AD service-account execution credential

The same modules load successfully when using Windows PowerShell 5.1 or when running with another execution account.

Workaround

Adding the standard module directories explicitly to the PowerShell 7 environment resolves the issue:

New-PSUEnvironment -Name "PowerShell 7" -Variables @('*') -Description "The PowerShell 7 version included with PowerShell Universal." -Type "PowerShell7" -PSModulePath @(

'C:\Program Files\PowerShell\Modules'

'C:\Program Files\WindowsPowerShell\Modules'

'C:\Windows\System32\WindowsPowerShell\v1.0\Modules'

)

After applying this configuration, I tested several affected scripts using the AD service account and they all completed successfully without any script-specific workarounds.

Expected behavior

The normal machine-wide PowerShell module directories should remain available when a PowerShell 7 job is started using an alternate execution credential, without requiring them to be added explicitly to every environment.

Could you confirm whether this is a known regression in 2026.3.0.0, possibly related to the changes around PowerShell versions or process hosting?

I can provide sanitized PSModulePath output or relevant logs if needed. Also, tell me if this needs to be filed as a Github issue!

Yep, confirmed working as intended now. Thanks a lot!

* Does this happen consistently with every script you have tested?

Yep. Also tried API endpoints, I see the same behaviour there.

* Which browser are you using?

I've so far tried Chrome, Firefox and Edge.

* After selecting `Edit`, does refreshing the browser page make the code editor editable, or is navigating away and reopening the script required?

No, I realized now that a simple F5 also works.

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

I tried upgrading to this new version from 2026.2.3, unfortunately it doesn't work. The installer says everything works good and the service starts answering, but it stays in the "Please wait, PSU is upgrading" (or whatever it's saying exactly) in the browser forever.

Pasting system log below. After this point it just keeps repeating.

2026-08-13 08:01:27.546 +02:00 [INF] appsettings file exists: C:\ProgramData\PowerShellUniversal\appsettings.json

2026-08-13 08:01:45.291 +02:00 [INF] Using database connection string: Data Source=C:\ProgramData\UniversalAutomation\database.db

2026-08-13 08:02:02.115 +02:00 [INF] PowerShell Universal Version: 2026.2.4

2026-08-13 08:02:02.117 +02:00 [INF] OS Version: Microsoft Windows NT 10.0.26100.0

2026-08-13 08:02:02.117 +02:00 [INF] OS Architecture: x64

2026-08-13 08:02:02.117 +02:00 [INF] Process Architecture: x64

2026-08-13 08:02:02.117 +02:00 [INF] Node Name: ITS-PSU-EXT-01

2026-08-13 08:02:02.177 +02:00 [INF] Starting PowerShell Universal...

2026-08-13 08:02:02.665 +02:00 [WRN] The entity type 'WorkflowDefinition' is configured to use schema 'Elsa', but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.

2026-08-13 08:02:02.665 +02:00 [WRN] The entity type 'WorkflowInstance' is configured to use schema 'Elsa', but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.

2026-08-13 08:02:02.695 +02:00 [INF] Acquiring an exclusive lock for migration application. See https://aka.ms/efcore-docs-migrations-lock for more information if this takes too long.

2026-08-13 08:02:02.789 +02:00 [INF] No migrations were applied. The database is already up to date.

2026-08-13 08:02:02.795 +02:00 [INF] Acquiring an exclusive lock for migration application. See https://aka.ms/efcore-docs-migrations-lock for more information if this takes too long.

2026-08-13 08:02:02.801 +02:00 [INF] No migrations were applied. The database is already up to date.

2026-08-13 08:02:02.802 +02:00 [INF] Running startup complete.

2026-08-13 08:02:02.840 +02:00 [INF] Checking for pending database migrations

2026-08-13 08:02:02.855 +02:00 [INF] Current migration version: 1

2026-08-13 08:02:02.858 +02:00 [INF] Database migration check completed in 17ms

2026-08-13 08:02:02.904 +02:00 [INF] Acquiring an exclusive lock for migration application. See https://aka.ms/efcore-docs-migrations-lock for more information if this takes too long.

2026-08-13 08:02:02.924 +02:00 [INF] No migrations were applied. The database is already up to date.

2026-08-13 08:02:02.959 +02:00 [WRN] The entity type 'SerializedKeyValuePair' is configured to use schema 'Elsa', but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.

2026-08-13 08:02:02.960 +02:00 [WRN] The entity type 'ActivityExecutionRecord' is configured to use schema 'Elsa', but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.

2026-08-13 08:02:02.960 +02:00 [WRN] The entity type 'BookmarkQueueItem' is configured to use schema 'Elsa', but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.

2026-08-13 08:02:02.960 +02:00 [WRN] The entity type 'StoredBookmark' is configured to use schema 'Elsa', but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.

2026-08-13 08:02:02.960 +02:00 [WRN] The entity type 'StoredTrigger' is configured to use schema 'Elsa', but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.

2026-08-13 08:02:02.960 +02:00 [WRN] The entity type 'WorkflowExecutionLogRecord' is configured to use schema 'Elsa', but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.

2026-08-13 08:02:02.960 +02:00 [WRN] The entity type 'WorkflowInboxMessage' is configured to use schema 'Elsa', but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.

2026-08-13 08:02:02.964 +02:00 [INF] Acquiring an exclusive lock for migration application. See https://aka.ms/efcore-docs-migrations-lock for more information if this takes too long.

2026-08-13 08:02:03.004 +02:00 [INF] No migrations were applied. The database is already up to date.

2026-08-13 08:02:08.466 +02:00 [INF] Loading app assets...

2026-08-13 08:02:08.586 +02:00 [INF] Initializing database...

2026-08-13 08:02:09.244 +02:00 [INF] Loading configuration files...

2026-08-13 08:02:09.332 +02:00 [INF] Reading configuration for Vault

2026-08-13 08:02:09.493 +02:00 [INF] Reading configuration for LoggingTarget

2026-08-13 08:02:09.753 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for Tag

2026-08-13 08:02:10.626 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for Variable

2026-08-13 08:02:12.128 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Automation.JobInvokerGrpcService: 4

2026-08-13 08:02:12.168 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Automation.TerminalService: 3

2026-08-13 08:02:12.181 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Authentication.AppTokenClient: 8

2026-08-13 08:02:12.192 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Authentication.IdentityClient: 6

2026-08-13 08:02:12.195 +02:00 [WRN][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] Type cannot be serialized; ignoring: System.IDisposable

2026-08-13 08:02:12.204 +02:00 [WRN][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] Signature not recognized for PowerShellUniversal.IConfigurationSystemWatcher.Pause; method will not be bound

2026-08-13 08:02:12.204 +02:00 [WRN][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] Signature not recognized for PowerShellUniversal.IConfigurationSystemWatcher.CheckSum; method will not be bound

2026-08-13 08:02:12.207 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by Universal.Server.Services.Configuration.ConfigurationSystemWatcher: 4

2026-08-13 08:02:12.212 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.AiAgentService: 5

2026-08-13 08:02:12.217 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.AiToolService: 5

2026-08-13 08:02:12.437 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.ComputerGroupService: 5

2026-08-13 08:02:12.465 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.DeploymentClient: 6

2026-08-13 08:02:12.519 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.EndpointDocumentationService: 5

2026-08-13 08:02:12.526 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.EndpointService: 5

2026-08-13 08:02:12.531 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.EnvironmentConfigService: 5

2026-08-13 08:02:12.536 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.EventHubService: 5

2026-08-13 08:02:12.581 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.FolderService: 5

2026-08-13 08:02:12.586 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.HealthCheckConfigService: 5

2026-08-13 08:02:12.590 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.ModuleConfigService: 5

2026-08-13 08:02:12.594 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.PortalComponentService: 5

2026-08-13 08:02:12.598 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.PortalPageService: 5

2026-08-13 08:02:12.618 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.PublishedFolderCommand: 5

2026-08-13 08:02:12.784 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.RoleService: 5

2026-08-13 08:02:12.789 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.ScheduleService: 6

2026-08-13 08:02:12.795 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.ScriptService: 7

2026-08-13 08:02:12.826 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.SettingsService: 5

2026-08-13 08:02:12.864 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.TagService: 5

2026-08-13 08:02:12.870 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.TerminalService: 5

2026-08-13 08:02:12.923 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.TriggerService: 5

2026-08-13 08:02:12.944 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.UserSessionService: 5

2026-08-13 08:02:12.947 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.UserSessionGrpcService: 1

2026-08-13 08:02:12.952 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Configuration.VariableService: 5

2026-08-13 08:02:12.957 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Secrets.SecretManagerService: 1

2026-08-13 08:02:12.962 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Workflows.WorkflowActivityService: 3

2026-08-13 08:02:12.968 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.Workflows.WorkflowModelService: 5

2026-08-13 08:02:12.985 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.JobDataService: 14

2026-08-13 08:02:13.007 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.BrandingService: 1

2026-08-13 08:02:13.009 +02:00 [WRN][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] Signature not recognized for PowerShellUniversal.Platform.ICacheService.GetCacheDataAsync; method will not be bound

2026-08-13 08:02:13.011 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.CacheService: 4

2026-08-13 08:02:13.013 +02:00 [WRN][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] Signature not recognized for PowerShellUniversal.IPublicClient.SyncComponent; method will not be bound

2026-08-13 08:02:13.082 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.PublicClient: 24

2026-08-13 08:02:13.107 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.ComputerClient: 7

2026-08-13 08:02:13.126 +02:00 [WRN][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] Type cannot be serialized; ignoring: PowerShellUniversal.EndpointProfile

2026-08-13 08:02:13.126 +02:00 [WRN][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] Signature not recognized for PowerShellUniversal.IStatsService.TrackEndpoint; method will not be bound

2026-08-13 08:02:13.127 +02:00 [WRN][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] Type cannot be serialized; ignoring: PowerShellUniversal.EndpointProfile

2026-08-13 08:02:13.127 +02:00 [WRN][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] Signature not recognized for PowerShellUniversal.IStatsService.EndTrackEndpoint; method will not be bound

2026-08-13 08:02:13.143 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.StatsService: 4

2026-08-13 08:02:13.151 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by Universal.Server.Services.DashboardGrpcClient: 7

2026-08-13 08:02:13.155 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by host.TestExecutionService: 1

2026-08-13 08:02:13.345 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by PowerShellUniversal.IGitSettingsService: 12

2026-08-13 08:02:13.351 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by UniversalAutomation.IPublicGitService: 3

2026-08-13 08:02:13.355 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by UniversalAutomation.IPublicApiService: 1

2026-08-13 08:02:13.362 +02:00 [INF][ProtoBuf.Grpc.Server.ServicesExtensions.CodeFirstServiceMethodProvider] RPC services being provided by UniversalAutomation.IPublicGitSyncService: 5

2026-08-13 08:02:13.660 +02:00 [WRN][Microsoft.AspNetCore.Server.Kestrel] HTTP/2 is not enabled for [::]:5000. The endpoint is configured to use HTTP/1.1 and HTTP/2, but TLS is not enabled. HTTP/2 requires TLS application protocol negotiation. Connections to this endpoint will use HTTP/1.1.

2026-08-13 08:02:13.685 +02:00 [INF][Microsoft.Hosting.Lifetime] Now listening on: http://[::]:60370

2026-08-13 08:02:13.685 +02:00 [INF][Microsoft.Hosting.Lifetime] Now listening on: http://[::]:5000

2026-08-13 08:02:13.685 +02:00 [INF][Microsoft.Hosting.Lifetime] Now listening on: https://[::]:443

2026-08-13 08:02:13.685 +02:00 [INF][Microsoft.Hosting.Lifetime] Now listening on: https://[::]:5464

2026-08-13 08:02:13.687 +02:00 [INF][Microsoft.Hosting.Lifetime] Application started. Press Ctrl+C to shut down.

2026-08-13 08:02:13.687 +02:00 [INF][Microsoft.Hosting.Lifetime] Hosting environment: Production

2026-08-13 08:02:13.687 +02:00 [INF][Microsoft.Hosting.Lifetime] Content root path: C:\Program Files (x86)\Universal

2026-08-13 08:02:16.352 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 POST https://api.redacted.se/_blazor/negotiate?negotiateVersion=1 - null 0

2026-08-13 08:02:16.803 +02:00 [INF][Microsoft.AspNetCore.Cors.Infrastructure.CorsService] CORS policy execution failed.

2026-08-13 08:02:16.803 +02:00 [INF][Microsoft.AspNetCore.Cors.Infrastructure.CorsService] Request origin https://api.redacted.se does not have permission to access the resource.

2026-08-13 08:02:17.622 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/_blazor/negotiate'

2026-08-13 08:02:17.628 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint '/_blazor/negotiate'

2026-08-13 08:02:17.630 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 POST https://api.redacted.se/_blazor/negotiate?negotiateVersion=1 - 200 316 application/json 1280.3009ms

2026-08-13 08:02:17.652 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 CONNECT https://api.redacted.se/_blazor?id=Zto663v8uWybYznONktgwA - null null

2026-08-13 08:02:17.657 +02:00 [INF][Microsoft.AspNetCore.Cors.Infrastructure.CorsService] CORS policy execution failed.

2026-08-13 08:02:17.657 +02:00 [INF][Microsoft.AspNetCore.Cors.Infrastructure.CorsService] Request origin https://api.redacted.se does not have permission to access the resource.

2026-08-13 08:02:17.978 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/_blazor'

2026-08-13 08:02:18.249 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 GET https://api.redacted.se/admin/platform/computers - null null

2026-08-13 08:02:18.255 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint '/_blazor'

2026-08-13 08:02:18.279 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 CONNECT https://api.redacted.se/_blazor?id=Zto663v8uWybYznONktgwA - 200 null null 626.3394ms

2026-08-13 08:02:18.281 +02:00 [INF][Microsoft.AspNetCore.Server.Kestrel] Connection id "0HNNP01LV5GSN", Request id "0HNNP01LV5GSN:00000003": the application completed without reading the entire request body.

2026-08-13 08:02:18.290 +02:00 [INF][Microsoft.AspNetCore.Mvc.ChallengeResult] Executing ChallengeResult with authentication schemes ([]).

2026-08-13 08:02:18.303 +02:00 [INF][Microsoft.AspNetCore.Authentication.Cookies.CookieAuthenticationHandler] AuthenticationScheme: Cookies was challenged.

2026-08-13 08:02:18.304 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 GET https://api.redacted.se/admin/platform/computers - 302 0 null 54.4998ms

2026-08-13 08:02:18.312 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - null null

2026-08-13 08:02:18.316 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/Login'

2026-08-13 08:02:18.332 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Route matched with {page = "/Login", action = "", controller = ""}. Executing page /Login

2026-08-13 08:02:18.353 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executing handler method PowerShellUniversal.Login.OnGet - ModelState is "Valid"

2026-08-13 08:02:18.844 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed handler method OnGet, returned result Microsoft.AspNetCore.Mvc.RazorPages.PageResult.

2026-08-13 08:02:18.880 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed page /Login in 543.8422ms

2026-08-13 08:02:18.880 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint '/Login'

2026-08-13 08:02:18.881 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - 200 null text/html; charset=utf-8 568.7061ms

2026-08-13 08:02:18.898 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 POST https://api.redacted.se/_blazor/disconnect - multipart/form-data; boundary=----WebKitFormBoundaryAHvgFDCoCWoCprOB 359

2026-08-13 08:02:18.900 +02:00 [INF][Microsoft.AspNetCore.Cors.Infrastructure.CorsService] CORS policy execution failed.

2026-08-13 08:02:18.900 +02:00 [INF][Microsoft.AspNetCore.Cors.Infrastructure.CorsService] Request origin https://api.redacted.se does not have permission to access the resource.

2026-08-13 08:02:18.903 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint 'Blazor disconnect'

2026-08-13 08:02:18.910 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint 'Blazor disconnect'

2026-08-13 08:02:18.910 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 POST https://api.redacted.se/_blazor/disconnect - 200 0 null 11.9523ms

2026-08-13 08:02:20.770 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - null null

2026-08-13 08:02:20.774 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/Login'

2026-08-13 08:02:20.774 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Route matched with {page = "/Login", action = "", controller = ""}. Executing page /Login

2026-08-13 08:02:20.776 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executing handler method PowerShellUniversal.Login.OnGet - ModelState is "Valid"

2026-08-13 08:02:20.784 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed handler method OnGet, returned result Microsoft.AspNetCore.Mvc.RazorPages.PageResult.

2026-08-13 08:02:20.788 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed page /Login in 13.5915ms

2026-08-13 08:02:20.788 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint '/Login'

2026-08-13 08:02:20.788 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - 200 null text/html; charset=utf-8 18.6287ms

2026-08-13 08:02:21.886 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for Translation

2026-08-13 08:02:21.924 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for Settings

2026-08-13 08:02:22.435 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for PowerShellMiddleware

2026-08-13 08:02:22.444 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for License

2026-08-13 08:02:22.465 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for Role

2026-08-13 08:02:22.624 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for ExecutionEnvironment

2026-08-13 08:02:22.703 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for Folder

2026-08-13 08:02:22.768 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - null null

2026-08-13 08:02:22.773 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/Login'

2026-08-13 08:02:22.773 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Route matched with {page = "/Login", action = "", controller = ""}. Executing page /Login

2026-08-13 08:02:22.775 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executing handler method PowerShellUniversal.Login.OnGet - ModelState is "Valid"

2026-08-13 08:02:22.782 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed handler method OnGet, returned result Microsoft.AspNetCore.Mvc.RazorPages.PageResult.

2026-08-13 08:02:22.783 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed page /Login in 9.2127ms

2026-08-13 08:02:22.783 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint '/Login'

2026-08-13 08:02:22.783 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - 200 null text/html; charset=utf-8 14.5524ms

2026-08-13 08:02:22.786 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for Script

2026-08-13 08:02:24.769 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - null null

2026-08-13 08:02:25.010 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/Login'

2026-08-13 08:02:25.011 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Route matched with {page = "/Login", action = "", controller = ""}. Executing page /Login

2026-08-13 08:02:25.012 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executing handler method PowerShellUniversal.Login.OnGet - ModelState is "Valid"

2026-08-13 08:02:25.018 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed handler method OnGet, returned result Microsoft.AspNetCore.Mvc.RazorPages.PageResult.

2026-08-13 08:02:25.019 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed page /Login in 7.7378ms

2026-08-13 08:02:25.019 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint '/Login'

2026-08-13 08:02:25.019 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - 200 null text/html; charset=utf-8 250.2889ms

2026-08-13 08:02:25.429 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for AuthenticationMethod

2026-08-13 08:02:26.179 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for EndpointDocumentation

2026-08-13 08:02:26.270 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for ComputerGroup

2026-08-13 08:02:26.520 +02:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for Endpoint

2026-08-13 08:02:26.769 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - null null

2026-08-13 08:02:26.773 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/Login'

2026-08-13 08:02:26.773 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Route matched with {page = "/Login", action = "", controller = ""}. Executing page /Login

2026-08-13 08:02:26.774 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executing handler method PowerShellUniversal.Login.OnGet - ModelState is "Valid"

2026-08-13 08:02:26.781 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed handler method OnGet, returned result Microsoft.AspNetCore.Mvc.RazorPages.PageResult.

2026-08-13 08:02:26.782 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed page /Login in 8.4467ms

2026-08-13 08:02:26.782 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint '/Login'

2026-08-13 08:02:26.782 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - 200 null text/html; charset=utf-8 13.2906ms

2026-08-13 08:02:27.320 +02:00 [INF][PowerShellUniversal.Automation.JobProcessManager] Starting job using Process as interactive.

2026-08-13 08:02:28.770 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - null null

2026-08-13 08:02:28.785 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/Login'

2026-08-13 08:02:28.785 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Route matched with {page = "/Login", action = "", controller = ""}. Executing page /Login

2026-08-13 08:02:28.786 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executing handler method PowerShellUniversal.Login.OnGet - ModelState is "Valid"

2026-08-13 08:02:28.794 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed handler method OnGet, returned result Microsoft.AspNetCore.Mvc.RazorPages.PageResult.

2026-08-13 08:02:28.795 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed page /Login in 8.9998ms

2026-08-13 08:02:28.795 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint '/Login'

2026-08-13 08:02:28.795 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - 200 null text/html; charset=utf-8 25.1176ms

2026-08-13 08:02:29.840 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - null null

2026-08-13 08:02:29.844 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/Login'

2026-08-13 08:02:29.844 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Route matched with {page = "/Login", action = "", controller = ""}. Executing page /Login

2026-08-13 08:02:29.845 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executing handler method PowerShellUniversal.Login.OnGet - ModelState is "Valid"

2026-08-13 08:02:29.852 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed handler method OnGet, returned result Microsoft.AspNetCore.Mvc.RazorPages.PageResult.

2026-08-13 08:02:29.853 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed page /Login in 7.8687ms

2026-08-13 08:02:29.853 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint '/Login'

2026-08-13 08:02:29.853 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - 200 null text/html; charset=utf-8 12.751ms

2026-08-13 08:02:30.900 +02:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 GET https://api.redacted.se/login?returnUrl=/admin/platform/computers - null null

2026-08-13 08:02:30.904 +02:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/Login'

2026-08-13 08:02:30.904 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Route matched with {page = "/Login", action = "", controller = ""}. Executing page /Login

2026-08-13 08:02:30.904 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executing handler method PowerShellUniversal.Login.OnGet - ModelState is "Valid"

2026-08-13 08:02:30.910 +02:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed handler method OnGet, returned result Microsoft.AspNetCore.Mvc.RazorPages.PageResult.

Upgraded to new version, everything works fine. These new AI functions seem worth investigating, but the documentations is a bit thin (the docs links in the platform leads me to "Page not found"), is this work in progress? Any pointers to a good starting point?

Just upgraded our PSU environments and it seems you've nailed it this time, now PS5.1 scripts works everywhere!

Nope. I’m sorry, but I still get “The term ‘Import-PowerShellDataFile’ is not recognized as the name of a cmdlet, function, script file, or operable program." in Windows Powershell 5…

Nice workaround! I’ll look at it, should be easily adaptable for my environment.

This upgrade works like a charm in one of my environments, in another I get the same problem I got with 2026.1.1 (mentioned here). It seems unable to load any PS modules whatsoever. Tried restarting the service and also rebooting the entire server, this didn’t help, so now it’s reverted to 2026.1.2 again. Any idea what this might be?

Check the history tab in the portal and select the running job

That doesn’t really solve this unfortunately. My aim is to provide an easy way for our first line to run scripts, input some parameters and see how it goes in real time.

We used the pages in PSU 4 with the “Show Output” checked, I’m trying to find a good way to reproduce this in PSU 5…

Product: PowerShell Universal
Version: 2026.1.2

Hi.

I just discovered the possibility to show a script in the portal, (ie the “portal” tab in the “edit script properties”) this could potentially save me loads of work. The one thing that I can’t get to work though is the “Display Output During Execution”, isn’t it supposed to make the output get printed out in real time to the user? It doesn’t for me, no matter if I check it or not all output is presented once the script is finished. I tried it with scripts doing things like this:

Write-Output “1”

Start-Sleep -Seconds 5

Write-Output “2”

Product: PowerShell Universal
Version: 2026.1.2

Hi.

I have a job that runs very often, polling our e services platform for new tickets. 99% of the times there is nothing to fetch, so the job log is quickly getting filled up by jobs that are not interesting, so finding the jobs that actually did something is hard. Also, even though I’ve set the max history of this script very high, the log posts quickly get rotated out.

Wouldn’t it be nice with a cmdlet that you could put in a script, telling the PSU environment that this particular job shouldn’t be stored in the job log at all? Is this something that would be possible to implement?

Calls to Import-Module just returns the following error:

The term ‘Import-PowerShellDataFile’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Just for the record: Tried 2026.1.2 and this problem mysteriously has vanished, even though I don’t see anything in the changelog about it. So now I got one environment that’s upgraded!

Hi.

I actually succeeded in upgrading one of my environments now and starting the service. However none of my scripts are actually working in this version, it seems unable to load any PS modules. Calls to Import-Module just returns the following error:

The term ‘Import-PowerShellDataFile’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Any idea what this is about?

none of the above issues seen

Wondering what could be the difference. I bet either it’s something to do with running the service using a domain account or authenticating against database using integrated logon.

I’ll file an issue tomorrow and include all my info there!