This error appeared out of the blue on a vDisk maintenance patch day after the scheduled auto-update was set to start. I was given notice by a colleague that the latest vDisk had failed and thus was not updated. Upon further investigation, turns out that when the update VM was set to boot, it pulls an IP from DHCP but is never served a vDisk even though PVS creates the proper maintenance version.
Good news! This fix is about as simple as it gets by only needing a single new key added to the PVS registry on each PVS server.
Windows Registry Editor Version 5.00
That’s it, copy/paste that into your GPO’s or SCCM deployments and your PVS maintenance VM’s will boot without issue. No PVS server reboot required!