General advice before using an HWID spoofer

1. Preparation: an organised workflow

• Check support for your game, Windows edition and build, motherboard model and BIOS version. Establish which identifiers the product is expected to change and which changes should survive a restart.
• Back up important files to a separate device. Keep your BitLocker recovery key, Windows sign-in recovery options and photographs of BIOS settings: storage mode, boot order, TPM, Secure Boot and memory profiles.
• Record initial values with the commands below. Note the date, spoofer version, connected devices and exact fields being checked. Keep the complete report privately.
• Follow the developer’s preparation and launch sequence. Do not run several spoofers and cleaners together: it becomes difficult to establish which action caused a change.
• Repeat the same checks immediately afterwards and after restarting. For permanent changes, also check after a complete shutdown and power-on when the instructions call for it.
• If the result differs from what was expected, save the report and error message. Diagnose the cause with support before buying components or flashing firmware.

2. Record the initial configuration

Open PowerShell. The following commands only read information; they do not change serial numbers, BIOS settings or devices. Some classes may be unavailable on a particular system. A missing field or failed query means the checking method needs investigation, not that the identifier does not exist.

Get-CimInstance Win32_BaseBoard |
  Select-Object Manufacturer, Product, SerialNumber

Get-CimInstance Win32_BIOS |
  Select-Object Manufacturer, SMBIOSBIOSVersion, SerialNumber

Get-CimInstance Win32_ComputerSystemProduct |
  Select-Object Vendor, Name, IdentifyingNumber, UUID

Get-CimInstance Win32_OperatingSystem |
  Select-Object Caption, Version, BuildNumber

Board serial number, system serial number and UUID are different fields. Compare the same fields using the same tool. Different formatting, spaces, byte order or values such as Default String and 00000000 do not establish that the whole PC is “clean”. SMBIOS information does not cover every low-level identifier either.

3. Windows reinstall, caches and user accounts

spoofer.shop describes a clean reinstall as mandatory. In a general guide, treat this as a scenario-specific requirement: if your spoofer’s developer requires it, an in-place build upgrade or a new Windows user does not replace a clean installation. Prepare official Microsoft installation media and network drivers beforehand.

• Identify the intended physical drive by model and capacity before deleting partitions. Deleting partitions destroys data; leave other drives containing backups and personal files untouched.
• If the installer or product instructions require clearing the system drive, restrict the operation to that drive. Reinstalling Windows does not change the physical serial number of an SSD, motherboard or TPM.
• Clear game and anti-cheat caches through their repair functions or the exact paths in the developer’s instructions. Avoid deleting arbitrary system folders or registry branches in pursuit of a “complete cleanup”.
• A new Windows account changes the user profile, not hardware identifiers. Reinstalling Windows or replacing a component does not remove a game-account ban either.

4. Fast Startup, hibernation and UEFI Fast Boot

Windows Fast Startup saves kernel and driver state using hibernation. Consequently, shutting down and powering on may differ from a full boot. Restart performs a full Windows boot cycle. UEFI Fast Boot is a separate firmware setting, generally shortening hardware checks during startup.

• If the instructions require Windows Fast Startup to be disabled, open Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable. Clear the Fast Startup checkbox and save. Labels vary by Windows version.
• Check available sleep states with powercfg /a. If the instructions also require hibernation to be disabled, run powercfg /hibernate off in an administrator terminal. This disables hibernation and Windows Fast Startup; powercfg /hibernate on enables hibernation again.
• Change UEFI Fast Boot separately according to the motherboard manual. None of these switches guarantees removal of traces, changes to every identifier or erasure of all memory.

5. Motherboard, BIOS, NVRAM and CMOS

NVRAM retains firmware data without power; settings and some platform data can survive a Windows reinstall. SMBIOS/DMI write support depends on the exact model, board revision, BIOS version and spoofer method. Values that appear changed before a restart but revert afterwards have not been shown to be permanent.

GoofyNest reports its experience with Gigabyte, ASRock, MSI and ASUS, including limitations of some newer ASUS BIOS versions. Use these observations as compatibility questions, not brand-wide guarantees: even boards in one series can have different firmware. Before buying, obtain confirmation for the complete model name and BIOS version.

• Update or downgrade BIOS only with a file for the exact board model and revision, following the manufacturer’s official procedure. An arbitrary older BIOS may not support the CPU or permit rollback. Recheck settings and spoofing results after an update.
• Clearing CMOS resets firmware settings; it is not a universal way to erase SMBIOS, NVRAM, device serial numbers or TPM keys. It can change boot order, storage mode and memory settings.
• For Clear CMOS, follow the board manual and the manufacturer’s power-disconnection instructions. Do not short unidentified pins or remove the battery while the system is powered on.

