How to change HWID on Windows 11: a step-by-step guide

You can change part of your HWID on Windows 11 — but only the layers that actually live in Windows and on your drives. The firmware-level identifiers stay put. This guide walks through what to change, in what order, and how to roll back if anything misbehaves.

A note up front: the same steps apply to Windows 10 with only minor menu differences. The principles do not transfer to Linux — Linux uses a different identifier set.

What "changing your HWID" actually means

HWID isn't a single value — it's a profile your PC composes from a dozen different identifiers spread across the registry, your disks and your firmware. "Changing HWID" means changing the ones in the layers where it is safe and reversible, and accepting that some pieces stay because they are physically burned in.

Changeable from Windows software:

• The MachineGuid and adjacent IDs in the registry
• NTFS volume serial numbers (one per drive)
• MAC addresses of physical network adapters
• ComputerName and hostname

Not changeable without firmware tools or kernel drivers:

• SMBIOS UUID and motherboard serial
• CPU brand string and CPUID
• Disk serials at the controller level
• TPM 2.0 endorsement key

This guide covers the first list. If you need the second list changed, that is outside what any honest user-mode software can do.

Step 1 — Back up your current state

Before changing anything, save the current values. If a change breaks software activation or you want to revert, you need the ability to put the old IDs back.

A proper backup includes:

• Export of the HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid registry key.
• Current volume serial for every fixed drive (vol C: shows it).
• MAC of every physical adapter (getmac /v).
• Current ComputerName.

A dedicated HWID change tool stores all of this automatically and gives you one-click rollback. If you are doing it by hand, write the values down somewhere you'll find them again.

Step 2 — Rotate the Windows registry identifiers

Do this with the system idle — log out other users and close heavy background tasks first. Open Registry Editor as administrator and replace:

• HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid — generate a fresh GUID (PowerShell: [guid]::NewGuid()).
• HKLM\SYSTEM\CurrentControlSet\Control\IDConfigDB\Hardware Profiles\0001\HwProfileGuid — same.
• HKLM\SOFTWARE\Microsoft\SQMClient\MachineId — same.
• HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId — replace; also clear SusClientIdValidation.

Each is a single string value. Replace, save, move on.

Step 3 — Rotate NTFS volume serials

This needs a low-level disk write at byte offset 0x48 of sector 0 on each fixed drive. Two things to know:

• The system drive C: has its serial cached at mount time. The new value only becomes visible to new processes after a reboot. Non-system drives reflect the change immediately.
• Doing the sector-zero write by hand is risky — get a single byte wrong and the partition will not mount. Use a tool that has been tested for this purpose; don't improvise with a hex editor.

Step 4 — Refresh MAC addresses

Each physical network adapter has a NetworkAddress property in its driver. Set it to a randomised 12-hex-character value (with the locally-administered bit set — second hex digit 2, 6, A or E) and restart the adapter.

Be aware: some NIC drivers ignore the override and keep using the ROM MAC. Verify with getmac /v after the change. If verification shows the old MAC, that adapter is in the "ROM-only" group and there is nothing software can do about that one specifically.

Step 5 — Verify

After a reboot, run a quick check:

• wmic csproduct get UUID — SMBIOS UUID (should NOT have changed; that is firmware).
• vol C: — volume serial (should be the new one).
• getmac /v — MAC (should be the new one).
• reg query HKLM\SOFTWARE\Microsoft\Cryptography /v MachineGuid — should be the new GUID.

If any of the changeable values shows the OLD one, that step did not take. Most commonly that is the MAC (see Step 4 caveat).

For a full visualisation of every HWID component, use a dedicated diagnostic utility.

When the change isn't enough

Two situations come up regularly:

1. The ban is firmware-bound. Some anti-cheats read SMBIOS UUID, motherboard serial and CPU info — none of which change in software. If your ban hinges on those, a software HWID change will not unblock you. The honest answer is a different motherboard (or different CPU, if that is what is flagged).

2. The identifier came back via the network. If you log the same account into the same game from the same PC after the change, the publisher can re-bind the new HWID to your old account by pattern matching. Use a fresh account on the changed PC.

FAQ

Will changing my HWID deactivate Windows?

Possibly. Digital licences are tied to a hash of your hardware. Windows often re-activates automatically after a few minutes once the new IDs settle, but a hardware change can require manual re-activation. Keep your Microsoft account credentials ready.

Is one reboot enough?

For most changes — yes. The volume serial on the system drive specifically only updates for new processes after a reboot, so a restart is needed to see it everywhere.

Do I need administrator privileges?

Yes, for every step. Registry edits, disk-sector writes and driver-property changes all require administrator. A dedicated tool handles the elevation for you.

How often should I change my HWID?

Only when you have a reason — a fresh ban, a new account on the same PC, a hardware-bound licence transfer. There is no benefit to changing routinely, and frequent changes can themselves look suspicious to some anti-cheats.

Does changing HWID also change my SMBIOS or BIOS serial?

No. Those live in motherboard firmware. No user-mode software changes them honestly. If you see a "spoofer" claiming to change SMBIOS UUID in software without a kernel driver, treat the claim with deep skepticism.

The takeaway

Changing your HWID on Windows 11 is straightforward once you know which layers software can touch and which it cannot. Order: back up first, rotate the registry identifiers, then NTFS volume serials, then MAC addresses, verify, reboot. Double-check each step if you're doing it by hand. And remember the honest limit — firmware identifiers stay where they are, and that is not a problem any software-only tool can solve.