Hard Disk Serial Number: Find, Check and Change It
Find your hard disk serial number in Windows, understand firmware vs volume serials, and learn how anti-cheats use disk identifiers for HWID bans.
By SensePublished
What Is a Disk Serial Number?
Every hard drive and solid-state drive carries serial numbers that identify it. But when people search for "disk serial number," they could mean two very different things:
- Firmware Serial Number: A unique string programmed into the drive's firmware during manufacturing. This is printed on the physical label of the drive and is unique to each unit worldwide.
- Volume Serial Number: A 32-bit identifier generated by Windows when a partition is formatted. This identifies the formatted volume, not the physical drive.
The distinction is critical because anti-cheat systems care about the firmware serial while many guides only show you how to find the volume serial. Let us cover both.
Firmware Serial Number
The firmware serial number is burned into the drive's controller during manufacturing. It is the serial you would find on the drive's physical label — a string like WD-WCC7K0RN1234 for a Western Digital drive or S4EVNX0T901234A for a Samsung SSD.
This serial is stored in the drive's firmware area, not on the data platters or NAND cells. Formatting the drive, reinstalling Windows, or even wiping the entire drive does not change it. It persists until the drive's controller firmware is reprogrammed — something that requires specialized tools and knowledge.
How to Find the Firmware Serial in Windows
Method 1: WMIC
wmic diskdrive get SerialNumber, Model, InterfaceTypeThis queries the Win32_DiskDrive WMI class and returns the firmware serial for each physical disk. The Model column helps you identify which serial belongs to which drive.
Method 2: PowerShell
Get-CimInstance -ClassName Win32_DiskDrive | Select-Object Model, SerialNumber, InterfaceType, SizeSame data, more structured output. The Size is in bytes — divide by 1GB for a readable number.
Method 3: Device Manager
Open Device Manager, expand "Disk drives," right-click your drive, choose Properties, and look at the Details tab. Select "Hardware Ids" or "Device instance path" from the dropdown. The serial number is usually embedded in the device instance path.
Method 4: CrystalDiskInfo
This free utility reads the drive's SMART data and identity information, displaying the firmware serial prominently. It also shows the firmware version, supported interface speeds, and health status.
Method 5: Command Prompt (SMART query)
The ATA IDENTIFY DEVICE command returns the firmware serial as part of the drive's identity sector. Tools that send raw ATA commands (like smartctl from the smartmontools package) can retrieve it:
smartctl -i /dev/sdaOn Windows, the device path is different (/dev/pd0, /dev/pd1, etc.), but the information returned is the same.
Firmware Serial Format by Manufacturer
| Manufacturer | Format Example | Notes |
|---|---|---|
| Western Digital | WD-WCC7K0RN1234 | Prefix "WD-" followed by alphanumeric |
| Seagate | ZA12345B | Short alphanumeric |
| Samsung | S4EVNX0T901234A | Alphanumeric, varies by product line |
| Crucial/Micron | 2144E5ABCDEF | Pure alphanumeric |
| Kingston | 50026B778C123456 | Often 16-digit hex |
| Intel/Solidigm | BTDA123456789012 | Prefix varies by product |
Note that Windows sometimes pads or reverses the byte order of the serial when reading it through WMI. If your serial looks scrambled — characters in a strange order, spaces between every character — this is a byte-order artifact. The raw ATA identity sector stores the serial in a specific byte ordering that Windows does not always interpret correctly for display purposes.
Volume Serial Number
The volume serial number is a completely different identifier. It is a 32-bit (8-character hex) value generated by Windows when a volume is formatted. You have seen it if you have ever run the vol command:
C:\>vol
Volume in drive C has no label.
Volume Serial Number is 1A2B-3C4DKey Differences from Firmware Serial
| Property | Firmware Serial | Volume Serial |
|---|---|---|
| Assigned by | Drive manufacturer | Windows during format |
| Unique scope | Globally unique per drive | Unique per format operation |
| Survives format | Yes | No (new serial generated) |
| Stored in | Drive firmware | Boot sector of the volume |
| Changeable | Requires firmware tools | Simple with free utilities |
How to Find the Volume Serial
vol C:Or in PowerShell:
Get-CimInstance -ClassName Win32_LogicalDisk | Select-Object DeviceID, VolumeSerialNumberThe volume serial is also accessible through the GetVolumeInformation Windows API function, which returns it as a DWORD.
Changing the Volume Serial
Because the volume serial is stored in the volume's boot sector (the VBR — Volume Boot Record), it can be changed by modifying a few bytes on disk. Several free tools do this:
- VolumeID (by Sysinternals/Microsoft): A command-line tool that takes the drive letter and the new serial as arguments.
volumeid C: ABCD-1234. - Hard Disk Serial Number Changer: A simple GUI tool that displays current volume serials and lets you set new ones.
Changing the volume serial is trivial and reversible. Format the drive again and Windows generates yet another serial. This is why anti-cheats give volume serials minimal weight in their fingerprints — they are too easy to change.
How Anti-Cheats Use Disk Identifiers
Disk serial numbers are among the most important identifiers in an anti-cheat's HWID fingerprint. Here is why:
Firmware Serial: High Value
The firmware serial is unique per drive, persistent across all operating system operations, and difficult to change. For anti-cheat systems, it is second only to the motherboard serial/UUID in reliability.
Anti-cheats read the firmware serial through several paths:
- WMI queries (
Win32_DiskDrive.SerialNumber): Easy to hook and spoof in user mode. - IOCTL calls (
IOCTL_STORAGE_QUERY_PROPERTYwithStorageDeviceProperty): A kernel-mode query that goes through the storage driver stack. Harder to intercept. - Direct ATA/NVMe commands: The IDENTIFY DEVICE (ATA) or Identify Controller/Namespace (NVMe) commands return the serial from the drive's firmware. Kernel-level anti-cheats can send these directly.
- SMART data: The serial is embedded in the SMART identity sector.
A naive spoofer that only hooks WMI will be caught when the anti-cheat reads the serial through a different path. Effective spoofing requires intercepting all these query methods consistently.
Volume Serial: Low Value
Anti-cheats may collect the volume serial but assign it minimal weight. Changing it is too easy to serve as a reliable identifier. Some anti-cheats ignore it entirely.
However, the volume serial can serve as a consistency check. If the firmware serial changes (suggesting spoofing) but the volume serial remains the same, this inconsistency itself can be suspicious. Effective spoofers change both to maintain a coherent identity.
NVMe Serial Numbers
NVMe drives have their own identification scheme separate from SATA/ATA. The NVMe Identify Controller command returns:
- Serial Number (SN): 20-byte ASCII string.
- Model Number (MN): 40-byte ASCII string.
- Firmware Revision (FR): 8-byte string.
NVMe drives also have a unique Namespace ID and EUI-64 or NGUID (Namespace Globally Unique Identifier). These additional identifiers give anti-cheats more data points to work with compared to SATA drives.
As NVMe drives become standard (they already are for system drives), anti-cheats have adapted to read NVMe-specific identifiers. A spoofer that only handles SATA serial queries will fail on NVMe systems.
Can You Change the Firmware Serial Number?
Yes, but it is significantly more involved than changing a volume serial.
Firmware Reprogramming
Drive manufacturers use specialized tools during production to write the firmware serial into the controller's non-volatile memory. For some older SATA drives, community-developed tools can access the firmware service area and rewrite the serial. This is:
- Risky: A wrong write can brick the drive.
- Model-specific: Each drive family uses different firmware structures and commands.
- Detectable: If the anti-cheat checks firmware version against the serial format, an inconsistency flags the modification.
For NVMe drives, firmware-level serial modification is even more complex due to the different command set and the tighter integration between controller firmware and NAND management.
Driver-Level Interception
The practical approach is intercepting the serial at the driver level rather than modifying the firmware. A minifilter driver or storage driver hook can intercept IOCTL calls that query the disk serial and return modified values.
Sense AC uses this approach, intercepting disk serial queries at the storage driver level to ensure that all paths — WMI, IOCTL, direct ATA/NVMe commands — return consistent spoofed values. The actual firmware is untouched, so there is no risk to the drive, and the original serial can be restored by removing the spoofer.
Why You Should Not Flash Firmware
Beyond the bricking risk, firmware modification has practical drawbacks:
- The drive's warranty is voided if the manufacturer detects a modified serial.
- RMA (Return Merchandise Authorization) becomes impossible because the serial on file no longer matches.
- The modification must be redone after any firmware update from the manufacturer.
- If the drive fails, data recovery services rely on the original firmware serial for their processes.
Software-level spoofing avoids all these issues while achieving the same result for anti-cheat purposes.
Multiple Drives and HWID Fingerprints
Modern systems typically have multiple storage devices: an NVMe boot drive, perhaps a SATA SSD for games, and maybe an external drive. Anti-cheats fingerprint all detected drives, not just the boot drive.
This means that adding or removing a drive changes the hardware fingerprint. Anti-cheats account for this with fuzzy matching — they do not require an exact match across all identifiers, but rather a threshold of similarity. If enough identifiers match (boot drive serial, motherboard serial, UUID, MAC address), the system is considered the same machine even if a secondary drive was added or removed.
This fuzzy matching is also why changing a single identifier is rarely sufficient to evade a ban. You need to change enough identifiers simultaneously to push the fingerprint below the matching threshold. For most anti-cheats, this means changing disk serials, motherboard identifiers, MAC addresses, and several other data points at once.
Checking Your Disk Serials: Quick Reference
| What You Want | Command |
|---|---|
| Firmware serial (all drives) | wmic diskdrive get SerialNumber, Model |
| Volume serial (all volumes) | wmic logicalDisk get VolumeSerialNumber, DeviceID |
| Detailed drive info | Get-PhysicalDisk | Select FriendlyName, SerialNumber, MediaType |
| NVMe specific info | Get-StorageAdvancedProperty -PhysicalDisk (Get-PhysicalDisk) |
| Drive health + serial | CrystalDiskInfo (free download) |
Summary
Disk serial numbers come in two types: the firmware serial (unique per drive, persistent, hard to change) and the volume serial (per-format, easy to change). Anti-cheats heavily weight the firmware serial in their HWID fingerprints and can read it through multiple paths including WMI, IOCTL calls, and direct drive commands. Changing the volume serial is trivial but ineffective against modern anti-cheats. Changing the firmware serial requires either risky firmware modification or a driver-level interception tool. Sense AC takes the safe approach — intercepting disk serial queries at the storage driver level to present consistent spoofed values across all query paths without touching the actual drive firmware.