6. Storage drives, RAID and the Windows drive

Get-CimInstance Win32_DiskDrive |
  Select-Object Model, SerialNumber, InterfaceType, PNPDeviceID

Check every internal and connected external drive, not just the system drive. A physical-drive serial number, volume serial number and partition identifier are different values. Changing a volume serial does not establish that the hardware serial changed. USB bridges and controllers may expose information differently; compare the same connection path.

GoofyNest specifically reports that Intel RAID 0 and AMD RAID/RAIDABLE should no longer be treated as a way to hide physical drive serials from Rust/Easy Anti-Cheat. This is the source’s report for a particular scenario, not proof of how every game behaves. Having RAID does not itself establish a ban, nor does it demonstrate that drives are hidden.

Do not create a RAID 0 array just to test this: changing the configuration can destroy data, and failure of one drive loses array data. SSD firmware changes, moving Windows, replacing a drive or using a bridge need separate compatibility confirmation. Running a game from another drive does not make a previously connected drive invisible.

7. TPM: checking, clearing and discrete modules

Get-Tpm |
  Select-Object TpmPresent, TpmReady, TpmEnabled, TpmActivated

TPM may be implemented in firmware as AMD fTPM or Intel PTT, or provided by a discrete module. TPM uses cryptographic keys; its identity is not just a number in an ordinary device list. TpmReady status alone says nothing about a ban.

Clearing TPM deletes associated keys and can affect BitLocker, Windows Hello PIN and other protected data. It does not guarantee replacement of the TPM’s hardware identity. Save the recovery key and a way to sign in without the PIN first. Microsoft recommends clearing through Windows rather than directly through UEFI. The path is Windows Security → Device security → Security processor details → Security processor troubleshooting → Clear TPM; labels can vary.

spoofer.shop’s advice to clear and then disable TPM does not apply to every game: some require TPM and Secure Boot to be enabled. GoofyNest discusses discrete TPM modules, but connectors, pin assignments and support vary between boards. Do not buy a module merely because its connector looks similar, or change TPM without a confirmed need and an access-recovery plan.

8. Memory: serial number and Asset Tag

Get-CimInstance Win32_PhysicalMemory |
  Select-Object DeviceLocator, Manufacturer, PartNumber, SerialNumber, Tag

Check each memory module separately. GoofyNest notes serial numbers on some newer DDR5 modules, including Corsair Vengeance. The actual system’s output matters more than the brand name. An empty or zero SerialNumber in this query does not rule out other SPD data or inventory fields. WMI Tag should not automatically be treated as the same Asset Tag reported by a DMI tool.

If support asks you to check Asset Tag or SPD, establish the exact field and suitable tool. Editing SPD or flashing memory modules is a separate operation: an error can prevent the PC from starting. A normal before-and-after comparison does not require writing to memory.

9. Graphics cards and integrated graphics

Get-CimInstance Win32_VideoController |
  Select-Object Name, PNPDeviceID, DriverVersion

This query shows model, PNPDeviceID and driver; it does not guarantee access to GPU UUID or physical serial number. On NVIDIA systems, an installed nvidia-smi may expose additional information; fields depend on the device and driver. Use the manufacturer’s diagnostic tools for other cards. A missing number in one tool does not prove that the device has none.

GoofyNest’s preference for AMD and disabling integrated graphics belongs to its particular setup. Check both graphics systems when present. Before disabling an iGPU, make sure the display is connected to a working discrete card and account for laptops with switchable graphics. There is no universal requirement to replace NVIDIA with AMD.

10. Monitors and EDID

function Read-MonitorText($Value) {
  ($Value | Where-Object { $_ -ne 0 } |
    ForEach-Object { [char]$_ }) -join ""
}

Get-CimInstance -Namespace root\wmi -ClassName WmiMonitorID |
  ForEach-Object {
    [PSCustomObject]@{
      Instance = $_.InstanceName
      Maker = Read-MonitorText $_.ManufacturerName
      Model = Read-MonitorText $_.UserFriendlyName
      Serial = Read-MonitorText $_.SerialNumberID
    }
  }

EDID contains display information, including manufacturer, model and sometimes a serial number. Check every connected monitor, including secondary displays, docks and adapters. Record the port and connection chain. Not every display provides a populated SerialNumberID through WMI.

GoofyNest describes EDID emulators and fusers with programmable EDID. An ordinary HDMI/DisplayPort adapter does not necessarily change this information; a device may also affect refresh rate, resolution, HDR and VRR. If this approach is actually needed, confirm the specific model’s capabilities and check each display separately.

