iPac Master Node Unresponsive

Tech Note: TN2606
Product: iPac
Version: All
Date Added: 2026-11-10

Issue

iPac Master Node unexpectedly freezing or crashing after update or third-party software installation.

Solution

The Windows nodes are VMs running on our Proxmox host. A Windows VM is running on a hypervisor (KVM). The nodes themselves must not run the Windows hypervisor. Any Windows feature that starts its own hypervisor inside it (Hyper-V, Virtual Machine Platform, WSL2, Windows Sandbox, memory integrity/VBS) is trying to run virtualization on top of virtualization. This either fails or is unstable.

Diagnosis

Run these in an admin PowerShell inside the iPac Master Node.

# 1. Boot setting: Auto = Windows hypervisor loads when a feature needs it; Off = never; empty = not set
bcdedit /enum | Select-String hypervisorlaunchtype

# 2. Hypervisor-related Windows features
Get-WindowsOptionalFeature -Online | Where-Object FeatureName -match "Hyper-V|VirtualMachinePlatform|HypervisorPlatform|DisposableClientVM" | Select-Object FeatureName, State

# 3. VBS: status 2 = running; services 1 = Credential Guard, 2 = memory integrity
Get-CimInstance -Namespace root\Microsoft\Windows\DeviceGuard -ClassName Win32_DeviceGuard | Select-Object VirtualizationBasedSecurityStatus, SecurityServicesRunning

# 4. Confirm it is a VM (Manufacturer/Model show QEMU or similar)
Get-CimInstance Win32_ComputerSystem | Select-Object Manufacturer, Model

It is correctly configured when launch type is Off or not set, every feature in check 2 is Disabled, and check 3 returns 0 / 0.

Resolution

In the iPac Master Node (admin PowerShell):

Disable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform
bcdedit /set hypervisorlaunchtype off

Then shut the iPac down fully.