Group Policy Object (GPO) VM Migration
Overview
Some Group Policy Object (GPO) settings can interfere with driver injection, which is critical for a successful VM migration. GPO is a Windows-specific feature that manages system settings for Windows VMs. Temporarily disabling these policies ensures that driver injection can proceed reliably.
What is Affected by GPO
Driver installation cannot be done properly, leading to:
- Blue Screen of Death (BSOD)
- Windows VM getting stuck in boot loop
- Migration failures due to hardware driver conflicts
What to Do
Option 1: Disable via GUI - Step by Step
-
Open Group Policy Editor (
gpedit.msc) -
Navigate to Driver Policies
Go to:
Computer Configuration→ Administrative Templates→ System→ Device Installation -
Disable ALL restrictive policies here
Check and set these to Not Configured (or Disabled where applicable):
- 🚫 Critical ones (must fix)
Prevent installation of devices not described by other policy settings→ Set to Not ConfiguredPrevent installation of devices that match any of these device IDs→ Not ConfiguredPrevent installation of devices using drivers that match these device setup classes→ Not Configured
- 🚫 Critical ones (must fix)
Option 2: Sure Shot Way - Remove GPO via PowerShell
Remove-Item -Recurse -Force "C:\Windows\System32\GroupPolicy" -ErrorAction SilentlyContinueRemove-Item -Recurse -Force "C:\Windows\System32\GroupPolicyUsers" -ErrorAction SilentlyContinueRemove-Item -Recurse -Force "HKLM:\Software\Policies" -ErrorAction SilentlyContinueRemove-Item -Recurse -Force "HKCU:\Software\Policies" -ErrorAction SilentlyContinue
gpupdate /forceThe PowerShell method completely removes all local Group Policy settings. Use this only when GUI methods fail or when you need to ensure complete GPO removal.