Hi Anjali
I think this kind of issue comes down to driver alignment between the host and the VM when you’re using GPU partitioning. Even if the host driver update went fine, the VM GPU drivers need to match the same branch and version family, otherwise you’ll see errors like “GPU partition adapter not available” or workloads dropping GPU access right after boot. The recommended process is to verify compatibility using GPU-P driver release notes from the vendor and cross‑check that both host and guest drivers are supported together. You can also use Device Manager or PowerShell (Get-VMGpuPartitionAdapter) to confirm the VM sees the adapter correctly.
Best practice before rolling updates is to keep a compatibility checklist: validate host driver version, confirm guest driver alignment, and test a pilot VM before patching the rest. If you’re running NVIDIA or AMD cards, their documentation usually lists supported host/guest driver pairs explicitly. Bottom line: don’t just patch the host make sure the VM drivers are updated in lockstep, and always validate with a test workload before production rollout.