krle

@abang I've opened an issue for us to track this and see if we can determine why the external PowerShell 7 processes fail to start. I'll update this thread when we have a resolution or any other questions.

@Adam Driscoll

We also observed that environments other than the Integrated environment fail to start after upgrading. We had to set the execute flag on /opt/psuniversal/Hosts/7.5/PowerShellUniversal.Host. Granted we are on a Linux install and not using a container image, so this might not apply.

@Adam Driscoll I can confirm that the execution flag is not set with the built-in PowerShell 7.5 in 2026.3.3.

@akapsch @Adam Driscoll - Any updates on this? We are seeing it on 2026.3.4 now aswell...

Hi,

Trying to setup github integration from one of our PSU containers, but its failing.

Tried with:

• New SSH keys and added it to github as deploy keys

• Ensured that the pod / container have access to github.com on port 22

• Cleared the .git folder in the Repository folder

• Deleted the git settings, and then created a new key and tried to enable git again

The notifications is showing:

SSH key error: The configured SSH key is invalid or not accepted by the remote. Verify your SSH key configuration.

But the key was created in PSU itself, and the public key was copied to github and ensured it have Read/Write

Hi :)

We have a bunch of servers that are running one-way git sync (only pulling).

Sometimes we have to create a new token on these servers, but the console is read-only = we cant do it.

So the "fix" is to change git settings, then create the new token, and then change the git settings back.

It would be great, if we could create new tokens, without having to do this.

Hi :)

If you search in Winget for Devolutions, you will see most of their products - it would be awesome, to have PSU in there as well.

Then we can in a very simple way, just update our products, and even include it in CI/CD pipelines.

@Adam Driscoll - Ohh thats awesome! Will it remove tags from PSU, if they are no longer present in the appsettings.json file - or do we have to perform a cleanup ourself? :)

@Adam Driscoll - Thanks!

I can confirm that the updated license is working, and it looks like a solo issue, and not related to the 2026.2.2 release.

Hi,

After upgrading from 2026.2.1 on 3 different containers to 2026.2.2, the license is now considered invalid.

Re-adding the license fails, even that the license is valid.

Downgrading to 2026.2.1 "fixes" the issue.

Update: Its also an issue on Windows deployments.

Hi :)

Normally we can put an App into maintenance mode, and prevent non-admin users from accessing it during maintenance.

But we have cases where we develop in the dev/test instance of our platform, sync to git, and then the production instance pulls it (one-way sync).

So we have to put the dev version into maintenance mode aswell, which is not ideal, since our Q&A testers cant actually test anything, if we need to debug on a new issue during the maintenance.

So - please allow us to set the maintenance mode for apps, even if one-way sync is enabled - and perhaps add a checkmark, that the maintenance mode will be reverted to its Git stage settings, on the next reboot of the service.

Hi :)

PSU sets a set of default tags on the computer object, that is based on the environment its in.

It would be ideal that we could add custom tags, such as the environment (Prod / Test / Dev), Owner, business service, etc - to align it better with our current CMDB platform.

I believe it should be in the appsettings.json, since this one is not normally synced to Git - so setups with a prod and a test instance of PSU, will not conflict on this.

It should also allow us to write anything we want, so that we arent "stuck" with a key/value set, defined from Devolutions.

Bonus - if the tags could be read on the fly, that would be nice. So adding a new tag, wouldnt have to restart the service, for it to appear - but its a nice to have thing.

The best thing you can do, is then to upvote / watch the issue ive submitted i guess.

Register-DbatoolsConfig dont register in Registry · Issue #8368 · dataplat/dbatools (github.com)

Because it does look like an bug in the module

Looks like you found the solution yourself

But you can run this command, to confirm if its pulling the value from Registry:

Its so awesome to see, that you “support” 3rd party tools on an best effort basis!

There seems to be an issue with the cmdlets, as described in this issue.

Register-DbatoolsConfig dont register in Registry · Issue #8368 · dataplat/dbatools (github.com)

Our PSU have been memory leaking like crazy lately, but after we manually defined the registry keys, it seems to have made huge difference.