PowerShell Universal - 2026.1.1

PowerShell Universal - 2026.1.1

avatar
Adam Driscoll

PowerShell Universal - 2026.1.1

Release Notes

Version 2026.1.1.0

Improvements

  • Added support for logging in with the Devolutions account after the first run wizard

  • Updated the /api/v1/status API to check if API endpoints were not started properly

Fixes

  • Fixed an issue where apps would not start

  • Fixed an issue where the Devolutions login button could be missing on the login page

  • Fixed an issue where the Docker Container would Not Start

  • Fixed an issue where the MSI truncates connection strings

  • Fixed an issue where the MSI upgrade would remove the service account

  • Fixed an issue where the role cleared out for local admin user

  • Fixed an issue where users were unable to Call Invoke-PSUScript in Certain Environments

  • Fixed an issue with New-UDTable and -ShowSelections

Downloads

Adam Driscoll

PowerShell Expert and Software Architect at Devolutions

2

All Comments (25)

avatar
(anonymous user)

Errors don’t leak in the console anymore. Thanks for taking care of it so quickly.

1
avatar
daniel2

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?

avatar
deroppi

Updated my test box from 5.6.11 to 5.6.12 to 5.6.13 to 2026.1.1

Looks ok so far.

But shows that fragment in the app page editor.

Deleting cookies is no help.

But deleting the cache fixes it.

1