11. Networking: Ethernet, Wi-Fi, Bluetooth, MAC and IP

Get-NetAdapter -Physical |
  Select-Object Name, InterfaceDescription, Status, MacAddress

Check all physical network adapters, not just the active connection. MAC address, public IP and device identifier are different information. Changing one does not establish that the others changed. MAC override support depends on the adapter and driver; recheck after a restart or driver update.

• If the instructions call for temporarily disabling unused Wi-Fi and Bluetooth, first ensure a working wired connection. On laptops, Bluetooth and Wi-Fi may share a module. A disabled device should not automatically be considered invisible to the entire system.
• Restarting a router does not guarantee a new public IP: the address may be reserved or provided through CGNAT. Compare it before and after, and ask the provider how changes work when needed. A VPN does not change hardware serial numbers and may increase latency.
• Consider replacing a PCIe/USB Ethernet or Wi-Fi adapter only after diagnosing that particular device. Avoid flashing an integrated network controller using an arbitrary guide.

12. USB devices and external storage

Get-PnpDevice -PresentOnly |
  Where-Object { $_.InstanceId -like "USB*" } |
  Select-Object Class, FriendlyName, InstanceId

List flash drives, external SSDs/HDDs, USB network adapters, mice, keyboards, webcams and other devices. InstanceId helps distinguish devices, but not every part of it is a physical serial number. USBDeview mentioned by the source is another viewing option; the built-in query above provides a basic list.

For a diagnostic run, safely eject unnecessary external storage and disconnect optional peripherals, keeping devices needed to operate the PC and access the network. Change one device at a time to identify the cause of differences. A general recommendation is not enough reason to replace every peripheral with a particular brand.

13. Cleaners and Device Instance ID

spoofer.shop mentions Tool.exe with Cleanup Devices, Cleanup Traces + Spoof Registry and FULL mode, plus DeviceInterfaceSpooferPerm.exe for Device Instance ID. These are third-party tools from that guide, not mandatory components of every spoofer. A filename alone does not establish publisher, contents or compatibility.

If your product’s developer requires such a tool, obtain it through the developer’s current link and establish which devices or entries the selected mode removes, what must be backed up and when to restart. Avoid combining several tools’ “full cleanup” modes. A changed Device Instance ID, registry entry or stored device profile does not by itself demonstrate a changed hardware serial number.

14. Verify the result and whether it persists

• For each relevant field, record three values: before the procedure, immediately after it and after a restart. Include the checking tool, version and device connection method.
• For a temporary spoofer, use its instructions to establish expected restart behaviour. Original values returning may be normal and mean that another launch is required.
• For a permanent spoofer, reverted values warrant checking BIOS support, the selected method and the persistence step. Avoid further blind flashing just because one run displayed new values.
• Check the complete agreed set of fields and devices. A changed motherboard UUID does not establish changes to drives, EDID, MAC, TPM or memory. One successful game login does not prove that a delayed ban is impossible.

15. When the result differs from the instructions

• The spoofer fails to launch or reports an error: record the exact message, Windows version, board model and BIOS. Check supported builds, current product status and its driver and security-setting requirements. Avoid disabling every protection using a universal checklist.
• Values changed but reverted after restarting: establish whether the method is temporary and repeat checks with the same tool. For a permanent method, give support the three-state comparison.
• Numbers changed but the game still blocks access: separately check account bans, game TPM/Secure Boot requirements, remaining devices and product compatibility. One changed field is not enough for a diagnosis.
• Windows will not boot after a BIOS change: stop further changes, compare the recorded storage and boot settings, use the manufacturer’s recovery process and supply the BitLocker key when requested. Formatting the drive should not be the first recovery attempt.

For support, prepare the product name and version, game, Windows build, exact board model and revision, BIOS, device list, action sequence, error message and before/after/restart comparison. Redact complete serial numbers and UUIDs from public posts; do not attach recovery keys, licences, passwords or tokens.

Sources and further instructions

GoofyNest and spoofer.shop describe their authors’ experience and particular configurations. This guide combines those topics into a common workflow explaining the purpose and limitations of each action. Windows behaviour and TPM-clearing precautions were checked against Microsoft. Consult your product’s current instructions before applying changes.

• GoofyNest — Important information
• spoofer.shop — Spoofer usage advice
• Microsoft — TPM configuration and clearing
• Microsoft — power states and Fast Startup
• Microsoft — reinstall Windows using installation media
• Product launch instructions
• Spoofer catalogue