Symptoms
Cannot recompose a new desktop pool or an existing pool in View ManagerRecomposing a desktop failsYou see the error: View Composer agent initialization state error (9): Failed to relocate disposable (waited 0 seconds)
Cause
This issue occurs if the paging file is disabled on the parent virtual machine or when the paging file has been modified to include additional drives, such as D:\.
Resolution
To resolve this issue, enable paging on the parent virtual machine.For more information, see:
Windows XP – To change the size of the virtual memory paging fileWindows Vista and Windows 7 – Change the size of virtual memory
Note: The preceding links were correct as of December 12, 2013. If you find a link is broken, provide feedback and a VMware employee will update the link.
Workaround
Legacy Details:
Persistent Disks & Linked Clones have been deprecated on the latest editions of Horizon since 2020. Persistent Disks are no longer supported in Horizon.
A move to a new profile technology is not contingent on a move to Horizon 8 and can be initiated in advance of upgrade to Horizon 8 as a separate task.Please see Ensuring a successful migration from Horizon 7 to Horizon 8 (89840) for additional advice.
We recommend you migrate from Horizon 7 to Horizon 8 as soon as possible. Horizon 8 offers numerous improvements in performance, scale, and experience for both Administrators and end users.
Related Information
If the parent machine is part of a domain:
Remove the parent machine from the domain. For more information, see How to Remove a Computer from a Domain.
Note: The preceding link was correct as of September 18, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.
Enable paging on the parent virtual machine.Log in to the parent virtual machine as Administrator and delete all cached profiles under C:\Users, except the Administrator profile.Take a new snapshot of the parent virtual machine and recompose the affected pools to this snapshot.
This issue may also occur if Bitlocker is installed or the policy for Bitlocker is enabled on the parent virtual machine.
To disable the BitLocker Drive Encryption service:
Click Start > Run, type Service.msc, and press Enter.Right click the BitLocker Drive Encryption service and click Stop.
To disable the policy for Bitlocker:
Click Start > Run, type gpedit.msc, and press Enter.Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Bitlocker Drive Encryption > Removable Data Drives.Deny write access to removable drives not protected by Bitlocker.Right-click the option and click Edit > Disable.Click OK.
