Common Issues — Spoofer
Frequently encountered problems with the Temp and Perm Spoofer and how to resolve them.
BSOD / Blue Screen after running the spoofer
- BSODs after spoofing are almost always caused by a driver conflict, Secure Boot being enabled, or a VPN client interfering at the kernel level.
- If you're stuck in a boot loop: restart into Safe Mode, open your spoofer folder, and run the included cleanup / restore tool first.
- In your BIOS: disable Secure Boot, disable TPM / fTPM, and disable Fast Boot — all three must be off before running the spoofer.
- Update your GPU drivers via DDU (Display Driver Uninstaller) for a clean reinstall, then also update your chipset drivers.
- If BSODs persist after driver updates, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an admin terminal.
Spoof doesn't seem to apply — HWID unchanged
- Make sure you run the loader as Administrator.
- Temporarily disable antivirus — security software can block driver injection silently.
- After spoofing, verify by checking your hardware IDs have changed in Device Manager → View → Devices by connection.
Game still detecting a ban after spoofing
- The spoofer changes hardware IDs but does not bypass an existing account ban — you also need a fresh account.
- If you've been IP banned, restart your router to get a new IP or use a residential VPN.
- Always spoof before launching the game, not after.
Still having issues?
Open a support ticket on Discord and describe your problem.
Average response time: ~10 min
