Hello All. Hoping the community can help me with a PVS/UEFI boot problem. I've create a new image from a master device. After the imaging process, if I remove the original drive from the vm and try to boot from vdisk, I get "A required device isn't connected...". I am using a boot CD to connect the target device to PVS, and I can see that it is indeed communicating to PVS on startup. If I re-attach the original disk, and still leave the target device in standard mode (e.g. boot from image and not boot from hard drive), it boots up but shows two disks mounted in Disk Manager - the original hard drive which is set as the boot drive, as well as the vdisk. I have followed Carl Stalhood's guide and I dont see what I am missing in the imaging process or after the image has been created. It seems like either Windows or the EFI boot record for the VM is still aware of the original boot drive and I am not sure where in the process that is supposed to be updated.

Try this: Keeping the original HDD attached to the vm, boot the VM using the vDisk in private mode (or maintenance mode), ensuing the OS is using PVS to boot. You will see 2 drives as you mentioned. while the image is booted in private mode, remove the second drive (original drive) from the VM (hot remove). at this point you will only have c: drive showing which was streamed via PVS. Shutdown and start up again and it should boot as normal without the error message "a required device isn't connected"...

Did you change the bios to boot from HD last as well as mark the vdisk partition as active. I have found many times that the imaging process does not mark the vdisk as active

@Amir Joseph Sayes When I boot up the device with the original disk attached, that drive is active and has the letter c:. The PVS disk is mounted as F: and I can't right click and set it as active. Hot-removing the hard disk in this state crashes the VM. Any other thought on how to set the vdisk as active?

I thought your original disk was being mounted as something else apart from C:… After the vdisk was created, have you booted it in private mode and was it set in the console to boot from vdisk? basically you are getting this error because the OS is expecting the original hard drive. If you are stuck, there are some youtube videos around PVS reserve imaging, which overlaps with what you are trying to do. Might be useful

I'm seeing a thread in the Citrix forums where someone said the image creator always produced a faulty vhdx when doing "Create vdisk". They suggested using the "Create an image file" instead. I am going to try that.