01 Windows 10 & 11
Windows 10 (22H2) or Windows 11 (21H2–24H2+)
Anti-Winver supports Windows 10 Build 19045 (22H2) and Windows 11 Builds 22000 through 26100+ (24H2). Earlier builds lack the system architecture required for module initialization and identity virtualisation.
STEP 01 — CHECK YOUR CURRENT BUILD
- 1. Press Windows Key + R
- 2. Type
winverand press Enter - 3. Confirm Build 19045+ (Windows 10) or Build 22000+ / 26100+ (Windows 11)
STEP 02 — UPGRADE TO WINDOWS 11 24H2
Windows Update (easiest)
Settings → Windows Update → Check for Updates
Clean install via ISO
Download the official ISO from Microsoft and perform a clean installation.
GET WINDOWS 1102 Secure Boot
Secure Boot Configuration
Anti-Winver's check is state-aware. The green/red status means different things depending on whether Anti-OS is active:
Anti-OS pre-loader is active. Secure Boot is emulated by the system layer — green means it is operating correctly. No action needed.
Anti-OS not yet active. Secure Boot must be physically OFF in BIOS before setup. Green = off (correct). Red = on (disable first).
STEP 01 — CHECK CURRENT STATE
- 1. Press Windows Key + R, type
msinfo32, press Enter - 2. Check BIOS Mode (must say UEFI) and Secure Boot State
STEP 02 — DISABLE SECURE BOOT IN BIOS (PRE-INSTALL)
Restart and enter BIOS (Del / F2 / F10). Or from Windows:
→ Troubleshoot → Advanced options → UEFI Firmware Settings
Find Secure Boot under Boot or Security tab → set to Disabled. Save with F10.
⚠ Legacy BIOS Users
If BIOS Mode shows LEGACY, convert your drive from MBR → GPT first using mbr2gpt /convert /allowFullOS, then switch BIOS mode to UEFI. Skipping this will prevent Windows from booting.
03 TPM 2.0
Trusted Platform Module 2.0
TPM 2.0 is required by Windows 11 and used by Anti-Winver during its session checks. It must be present, active, and version 2.0.
STEP 01 — CHECK TPM STATUS
- 1. Press Windows Key + R, type
tpm.msc, press Enter - 2. Check the status message and Specification Version
STEP 02 — ENABLE TPM IN BIOS
Restart into BIOS, find TPM under Security or Advanced tab:
Save with F10. Rerun tpm.msc to confirm.
⚠ BitLocker Warning
If BitLocker is active, changing TPM settings may trigger a recovery key prompt. Suspend BitLocker first: Control Panel → BitLocker Drive Encryption → Suspend protection.
04 DSD
System Compatibility Layer
Windows requires all system components to meet specific compatibility requirements before they can operate. Anti-Winver's system layer ensures these requirements are met automatically during setup — no manual configuration needed.
How it works
During startup, the Anti-OS pre-loader configures system integrity settings before Windows initialises. This takes effect for the entire session without modifying any files on disk.
DSD IS RED — WHAT TO DO
DSD depends on the Anti-OS pre-loader being active and the system having been configured correctly on this boot. If DSD is red:
- 1. Check that EFI-B is green — if not, complete guide 05 first
- 2. If EFI-B is green but DSD is red — system configuration may not have applied. Reboot and check again
- 3. If the issue persists after a clean reboot — contact support with your Windows build number
⚠ Do not use test signing mode
Do not use bcdedit /set testsigning on as a workaround. It does not satisfy the compatibility requirements Anti-OS enforces and may be flagged by security software.
05 EFI-B
Anti-OS Pre-Loader
The Anti-OS pre-loader is the foundation of Anti-Winver. It initialises before Windows loads, ensuring the system is in the correct state for full identity virtualisation to operate. Without it, other components cannot activate.
STEP 01 — PREREQUISITES BEFORE INSTALL
STEP 02 — INSTALL VIA THE MANAGER
- 1.Open Anti-Winver Manager as Administrator
- 2.Log in with your licence key
- 3.Navigate to the System Check tab — confirm Windows, TPM, and Secure Boot are green
- 4.Click Install Anti-OS — the Manager runs safety checks, securely backs up your existing configuration, then deploys the pre-loader
- 5.Reboot when prompted
- 6.After reboot, return to the Manager — EFI-B, DSD, and Anti-OS should all be green
⚠ Restore is always available
The Manager's Revert Profile function fully reinstates your original configuration from a verified backup baseline. The restore process is triple-verified before completing.
06 Anti-OS
Anti-OS Core Service Active
This check confirms the Anti-OS system component is loaded and active. It is responsible for hardware identity virtualisation in real time and only activates once all other requirements are satisfied.
ANTI-OS IS RED — DIAGNOSIS
EFI-B and DSD are also red
Anti-OS pre-loader is not active. Complete guide 05 (EFI-B) first — Anti-OS will activate automatically on the next boot.
EFI-B is green, DSD is green, Anti-OS is red
Pre-loader is active but the system component did not initialise. Most likely cause: a security scan intercepted the component file. Temporarily pause real-time protection, then use the Manager to re-deploy.
Service was active but session expired
Open the Manager and apply your profile from the main tab to re-activate the session.
07 Drive Space
Windows Drive Space
Anti-Winver requires at least 50 MB free on your Windows system drive (usually C:\) to deploy its components. The actual space used is small — this threshold is a safety margin. The Manager displays your exact free space next to this check.
DRIVE SPACE IS RED — FREE UP SPACE
Disk Cleanup
Storage Sense
Temp files
After freeing space, return to the Manager and click Refresh on the System Check tab.