The vendor has published 9 unique mention(s) for this bug: 1. Ensure that the store used for write cache files uses an SSD persistent disk instead of a Standard disk. 2. In GCP environments, Citrix Virtual Apps and Desktops™ Setup Wizard fails to remove server-side write cache files that are located in the WriteCache directory of Citrix Provisioning store. The write cache files are used to format the write cache when you first start the VMs. Therefore, the files must be removed even if provisioning fails to avoid wasting disk space. To resolve this issue, do one or both of the following: Ensure that the number of threads has a value of 20. Do one of the following: Set the value in the registry setting key: Computer\HKEY_CURRENT_USER\Software\Citrix\ProvisioningServices\VdiWizard\MAX_VM_CREATE_THREADS_PER_HYPERVISOR Remove the registry setting key. Ensure that the store used for write cache files uses an SSD persistent disk instead of a Standard disk. 3. In GCP environments, Citrix Virtual Apps and Desktops™ Setup Wizard fails to remove server-side write cache files that are located in the WriteCache directory of Citrix Provisioning store. The write cache files are used to format the write cache when you first start the VMs. Therefore, the files must be removed even if provisioning fails to avoid wasting disk space. To resolve this issue, do one or both of the following: Ensure that the number of threads has a value of 20. Do one of the following : Set the value in the registry setting key: Computer\HKEY_CURRENT_USER\Software\Citrix\ProvisioningServices\VdiWizard\MAX_VM_CREATE_THREADS_PER_HYPERVISOR Remove the registry setting key. Ensure that the store used for write cache files uses an SSD persistent disk instead of a Standard disk. 4. In GCP environments, the Citrix Virtual Apps™ and Desktops Setup Wizard fails to remove server-side write cache files that are in the WriteCache directory of the Citrix Provisioning store. The write cache files are used to format the write-cache when you first start the VMs. Therefore, the files must be removed even if provisioning fails to avoid wasting disk space. To resolve this issue, do one or both of the following: Ensure that the number of threads has a value of 20. Do one of the following: Set the value in the registry setting key: Computer\HKEY_CURRENT_USER\Software\Citrix\ProvisioningServices\VdiWizard\MAX_VM_CREATE_THREADS_PER_HYPERVISOR Remove the registry setting key. Ensure that the store used for write-cache files uses an SSD persistent disk instead of a Standard disk. 5. Ensure that the store used for write-cache files uses an SSD persistent disk instead of a Standard disk. 6. In GCP environments, the Citrix Virtual Apps™ and Desktops Setup Wizard fails to remove server-side write cache files that are in the WriteCache directory of the Citrix Provisioning store. The write cache files are used to format the write cache when you first start the VMs. Therefore, the files must be removed even if provisioning fails to avoid wasting disk space. To resolve this issue, do one or both of the following: Ensure that the number of threads has a value of 20. Do one of the following: Set the value in the registry setting key: Computer\HKEY_CURRENT_USER\Software\Citrix\ProvisioningServices\VdiWizard\MAX_VM_CREATE_THREADS_PER_HYPERVISOR Remove the registry setting key. Ensure that the store used for write-cache files uses an SSD persistent disk instead of a Standard disk. 7. 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. 8. In GCP environments, the Citrix Virtual Apps and Desktops™ Setup Wizard fails to remove server-side write cache files that are in the WriteCache directory of the Citrix Provisioning store. The write cache files are used to format the write cache when you first start the VMs. Therefore, the files must be removed even if provisioning fails to avoid wasting disk space. To resolve this issue, do one or both of the following: Ensure that the number of threads has a value of 20. Do one of the following: Set the value in the registry setting key: Computer\HKEY_CURRENT_USER\Software\Citrix\ProvisioningServices\VdiWizard\MAX_VM_CREATE_THREADS_PER_HYPERVISOR Remove the registry setting key. Ensure that the store used for write cache files uses an SSD persistent disk instead of a Standard disk. 9. In GCP environments, the Citrix Virtual Apps™ and Desktops Setup Wizard fails to remove server-side write cache files that are in the WriteCache directory of the Citrix Provisioning store. The write-cache files are used to format the write-cache when you first start the VMs. Therefore, the files must be removed even if provisioning fails to avoid wasting disk space. To resolve this issue, do one or both of the following: Ensure that the number of threads has a value of 20. Do one of the following: Set the value in the registry setting key: Computer\HKEY_CURRENT_USER\Software\Citrix\ProvisioningServices\VdiWizard\MAX_VM_CREATE_THREADS_PER_HYPERVISOR Remove the registry setting key. Ensure that the store used for write-cache files uses an SSD persistent disk instead of a Standard disk. Latest urls for this bug: 1. https://docs.citrix.com/us/en/provisioning/2206/whats-new/known-issues.html 2. https://docs.citrix.com/us/en/provisioning/2209/whats-new/known-issues.html 3. https://docs.citrix.com/us/en/provisioning/2212/whats-new/known-issues.html 4. https://docs.citrix.com/us/en/provisioning/2303/whats-new/known-issues.html 5. https://docs.citrix.com/us/en/provisioning/2305/whats-new/known-issues.html 6. https://docs.citrix.com/us/en/provisioning/2308/whats-new/known-issues.html 7. https://docs.citrix.com/us/en/provisioning/2402-ltsr/known-issues.html 8. https://docs.citrix.com/us/en/provisioning/2407/whats-new/known-issues.html 9. https://docs.citrix.com/us/en/provisioning/2411/whats-new/known-issues.html 10. https://docs.citrix.com/us/en/provisioning/2511/whats-new/known-issues.html