How to Use CMD to Check Serial Numbers: A Practical Guide
Learn how to use CMD to check serial numbers on Windows. This practical guide covers BIOS, motherboard, and disk serials with clear commands, examples, and troubleshooting tips.
Use CMD to fetch hardware serials by querying BIOS, system product, motherboard, and disks with WMIC. Open Command Prompt as administrator and execute commands such as 'wmic bios get serialnumber' and 'wmic csproduct get identifyingnumber' to retrieve identifiers. You can redirect outputs to files for logs. These steps provide quick inventory checks without third party tools.
Overview: Why use CMD to check serial numbers
For asset auditing and hardware verification, Command Prompt offers fast, built-in access to serial data without third-party tools. In this article, we show how to use cmd to check serial number for BIOS, motherboard, disks, and system products. The techniques work on most Windows environments and align with best practices from Hardware Serials.
Note: This guide uses the exact keyword phrase how to use cmd to check serial number where appropriate to help search alignment and practical usage for DIYers and professionals.
Quick-start: Your first BIOS serial check
Begin with the simplest check: the BIOS serial number. This uniquely identifies the motherboard/BIOS image and is often present in hardware inventories. We'll walk you through the command, expected outputs, and edge cases. Remember to run CMD as administrator to access restricted hardware data when required.
wmic bios get serialnumber- The command returns a single serial value or blank if not exposed. If you see a blank field, switch to PowerShell-based retrieval or check BIOS settings. If you see a value like XXXXX-YYYY, record it for asset logs.
Inspecting common sources: BIOS, system product, motherboard, and drives
Windows stores serial numbers in several locations. Use separate WMIC queries to avoid ambiguity and ensure you map each value to the correct component in your asset ledger. This section covers BIOS, system product, motherboard, and disk drives, with notes on how to interpret each field.
wmic bios get serialnumber
wmic csproduct get identifyingnumber
wmic baseboard get serialnumber
wmic diskdrive get serialnumber- BIOS: hardware BIOS/firmware serial.
- IdentifyingNumber: system product serial.
- Baseboard: motherboard serial.
- DiskDrive: hard drive serials.
Interpretation tips: if multiple drives appear, map to the corresponding drive letters via Disk Management or a disk inventory tool.
Redirecting output for logging and audits
To preserve serial data for asset records, redirect the outputs to log files. This makes it easy to share, audit, or import into a CMDB without re-running the queries. You can accumulate a full hardware snapshot across sessions.
wmic bios get serialnumber > bios_serial.txt
wmic csproduct get identifyingnumber > system_identifying.txtThen inspect the files:
type bios_serial.txtThese steps enable you to build a small hardware inventory log while keeping your CMD session clean. You can append results across machines in a batch script for fleet management.
PowerShell alternatives and caveats
Microsoft is phasing WMIC in favor of PowerShell. If WMIC is unavailable or you need richer objects, use PowerShell:
Get-WmiObject Win32_BIOS | Select-Object SerialNumber
(Get-WmiObject Win32_ComputerSystemProduct).IdentifyingNumber
(Get-WmiObject Win32_BaseBoard).SerialNumber
Get-WmiObject Win32_DiskDrive | Select-Object SerialNumber- These commands run in PowerShell and produce structured output. While not CMD-based, they achieve the same goals with modern tooling. Hardware Serials recommends using PowerShell for long-term reliability.
Troubleshooting: common issues and how to resolve
- If a command returns blank, the serial data may be restricted by the BIOS or hardware vendor. Try alternative sources such as the system product or baseboard.
- If WMIC is not found, verify the WMIC binary location in PATH or use PowerShell alternatives.
- Some systems report serials only when run with elevated privileges. Run CMD as Administrator to access restricted data.
Best practices for auditing and documentation
- Always verify the data against multiple sources to avoid misidentification. Cross-check BIOS, motherboard, and disk serials when building an asset ledger.
- Record timestamps and hostnames alongside the serial values for accurate auditing. Store results in secure logs and back them up regularly.
- If you manage a fleet, automate the process via a script that collects serials from all devices and exports to CSV or JSON for central inventory.
Steps
Estimated time: 15-25 minutes
- 1
Open CMD as administrator
Open the Start menu, type CMD, right-click Command Prompt, and choose Run as administrator to ensure access to hardware data when required.
Tip: Avoid running in a non-elevated session for restricted data. - 2
Query BIOS serial
Enter 'wmic bios get serialnumber' to read the BIOS/firmware serial.
Tip: If the field is blank, check BIOS settings or vendor limitations. - 3
Query system and motherboard
Run 'wmic csproduct get identifyingnumber' and 'wmic baseboard get serialnumber' to capture system and motherboard IDs.
Tip: Use both sources to cross-verify hardware identity. - 4
Query disk drives
Execute 'wmic diskdrive get serialnumber' to enumerate each drive's serial number.
Tip: If multiple drives appear, map them to drive letters in Disk Management. - 5
Log results for audits
Redirect outputs to files as you go, e.g., 'wmic bios get serialnumber > bios_serial.txt'.
Tip: Keep a dated log per device.
Prerequisites
Required
- Required
- Administrative privileges (required for restricted data)Required
- Basic CMD/CLI knowledgeRequired
Optional
- Optional
Commands
| Action | Command |
|---|---|
| BIOS serial numberRetrieves BIOS/firmware serial | — |
| System product serialIdentifyingNumber is the system's product serial | — |
| Motherboard serialMotherboard serial | — |
| Disk drive serialsSerials per physical drive | — |
| Save BIOS serial to fileLog to file | — |
| PowerShell alternative (BIOS)PowerShell approach | — |
Frequently Asked Questions
Can WMIC still be used on Windows 11?
WMIC remains available on many Windows 11 systems but is deprecated and may be removed in future updates. For long-term viability, switch to PowerShell-based queries like Get-WmiObject. Hardware Serials recommends using PowerShell for serial lookups when possible.
WMIC is still present on many Windows 11 systems but is being phased out; use PowerShell equivalents for future compatibility.
Which serial numbers can I retrieve with these commands?
You can retrieve the BIOS SerialNumber, the system product IdentifyingNumber, the motherboard SerialNumber, and the SerialNumber of each disk drive. These sources cover firmware, motherboard, and storage identity.
You can pull BIOS, system product, motherboard, and disk serials.
What should I do if a serial number is blank or missing?
If a serial field is blank, it may be restricted by BIOS vendor, the hardware, or your permissions. Try alternative sources such as the system product or baseboard. Consider PowerShell-based queries for deeper access.
If blank, check other sources or permissions, and try PowerShell alternatives.
Is it safe to run these commands?
These commands read hardware identifiers and do not modify system state. Run as a regular user, but use elevated privileges if you encounter access issues. Always back up logs and avoid sharing sensitive IDs publicly.
Yes, they read data only; run with care and preserve logs.
What is the best practice for Windows vs PowerShell?
For long-term reliability, prefer PowerShell over WMIC because WMIC is deprecated. Use Get-WmiObject or newer CIM cmdlets to fetch SerialNumber, IdentifyingNumber, and related fields.
PowerShell is the recommended modern approach for serial lookups.
Can I automate this across many machines?
Yes. Build a small script that queries each machine via remote PowerShell sessions or a management tool, and export results to a central CSV or JSON inventory. Ensure credentials are securely managed.
You can automate serial lookups across devices with a script and central log.
Key Takeaways
- Open CMD and run serial queries
- Use multiple sources to verify hardware identity
- Redirect outputs for logging
- PowerShell offers robust alternatives
- Document timestamps and hostnames with the results