System UUID: What It Is and How to Find It
Learn what the System UUID is, how to find it in Windows with WMIC and PowerShell, and why anti-cheat systems use it for hardware identification.
By SensePublished
What Is the System UUID?
The System UUID (Universally Unique Identifier) is a 128-bit value stored in your computer's SMBIOS firmware tables. It is meant to uniquely identify the system — not just the motherboard or any single component, but the machine as a whole.
The UUID follows the standard format of five groups of hexadecimal digits separated by hyphens:
4C4C4544-0042-4810-8054-B7C04F4A5331This 36-character string (32 hex digits plus 4 hyphens) is written into the SMBIOS Type 1 (System Information) structure by the motherboard manufacturer during production. It is stored in non-volatile memory on the board and persists across operating system installations, BIOS updates (in most cases), and hardware swaps.
UUID Versions and Format
The SMBIOS specification references RFC 4122, which defines several UUID versions:
- Version 1: Time-based. Encodes a timestamp and the MAC address of the generating machine. Some older motherboards used this approach, which means the UUID itself leaked the board's MAC address.
- Version 4: Random. Generated from a cryptographically random or pseudo-random number. Most modern motherboards use version 4 UUIDs.
- Version 5: Name-based with SHA-1 hashing.
You can identify the version by looking at the first digit of the third group. A UUID starting with 4C4C4544-0042-4810-... has 4 as the first character of the third group, indicating version 4 (random).
Some manufacturers, notably Dell, encode the Service Tag within the UUID. Dell UUIDs often start with 4C4C4544, which decodes to LLLD in ASCII — a Dell signature. The remaining bytes encode the system's service tag, making the UUID predictable if you know the tag.
How to Find Your System UUID in Windows
Method 1: WMIC
Open Command Prompt or PowerShell and run:
wmic csproduct get UUIDThis queries the Win32_ComputerSystemProduct WMI class and returns the SMBIOS System UUID directly.
Method 2: PowerShell
The modern PowerShell equivalent:
Get-CimInstance -ClassName Win32_ComputerSystemProduct | Select-Object UUIDBoth methods read from the same underlying SMBIOS data, so the result is identical.
Method 3: Command Prompt with systeminfo
The systeminfo command does not directly display the UUID, but you can pull it from the registry where Windows caches SMBIOS data:
reg query "HKLM\SYSTEM\HardwareConfig" /v LastConfigHowever, this registry value is the Hardware Configuration ID, which is derived from the System UUID but is not always identical to it. For the raw SMBIOS UUID, stick with WMIC or PowerShell.
Method 4: Linux (dmidecode)
On Linux systems, the standard tool is dmidecode:
sudo dmidecode -s system-uuidThis reads the SMBIOS tables directly from firmware and returns the UUID. The lshal and hwinfo commands also expose it but are less universally available.
Method 5: BIOS/UEFI Setup
Some UEFI firmware interfaces display the System UUID in the System Information or Main tab. This varies by manufacturer — ASUS, MSI, Gigabyte, and ASRock all handle it differently. Consumer boards often do not expose it in the UEFI GUI at all, while server and workstation boards typically do.
Where Is the UUID Stored?
The System UUID lives in the SMBIOS (System Management BIOS) tables, specifically the Type 1 structure. SMBIOS is a specification maintained by the DMTF (Distributed Management Task Force) that defines how firmware exposes hardware information to the operating system.
The SMBIOS tables are stored in the motherboard's SPI flash, the same chip that holds the UEFI firmware. When Windows boots, it reads these tables through the firmware interface and caches certain values in the registry.
Because the UUID resides in flash memory, it survives:
- Operating system reinstalls
- Hard drive replacements
- RAM changes
- GPU swaps
- BIOS settings resets (Clear CMOS)
It does not survive:
- Motherboard replacement (the UUID goes with the board)
- Some BIOS reflashing procedures (manufacturer-dependent)
- Manual modification through SMBIOS editing tools
Can the System UUID Be All Zeros or All Fs?
Yes, and it happens more often than you would expect. The SMBIOS specification defines two special values:
00000000-0000-0000-0000-000000000000: "Not present." The system does not have a set UUID.FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF: "Not settable." The UUID field exists but cannot be programmed.
Cheap or white-label motherboards sometimes ship with one of these placeholder values. Custom-built systems using OEM boards may also lack a proper UUID. This creates problems for any software that relies on the UUID for licensing or identification — and for anti-cheat systems trying to fingerprint the machine.
How Anti-Cheats Use the System UUID
The System UUID is one of the most valuable identifiers for anti-cheat HWID fingerprinting. Here is why:
- It is persistent. Unlike a MAC address that can be changed with a single command, the UUID requires firmware-level tools to modify.
- It is unique. Each motherboard (from reputable manufacturers) ships with a distinct UUID.
- It is easily accessible. A single WMI query retrieves it. No kernel driver needed.
- It is tied to the motherboard. Since the motherboard is the hardest component to swap, banning based on the UUID effectively bans the physical machine.
Anti-cheat systems like Vanguard, EasyAntiCheat, and BattlEye include the System UUID in their composite hardware fingerprint. The exact weight it receives varies by implementation, but it is generally considered a high-value identifier alongside disk serial numbers and motherboard serial numbers.
Some anti-cheats also cross-reference the UUID with the motherboard serial number (SMBIOS Type 2, Base Board Information). If the UUID changes but the motherboard serial does not, this inconsistency itself becomes a flag.
System UUID vs. Machine GUID
These two identifiers are frequently confused but are fundamentally different:
| Property | System UUID | Machine GUID |
|---|---|---|
| Source | SMBIOS firmware | Windows installation |
| Stored in | Motherboard flash | Registry (HKLM\SOFTWARE\Microsoft\Cryptography) |
| Survives OS reinstall | Yes | No |
| Survives motherboard swap | No | Yes (if same disk) |
| Per-unit unique | Yes (usually) | Yes (generated at install) |
The Machine GUID is generated by Windows during installation and stored in the registry at HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid. It changes when you reinstall Windows but persists across hardware swaps as long as the same installation is running.
Anti-cheats collect both. The System UUID anchors the fingerprint to the physical hardware, while the Machine GUID anchors it to the software installation. Together, they make it difficult to evade a ban through either a hardware swap or an OS reinstall alone.
Can You Change the System UUID?
Changing the UUID requires writing to the SMBIOS tables in the motherboard's SPI flash. This is not something Windows exposes through any standard interface. There are several approaches, each with different trade-offs:
BIOS Modding
Tools like AMIBCP (AMI BIOS Configuration Program) can modify SMBIOS values in a BIOS image, which is then flashed back to the motherboard. This approach works but carries risks: a bad flash can brick the board, and the modification will be overwritten by the next BIOS update from the manufacturer.
Manufacturer Tools
Some motherboard manufacturers provide OEM tools for setting SMBIOS values. Dell, HP, and Lenovo have utilities for configuring the asset tag, serial number, and UUID on their business-class machines. These tools are not available for consumer boards.
HWID Spoofers
The most practical approach for most users is an HWID spoofer that intercepts the system calls anti-cheats use to read the UUID. Rather than modifying the actual firmware, the spoofer sits between the anti-cheat and the operating system, returning altered values when the UUID is queried.
Sense AC takes this approach. When an anti-cheat queries WMI for the System UUID, Sense intercepts the call and provides a randomized UUID that is consistent across all queries within the session. This means the anti-cheat sees a coherent but different machine identity.
Registry Editing
Editing the cached UUID values in the Windows registry does not work. Anti-cheats that operate at the kernel level read SMBIOS tables directly from firmware rather than relying on the WMI cache. Even if you modify the registry, the kernel-level query returns the original value.
UUID Byte Order: A Technical Note
The SMBIOS specification uses mixed-endian byte ordering for the UUID, which causes confusion. The first three groups (time_low, time_mid, time_hi_and_version) are stored in little-endian order, while the last two groups (clock_seq and node) are stored in big-endian order.
This means that SMBIOS versions before 2.6 might display the UUID with incorrect byte ordering. If you see your UUID displayed differently by different tools, the byte order interpretation is likely the cause. SMBIOS 2.6 and later standardized on the RFC 4122 mixed-endian format.
For anti-cheat purposes, this technicality rarely matters because the anti-cheat and the spoofer read from the same source using the same interpretation.
Checking UUID for Troubleshooting
Beyond gaming and anti-cheat contexts, the System UUID serves several practical purposes:
- Windows licensing: Some OEM licenses are tied to the hardware, and the UUID contributes to the hardware hash that Microsoft uses for digital entitlement.
- Enterprise management: Tools like SCCM (Microsoft Endpoint Configuration Manager) use the UUID as a primary key for device identification. Duplicate UUIDs in an enterprise environment cause management conflicts.
- Virtualization: Hypervisors assign UUIDs to virtual machines. VMware, Hyper-V, and KVM all set SMBIOS UUIDs for their VMs, which is how guest operating systems and applications identify the virtual hardware.
If your UUID shows as all zeros or all Fs, it may cause issues with Windows licensing, enterprise enrollment, or any application that uses the UUID for machine identification.
The Role of the UUID in HWID Bans
When a player receives a hardware ban, the anti-cheat stores a hash of the machine's hardware fingerprint. The System UUID is a key ingredient in that hash. Because the UUID is:
- Unique per motherboard
- Persistent across OS reinstalls
- Difficult to change without specialized tools
...it serves as an anchor point for the entire fingerprint. Even if a player changes their disk serial, MAC address, and other software-level identifiers, the UUID often remains the same, and the ban persists.
This is exactly why comprehensive HWID spoofing tools like Sense address the UUID alongside every other identifier. Changing just one identifier while leaving the UUID intact is like changing your clothes but keeping the same face — the anti-cheat still recognizes you.
Summary
The System UUID is a 128-bit identifier stored in your motherboard's SMBIOS firmware tables. It uniquely identifies the physical system, survives OS reinstalls and hardware swaps (except the motherboard itself), and is a high-priority target for anti-cheat HWID fingerprinting. You can find it with a simple WMIC or PowerShell command, but changing it requires either firmware modification or a spoofing tool that intercepts the query at the system level.