HyWorks Controller Known Issues and Limitations

Last Updated: 22-May-2026

Release: HyWorks v4.1

Note

The known issues list is updated with every release. Listed below is the latest summary of issues.

---

Controller and Management Console Known Issues and Limitations

Bug ID	Description
69227	End users may not receive an appropriate error message when the server is facing licensing issues. Correct details are available in the logs.
69191	If the Dedicated Linux VM Pool option is not selected for non-deployed desktop pools, or the Source VM type is not set to Linux for provisioned pools, the desktop pool may be created as a Windows pool, resulting in functional issues. Having these options automatically identified or forcefully selected by the administrator will help reduce the chances of deploying desktop pools with incorrect configurations.
69186/ 67182	In very rare cases, cloning with the newly supported connector, HPE VM Essentials, in HyWorks v4.1 may not be processed, even when no explicit errors are reported. This behavior may potentially occur with other connectors as well. The issue was resolved automatically after restarting the HyWorks Controller service.
68986	For non-deployed VMs, Disk Encryption and Customization are displayed as Invalid on the Desktop Details page. Impact: No functional impact.
68523	HyWorks logs do not provide sufficient details related to graceful recompose and contain repeated recompose-related keywords. This does not have any functional impact, but it may reduce the usefulness of logs for audit and troubleshooting purposes.
68489	Logs generated on the HyWorks Controller when certificates cannot be fetched from Accops Certificate Manager (ACM) display the exceptions returned by ACM or related services and may not clearly indicate the exact problem area.
68488	In HyWorks v4.1, improvements have been made to reduce the likelihood of duplicate user entries when the SamAccountName changes. However, previously created duplicate entries are not automatically cleaned up.
68426	The error message displayed when adding a VMware connector with an invalid host address is not user-friendly and may not clearly indicate the issue.
67939	Administrator login to the HyWorks Controller Management Console may fail after reverting the system date from a future date back to the current date. Workaround: Restart the HyWorks Controller server.
67772	In rare cases, a commonly used dependency DLL file may be replaced in HyWorks by an unknown module, resulting in user logout failures with the error: "Could not load file or assembly Microsoft.Extensions.Configuration.Abstractions."
67696	In some cases, disconnect codes logged on the HyWorks Controller may not provide the exact reason for a session disconnection, which can cause confusion during troubleshooting.
66841	In rare cases, login from the HyWorks client may fail with a Guava mismatch error. The affected environment had Single Sign-On enabled in the HySecure client profile, and disabling it improved the behavior. The exact root cause is currently unknown.
66543	Desktop pools under graceful recompose with the Limited To option selected are not listed for the Move to Version scheduled action. This is expected behavior to avoid conflicting operations.
66038	VMs from a non-persistent pool may not be listed when creating scheduled actions, such as Move to Version, during graceful recompose. No information is displayed to indicate why these pools are excluded.
65997	In the Advanced Settings section of the Management Console, related settings may not appear together, making the section harder to navigate.
65692	In rare cases, when the monitoring service does not capture resource data from the system, Broker Node resource metrics — CPU, RAM, and HDD — may remain static and fail to reflect actual utilization in the Management Console dashboard.
65167	When HyWorks Controller and SQL Server are installed on separate servers, the backup file is created on the SQL Server at C:\Program Files\Microsoft SQL Server<instance>\MSSQL\Backup. The HyWorks server creates an empty folder at the default backup path. Log entries may not clearly indicate which server the backup resides on.
65136	Stopping provisioning mid-recompose in a linked-clone pool may leave un-recomposed VMs unusable, as their parent disk references the old replica. Workaround: Do not stop provisioning during a linked-clone recompose unless replica recreation is confirmed complete.
65093	Desktop power operations may fail intermittently when they conflict with the provider’s cache update, which runs by default every hour.
64965	No log entry is generated when a DVM agent upgrade completes. The installed agent version may not be recorded in the controller logs.
64849	In an isolated incident, after a username change in Azure AD with SSO configured, the application launch may not complete. HyWorks may continue using the previous username for session brokering. Workaround: Re-register the user or clear the controller session cache.
64847	When an administrator initiates a disconnect action from the Management Console on a session that is already disconnected, the action proceeds without error, and a disconnect reason may be logged for the already-terminated session.
64682	When the Username Option is set to 2 (domain\username), HyWorks incorrectly reformats the username internally to username@domainname, which may cause RDP authentication issues.
64582	Policy assignments that use a nested OU name rather than the full OU path may not apply. The policy is saved without error but has no effect. Workaround: Specify the full OU path in the assignment filter.
63054	The controller log message 'No valid response from Desktop agent' may appear in multiple scenarios — including Gold Master addition, desktop connection, and customization — and may not provide sufficient context or a specific reason, making troubleshooting less straightforward.
62583	Applying a license on the HyWorks Controller from the management console may fail with the error "Key may not be valid for this version". Cause: While creating the license, the product was initially selected as HySecure with a version, and later switched to HyWorks. If this license is tried, the failures are observed. Get a new license key from the Accops team.
61722	Power management behavior may vary when multiple control mechanisms are active simultaneously — including auto-shutdown settings, non-persistent pool behavior, pool-level DVM power operations, capacity plan-based power management, and scheduled actions. In some configurations, these may produce conflicting outcomes. A consolidated power policy framework is planned for a future release.
61694	In cases where the HySecure session is logged out first, and HyWorks may not receive the user logout notification, the VM may remain assigned. Subsequent assignment of that VM to other users may not occur until the assignment is released.
58105	When an incorrect Customer ID is entered in the ACM Advanced Configuration settings, the log entry may not clearly reflect the specific reason.
56901	HyWorks may not display the reason for cloning or other operational failures in some cases, when the response from the provider may not include those details.
55258	When the HyID authentication server is unreachable, the controller log may not identify which service is unavailable.
54775	Classification rules may continue to apply to pools and reservations even when the IsClassificationRulesFeatureEnabled flag is set to false. Note: Some advanced feature flags may not completely disable the associated feature.
54637	User login restriction may still be in effect when the license count is exceeded, even when the IsLicenseCheckEnabled flag is set to false. Note: Some advanced feature flags may not completely disable the associated feature.
54610	When IsUpdateLastClientLoginDetails is set to false, users may not be added to the database and may not appear on the Registered Users page. Note: Some advanced feature flags may not completely disable the associated feature.
54434	DVMs already present in Precalculated Desktop Entries may not be cleared when the associated session provider is marked inactive and may still be assigned to users.
53912	In some cases, the Display Settings page in Device Settings may not appear, preventing configuration of the resolution and frame rate for registered devices.
53413	When HyID is configured as the authentication server, user search in HyWorks MMC may not return results for users whose display name or UPN contains an apostrophe.
52757	Group-based assignment may not be supported for enterprise applications with Microsoft Entra ID Free. Only individual user assignments are available. HyID as Auth may not be recommended for environments using the Entra ID Free license tier.
52506	When no session hosts are deployed in a server team, creating or updating an application for that team may generate log entries that may not reflect the underlying reason.
50084	With the VM Selection Strategy set to 0 (Stored Procedure) in a Master Pool, low-priority VMs may be assigned even when higher-priority VMs are available.
49723	When searching for users with special characters (such as ~, `, !, @, #, $, %, ^, &, *, (, ), _, +, {, }, :, ", <) in OUD/Novell LDAP, the search may not return results. Usernames containing these characters may not be available for entitlement assignments.
49375	On the Registered Users page, user details are retrieved from the current organization's authorization server. If a user belongs to a different authorization server, some details may not reflect the correct values.
49204	MMC and RMS logins for OUD or Novell LDAP users may not complete when the login attribute is filtered.
48083	When the controller database name contains special characters such as ~, `, !, @, #, -, $, %, ^, &, or :, a log entry may appear on the secondary controller in an active-passive setup. There is no functional impact.
47430	When a snapshot referenced by a pool is no longer available on the provider, the pool may not clone successfully after the next save. No warning is displayed during pool editing.
46671	Under sustained high load, log viewing in the Management Console may become slower, and logs may take longer to display.
46670	Under high load, the controller may accumulate log records beyond the configured threshold, delaying automatic cleanup.
46345	In some cases, changing the server team of an existing session server may fail with a non-descriptive error. The server may not be moved to the new team.
43644	The controller log may not include the username of the administrator who updates an authentication server configuration.
42752	HyWorks continues to use the old cached secret for the Azure Connector even after changing it in the HyWorks Management Console, and the HyWorks Controller Service must be restarted. Solution: The HyWorks Controller service has to be restarted on the management node.
42142	After upgrading HyWorks Controller from v3.4 SP1 HF6 to v3.4 SP2, the Message Queue password may require a manual update. If not updated, the controller may log a non-hex character error against the stored password. Cause: This has started occurring due to the encryption added to the MQ password in v3.4-SP2. Workaround: Update the MQ password after the upgrade.
41507	Users may not log in to a new organization in HyWorks if they already have an active session on the same device in another organization. Error: 'failed to register device'. Workaround: Either log in to another organization and clear the session, then attempt to log in to the new organization, or have the administrator delete the old device and session from the other organization.
41471	The task manager may not be available on the application session page and is only available on desktop sessions.
40899	Recompose operations may fail if the internal ID of the Gold master has changed in HyWorks. Cause: The Original GM is deleted from the hypervisor, and during the VM list update, the controller has another VM with the same name.
40731	HyWorks may clean up user sessions when the associated desktop session is removed, if "Desktop Session Monitoring on RDP Status type" is enabled. Cause: The issue occurs when the HyLite desktop session is disconnected and then reconnected due to a network glitch, but the desktop session entry is removed on the Controller side.
40649	HyWorks may not display an appropriate error when it fails to connect to Azure due to internet issues.
40381	Controller servers in secondary/Fault/Maintenance mode deny communication to clients with the message "Server mode may not allow this operation," but do not log anything.
40231	"Move to version" failure logs may not include information about the VM and Pool, and thus may not correctly identify the affected VM and Desktop Pool.
39959	HyWorks Controller: Active-passive setups may enter an error state, with the DB sync failing with the error "remote peer is outdated". Cause: This has been observed in setups where the primary and secondary nodes have not synced for a long time, and then they attempt to sync.
38952	In rare cases, pool cloning may not be initiated during pool save and update operations performed from the Management Console.
38265	VM scale booster may update the wrong RDP session when multiple entries with the same desktop ID are pushed from the desktop agent side.
38232	In a very isolated case, a new version may not be getting created for a specific pool after version '9', with no clear error in HyWorks Controller logs. Workaround: Restart the HyWorks Controller service or switch to the secondary HyWorks Controller and create a version from the new primary server.
38191	The Proxy configuration saved in the EDC.service.exe config file is removed after upgrading HyWorks Controller and must be reconfigured post-upgrade.
37556	In some rare cases, the Management console became inaccessible after some Windows updates on Windows 2019 servers. Workaround: Uninstall and reinstall the IIS role on the Windows Server, then repair the HyWorks Controller Management Console.
37521	The desktop agent may report the HyWorks detected address (GW address or visible network) as the WAN IP to ARS when directly connecting via the HyWorks Controller. Cause: HyWorks uses the visible network as the WAN IP if the client has not reported one.
37322	In the following cases, desktop pools may not be listed for scheduled actions, and thus administrators may not get clear leads on the next action: 1. A pool having only a version with a non-zero count of graceful recompose may not be visible, and the admin may not know. 2. When the limit is set to non-zero, while creating a schedule action for move to version, the pool name may not be listed, and the admin may not be aware of this.
36984	In an isolated case, a Message Queue user created by the script with a specific set of passwords is unable to log in to the RabbitMQ console and receives an authentication may fail error. Workaround: Try resetting and using a different password, avoiding the one that is not working.
36595	The action processor works on the primary only; if it stops working while other modules (Controller, Scheduler services) are still running, features associated with it, such as scheduled actions or capacity planning, may not function.
35800	A change in a user's group membership may not be reflected in HyWorks desktop/app access unless the user logs in again. The AD group-based classification rule performs the calculation on logon.
35736	Classification Rule recalculation on Connect Desktop occurs only for HyLite and may not work with HyDesk Client. Classification rule recalculation in the Connect Application may not be supported; it is supported only for Connect Desktop.
34924	In some very rare cases, recompose may not get initiated (both Forceful and Graceful), with no error logs. Workaround: Switching to another management node and initiating the operation may work, or restarting the HyWorks Controller service and trying the operation again.
34756	Syslog settings may not be synced across controller nodes and must be configured on each node.
34735	In a rare case, HyPrep was not initiated for multiple VMs deployed through self-study reservations. Cause: Due to duplicate IPs and VMs not being deleted from past reservations.
34607	Some logs of child organizations are created in the default organization. Downloads specific to the organization may not create those logs in default organizations. Workaround: Download logs of all organizations for troubleshooting.
34216	In a rare case, logs for making user sessions idle were not created, which caused confusion about how the sessions were terminated without appropriate logs.
34159	With the advanced setting "Allow Org change" enabled and a user with a session in one organization trying to switch to another, the session will be terminated without any notification to the user. Impact: The User may lose any unsaved data in the sessions. Important: This is not the default configuration.
34151	With multiple datastores selected and no resource pool specified, HyWorks may attempt to clone to the resource pool of the best host and may fail if permissions are missing. Solution: With multiple datastore selections, the admin should have rights on all objects (hosts/ resource pools) associated with the datastore.
33696	For non-persistent desktop pools, assigning VMs (having restore point creation may fail) from the management console is allowed.
33562	With too many devices, short device heartbeats, and a high login rate, database operations may become bottlenecked, causing functional failures, including user logins.
33492	When using the email attribute for login, the last login time may not be updated for existing users, and for new users, entries may not be created in Registered Users.
33361	With the 'Disable RDP port ping for session host machine' flag set as 'False' from Advance Settings, HyWorks may skip checking RDP port connectivity in some cases. Impact: Under certain conditions, when only the RDP port becomes unreachable, the Controller may continue to assign sessions and thus fail the connections in the end.
32528	Power Operations initiated from the HyWorks Client may fail if broker nodes lack connectivity to the Hyper-V provider.
32481	OS Disk size is copied from the image, and not copied from GM while cloning from the image.
32162	HyWorks Controller service can not be configured with a gMSA account to connect with an MS SQL server. Issue: Controller service and Licensing service fail to start when configured with a service logon account that is a gMSA.
32107	MSRA (by default) may not use the provided session ID (when multiple sessions are present) but instead prompts the administrator for a list of sessions.
30952	On the HyLabs portal, the connect button may not be automatically updated for users when the status is changed.
30914	HyWorks Controller allows adding nodes to a cluster with different time zones in a setup without any warnings or errors, but this causes functional failure.
30352	If Spare VM creation may fail for a floating desktop pool, subsequent spare VM creation may not be triggered automatically, which may cause connection failures for new users, as no spare VMs will be available.
29930	Applying a license in a multi-node setup is very tedious and requires multiple steps for each node.
29926	HyWorks may not retain the network information of VMs whose cloning has may fail; thus, even if preserve network is enabled, newly created VMs may not have this information.
29832	A replica is deleted when the linked cloned pool is deleted, even if the admin has checked the option to retain the desktops.
29656	In rare cases, the managed SHD VM entry may not be removed from the load-balancing page when the cloned SHD VM is deleted from the VMs page, and the shared desktop status remains inactive.
29213	Resource Group could not be created.' Errors are logged when the resource group may not be available in the AWS region.
29079	Failsafe may not work with AWS/Oracle connectivity, which is down on the HyWorks Controller.
29040	The broker node initiates the spare VM creation operation if the trigger is due to a login or another brokering operation. Thus, provider connectivity is needed from management and broker nodes. Lacking connectivity to the provider may cause functional failures.
28559	In rare cases, the pool status may not be updated even after cloning and Hyprep completion, and the cloning-completion logs may not be logged on the controller.
28430	Could not retrieve Desktops. Session Provider is missing or deleted, errors observed after updating the desktop pool in some cases, with no impact on functional aspects.
28356	The controller creates only a single replica VM, even when the Concurrent Full Clone flat is set for more than one.
28222	In some cases, 'Object reference not set to an instance of an object' errors are thrown when desktop cloning has may fail due to connectivity problems with the provider.
27761	In a very rare incident, a production license that had already been applied for was corrupted during the evaluation license application.
26745	In rare cases, provider sync may fail due to a database deadlock. Workaround: Periodic server restarts may help in overcoming these issues. Also, the Desktop provider cache update can be made false to improve.
26515	Deployment settings such as Network preserve, Cloned VM deployment settings, Encryption type, and DVM reset may not be getting saved in version details.
26215	With deployment settings set to the default, all cloned VMs are deployed to a single host on which the gold master is running, even when the gold master is in a cluster. Workaround: Make sure to specify deployment settings to be deployed at the cluster level.
25937	Secondary AD may not get synced in DCDR if primary AD is already synced on the DR site and 'AUTHENTICATIONSERVERSSYNCEDONDR' is set as False. Workaround: Manually add the secondary AD on the DR side.
25685	DCDR syncs License distributions on the Controller, making it mandatory to have the same licenses on both the DC and DR sites. Having a different configuration may cause licensing issues.
25346	Controller continues to show old platform for logged in user and may not refreshes the platform information.
24997	Same users from different authentication server can be added, if configurations are changed in auth-domain, e.g. auth-domain configuration is changed from built-in/built-in to LDAP/built-in or vice versa. Impact: The duplicate entries may confuse administrator and also may result in login or authorization failures sometimes. Recommendations: The organization configurations should be planned well so that it may not require change. Even if it needed change, clean-up of HyWorks should be done to remove all users from previous auth-domain configurations.
24885 / 22968	Oracle Data Disk and OS Disk snapshot may not be getting deleted in set time and in case of recompose the old snapshot may be used for provisioning causing the changes done on Gold master to be ignored.
24527	In some rare cases VM deletion was may fail with error "The Object context instance has been disposed and can no longer be used for operations that require a connection", while deleting the desktop pool. Workaround: Manually remove the VM from HyWorks and respective provider.
24380	Password change may fail with exception, if port 636 may not be reachable from HyWorks Controller or appropriate certificate configurations may not be done on active directory server and option 6 is used for active directory connection. Exception: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
24373	HyWorks Controller may not log VM image creation on AWS. There is no impact of this but eventually can create some confusion as VM image deletion logs are generated after cloning is completed.
23805	Provisioned SHDs published as physical PCs may not be responding without showing error displayed. The issue is because, all the physical VMs added with same IP address are going to have duplicate IP and in that case controller may not show agent status.
21958	Client entry may not be getting updated after updating DN for a user and so multiple client entries are created.
21829	By default for fresh controller installation, with active directory option# 6 for user authentication and authorization, built-in groups and nested groups may not work in HyWorks Controller. If required it can be changed from HyWorks Controller > Advance Settings.
21731	Controller may not create synchronization logs for a very long period of time when the secondary server with a very large number of records has been added to a controller.
21724	SQL transactions may fail on the Controller, when too many devices (100K) are registered.
21287	With small timeouts on HyWorks (< 5 minutes), sessions taken from HyLite may get logged out abruptly though user is working. This happens because the default sync time between HyLite and Controller is 5 minutes. It is recommended to have timeouts more than 10 minutes, when delivering with HyLite.
21044	Controller access via VIP may not work, if network adapter used for VIP configuration is having space in it. Workaround: Change network adapter name to have no spaces and same name on both controllers.
20866	Controller sets display name same as username while importing users from LDAP and may not use the actual display name configured on LDAP.
20800	On initiating sync session info action on inactive session provider, controller displays a success status but may not perform any sync operation. The behavior is also different, when performing the same operation on session team with inactive session provider where appropriate logs will be created.
20733	Active directory server may fail to be added into HyWorks, having following policy enabled: Policy: "Domain controller: LDAP server signing requirements" enabled and configured as "Require signing" Exception: Additional non-parsable characters are at the end of the string.
20616	With too many records for synchronization (more than 100000), cluster configuration may fail and primary server may go into fault mode. Workaround: Create secondary server with backup of primary database and then add to HA, avoiding too much synchronization.
20296	Adding a deployed shared hosted desktop pool creates a team with same name as desktop pool name but updating the desktop pool name may not update the team name.
20202	Network Settings details may not be integrated in CSV export from session teams page.
20124	Reason of service not responding for Linux session host server is shown as "Feature not available" and may cause little confusion.
20119	If a Windows session host server configured in HyWorks is powered-off, it can create a confusing log. Log: The Session Provider 'provider name' may not be reachable. More Info :Unable to connect to the Session Provider hosted at 'Not Available'. Reason: Unable to parse URI 'http://Not Available, Reason: Invalid URI: The hostname could not be parsed..
20009	In some cases, HyWorks may log an error while deleting desktop pool, though related objects are deleted successfully. Error: Store update, insert, or delete statement affected an unexpected number of rows (0). Entities may have been modified or deleted since entities were loaded.
19984	Configuring static IP address on Gold master may result in duplicate IPs in the network post provisioning.
19983	Controller may fail to delete a device having associated session and attempts to register into another organization. Ideally Controller should delete the associated sessions also.
19868	The shutdown operation on Linux VMs is kept on hold, if someone has logged-in to the VM from hypervisor console session.
19664	Controller lists all attached VIPs, while trying to change primary IP for the VM. Ideally VIPs should not be listed as they may not be always attached to virtual machines.
19560	Saving a session team with a very long range of VIP may get stuck and cause high resource (memory/CPU) utilization by controller service. Workaround: Create some small network range and configure it on team.
19091	Controller by default uses the primary or first IP on the network interface added on Azure VM, though VM has multiple IP addresses configured on network interface. Option to choose primary IP may not work for Azure provider VMs.
19038	If a permanent VIP is having issue, the user session will be rejected unless the issue is solved or a new VIP is assigned.
18507	With too many concurrent user connections (more than 10 per second), functional failures may occur.
18327	Controller transactions with SQL may get may fail with timeout exception if database diagram is created. Usually database diagram is created when user clicks on it and it checks with user to create it.
18078	In case of domain controllers are deployed in child-parent configuration and HyWorks is configured with child domain, it may not fetch groups or OUs from parent domain controller.
18015	Changes to management may not be forbidden from session nodes, so if any deployment is having management console installed on session nodes, changes can be done from session nodes as well.
18006	Controller displays a confusing error invalid username and password, when SAM Account Name is to be used for logon but truncate is off and user is using username@domain-name or domain-name/username to sign-in.
14404	If special characters %/" are included in Gold Image (Source VM) name or snapshot name for vCenter, snapshot of replica is getting created every time after increasing the count of VM for Persistent pool of type linked clone Avoid using special characters in Gold Image (Source VM) name or snapshot name.
14376	Incorrect error message is displayed in Test connection of AD, when configured admin account is locked.
14375	If the user has changed password, Auth domain (AD/Built-in) and synchronization as May not create/ Manual, connection to dedicated desktop may fail.
14083	Deleting a node from HyWorks Controller active-active setup requires node to be destroyed before removal as on service start the node may again get added.
13923	Controller may fail to authenticate users, who are member of "CNF" group in AD. Exception: XML parsing: line 1, character 1744, illegal xml character. How is CNF group created: If an object is created on one domain controller and an object with the same name is created in the same container on another domain controller before replication occurs, it creates an object name conflict. Active Directory automatically changes the relative distinguished name of the object with the earlier timestamp to a unique name. Reference: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/bb727059(v=technet.10)?redirectedfrom=MSDN.
13889	Internal configuration is displayed in the error message when user may not be able to connect to the AD server.
13767	Even when the single Monitor usage is set in the Endpoint, user is able to use multiple monitors.
13667	Users may not be notified about the destruction of desktops they are working on.
13334	In User Details, primary AD server details are displayed even when user is authorized from the secondary server.
13189	User friendly logs may not be displayed when controller tries to get the weight of SHD servers which may not be in a reachable state.
12972	While performing power operation, internal configuration is displayed in the Controller logs. Due to this, Administrator may not understand which desktop is affected.
12971	Connect desktop logs may not be user friendly.
12942	It may not be possible to delete vCenter server with 6000 or more VMs.
12871	AD User may not be able to log in to client with 256 character length password.
12792	Unpredictable behavior when Round robin load balancing is used with multiple teams.
12564	With UPN as logon attribute, following special characters may not work in username “|\@”`.
12561	User, Group or OU with pipe | character may not be supported in HyWorks so user logon may fail.
12547	Fetching OU in entitlements may fail if search string includes bracket ( ). Workaround: Search without bracket.
12539	If backslash() is included in username, user might have login issues while logging from client using UPN.
12518	Secondary controller hangs and may not be able to sync if primary controller is having a large amount of data (1L rows).
12517	Authorization with built-in and nested AD group may not work when Group retrieval type is set to 6. Workaround: Add entitlement using groups created manually and specific groups only.
12458	Desktop provisioning continues even when enough resources may not be available on desktop provider (VMware, Nutanix, Azure, Hyper-V).
12439	Unable to delete the AD when reservations created by AD user exists in RMS. Workaround: Delete all the associated objects from database before removing AD.
12436	User friendly errors may not be logged when cloning may fail and Administrator has to check respective Hypervisor or cloud logs.
12434	In many cases, test connection failure may not give detailed exception and thus more analysis of controller/ AD server is required.
12432	Controller may fail to fetch OU details if domain name provided in AD configuration may not be same as NetBIOS name.
12406	Desktop status is shown incorrectly as Not synced instead of Missing if configured DVM is deleted from the session provider.
12403	Misleading status of desktop VM, when user initiates shutdown internally. HyWorks may not support stop with de-allocation and because power-off is equivalent to stop with de-allocation, incorrect status is displayed.
12402	Status of Desktop agent may not be Responding, when multiple VMs with different IP addresses are present in HyWorks with same IP address.
12399	HyWorks Controller Logs : Username and APPS name may not be appearing in Log Details.
12384	Controller Installation on WVD: 1. IIS installation externally (Class not registered) 2. MSMQ installation externally ([RMSBackgroundWorker] while monitoring import events).
12341	Large deployments with 10000 users might fail due to application connection issues.
12328	AD server configuration may fail with error "The specified forest may not exist or may not be contacted." Workaround: Enable Skip attribute verification.
12319	Skip Login Attribute Verification settings may not be retained after updating AD server. Workaround: Check this configuration every time active directory configuration is updated.
12317	Session nodes logs provide misleading information when management nodes get switched ON.
12187	Incorrect error message shown to user when user account has expired in AD and Group retrieval type is set as '3'
11950	When the Controllers in HA cluster are configured with different ports than information about different ports may not be visible on client Workaround: Use same port for both the Controllers.
11884	Controller installation on other than default port may not get updated in management console configuration. Workaround: Update Management console configuration file to point to modified ports.
11784	[Azure] FQDN of cloned VM not reflecting on desktop VM page.
11780	On user session reconnection (re-login by user), controller may give reconnect of disconnected RDS session with no app running in some rare case, where user has closed the remote app before the disconnection.
11635	Session host server resource data may not get updated in real time and thus with adaptive load balancing server score will be updated after 30 second duration and may cause session from same server for some time until score gets updated.
11349	External load balancers must use HyWorks health probe service to detect node health, using port reachability may cause failure in detection of node down due to reasons such as licensing or SQL connection issues.
11334	Current weighted round robin may not work in the expected manner and may end up giving more session than expected.
11330	HyWorks uses Least connection load mechanism to serve the session when multiple sessions are requested at the same time. Due to this it might happen that multiple sessions may get served by the same server.
10575	Sometimes power off operation may not work with Nutanix dedicated session provider.
10327	Nutanix may keep old IP cache for some time and thus may result giving two IPs to HyWorks Controller causing issues. Workaround: Configure controller to use appropriate IP filtering.
9569	HyWorks may fail to authorize from a configuration using AD for authentication and built-in for authorization when UPN is used as the logon attribute.
9519	HyWorks sends logs to Accops Reporting Server or Syslog only once. Due to this, if it may fail to send logs, these logs are lost and reports may not show data points of that duration.
9493	HyWorks database restore may fail if the parameters - Username, password, SQL server version, location; configured in the new SQL server and the one which is to be restored are same.
8555	HyWorks may not work correctly with proxy authentication server e.g. Accops directory server.
8439	Shadow sessions are created using the connection profile of the actual user session. Due to this, it might happen that Shadow session may not have features it actually requires. E.g. In user session, connection bar is disabled but in shadow session it will be needed.
7478	Power off, Reset or suspend events may not be known to DVM agent and thus controller may not be notified immediately. Power status will be updated as per timeouts in HyWorks Controller.
7466	DVM Push may not work with SQL installed in Windows authentication mode only.
7082	Virtual IP for HA script may not support Ethernet name with space.
6380	Sometimes error log 'Object reference not set to an instance of an object' are generated, while restarting session host server.
6330	Logs may not be generated, when desktop may not be assigned to users if they are in maintenance mode on desktop pool.
6114	HyWorks Controller requires restart to refresh time zone details.
5729	In some cases, HyWorks Controller installer is unable to detect correct OS type & previous installation of controller.
5698	Sometimes, select checkpoint in desktop pool wizard may not work in single click and may require reselection.
5681	With large deployments Hyper-V connector may stop responding and communication issues may occur due to timeouts or SSL errors.
5278	In Desktop pools - OU with special character is shown with garbage characters and after saving changes to "on" string.
5273	HyWorks Controller may not support provisioning using templates with vCenter Server dedicated session provider.
5171	Previous entitlements with authorization AD can login into client when authorization is changed to built-in when removal of entitlements.
5083	Updated AD group membership change may not be getting fetched and thus failing to assign the desktops/apps runtime. Workaround: Use advanced settings to use alternate methods of fetching groups.
5026	Desktop pools and reservations become accessible once associated client groups are deleted.
4840	Gold master concurrent access may not be restricted, and hence multiple users can access desktops which supports multi-user sessions e.g. Linux desktops.
—	Deleting a node from HyWorks Controller active-active setup will require node to be destroyed before removal as on service start the node may again get added.
—	Database gets deleted after session node is uninstalled. This happens because by default database is removed after uninstalling node. Workaround: Uncheck Post installation database removal permission.
—	Base DN and User DN is mandatory for configuring directory searcher option as LDAP searcher from advance config.
—	As Controller requires FQDN to communicate with AD over SSL, if Controller needs to point to a specific AD instance, its host entries must be created otherwise Controller will continue to use first resolved AD. With multiple session manager nodes, this is required for all the nodes.
—	DVM Power Policies in DVM Pool may conflict with Auto-login (Auto-login will keep the machine powered-on whereas power policy may try to power-off the DVMs). Administrators are required to keep power policies as default or disabled in DVM pools if intending to have auto login on registered devices.

Bug ID	Description
65311	When editing a desktop pool, the folder name field in client settings may display a previously used name instead of being empty.
65292	When a folder name exceeding 100 characters is entered in Desktop Pool client settings, the resulting message may not clearly indicate the character limit.
65287	The folder name field in Desktop Pool client settings may not restrict special characters. Using special characters in the folder name may result in display issues on the client desktop.
65009	On xUbuntu 24.4, the 'File Manager' application icon may not be visible in HyShell after the application is saved, even if the icon is retrieved successfully.
64712	'Propagate to child' may not function as expected for HyLabs. A user added as Reservation Admin in a parent organization with AD propagation enabled may not be able to log in to HyLabs. Workaround: Assign the role directly within the specific organization.
64578	The Schedule wizard time picker may not display the 01-minute entry. Typing the value manually is a workaround.
60728	In some cases, HyLite may display a message indicating an issue during desktop power-on for on-demand capacity plan pools, even when desktops are available in HyWorks.
58023	The Registered Users page may take longer to load or may not display results under high concurrent login load when the registered user count is large.
54037	In some rare cases, user login may not complete when HyID is configured as the authentication server.
52996	Some filter options available on the Shared Hosted Desktop page, such as Customization Type and Desktop Agent Version, may not be currently available on the Personal Desktop page.
52652	The scheduled database backup may not trigger at the configured time and backup confirmation emails may not be received.
50407	When adding groups to a Master Pool entitlement, no warning is shown when a group with a similar name to an existing entry is added.
47908	When an on-demand desktop pool reaches maximum capacity, a notification may not be displayed on the deployment page. There is no functional impact on existing sessions.
46863	USB device class types in USB profile policy rules are identified by internal codes, which may make it difficult to identify the intended device class.
2042/ / 42540	Updating the username and password for ESXi/vCenter Server for the first time may fail due to an old key being used. Attempt to test the connection multiple times with the correct password, and it will show a success message in a couple of attempts.
42406	"Max Transferable Content Limit" value is getting Reverted to KB post updating of Connection Profile.
35390	Admin may not have option to change VM deployment settings (e.g. use last known settings) while recreating individual VMs from the Desktops page. Workaround: The configurations have to be changed from the desktop pool settings.
34487	Downloading logs may fail with too many logs in specified date range to download logs from HyWorks Controller Management Console.
34160	Different source IPs (Different when accessed using https://, https://, https://) are reported in logs, when management console is invoked using different addresses from the same server.
33778	With IIS_Users not having sufficient permissions on MMC folder inside of HyWorks Controller installation directory, the download logs option may not work and admin may not be shown any error messages. Workaround: The user permissions can be configured to make it working. The issue is not common and may have occurred because of explicit user/ permission removal.
32967	Admin may not be informed while selecting capacity plan associated desktops for scheduled actions but later actions are skipped because of the same reason.
32457	With the option 'Enable shortcut to minimize window [Alt + Ctrl + Shift] (Windows only)' enabled in connection profile: On clicking on restore button on the desktop session, the session gets minimized.
30072	The filtering option may not have option to filter-out physical desktops by its type.
27859	The time shown for "Info Last Updated on" in exported CSV of Desktops, may not be in IST or local timezone but in UST format.
27320	On exporting the pool details with CSV pool having display name in Japanese character are being imported with some garbage characters instead of Japanese strings.
26323	A misleading error "There is no authentication server configured" is shown while searching for a user with dot and auth-domain configuration is using built-in users.
24804	Management Console may fail to open, where its installed on Windows 2012R2 or lower with internal error 500.19. Workaround: Delete the following flag from web.config:.
22523	HyLite may not use the portal settings of HyWorks - Organization and thus all the customization have to be run via HySecure management console or HyLite configurations.
20961	Saving a session team after assigning more than 2.5K applications, management console may become inaccessible.
20959	Server page in Management console displays list of configured servers without IP address, if the ethernet card, holding the primary IP address used to configured server on HyWorks is deleted from the provider.
18827	To play session recording using HyWorks management console, either appropriate certificate must be configured on the SRMS server or exception should be added on user's machine. To add exception: Get the complete recording URL by inspecting recording icon, open it in browser, when the warning is displayed, accept it to proceed. Now, the media or recordings can be played.
18524	Files deleted from the SRMS server by the administrator may not be removed from the management console list and may fail to play.
14424	It may not be possible to exit the Desktop pool wizard if the Administrator has specified a VM name prefix with unsupported chars and later corrected it.
14405	Fetching Gold Master at the time of recompose results in an exception if the Gold Master name includes special characters.
14386	The error “Value may not be null. Parameter name: source" is shown when a user who may not have edit permission on the capacity plan tries to edit any existing plan.
14384	Change mode reflects with quite a delayed response on UI and requires manual refresh.
14371	The DVM Reset option is getting enabled and editable on selecting recompose for a non-persistent pool, though no function impact even when unchecked.
14365	On enabling Unassign User on VDI Logoff during Desktop pool creation, it is showing a warning that Hybrid mode may not be enabled even when the Hybrid mode is enabled.
14324	The adaptive load-balancing type option should not be visible for the Linux session team, as the monitoring service may not be implemented in Linux SHD.
14314	[Licensing] License is getting allocated to child Organization after 100% utilization in parent organization if licenses are all shared.
14313	[Licensing] Unable to update license if all the license is used (Reserved + Shared) with 100% utilized license to (all Reserved with unlimited check).
14268	Desktop VM page takes a long time to sync after deleting VM from it.
14258	The 'Browse' option should not be visible on the Server team page of the Linux application.
14236	In the Sessions Team page, the Session mode column may not be applicable for an unmanaged session team but is still displayed.
14228	At times, when the user launches an application, the SHD session is launched instead of the application.
14079	'Get icon automatically' option for application getting may fail for Windows 2k19 server.
14060	Desktop removal on editing desktop pool may not be working for Managed SHD pools.
13510	Select source VM test call may fail in case of multiple IPs.
13235	It is possible to decrease the configured count of Maximum capacity than the already deployed desktop count for the SHD cloning pool. Ideally, it should not be possible to decrease.
13207	The controller is truncating the LDAP user who has leading and trailing spaces, making it impossible to log in to the Linux SHD.
12977	Manual assignment may not work when the user selects Group in Desktop Pool.
11861	Some labels or column values are different than their actual value in the database, and thus searches on those columns may not work as expected.
7764	Dashboard - The License section graph gets refreshed with abrupt flickering.
7439	Dedicated providers are added when they are unreachable with an active flag.
7431	The HyWorks management console session persists, so the user is able to access the Console even without a password by using the previous and next buttons of the browser.
6712	“Limit Single Instance per user” should be enabled and non-editable for Linux applications.
6666	The device-based assignment gets removed for floating pools if the user from that device is logged off.
6614	Existing Custom URLs may not have the edit option.
6612	The Linux SHD server is added incorrectly as Windows SHD.
6125	MS Edge - Unable to scroll using the mouse wheel once the User Sessions/Logs page is opened.
5675	With too many authentication servers or shared hosted desktops, the dashboard appears with lots of blank space.
5284	Display name in the User Details page displays garbage data if the user belongs to OU with all special characters.
5277	Unable to add OU with pipe "|" operator in its name in Entitlements.
5276	Incorrect data is displayed in Total powered on ready desktop VMs (includes shared hosted desktops as well) in event logs produced in HyWorks Controller.
5275	In the Add Desktop Pool wizard, sometimes the source VM may not get selected in a single click with the Microsoft SCVMM/Hyper-V dedicated session provider.
5193	Desktop pool is saved without assigning desktop to user in desktop assignment tab when auto-assignment is disabled.
5191	Group entitlements / User entitlements may not be deleted from UI after deleting the group or user.

---

Upgrade Service Known Issues and Limitations

Bug ID	Description
5027	High memory consumption by Upgrade Service with too many upgrades initiated for DVM tools.