Fixed issues

The management service could stop responding while processing server actions, leaving devices unable to connect until the service was restarted.

Under Citrix License Server licensing, the 14-day grace period did not work correctly.

In a contained AlwaysOn availability group, the license was not detected after a failover, causing repeated license re-validation.

In a classic AlwaysOn availability group on SQL Server 2022 with ODBC Driver 18, the availability group could not be read.

Scout Board showed the wrong Unicon entitlement expiry date (always about a month too far out).

Entitlement telemetry could not be uploaded in License Server mode because the reporting token was issued already expired.

OpenSSL has been updated to 3.0.21 to address a reported vulnerability (S-CERT-2026-1820).

First-time setup could stall because the setup wizard was not closed before the initial update started.

After a brief network interruption, Imprivata sign-in stayed unavailable for several minutes instead of recovering right away.

A rotated (portrait) secondary monitor switched to the wrong resolution after a restart.

Displays that support 5120x1440 could only be set as high as 3440x1440.

Calls in AmazonConnect were being dropped.

A device could become unmanaged if a settings read briefly timed out.

The on-screen CapsLock indicator appeared twice on web pages in the Builtin Browser.

An audio device excluded from automatic default selection was still selected as the default.

Imprivata single sign-on stayed inactive after badging out and back in when reconnecting to a persistent session.

After first contact with the management server, the update agent could hang and stop responding until the device was restarted.

The taskbar disappeared and desktop icons collapsed when a connected monitor reported a special character in its monitor identification data (EDID).

A connected monitor was missing from the display layout, leading to erratic mouse cursor movement.

Time zone data was out of date, so device clocks could show the wrong local time.

Applying a configuration could unexpectedly close a running application.

StickWizz and container exports did not work.

ELIAS could restart when a client disconnected during an import.

ELIAS could hang while solving an image.

A template imported from another container into the same ELIAS could not be opened.

Image solving could select the wrong Zoom or Google Chrome package and fail to resolve the latest Chrome EPM.

During eLux RP6 to eLux 7 migration, device-facing routes returned no content (204) for containers whose name and display name differed.

Importing an archive that contained a .dd file could crash when the target container had no distribution, permanently orphaning the container.

An image could appear as "not solved" in ImageView while the Image Library tile showed it as solved.

Uploading a single UEFI file (.udf/.cab/.cap/.bup) could store the blob under a mismatched name, leaving orphaned blobs and a silent "not found" error on access.