Help diagnose VBS requirements

[verdy-p]

Describe the bug

Please help diagnose the requirements for VBS

To Reproduce

Steps to reproduce the behavior:

1. Go to https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-vbs
2. Scan the list of features, and their requirements
3. Help identify the features that do not work (the Microsoft doc does not explain anything to end users but jsut drives to very technical documentations for OEMs)

Expected behavior

If a VBS feature is missing, idenify which one it is precisely, according to the model of CPU, this may be a problem of BIOS, or a problem in UEFI settings in the EFI BIOS, or a driver update missing, or a setting of the OS itself in the registry (including OS startup mode, conflicting (but unused) drivers that forces VBS to be turned off (notably when Windwos PnP tries to identify if a driver is appropriate to use, the self-test may use unsecure means such as DMA tests; this includes notably the simple presence of an Intel non-DCH drivers (*.INF + their declared *.SYS)) on the system, that MUST be uninstalled/deleted from the DriverStore, EVEN if these devices are NOT present on the PC or have been compeltely disabled in BIOS settings: these drivers still makes Wndows's PnP to tryt loading them and performing device presence/activation tests)

Desktop (please complete the following information):

• OS: Windows 10 or 11
• Version: (any version in Release, Insiders Beta and Dev channels)

Note that Microsoft, CPU vendors and BIOS and PC manufacturers use different terminologies: it is not easy at all to see if we have enabled "SLAT", or IOMMU or SMMMU. Often, BIOS manufacturers (all branches), do not detail these settings or oversmplify it, e.g: "security device", "safe boot", "secure boot", "hardware virtualization", energy settings (including Wake on LAN, S0/S1/S+ power modes, ErP). as well Windows stioll does not allow seeing EFI ios settings (notably if they expose their "firmware support for SMM protection" with the "WMST" table, or "IMAT". As well Windows provides NO help at all to allow identifying the device drivers that cause windows to NOT run VBS, even if it was configured.

A tool like MSINFO32.EXE does not help much as well