Known Issues and Limitations of Windows-Based Shared Hosted Desktops and Virtual App Delivery
-
Last Updated Date: 22-May-2026
-
Release: HyWorks v4.0
Note
The known issues list is updated with every release. Listed below is the latest summary of issues.
| Bug ID | Description |
|---|---|
| 68848 | RTT data may stop reaching ARS if session recording is enabled on the same desktop and the session recording is paused due to the 'user idle timeout' configuration. |
| 68020/ 64614 | In some cases, in environments with Virtual Smart Card Certificate-based Single Sign-on, desktop session reconnection may fail due to a certificate import error or because the slot is in use by another user. |
| 67968 | In some cases, desktop agents may not log sufficient details to identify the root cause when they fail to process certificates (e.g., import failures). |
| 67040 | In some cases, the end-point system may not enter Power Saver mode even when the configured battery threshold is reached. It may also cause the battery percentage to get stuck and continue displaying the last updated information. |
| 65716 | In some cases, the network monitoring logs may show the source IP address as 0.0.0.0 or the actual source IP. No functional impact has been identified from this issue, but it may cause inconsistencies in the source IP information in network monitoring logs. |
| 65342 | With Accops Virtual Camera, audio and video synchronization issues are observed in Windows 11 desktop sessions. |
| 65286 | [Built-in USB Redirector] A delay may be observed when reconnecting USB devices in desktop sessions after frequent connect/disconnect cycles with the Built-in USB Redirector. |
| 65085 | With the connection profile configured to log out on idle, the agent still disconnects the session before logging it out, even though it is configured to log out the session directly when the idle timeout threshold is reached. |
| 64671 | Desktop session sign-out may take longer than expected when Virtual Smart Card Certificate-based Single Sign-on is enabled on the desktop. |
| 64584/ 35530 |
In some cases, when shadowing a Remote App session via RDP, the session may open on a black screen, and the application UI may not be visible during the shadow session. |
| 64363 | Other running apps in the desktop session temporarily disappear when hovering over their name in the App maximizer. App maximizer is a feature that brings local running apps to the front of the desktop session. |
| 64014 | With Virtual Smart Card Certificate-based Single Sign-on, the login page UI loader intermittently flickers on the Cancel button. |
| 63822 | With Virtual Smart Card Certificate-based Single Sign-on, after canceling the login, the loader may take 20-40 seconds to show the Username/Password prompt. |
| 63820 | With Virtual Smart Card Certificate-based Single Sign-on, user authentication may take longer than password-based logon. |
| 63560 | With Virtual Smart Card Certificate-based Single Sign-on, desktop connections will work only via HyLite or Linux endpoints, with remote desktop security set to RDP only. Any other configurations may cause connection failures. The configurations can be done from the connection profiles or from the Windows Group Policy. |
| 63520 | Enabling Virtual Smart Card Certificate-based Single Sign-on using agent registries requires the desktop to be shut down; upon service restart, the VM is also automatically shut down. |
| 63513 | With Virtual Smart Card Certificate-based Single Sign-on, in some cases, imported certificates may not be deleted; for example, clicking the cancel button multiple times. |
| 62780 | If the camera is plugged into an already running desktop session, then it is not detected. The user must have a camera connected before initiating the session. |
| 60931 | In rare cases, HyPrep initialization for a managed SHD pool may not complete on the first attempt. Retrying the operation typically succeeds. |
| 59191 | Volume gets reset to 100% on logging off and re-logging into the desktop session. The volume settings in the remote session are not remembered. |
| 59188 | With RTT enabled on the desktop side, during RTT data fetching with the client, the desktop session may cause input delays. This issue has already been fixed in the Windows workspace client and will be released in the upcoming Linux Workspace client. |
| **** | Adding Microsoft Edge-like applications in the User Resource Management Rule may not work correctly with errors in logs for process IDs. The issue may be observed in applications like MS Edge that spontaneously open and close parent and child processes, causing the agent to lose track of them. |
| 58794 | In some cases, on Linux endpoints, turning off the monitor may cause the running desktop session to disconnect. However, the issue is not related to the desktop side. |
| 58793 | [Virtual Camera] Camera is in use in the desktop session, and then the network goes down. On reconnection, the user may have to click multiple times to re-enable the camera. |
| 58791 | In some cases, the user may need to re-plug the audio device after reconnecting the Linux Workspace client. The audio device may not work post-reconnection. |
| 56822/ 56332/ 40424 |
MSIX App attachment did not work on Windows 11 24H2 [Working on Windows 11 22H2]. MSIX app attachment does not work on server systems such as Windows Server 2019, 2022, and 2025. |
| 56653/ 56394 |
Session recording does not work on Windows-based desktops when a user logs in with UPN. Errors are observed when accessing the Raw recording directory. |
| 55632/ 55481 |
The Shortcut Clipboard does not support transferring content of 1 GB or more. |
| 55631 | No progress indicator or feedback is shown while pasting large amounts of clipboard content into the desktop session. |
| 55425 | Bulk Provisioning Package fails Azure AD join on Windows 11 Enterprise multi-session 24H2 but works fine on Windows 10/11 Enterprise multi-session 22H2. |
| 55401 | Advanced drive redirection is not working on a few setups because the OpenSSH server module is not being installed via DVM tools. It has internet dependency. |
| 54903 | In some cases, even though the application is being tracked for file transfers via the Appstract utility, it fails with an invalid file type error when saving a file. Appstract is a use-case-specific module that forces file save options for configured applications. Appstract is very use-case specific. |
| 54754 | Unlike Windows native clipboard, which supports both file transfers and content copy/paste, Accops smart clipboard and smart file transfer must be enabled separately from the connection profile. |
| 54205 | [Virtual Camera] The camera may not work when the virtual desktop has multiple NIC cards, and the server-side module uses an inactive network to send the stream. |
| 53168 | In session recording reports, the "Pool Name" may not be available for application sessions. |
| 54112 | In some cases, the session recording chunk upload from the raw_data folder to the upload path for intermediate files fails after a user logs out. This occurs when the file size exceeds the supported limit. |
| 53917 | In some unknown cases, file transfer via Appstract does not work. Appstract is a use-case-specific module that forces file save options for configured applications. Appstract is very use-case specific. |
| 52041 | The DVM tool installer takes more than 20 minutes to complete the installation when Advanced drive redirection is enabled. The installer requires an internet connection for this module, and the internet must be stable for a fast, complete installation. |
| 51956/ 47978/ 47826 |
Though supported as a feature, USB over network does not work reliably. In actuality, over the internet connections via HySecure, it fails. In some cases, ports used for USB redirection over the network are not cleaned up after user logout, causing subsequent Eltima over-the-network connections to fail on the same server. Sometimes it is unable to reserve the specified port range and then fails to work. |
| 47095 | Newly created folders in File Explorer do not appear automatically when using Advanced HyShell-enabled shared hosted desktops. |
| 47093 | The search option is not visible on the desktop with the advanced HyShell, though it is enabled in the respective configuration file. |
| 46912 | The mouse cursor flickers inside a shadowed desktop session. |
| 43735 | When uninstalling the DVM tool by selecting HyWorks USB Redirection, the process redirects to an external URL, causing unnecessary delays. |
| 42759 | With Windows 11 IoT endpoints, built-in USB redirection is experiencing intermittent issues in which the USB device in the launched session gets stuck in "waiting for connection" and becomes unusable. |
| 40541 | Microsoft Edge, published as a virtual app, does not function in the system context, and the session gets logged out. |
| 39226 | Shell-mode apps are not launching for the user. The controller app session is displayed as connected, and the controller sends response code 0 to the client, prompting the client to launch a new RDP window. |
| 37413 | The "Destination" field appears as "NA" in ARS logs for the "File downloaded to local computer" event in HyFR. |
| 36812 | App sessions reconnect on the same server, even when the server is inactive, and the controller's advanced configuration to give reconnection from an inactive server is not enabled. |
| 35669 | The user must click the app name in the widget twice when another app is running in the foreground. App maximizer is in front of the desktop session. |
| 35580 | When connecting to the shadow session with local administrator credentials, the session shadow fails. The local admin’s current session is connected to the user's session. This issue is related to Windows Server 2019 and may be due to issue #34179. |
| 35217 | Some system processes or applications may still use the system IP even when virtual IPs are assigned for the user session. |
| 35197 | In very rare, unknown cases, Accops EMF and A4 Printers fail to print more than 2 pages when printing a PDF file opened in Adobe Reader. |
| 35196 | HyPrint Printer generates a large-sized output PDF file. This is a known behavior. |
| 34486 | The desktop agent depends on the system for session connection events and, thus, in the case of frequent, simultaneous reconnections, it may log session events as received out of order. Although this has no functional impact, the analysis can become confusing in some cases. |
| 34179 | 2023-08 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5029247) - Causing Multi-session and Reconnection Issues. Recommendations: 1. A new shell launch method can be tried if facing issues with multiple shell apps on Windows 2019 and 2022 servers. 2. Desktop publishing with HyShell can be used with restrictions on the file system and the desktop. A new, advanced shell is being released soon to address some of the existing issues. |
| 33716 | With Appstract, when a file already exists at a shared location, performing the 'Save' operation on the same file saves it to the user's temp folder instead of the configured shared path. |
| 33713 | With Appstract, the session host server's file system dialog is displayed when the client machine's file system dialog is closed, even though 'OnOpenFileCancelShowLocal' is false. |
| 33619 | With Appstract, the Local machine's file system dialog box does not open when a user tries to save the uploaded file; the file is saved on the session host server. |
| 33617 | With Appstract, a delay is observed when opening the local file system dialog box when the user clicks the 'Save' & 'Save as' options. |
| 33453 | With Appstract, file transfer enabled, on opening the 'Open File' dialog, first it opens the ‘ Open’ SHD server's dialog box and then the base machine's dialog. |
| 31822 | The exclude process (to use system IP instead of virtual IP) is not working with the SHD pool. |
| 29789 | The controller does not remove the virtual IP configured when disabling the feature from the Advance settings. This is to be done manually. |
| 26461 | The session host IP virtualization feature does not work in cloud deployments (Azure/AWS/Oracle). |
| 24995 | Some exceptions are logged in session host logs when a session host with multiple running sessions (with VIP enabled) is restarted. Exception: The underlying provider may fail on Open. |
| 24888 | An error is logged in the session host logs only after a shared hosted desktop pool is provisioned. Error: region LastServiceForcedExit failed. Error: The media is write-protected. |
| 23964 | The successful VIP removal log is not being logged on the controller when the session is logged out from within the session (SHD). |
| 23408 | Users fail to read the notification because the Tray agent is open in the background during the remote app session recording. |
| 23297 | The controller does not support upgrading session host servers that are currently running sessions. As a result, such servers must be accessed and upgraded manually. |
| 22590 | Windows Server 2022, by default, does not support multiple sessions for a single user. This can adversely affect virtual app delivery in shell mode. Solution: Configure the following Group Policy on Server 2022: - Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections. - Set the Restrict Remote Desktop Services user to a single Remote Desktop Services session to Disabled. |
| 22519 | Recording does not stop for applications configured to record, even after the application is closed or when it is not in use. The same behavior is observed for the configured network address. |
| 22170 | When the remote app sessions are removed from the controller, the provider session enters a disconnected state. Workaround: Configure Group Policy to log out remote app sessions immediately (via gpedit).msc > Computer configuration > Administrative template > Windows components > Remote desktop services > Remote desktop session host > Session Time limits > Set time limit for logoff of Remote app session. |
| 21254 | Logs are not generated on the HyWorks controller when the session host server fails to create local users. |
| 20938 | Session recording may not start if it is configured to start with the specific process launch and the process is initiated within 10 seconds of the session start. |
| 20725 11145 | Mozilla Firefox and Microsoft Internet Explorer do not work correctly when initiated in a different user's context, i.e., opened as a different user. This should be avoided. |
| 19910 | In rare cases, the monitoring service database contains invalid values, and the service may not respond. Replace the database with an empty one, then restart the monitoring service to resolve the issue. |
| 18860 | Session recording is not functioning when accessing an SMB2-based network. |
| 16949 | Upgrading PowerShell to version 3.1 is necessary for Windows 2008 R2 SP1 to repair trust relationships. |
| 16941 | Messages shown to the user via virtual channels are outside of the remote session. Thus, the user may find it difficult to associate them with sessions, especially when running multiple virtual apps in shell mode. |
| 16929 | The capacity plan will continue to affect the managed session team even when: 1. The plan is inactive. 2. The session team has been removed from the capacity plan. 3. Schedule has expired. 4. The capacity plan is changed from enforced to disabled. |
| - | The Chrome browser does not launch in multiple remote sessions of a single user on a Windows session host server. Workaround: As many deployments need to access Chrome browser as a virtual app in shell mode, which will require multiple sessions of a single user from a single session host server, specifying the following command line will enable accessing Chrome in shell mode multiple times: Additional Command-line: --user-data-dir=%localappdata%\Google\Chrome\%sessionname% |
| 14208 | After an upgrade or a fresh installation of the session host server, a couple of PowerShell windows will briefly appear on the server's first logon. |
| 13922 | The RDS role is not available on Windows 2019 Essentials and therefore cannot be used for virtual application or shared-hosted desktop delivery. |
| 6978 | While printing a large PDF file (File Size: 65965 KB) from HyLite\HyWorksClient using Accops Printer (Light speed printers), an error is given that the print job to the client failed. |
| 6644 | Initiating multiple file transfers at once does not indicate any queued transfers; it still shows the first one started. The behavior can be confusing for end users. |
Known Issues and Limitations for New Shell Mode with Multiple Virtual Apps
While working on the new shell mode with multiple virtual apps, the following points should be considered carefully:
| Bug ID | Description |
|---|---|
| - | The delivery mode can only work with compatible client, controller, and session host versions. Support for other endpoints (e.g., HyLite, MAC Client, Linux Client, Android client) will be integrated soon. Check compatible versions of different modules here. |
| - | If any incompatible client tries to access the apps in new shell mode, the applications will launch within the already-running remote session, but an error will be displayed: "Error: You are likely encountering this error due to an older version of the client." The application will automatically launch within an existing session. Please check with the administrator to obtain a compatible client version. |
| 46941 | New shell app multiple issues while connecting via HyLite: 1. The taskbar gets hidden intermittently. 2. Confusing behavior while opening a second instance of the app. 3. Already opened apps grouping is not user intuitive. 4. Incorrect Shell app naming: On reconnection, it automatically changed back to the last opened app. 5. New app opening behind an already opened app in maximized mode. |
| 42760 | In case of multiple Shell applications, the Write Application vanishes after being minimized. Restoration of minimized applications is not smooth from the taskbar. |
| 40534 | When reconnecting an existing virtual app session in shell mode, the application is minimized in the remote session. The behavior is observed only on Windows Server 2022. |
| 40390 | Pin, unpin, and close options, such as those on the Windows taskbar, are not available when right-clicking on the app button. |
| 40387 | The tooltip flickers when the mouse hovers over the minimized app icon on the taskbar. |
| 40386 | With multiple (>8) virtual apps in a single shell session, the user has difficulty accessing applications in the taskbar because the "Show more apps" arrow button is clearly visible but does not work on the first click. |
| 40371 | App windows are not visible when hovering over app icons on the taskbar (similar to the Windows taskbar). |
| 40367 | App group buttons are not aligned with the taskbar. |
| 40023 | Assigned VIPs in a session with multiple apps will only be detached upon session logout, not upon app closure (VIPs were assigned to the app). |
| 39666 | With multi-monitor setups, the remote session window launches in full screen, but the actual app and taskbar are not aligned with the full screen and appear to float in the middle. |
| 33399 | In the case of an application session, the AUEM tray is not available in this release for accessing connected devices/Task Manager/Notification history/Hide notification/Battery manager, etc. |
Power Management Known Issues and Limitations
| Bug ID | Description |
|---|---|
| - | Session host server power management applies only to deployed managed session host server teams and does not apply to existing manually created teams. Azure configuration must be performed manually using a privileged user account. |
| 24889 | While scaling down, the maximum provisioned capacity is used instead of the minimum running capacity, which can result in running more servers than planned. |
| 22037 | Capacity planning checks the plan objective closest to 12:00 am/0:00 in the current plan only; even if multiple plans are applied to the single-session team, it may fail to implement objectives from other plans. |
| 21875 | The Action Processor service crashes when AccopsMQ is unreachable. |
| 21735 | On-demand scaling via capacity planning is not supported for virtual application sessions and applies only to shared hosted desktop sessions. |
| 21652 | In some rare cases, the action processor has cordoned more servers than expected. Running sessions will not be affected, but new users may have to wait for servers to be un-cordoned. |
| 19776 | The schedule background worker's CPU usage can increase significantly while saving a session for a team. |
| 17689 | If a managed (deployed) session team already exists and the controller has been upgraded to v3.4, the session team must be updated at least once to generate schedule IDs. |
| 16904 | Some known limitations of automatic power management in HyWorks: 1. Backend call for plan implementation will occur at a minimum 10-minute interval at 00, 10, 20, 30, 40, 50. 2. The action processor has two calls, i.e., 1. Plan implementation 2. Dynamic scale, hence scale may happen in the next cycle if a call to scale occurs first 3. Virtual channel-based notifications to end-users will work with Windows endpoints only and will require virtual channels to be enabled in the session using connection profiles. 4. Notification settings need to be configured through the appsettings.json file, and a service restart is also required. 5. Admin does not have control over dynamically managed teams, which essentially means that even if some servers are powered on or off, they may revert to their original state as per capacity plans. 6. Actual shutdown of the cordoned server may not happen at the notified time and will occur on the next dynamic scale trigger. 7. CPU/ RAM thresholds (if applied) can conflict with the capacity plan, as it only considers the max sessions allowed per server. 8. Overlapping of two objectives will result in the implementation of the current objective, and thus, the previous plan objective in progress may be affected. |
| 13794 | The log should be enabled on the controller when power-off/on operations are not required; currently, no logs are being recorded on the controller. |
| 13793 | When SHD cloning fails, power management for the session team should be based on the number of VMs successfully cloned. It continues to use the desktop count as specified in the desktop pool. Workaround: Update the desktop pool with a new count or clone again to match the count. |
| 13789 | For every managed session team, we need Azure access to create a Logic app. |
| 13777 | When the team size is reduced, power management should work accordingly. |