PVS image published from App Layering gives a BSOD with inaccessible boot device error

Please note that there are any number of possible ways to get a PVS boot failure. This is only one.

A cache disk on the Target device can cause this problem. When using a cache disk, the disk must also be added to the platform layer.

The first thing to do is to Add Version to your Platform Layer (or create a new one), and attach a copy of the Cache Disk that your Target Machines are using to the Packaging Machine. This allows Windows to identify and install that exact disk in the Platform Layer, so that images published that include that Platform Layer will have already seen that disk once. Use the actual Cache Disk that is attached to your Target Machine template if possible to ensure that the signature matches.

Restart when prompted. When you double-click on “Shutdown for Finalize”, let the machine shut down, but do not go back to the Management Console (LMC) and run Finalize yet. You must remove that extra disk from the Packaging Machine before you Finalize; otherwise, Finalize will fail because it’s looking at the wrong disk.

Once the extra disk has been removed, do not power the Packaging Machine on again. Run Finalize from the LMC. Then use that new Platform Layer with images for those Target Machines.

One additional consideration for the Target Machines themselves: make sure the Cache Disk itself is attached to the Target Machine at device node SCSI 0:0. It’s possible to attach the disk to any SCSI port, but if it’s anywhere other than SCSI 0:0, Windows will likely prompt you to restart even though the Platform Layer has definitely seen this disk before – likely on SCSI 0:2. Apparently the Cache Disk must be on the first unused SCSI port.

PVS Target Device software missing from the platform layer will also cause this issue. Just because they say they installed PVS in the platform layer does not mean they installed the correct piece of PVS.


Leave a Reply