SETUP GUIDE

GETTING STARTED WITH CRAW/WARE

THANK YOU FOR CHOOSING US AS YOUR PROVIDER,
PLEASE FOLLOW THIS GUIDE VERY CAREFULLY.

1. System requirements

Discord overlay and legacy overlay must be enabled for the software to appear and function.

| OS | Windows 10 64-bit (1909+) OR Windows 11 (any build)

| CPU | 64-bit Intel with VT-x OR 64-bit AMD with SVM

| Firmware | UEFI (Secure Boot disabled, see below)

| RAM | 8 GB

| GPU | Any DX11-capable card

| Disk | EFI System Partition present (default on any UEFI Windows install)

Legacy/BIOS-mode Windows installs (MBR disks, CSM boot) are not supported - the loader will report `Could not mount EFI System Partition (BIOS-mode boot?)` and refuse to install.

2. Prerequisites (one-time BIOS / Windows setup)

Do these once, in this order. You can skip any item that's already configured.

2.1 Enable CPU virtualization in BIOS

Reboot into BIOS/UEFI setup ('F2', 'Del', 'F10' - varies by motherboard). Find and enable:

-Intel boards: Intel Virtualization Technology / VT-x, plus VT-d if present.

-AMD boards: SVM Mode / AMD-V.

Save and exit. If you skip this, the loader will deny functionality.

2.2 Disable Secure Boot

Still in BIOS, find 'Secure Boot' (usually under 'Boot' or 'Security') and set it to Disabled.

2.3 Disable Memory Integrity (HVCI) and Virtualization-Based Security

In Windows:

1. Open Windows Security -> Device security -> Core isolation details.

2. Turn Memory integrity off.

3. Reboot.

If "Memory integrity" is greyed out, run this in an admin PowerShell terminal:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard" /v EnableVirtualizationBasedSecurity /t REG_DWORD /d 0 /f

reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v Enabled /t REG_DWORD /d 0 /f

Then reboot.

2.4 Hypervisor compatibility

| Microsoft Hyper-V enabled | OK

| Microsoft Hyper-V disabled | OK

| VMware Workstation / Player | Not supported - run on a host without it

| VirtualBox | Not supported - run on a host without it

| KVM / Xen / QEMU | Not supported

The loader detects these and prints a warning before refusing to install.

2.5 Anti-virus

Disable Windows defender with DControl by Sordum, or add an exclusion to the CRAW/WARE loader for your cheat.

3. First install

1. Download the loader

2. Right-click the loader -> Run as administrator.

3. Log in with your username and password, or create an account with the key you were given.

4. Click launch cheat, A dialog will prompt "CRAWHV was installed on the EFI System Partition. A reboot is required for it to take effect. Reboot now?" Click yes. You will see a message in the top left of your screen during reboot if everything was successful, if not, open the loader and try again.

4. Day-to-day use

After the first reboot, the flow is:

1. Right-click the loader -> Run as administrator.

2. Log in.

3. The init panel races through:

[+] Authenticated as:

[+] Status: undetected

[+] CPU: ...

[+] CRAWHV is already running.

=== Game Detection ===

[*] Waiting for [GAME]...

4. Launch the game (Arma Reforger or DayZ) any way you normally do. Steam, desktop shortcut, etc.

5. Common errors and fixes

| Loader message | What it means | Fix |

| Run as Administrator -- CRAWHV install needs ESP write access. | You launched as a normal user. | Right-click -> Run as administrator.

| CPU lacks VT-x / SVM. Enable virtualization in BIOS. | Hardware virt is off. | Reboot into BIOS, enable VT-x (Intel) or SVM (AMD), save.

| Server unreachable or returned bad bytes | The loader couldn't fetch the hypervisor blob from the CDN.

| Could not mount EFI System Partition (BIOS-mode boot?) | Your Windows install is on an MBR disk / legacy BIOS boot. | CRAW/WARE requires UEFI. Reinstall Windows in UEFI mode if you want to use the cheat.

| Could not register "Windows (safe)" firmware boot entry; aborting install... | The installer did not touch your boot path - the system is still bootable. | Disable AV / boot-protection software, re-run loader.

| BSOD HYPERVISOR_ERROR (0x20001) | An older Intel build had a VMEXIT regression. | Message support with your CPU model.

6. Support

If anything in this guide doesn't match what you're seeing, open a ticket in the dashboard with:

- The exact text of the error message,

- Your CPU vendor/model,

- Windows build (`winver`),

- A screenshot of the INITIALIZING panel.