Known Limitations and Issues in SHD and App Delivery
-
Last Updated Date: 28-Aug-2025
-
Release: HyWorks v3.6
Note
The known issues list is updated with every release. Listed below is the latest summary of issues.
Windows-Based Shared Hosted Desktops and Virtual App Delivery Known Issues
Important Bug with AUEM v3.6.0.421 in Session Host Server(v3.6-HF1: v3.6.0.150) and DVM Tools(v3.6-HF1: v3.6.0.1305). Releases with fixes are available.
-
Issue #57343: When a user session disconnects, network-mapped drives are deleted and fixed in the latest releases.
-
This issue affects only the specified releases and does not exist in previous releases.
-
Use this build only if it’s absolutely critical for deployment, and mapped network drives are not being used.
-
HyWorks DVM Tools for Windows (v3.6.0.1314) and HyWorks Session Host Server for Windows (v3.6.0.153) have been released with a fix for this issue and are recommended for use. Refer to the Release Article for more information.
Note
-
If you need to use this release and a mapped drive is required, you can disable the AUEM Tray Agent (located at C:\Program Files(x86)\Accops\AUEM\AUEMTray.exe) by renaming it (Do not delete). The following features will not work after disabling the AUEM Tray, and thus make sure these features are not used in the deployment:
-
Session recording, Advanced drive redirection, USB Redirection using Built-in (Eltima) USB redirection driver, AUEM Notifications, RTT Data Calculations, Advanced Clipboard, and Smart File Transfer.
| Bug ID | Description |
|---|---|
| 40541 | MS Edge, published as a virtual app, does not work 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 a response code 0 to the client, prompting the launch of a new RDP window. |
| 35580 | When connecting to the shadow session with local administrator credentials, the session shadow fails. The existing session of the local admin 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. |
| 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. |
| 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 Advanced settings. This is to be done manually. |
| 26461 | The session host IP virtualization feature does not work in cloud deployments (Azure/AWS/Oracle). |
| 25474 | Shadow sessions are considered direct RDP sessions and may get removed by the agent. Workaround: Temporarily disable the direct RDP block feature. |
| 25118 | Session host installation may not display any errors if the user running the setup does not have the necessary rights to add or update registries. This may result in functional failure at a later stage during the setup. Recommendation: Session host installation logs should be verified post-installation. |
| 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 manually accessed and upgraded. |
| 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 that are configured for it, even after the application is closed or when it is not in use. The same behaviour is observed for the configured network address. |
| 22170 | When removing the remote app sessions from the controller, the provider session enters a disconnected state. Workaround: Configure the group policy to log out the remote app sessions immediately: 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 created on the HyWorks controller when the session host server does not 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 an infrequent case, the monitoring service database contains invalid values, and as a result, the service may not respond. The database should be replaced with an empty database, and the monitoring service should be restarted to solve 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. 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 be displayed briefly on the first logon to the server. |
| 13922 | The RDS role is not available on Windows 2019 Essentials and thus cannot be used for virtual application or shared hosted desktop delivery. |
Known 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:
| # | Subject |
|---|---|
| - | The delivery mode can only work with compatible client, controller, and session host versions. The support in 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, applications will get launched inside of the already running remote session, but an error will be shown: - 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. |
| 40534 | On reconnecting an existing virtual app session in shell mode, the application is getting minimized inside the remote session. The behavior is seen on Windows Server 2022 only. |
| 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 experiences difficulty in accessing applications in the taskbar, as the arrow button to show more apps has clear visibility and 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 and will not be detached upon app closure (VIPs were assigned to the app). |
| 39666 | With multi-monitor setups, the remote session window is launched in full screen, but the actual app and taskbar are not aligned with the full screen and appear to be floating in the middle of the screen. |
| 33399 | In case of an application session, the AUEM tray is not provided in this release for the user to check the connected devices/Task Manager/Notification history/Hide notification/Battery manager, etc. |
Power Management Known Issues
| # | Subject |
|---|---|
| - | Session host server power management is applied only to the deployed managed session host server teams and will not work for existing manually created teams. Azure configuration must be performed manually using a privileged user account. |
| 24889 | While scaling down, the maximum provisioned capacity is considered instead of the minimum running capacity, and this can result in running more servers than planned. |
| 24868 | Error observed in HyWorks controller logs when attempting to use cordoned servers for capacity plan scale-up. Error: Team ID or desktop provider IDs can not be null. |
| 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, and thus it may fail to implement objectives from other plans. |
| 21875 | The Action Processor service crashes when AccopsMQ is unreachable. |
| 21735 | On-demand scaling using capacity planning is not supported for virtual application sessions and works only for 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, to generate schedule IDs, the session team must be updated at least once. |
| 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 operation is not required; currently, no logs are being logged onto the controller. |
| 13793 | When SHD cloning fails, power management for the session team should work according to the successful cloned VM count. 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. |
| 13792 | Logic App logs utilize the session team ID and provider ID; therefore, the admin must identify the affected team using these IDs. |
| 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. |