Build 05 live · free build hwid spoof / user + kernel / native x64 --:--:--
Countroublefree builds
free builds · direct support
countrouble · 2026
build 05 v2.0.0 hwid spoof free

CounTrouble's Spooferhwid spoofer

Two layers, one panel. User mode rewrites the Windows identity, the volume boot-sector serials and the MAC of every physical card. An optional kernel driver takes over the values the system reads from hardware: SMBIOS, disk descriptors, EFI variables, WMI monitor serials. Seven pages, one profile, no license.

  • ten identity fields in the registry
  • boot-sector serials for NTFS, exFAT and FAT
  • MAC per adapter, restart built in
  • kernel driver, no IOCTL
  • originals saved before every write
  • English panel, seven pages
x64 win32 · d3d11 · imgui 1.93 2.42 mb exe free forever
01 / capability

Two layers.
One identity.

The user layer works on a clean Windows install with admin rights. The kernel layer is optional and waits for a signed driver.

◈

Identity

Ten registry-backed fields: hostname, MachineGuid, hardware profile, Product ID, SQM id, Windows Update client id, BIOS and board serials, hardware id and CPU name. Generator and copy on every row.

▤

Volume serials

The serial is written into the boot sector of each volume: NTFS at 0x48, exFAT at 0x64, FAT at 0x43. The volume is locked during the write.

⌁

Network

NetworkAddress per card in the class key, then a restart through pnputil. Physical and virtual adapters are separated; multicast or null addresses are refused.

⌸

Kernel driver

CounTroubleSpoofer.sys spoofs at load time: disk and RAID descriptors, SMBIOS, EFI variables, WMI monitor serials, GPU, USB and TPM. No IOCTL, no unload routine.

⟲

Originals first

Every target is copied into originals.ini before its first write, once per target. Restore puts identity, serials and MACs back without a reinstall.

⌘

Seven pages

Dashboard, identity, volumes, network, kernel, profile, log. Startup entry with --auto reapplies the saved profile at logon, windowless.

02 / the panel

Every surface, one rail.

Captured from the demo build at 1160×760 — sample values, writes disabled, same widgets.

03 / boot output

Reads the machine before it writes.

The dashboard counts the fields, volumes and physical cards at launch, then reports the driver gate: file, service, Secure Boot, testsigning, HVCI and elevation. Nothing is written until a button is pressed.

Install steps

spoofer.bootadmin / x64
C:\> CounTroubleSpoofer.exe CounTrouble's Spoofer 2.0.0 [identity] 10 fields · machine guid · hw profile [volumes] C: 9A4C-21E7 · D: 3F81-B6D2 · E: 6C27-D9A4 [network] 2 physical cards · 1 virtual [kernel] CounTroubleSpoofer.sys · 14 KB · 8855… [state] admin · secure boot off · testsigning on panel ready
04 / specification

Under the hood.

One executable plus one driver, static CRT, no service left behind. The driver spoofs inside DriverEntry and stays resident until reboot; the app copies it to ProgramData and loads it through NtLoadDriver.

Host
Windows 11 / 10 · x64
Build
C++17 app · C++20 driver · Win32 · D3D11 · ImGui 1.93
Binary
2.42 MB exe + 14 KB sys · static CRT `/MT`
Pages
7 · dashboard, identity, volumes, network, kernel, profile, log
Identity
10 HKLM fields · hostname via SetComputerNameEx
Volumes
boot sector · NTFS / exFAT / FAT · locked write
Network
NetworkAddress per class key · pnputil restart
Driver
SMBIOS · disk · RAID · EFI · WMI · GPU · USB · TPM
Signature
local test cert via Signer.cmd · testsigning
State
%LOCALAPPDATA%\CounTrouble\Spoofer
Network
none · no telemetry
Price
free · no license check
05 / install

Five steps to a new identity.

Free zip, one exe, one driver. The user layer needs nothing but admin rights.

direct download

CounTrouble's Spoofer 2.0.0

Zip · 1.09 MB · Windows 10 22H2 / 11 x64 · administrator · Secure Boot off for the driver.

Download zip
SHA-256917054F2A450ABBA348F9335BF53C7A3C809357681AF8DA5100406FCA9F141C9
01

Download and extract

Grab countrouble-spoofer-2.0.0.zip and extract it to a folder you keep. It holds the exe, the driver, Signer.cmd and the readme.

02

Run as administrator

Double-click CounTroubleSpoofer.exe and accept the UAC prompt. The dashboard reads identity, volumes, adapters and driver state before any write.

03

Apply the user layer

On Identity, regenerate and apply. On Volumes, apply the new serials. On Network, randomize, apply, then restart each physical card. Hostname and Product ID land at the next reboot.

04

Sign the driver

Disable Secure Boot in the BIOS, then run Signer.cmd as administrator. It creates a local test certificate, trusts it, signs the sys and the exe, and turns testsigning on. Reboot.

05

Load the kernel layer

Open Kernel and press LOAD DRIVER. The console reports the NTSTATUS. The driver has no unload routine: it stays until the next reboot.

before you run: the exe and driver are unsigned. SmartScreen will ask once; testsigning refuses the driver until the certificate is trusted. Compare the SHA-256 from the release card.
06 / changelog

Spoofer history.

Current build is 2.0.0. The exe version and the zip name match.

2.0.0current · free release
  • Countrouble panel: amber rail, seven pages, live value chips
  • identity: ten registry fields, per-field generator, selective apply
  • volumes: boot-sector serial write for NTFS, exFAT and FAT with volume lock
  • network: NetworkAddress per adapter, physical filter, pnputil restart
  • kernel: test-signed driver, load through NtLoadDriver, SHA-256 and gate readout
  • profile: originals captured once, restore, HKCU startup entry
  • demo mode (--demo) for screenshots without writes
  • free: no key, no activation call, no checkout
07 / faq

Before the first write.

Does it need the driver?

No. Identity, volume serials and MAC addresses are user mode and work immediately. The driver adds the values Windows reads from hardware: SMBIOS, disk descriptors, EFI variables, WMI monitor serials.

Does Secure Boot have to be off?

Only for the driver. Tests signed images are refused while Secure Boot is active. The user layer is unaffected; you can run it on a locked machine.

What survives a reboot?

Registry values, volume serials, MAC addresses and the startup entry. Hostname and Product ID are read by services at boot, so they settle after a restart. The driver does not reload itself: press LOAD DRIVER after each boot.

How do I undo everything?

Page Profile > RESTORE replays every saved original: identity, serials and MACs. Then bcdedit /set testsigning off, reboot, and delete the app folder, the ProgramData copy and the test certificate.

Why does SmartScreen complain?

The exe and driver carry no publisher certificate. The zip ships the signer so the driver can be trusted locally. Compare the SHA-256 from the release card before running it.

Where does it write?

HKLM registry values, the boot sector of the volumes you apply, the NIC class keys, %LOCALAPPDATA%\CounTrouble\Spoofer for profile and journal, and %ProgramData%\CounTrouble\Spoofer for the loaded driver. No network call.