Skip to content

Table of Contents

Release notes

Hyperstream 2026.2 is a quality-focused release that improves day-to-day session stability while also making the platform easier to operate and troubleshoot. Much of the work in this release centers on customer-reported issues, better telemetry and structured logging, and fixes in collaboration, notifications, FileBrowser, authentication, and reconnect behavior.

🚀 New features & enhancements

  • Expanded observability foundations with improved OpenTelemetry support across Hyperstream services.

  • Added structured logging and improved log context to help surface actionable session and service events more clearly.

  • Improved telemetry coverage for session health, connection behavior, and black-screen detection to support faster diagnosis of user-impacting issues.

  • Enhanced session and service health reporting for supporting systems such as notification services.

✨ Improvements to existing features

  • Improved Virtual Classroom reliability in multi-server environments, including more dependable thumbnail updates and cleanup of legacy single-server logic.

  • Improved virtual camera reliability with stronger recovery behavior and bounded retry handling.

  • Improved FileBrowser usability, including better default behavior and clearer download interactions.

  • Improved network indicator behavior and related warning logic to better reflect actual connection conditions.

  • Improved reconnect and session handling to reduce timeout-related disruption and stale-session side effects.

  • Improved notification service behavior by better scoping subscriptions, cleaning up orphaned streams, and stabilizing stream handling.

  • Improved browser and codec compatibility, including updated WebCodec logic and fixes related to fullscreen input and browser-specific clipboard behavior.

🐞 Fixed issues

  • Fixed Virtual Classroom issues where thumbnails could stop updating, remain visible after app close, or behave incorrectly across multi-server deployments.

  • Fixed several messenger and screen-sharing issues, including session-end handling, notification reliability, and service instability.

  • Fixed reconnect scenarios that could trigger long delays or guacd timeout behavior when users rejoined active sessions.

  • Fixed assignment-related issues affecting upload success, submission confirmation, and success notifications.

  • Fixed support request file upload validation failures.

  • Fixed issues in FileBrowser logout handling and download behavior.

  • Fixed copy/paste issues affecting Firefox and macOS-based workflows.

  • Fixed language and introduction wizard issues, including duplicate controls, restart behavior, and missing translations.

  • Fixed fullscreen keyboard input issues in certain on-prem environments.

  • Fixed VM reboot and Linux reboot recovery issues in affected scenarios.

  • Fixed session messaging that could incorrectly show connection problems even after a successful connection.

  • Fixed sharing-session history behavior that could fail in multi-backend environments.

  • Fixed notification-service compatibility and timeout issues that could interrupt server-sent events.

  • Fixed several authentication and certificate-generation script issues related to SSO and supporting services.

🛠️ Technical changes

  • Applied a broad set of security and dependency updates across Hyperstream components, including client, auth, Portia, FileBrowser, Kurento, and supporting libraries.

  • Backported selected upstream Guacamole stability fixes.

  • Improved service resilience through better scheduler, worker-pool, and thread-handling behavior in supporting services.

  • Added or improved metadata in Hyperstream metrics to support better operational analysis.

  • Updated release and artifact publishing workflows for improved delivery consistency.

Customer impact

  • No major configuration changes are expected for most customers.

  • Customers should experience better reliability in collaboration, reconnect, camera, FileBrowser, and session handling scenarios.

  • Support teams should benefit from clearer diagnostic data and improved observability when investigating issues.

Live Demo