Why check first?

The GPMBoxPlus Pre-Install Checker (GPMBoxPlusChecker.exe) is a small tool that tells you whether Windows on your PC will allow the GPMBoxPlus host drivers to load. The host drivers are not yet signed by Microsoft (Microsoft Partner registration and driver submission are in progress), so if your PC does not meet the requirements, installation still succeeds but no virtual machine can start. Running the Checker first tells you exactly what to fix up front, so you don't have to reinstall repeatedly.

Download and run the tool

Download GPMBoxPlusChecker.exe
Download it from gpmboxplus.com. It is a single exe file that runs right away on Windows 10/11, since .NET Framework 4.8 is already built in. No installation is needed.
Run the tool
Double-click GPMBoxPlusChecker.exe. A standard user account is fine. To also read the driver block history, click Run again as Administrator.
The interface is available in two languages, English (default) and Vietnamese. Switch languages in the top-right corner of the window.

Reading the results

The verdict at the top of the window shows one of three states:

Verdict	Meaning	What to do
This PC is ready for GPMBoxPlus	Windows will load the host drivers normally.	Continue to installation.
GPMBoxPlus can be installed, with some caveats	The drivers can load, but some items may slow down virtual machines or cause errors.	Review the yellow items. Fixing them before installing is recommended.
GPMBoxPlus cannot be installed on this PC yet	Windows will block the drivers, or the PC is missing a required condition.	Fix the red items — most commonly Secure Boot is on — then click Check again.

Each check is labeled PASS INFO WARNING FAIL, together with the value detected on your PC, why the check matters and, if it did not pass, a How to fix section.

The 16 checks

Check	Level	Passes when	How to fix
Secure Boot	Required	Off, or the PC uses Legacy BIOS	Disable Secure Boot in UEFI (see the Disable Secure Boot page).
Driver signature enforcement mode	Info	Normal or Test mode	Test mode is not required.
Driver block history (CodeIntegrity, 30 days)	Warning	No VBox/GPMBox drivers have been blocked	Click “Run again as Administrator” to read the log. If any events occurred after your most recent configuration change, send the report to support.
Windows architecture	Required	x64	ARM64/x86 are not supported.
Windows version	Required	Windows 10/11 client	Upgrade to Windows 10/11. Windows Server has not been tested.
Memory Integrity (HVCI)	Warning	Off	Windows Security → Device security → Core isolation details → Memory integrity = Off → restart.
Smart App Control	Warning	Off or not present	Windows Security → App & browser control → Smart App Control settings → Off. Note: once turned off, it can only be turned back on by reinstalling Windows.
App Control (WDAC) policy / S mode	Warning	Not present	Corporate PCs: ask IT to add GPMBoxPlus to the allow list. S mode: Settings → System → Activation → Switch out of S mode.
Hardware virtualization (VT-x / AMD-V)	Required	Enabled	Enable “Intel Virtualization Technology” or “SVM Mode” (AMD) in BIOS/UEFI.
Windows hypervisor (Hyper-V / VBS / WSL2)	Warning	Not running	Turn off Memory Integrity, run bcdedit /set hypervisorlaunchtype off as Administrator, then restart.
BitLocker on C:	Warning	Off / suspended, or Secure Boot already off	Save your recovery key and suspend BitLocker before disabling Secure Boot.
RAM	Required	≥ 8 GB (4–8 GB: warning)	At least 4 GB is required.
Free space on C:	Required	≥ 20 GB (2–20 GB: warning)	Free up space, or store virtual machines on another drive.
Pending restart	Warning	None	Restart the PC and run the tool again.
Cross-signed driver trust policy (Windows 11 24H2+)	Info	Not applicable	On build 26100 or later: keep an eye on the Driver block history item after installing.
Administrator rights	Info	Yes	Not required. The installer will show a UAC prompt itself.

Buttons in the tool

Button	What it does
Check again	Re-reads the configuration after you have fixed an item.
Copy report	Copies the full results as text to the clipboard so you can send them to support.
Run again as Administrator	Required to read the CodeIntegrity log, which records drivers that Windows has blocked.
Restart to UEFI…	Restarts directly into the UEFI setup screen so you can disable Secure Boot. Asks for confirmation and UAC.

Sending a report to support

If you have followed every step and virtual machines still won't run, click Run again as Administrator, then click Copy report and send the contents to GPM support. The report contains everything needed (Windows version, Secure Boot status, HVCI, blocked-driver log…) to quickly pinpoint the cause.