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.
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.
The user layer works on a clean Windows install with admin rights. The kernel layer is optional and waits for a signed driver.
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.
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.
NetworkAddress per card in the class key, then a restart through pnputil. Physical and virtual adapters are separated; multicast or null addresses are refused.
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.
Every target is copied into originals.ini before its first write, once per target. Restore puts identity, serials and MACs back without a reinstall.
Dashboard, identity, volumes, network, kernel, profile, log. Startup entry with --auto reapplies the saved profile at logon, windowless.
Captured from the demo build at 1160×760 — sample values, writes disabled, same widgets.
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.
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.
Free zip, one exe, one driver. The user layer needs nothing but admin rights.
Zip · 1.09 MB · Windows 10 22H2 / 11 x64 · administrator · Secure Boot off for the driver.
917054F2A450ABBA348F9335BF53C7A3C809357681AF8DA5100406FCA9F141C9Grab 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.
Double-click CounTroubleSpoofer.exe and accept the UAC prompt. The dashboard reads identity, volumes, adapters and driver state before any write.
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.
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.
Open Kernel and press LOAD DRIVER. The console reports the NTSTATUS. The driver has no unload routine: it stays until the next reboot.
Current build is 2.0.0. The exe version and the zip name match.
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.
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.
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.
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.
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.
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.