Version 2026.1.11.0 (March 19, 2026)

Version 2026.1.11.0 (March 19, 2026)

avatar

If you are using a client (RDM, PowerShell, etc.), version 2026.1 is required for this DVLS version

IMPROVEMENTS

  • Core - Added "Show Release News" preference to control release notification visibility
  • Core - Free License users now appear disabled with a clear visual indicator to explain login restriction
  • Core - Renamed "System Dashboard" to "Administration Dashboard" for clearer terminology


FIXES

  • Core - Fixed "Allow API Key" setting not persisting after save
  • Core - Fixed "Apply Least Permissions" failing when permissions were preconfigured
  • Core - Fixed "Unable to save" error when users customize dashboards with a default dashboard set
  • Core - Fixed clipboard restrictions not applying in RDP web sessions
  • Core - Fixed contractor users unable to launch RDP sessions via permalink
  • Core - Fixed error when running Last Usage Logs report for regular users
  • Core - Fixed inability to update password generator templates
  • Core - Fixed inability to view inherited OTP codes from root
  • Core - Fixed intermittent dashboard widget reordering not applying
  • Core - Fixed missing activity logs for User Group restore and delete actions
  • Core - Fixed new users not being enabled by default when created
  • Core - Fixed performance issues with Conditional Access Policies enabled
  • Core - Fixed session termination redirecting incorrectly in Active Sessions view
  • Core - Fixed user edits unintentionally removing assigned licenses
  • Core - Fixed vault permissions appearing disabled for non-admin users
  • Core - Resolved SQL collation issues during database and web backups
  • Gateway - Added update notification to System Dashboard
  • Gateway - Fixed advanced domain settings not saving
  • Gateway - Fixed drain mode and scan option issues in Gateway farms
  • Gateway - Fixed inability to terminate sessions using credential injection
  • Gateway - Fixed session launch failures with inherited Gateway Rule Sets
  • PAM - Fixed duplicated parent folders during account import
  • PAM - Fixed incorrect error title on recurrent SSH key scan failure
  • PAM - Fixed missing out-of-sync icon for SSH key accounts
  • PAM - Fixed module admins unable to see external vaults during import
  • PAM - Fixed PAM logs and rotation reports stuck loading on refresh
  • PAM - Fixed SSH checkout approval error with "Yes, unless it's JIT" option
  • PAM - Fixed unauthorized users appearing in checkout approver list
  • PAM - Restored custom fields visibility in connection overview
  • Web - Fixed "Access Denied" error for non-admin session launches with credential injection
  • Web - Fixed PAM checkout redirect causing 404 error
  • Web - Fixed Remote PowerShell entries not launching in web client


** CONSOLE RELEASE NOTES **

IMPROVEMENTS

  • Core - Hid certificate passwords when updating Gateway certificates


FIXES

  • Core - Fixed error when editing Certificate Store locations
  • Gateway - Fixed inability to add certificates when editing Gateway

All Comments (2)

avatar

Hi Devolutions-Team,
I updated from 2025.3.15.0 to 2026.1.11.0.
On first try the Scheduler Service would not start but the install process finished as successful.

.....
Upgrading database for data source 'DVLS' with version 1160
EXECUTED 

Done!
Restoring the custom folders...
Done!
Restoring appsettings.json file...
Done!
Merging configuration on upgraded install...
Done!
Restoring the EncryptionConfig file...
Done!
Updating encryption file...
Done!
Setting rights on appsettings.json file...
Done!
Register Devolutions Server Event Source...
Allowing Anonymous Authentication Feature Delegation...
Starting scheduler service...
Failed to start service
Starting IIS Application Pool...
Done!
Checking for WebApp ID...
Done!
Ensure decryption test is in place...
Done!
Starting the server may take longer than usual if a data migration is required. This means that you may have to wait before the web page is available.

After some search in the Event Viewer I stumbled over missing dependencies to .net Core 10.0.5 and .NET Runtime 10.0.5.

I reverted the installation using a snapshot, installed the .Net components and tried again. -> Works.

What I want to say: Would it be possible to integrate some checks for the required software BEFORE the installation starts?

Best wishes

avatar

Hello,

Thanks for reporting this.
We're investigating this behavior.

Best regards,

Alex Belisle