Update 26220.8491: Win11 Update Freezes at 38% - Hypervisor Launch Failed (No VMX)

Title: Win11 Update Freezes at 38% - Hypervisor Launch Failed (No VMX)

Issue Description:

During the offline installation phase of the latest update, the process completely freezes at exactly 38 percent, requiring a hard reset to roll back. The system processor does not support hardware virtualization (no VMX support).

Diagnostic Signatures:

After the rollback completes, the System Event Log consistently shows Event ID 41 and 1001 from the hypervisor source, stating that the launch failed because virtualization features are not present or enabled in the system setup.

The Problem:

The offline installation engine seems to ignore host operating system configurations when it stages the update environment. Attempts to turn off the hypervisor launch type globally, disable virtualization security components, or change the driver startup parameters have no effect because the temporary update environment regenerates its own settings and tries to validate the hypervisor stack anyway. When it hits the missing hardware capability, it locks up.

Is there an official command-line deployment switch or an undocumented parameter for the update engine that forces it to completely skip the installation and migration of virtualization-dependent packages?