Does a Factory Reset Change Your HWID? What Actually Changes on Windows

A factory reset normally does not change a hardware-based HWID. It reinstalls Windows and may replace installation-specific identifiers, but it does not rewrite the serial numbers stored in your motherboard, BIOS, CPU, SSD or network adapter. If an application builds its HWID mainly from those physical-device values, it will probably recognize the PC after the reset.

The less satisfying — but more accurate — answer is that HWID is not one Windows value. Each game, licensing system or management product decides which signals to collect and how to compare them. A reset can therefore change an application's device ID without changing the underlying hardware. Conversely, wiping every personal file can leave a hardware fingerprint unchanged.

This article is about Windows 10 and Windows 11. Microsoft calls the built-in feature Reset this PC; “factory reset” may also refer to an OEM recovery image or a clean installation from USB. Those procedures are not identical, so the distinction matters.

What a Windows factory reset actually does

According to Microsoft's Reset your PC documentation, Reset this PC reinstalls Windows. Keep my files preserves personal files while removing applications and resetting settings. Remove everything also removes personal files. Cloud download obtains fresh Windows installation files; Local reinstall uses files already on the PC.

None of those choices replaces a physical component. Even the optional drive-cleaning setting is a data-erasure operation intended to make deleted files harder to recover. It does not ask an SSD or hard drive to adopt a new manufacturer serial number.

A clean USB installation goes further than Reset this PC because you can delete and recreate partitions. An OEM recovery may restore manufacturer software and configuration. But all three remain software operations unless a repair technician also changes hardware.

What stays the same after a reset

These identifiers normally survive Reset this PC, an OEM recovery and a clean Windows installation:

Microsoft documents Win32_ComputerSystemProduct.UUID as a read-only value sourced from SMBIOS, and Win32_DiskDrive.SerialNumber as the manufacturer-assigned number for physical media. Reinstalling an operating system does not modify either source.

A motherboard replacement is different: it usually changes the SMBIOS UUID and board serial, and may also replace a firmware-backed Windows product key or TPM. Replacing the system drive changes the physical disk serial. Those are hardware changes, not factory resets.

You can inspect the raw values with the commands in our CMD and PowerShell HWID serial reference. Values such as To Be Filled By O.E.M., all-zero UUIDs and blank RAM serials are firmware limitations; a reset will not repair them.

What may change after a reset

Software-derived identifiers are a different category.

MachineGuid is stored at:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\MachineGuid

It identifies a Windows installation, not the motherboard. A clean installation typically creates a new value, and a properly generalized deployment image creates installation-specific state when it is specialized. Reset this PC is more complicated: its behavior can vary with the reset path, Windows release and OEM recovery process. Microsoft does not publish a compatibility promise saying third-party software may rely on MachineGuid either changing or remaining unchanged after every reset. Treat it as something to measure, not predict.

Other values that can change include:

• the Windows installation ID and application-generated device IDs;
• local application files, registry entries and cached tokens;
• the filesystem volume serial number if the volume is recreated or reformatted;
• virtual adapter identifiers when VPN, Hyper-V or virtualization software is removed and reinstalled;
• randomized Wi-Fi MAC addresses, depending on network and privacy settings.

The volume serial is often confused with the physical disk serial. vol C: prints a short filesystem value such as 7A2F-19C4; formatting can replace it. A Samsung or Western Digital serial reported by Get-PhysicalDisk comes from the drive and remains the same.

Why the final HWID may still change

Imagine a licensing client hashes four fields:

SMBIOS UUID + disk serial + CPU ProcessorId + MachineGuid

After a reset, the first three stay constant while MachineGuid may change. If the client computes one strict SHA-256 hash, changing that single input produces a completely different output. If the server compares components individually and tolerates one changed field, it can still recognize the machine.

This explains apparently contradictory reports online. Two users can reset identical PCs and see different results because they are testing different products, not because hardware serials behave differently. One product may use only MachineGuid; another may use firmware values; a third may combine local state with an account-bound server record.

Well-designed HWID-based licensing generally avoids treating one opaque hash as infallible. Component-level matching, self-service deactivation and a documented reactivation path handle legitimate reinstalls more reliably.

Windows activation itself illustrates the distinction. Microsoft's activation guidance says a digital license can reactivate the same edition after Windows is reinstalled on the same device, while a significant hardware change such as replacing the motherboard may require reactivation. That does not reveal Microsoft's complete activation algorithm, but it demonstrates that “new Windows installation” and “new hardware” are not equivalent.

How to check before and after a reset

If the answer matters for a license, inventory record or your own diagnostics, record the raw identifiers before resetting. Do not save the report only on the drive you plan to erase.

Run these in PowerShell:

[PSCustomObject]@{
  SmbiosUuid  = (Get-CimInstance Win32_ComputerSystemProduct).UUID
  BoardSerial = (Get-CimInstance Win32_BaseBoard).SerialNumber
  BiosSerial  = (Get-CimInstance Win32_BIOS).SerialNumber
  DiskSerials = (Get-PhysicalDisk | ForEach-Object { $_.SerialNumber.Trim() }) -join ', '
  CpuId       = (Get-CimInstance Win32_Processor).ProcessorId
  MachineGuid = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Cryptography').MachineGuid
} | Format-List

Save the output to an external drive or another trusted device, then run the same block after the reset. Compare each field rather than comparing only a composite hash. Our portable Windows checker can also export a local report, but its composite SHA-256 is our own diagnostic value; it is not guaranteed to match the HWID used by another product.

Before resetting a licensed workstation, deactivate software where vendors provide that option and retain proof of purchase or recovery credentials. For Windows itself, confirm activation and link the digital license to your Microsoft account where appropriate; Microsoft's activation guidance recommends doing this before significant hardware changes.

Will a factory reset remove an HWID ban?

Do not assume it will. A reset may remove local application data, but a service can retain server-side account, device and enforcement records. If its device matching uses motherboard and disk identifiers, those signals survive the reset. If it uses several signals, nobody outside the vendor can determine the result from one displayed “HWID.”

Repeated resets are therefore a poor diagnostic method and can cost data without answering the question. Use the service's appeal or support process. Our HWID ban checker can help distinguish account-, IP- and hardware-like symptoms, but it cannot see or override a publisher's records.

The practical answer

A factory reset changes the software environment much more than the hardware identity:

• Reset this PC does not normally change motherboard, BIOS, CPU or physical-drive identifiers.
• Installation-level IDs such as MachineGuid and application-created device IDs may change, but their reset behavior should not be assumed.
• A vendor's final HWID may stay the same or change depending on its inputs and matching policy.
• Replacing hardware is fundamentally different from reinstalling Windows.

The forward-looking lesson is that device identity should be treated as a set of signals with different lifetimes, not a permanent serial stamped on the whole computer. As Windows recovery becomes more cloud-driven and privacy features randomize more network identifiers, systems that explain their reactivation policy and tolerate expected software changes will age better than systems built around one brittle hash.