Fixed issues

When running the Configuration Wizard in silent (answer file) mode, database administrator credentials supplied in the answer file were sometimes cleared, causing the wizard to fail with no error message. The credentials are now preserved and a clear error is logged if a genuine credential problem occurs.

After upgrading from an earlier release, the Notifier service might leak database connections until the SQL Server maximum connection limit was reached, disrupting operations. Connections are now released correctly, and the service also handles oversized or malformed notification packets more robustly.

Target devices whose personality string length was an exact multiple of the packet size might get stuck after retrieving vDisk and cache details, never completing boot. These devices now retrieve their personality data correctly and continue starting up.

When setting up virtual machines with a vDisk write cache type other than "Cache in device RAM with overflow on hard disk", the Virtual Machines page no longer displays a misaligned layout with an unnecessary hard disk size field. The write cache disk size field is now hidden unless it applies.

Standard (non-administrator) users were previously unable to run PVS PowerShell commands because the environment details were stored in a protected registry location. PVS PowerShell now works for non-elevated users.

Previously, machines using MCS I/O might crash with a blue screen at boot because the disk filter driver was not loaded early enough in the boot sequence. The driver is now configured to load correctly during startup, so affected machines power on normally.

When the license server supports the newer LAS interface but the legacy v6 interface is unavailable or disabled, the Configuration Wizard now completes successfully instead of reporting a licensing failure. This prevents customers from appearing unlicensed on license servers where the legacy v6 interface has been removed.

Previously, if a license activation's expiration date passed while the product might not communicate with the license server, the farm might remain incorrectly treated as licensed. The farm is now correctly considered unlicensed once the activation expiration date has passed.

Previously the SSL Certificate page in the Configuration Wizard might fail to identify valid server certificates whose private keys were provided by the legacy CryptoAPI, preventing their selection. This step might result in an error:

The SSL certificate is not a valid certificate. It does not have a private key, or the private key cannot be exported.

Such certificates are now correctly detected as usable, and the wizard reports all certificate validation issues at once rather than stopping at the first error.

Previously, a missing server entry in the connection cache might cause an unhandled error during target-to-server communication. Lookups now handle absent entries gracefully so connections proceed reliably.

Previously the Configuration Wizard rejected valid server certificates whose trust relied on an intermediate certificate. This step might result in an error:

The SSL certificate is not a valid certificate. The certificate of the issuer cannot be found.

Such certificates are now accepted, with the wizard correctly locating the signing certificate in the chain or in the system certificate stores.

Previously, while some provisioning servers were upgraded and others were not, targets booting from virtual disks in private image mode or maintenance mode might fail to connect or reconnect, and some management commands failed with communication errors. Servers now communicate reliably throughout the upgrade, so these targets connect as expected and management commands succeed.

Previously, running Citrix Provisioning Services under the Network Service account caused features such as KMS activation, cached secrets clearing during vDisk promotion, and daylight savings domain trust handling to fail. These features now work as expected under the supported service account configuration.

Previously, in GCP environments, the Citrix Virtual Apps and Desktops Setup Wizard failed to remove server-side write-cache files from the store, wasting disk space when provisioning did not complete. These files are now removed correctly, even when provisioning fails.