Known Issues and Limitations of Connectors or Session Providers
- 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.
Accops Hyper-V Manager (AHM), Hyper-V Connector (Hyper-V/SCVMM) Known Issues and Limitations
| Bug ID | Description |
|---|---|
| 69716/ 69706 |
Preserving the MAC address on the recompose feature is not supported with Hyper-V. |
| 69657 | After adding Hyper-V hosts to AHM, VMs on the newly added Hyper-V host(s) may not be automatically synchronized or refreshed, and AHM may continue to display previously cached data. For fresh configurations, the VM count may remain zero until a manual refresh is performed. Workaround: Update the connector to manually initiate synchronization after adding Hyper-V hosts as members. |
| 69576 | After adding Accops Hyper-V Manager (AHM) as a connector and not updating it at least once, attempting to add a desktop pool with the type set to dynamic may cause the loader to display indefinitely. Workaround: Update the connector to manually initiate synchronization after adding Hyper-V hosts as members. |
| 69550 | The behavior while adding a standalone Hyper-V host is not very intuitive and differs from the behavior observed when adding Hyper-V host(s) from a cluster. This does not have any functional impact. |
| 69548 | While adding hosts fetched from a cluster, unselecting all hosts, and proceeding still adds the host used for fetching the cluster details. This behavior is currently not intuitive, but does not have any functional impact. |
| 67967 | Desktop pool cloning or recompose operations involving multiple desktop pools with different source VMs execute sequentially instead of in parallel when using the Accops Hyper-V Manager connector. |
| 67658 | Console connection to AHM may fail after VMs are migrated from one Hyper-V host to another within the cluster. |
| 67611 | Cloning a source VM may fail if the VM was created in Hyper-V and has locally attached hardware resources, such as ISO-mounted CD/DVD drives. Removing all locally attached resources and retrying provisioning should resolve the issue. |
| 65978 | When multiple pools are deleted simultaneously, and a member Hyper-V server is unresponsive, VM deletion in SCVMM may fail and not be reattempted. Workaround: Manually remove any residual VMs from the hypervisor after deleting the pool. |
| 61211 | In a rare case, the network is not showing as connected for cloned VMs in SCVMM, even though the source VM (Gold master) has a network with a VLAN ID attached. |
| 23613 | The controller cannot process Hyper-V VMs with special character sequences "< ?" or "[ ]" in their names. An example of a processing failure is being unable to obtain an IP address. |
| 15298 15330 |
Hyper-V or SCVMM (Hyper-V connector) may occasionally become unreachable without providing relevant logs on the HyWorks Controller. Timeouts are sometimes observed. |
| 15249 | When deleting a provisioned desktop pool from an inactive Hyper-V connector, the actual VMs in Hyper-V or SCVMM are not deleted, and the administrator is not notified. |
| 14574 | Operational failures can occur if parallel operations (deleting VMs and provisioning) are initiated on Hyper-V 2012 R2 or 2016. Recommendations: Follow careful provisioning and operational procedures when working with Hyper-V. |
| 14501 | Hyper-V 2012 - Cloning will fail with an object reference error if the source VM name has the following special characters: ` ~! $ % ^ & ( ) [ ] { } . |
| 14419 | [Hyper-V/ SCVMM] Cloning failures due to special chars in Gold Image (Source VM) name or Snapshot name (Feature: Clone from Snapshot) Recommendations: The following special characters should not be used in Hyper-V or SCVMM source VM name or snapshot name. [For SCVMM] Characters not supported in - VM name: space,,?,:,<,>,/,|,\,",',{,} Characters not supported in Snapshot name: `,&,\,",' [For Hyper-V] Characters not supported in VM name: ,?,:,<,>,/,|,\,",',{,},[,]. |
| 14383 | Sometimes, cloning fails in Hyper-V with the error: "Creating the disk at location Workaround: Reboot the Hyper-V server. |
| 14382 | Installer cancellation fails with an invalid error when the Hyper-V Connector setup is canceled in the Platform Configuration Window. |
| 14381 | Hyper-V connector installer proceeds with the local system account even when credentials are given as administrator without a domain name Workaround: Provide credentials as hostname\username. |
| 14380 | The Hyper-V connector installer takes a long time to set up credentials (when not using the Local System Account). |
| 14345 | Hyper-V cloning will not happen in parallel; it happens one after another because we are taking locks on clone tasks. |
| 14629 | Clone from Snapshot fails with an error: "Unable to acquire a 'Delete' lock on object of type VirtualDVDDrive." |
| 14624 | Sometimes, the SCVMM provider goes into the Not Reachable state with the error "The connection to the VMM management server localhost was lost". This happens due to a heavy load on SCVMM, which prevents it from accepting test connections from the connector. |
| 6877 | Direct upgrade of Hyper-V connector is not supported and requires uninstallation of the previous version Recommendation: Uninstall any previous version and install the new version. The Hyper-V connector does not retain any information, so data will not be lost during uninstallation and reinstallation. Take a backup of the custom configuration before uninstallation. |
| 6874 | Known Issues - Hyper-V/SCVMM |
| 6873 | In a Hyper-V 2016 VM, the DNS name is always shown as the Hyper-V server's hostname. |
| 5420 | Cloning fails if communication with the Hyper-V Connector (SCVMM) fails. |
| 3294 | Cloning fails on SCVMM 2016 due to a task lock issue. The issue occurs when Gold Image is modified from Hyper-V and a local DVD drive is attached. Recommendation: Use a gold master with no local DVD drive attached. |
Azure Connector Known Issues and Limitations
| Bug ID | Description |
|---|---|
| 62877 | When cloning from an image on Azure, the data disk type is not copied from the Gold Master. Cloned VMs may have a different disk type than the source. |
| 61325 | The Suspend (Hibernate) action is displayed for all configured Azure VMs, regardless of whether hibernation is enabled on the VM. If initiated on a VM where hibernation is not configured on Azure, the operation may not complete. |
| 58878 | On Azure Local, the controller does not log the acquisition of the Gold Master lock at the start of cloning. When two pools use the same Gold Master simultaneously, the logs do not make it clear why the second pool's cloning is delayed. |
| 58574 | On Azure, recomposing a pool where the original cloning method was 'Clone from Image', with image cloning disabled and Preserve Network enabled, may not complete as expected. This specific combination of settings is not supported. |
| 46496 | For VMs on the Azure provider, the DNS name may not always be available in the HyWorks database, which may affect certain operations, such as Active Directory unregistration. |
| 59003 | After upgrading from an earlier version to HyWorks 3.6 SP1, image (version) creation fails for Linux Gold Masters that were already generalized on Azure during image-based cloning. |
| 16160 | Limitations of disk encryption with HyWorks on Azure: 1. If the controller service goes down when encryption is running, then the status will not get updated, and the only workaround is to recreate the VM. 2. Disk encryption with Linux VMs is not yet supported on MS Azure. 3. SSE (CMK / CMK+PMK) based encryption is done after customization. |
AWS Connector Known Issues and Limitations
| Bug ID | Description |
|---|---|
| 60900 | When cloning from a Gold Master VM on AWS with a non-elastic public IP, the public IP configuration may not be carried over to the cloned VMs, leaving them unreachable. Workaround: Assign an Elastic IP to the Gold Master before cloning, or configure the pool to use internal IP addressing. |
| 26461 | The virtual IP feature for shared-hosted desktops or virtual applications is not supported by any cloud provider, i.e., Azure, AWS, or Oracle. |
Nutanix Known Issues and Limitations
| Bug ID | Description |
|---|---|
| 62942 | In the Nutanix snapshot cleanup utility (a custom tool for removing residual snapshots), confirming snapshot deletion with option 3 (select by UUID) may cancel the operation rather than delete the selected snapshot. |
| 65381 | On Nutanix Prism Element with V2 API, desktop pool cloning may not complete in some cases. The pool must be updated to restart cloning. Accops recommends using Nutanix Prism Central with API V4 for improved compatibility. Refer to the Nutanix configuration guide. |
| 64340 | On Nutanix, VMs with multiple disks on different storage containers may not be handled correctly during recompose or migration, and the operation may not complete as expected. |
| 64186 | On Nutanix Prism Element with V2 API, the controller may log a deletion warning for each VM individually during pool deletion. Accops recommends using Nutanix Prism Central with API V4 for improved compatibility. Refer to the Nutanix configuration guide. |
| 64133 | Cloning of subsequent batches may fail on Nutanix Prism Central with API V4. This is not a HyWorks issue and is under discussion with Nutanix. |
| 63955 | On Nutanix Prism Central with API V4, batch shutdown during recompose may take longer than expected. This behavior is associated with Nutanix task execution and may vary across environments. |
| 63631 | Based on the Nutanix Prism Central deployment size, the HyWorks batch size should be configured in Advanced Settings. A higher batch size may cause functional failures, such as deployment or power operation errors. |
| 63559 | With Prism Central configured with API V3, snapshot deletion may fail during VM deletion. Logs may suggest manual clean-up of orphaned snapshots. This is due to the absence of native snapshot deletion APIs in API V3. Accops recommends using Nutanix Prism Central with API V4 for improved compatibility. Refer to the Nutanix configuration guide. |
| 62954 | In Nutanix Prism Central with API V3, snapshots may not be automatically cleaned up when VMs are deleted from HyWorks. Accops recommends using Nutanix Prism Central with API V4 for improved compatibility. Refer to the Nutanix configuration guide. |
| 62341 | On Nutanix Prism Central with API V4, expired recovery points remain listed and selectable during pool creation, Gold Master addition, and reservation creation. |
| 57751 | Adding both Nutanix Prism Central and its managed Prism Element as session providers in HyWorks may cause functional failures due to duplicate VM entries. Accops recommends configuring only one of the two as a session provider. |
| 57031 | When both Nutanix Prism Element and Prism Central are configured as session providers simultaneously, recompose operations may not complete as expected. Accops recommends using Nutanix Prism Central with API V4 for improved compatibility. Refer to the Nutanix configuration guide. |
| 30866 | With Nutanix as the connector, the hostname of the configured VMs is not shown in the HyWorks Controller Management Console. Workaround: Configure the VM Scale booster to retrieve this information via the DVM Push feature. |
VMware Connector Known Issues and Limitations
| Bug ID | Description |
|---|---|
| 58678 | Deployment profiles are not supported for Move to Version operations on VMware. VMs created during Move to Version may use default deployment settings. |
HPE VM Essentials Known Issues and Limitations
| Bug ID | Description |
|---|---|
| 67965 | With the HPE VM Essentials connector, the operating systems (RHEL v9.4, Rocky Linux v8.10, Ubuntu/xUbuntu 24) have been found to have issues during provisioning and thus are not listed as supported.The issue is being tracked with the HPE team, and OS support will be reevaluated with any fixes or steps from the HPE team. |
| 67796 | Intermittent delays of 4–5 minutes may occur during IP assignment on cloned VMs with the HPE connector, resulting in slower VM preparation for end users. |
Red Hat OpenShift Known Issues and Limitations
| Bug ID | Description |
|---|---|
| 67625 | With OpenShift using pod networking in masquerade mode, all VMs may identify the same IP range, such as 10.0.2.x. This behavior may affect modules that rely on detected IP addresses. For example, HyWorks Controller nodes use detected IPs for high-availability checks, and incorrect IP detection can cause failures. Refer to the OpenShift deployment preparation documentation for more details. |
Proxmox Known Issues and Limitations
| Bug ID | Description |
|---|---|
| 67431 | Node change is not supported for linked clones with the Proxmox connector. This limitation is introduced to avoid cloning failures, as linked clone source VMs may contain locally attached media or dependencies. |