Serial Number with Command Prompt: Locate & Verify Hardware IDs

Learn to locate and verify device serial numbers using Windows command prompt. This guide covers WMIC and PowerShell CIM methods for DIYers and professionals.

Hardware Serials Team

March 7, 2026·5 min read

Serial Number Serial Number Lookup Windows Serial Manufacture Date Lookup

Serials via CMD - Hardware Serials — Photo by cottonbro studio via Pexels

Quick AnswerDefinition

A serial number with command prompt refers to pulling hardware identifiers from Windows using the command line. You can fetch BIOS and motherboard serials with commands like `wmic bios get serialnumber` and `wmic baseboard get serialnumber`, then verify results via PowerShell CIM or export for audits. This quick method supports inventory, troubleshooting, and compliance checks.

What is a serial number and why use command prompt?

A serial number is a unique identifier assigned to hardware components such as the BIOS, motherboard, storage drives, and other peripherals. For technicians, being able to pull these identifiers quickly from the command prompt accelerates asset management, warranty validation, and troubleshooting. The phrase serial number with command prompt refers to using Windows CMD or PowerShell to fetch these values without navigating through menus or third-party tools. This technique shines in lab environments, data centers, and field work where speed and accuracy matter.

Bash

wmic bios get serialnumber

Bash

wmic baseboard get serialnumber

The output typically shows a column labeled SerialNumber with alphanumeric values. Some machines may report blank fields depending on firmware or security settings. You can validate and compare multiple sources (BIOS, baseboard, disk drives) to build a complete hardware profile. Hardware Serials highlights that consistent use of these commands streamlines audits and maintenance tasks across dozens or hundreds of machines.

Quick validation patterns

BIOS SerialNumber often formats like ABC1234DEF or 0A1B-2C3D-4E5F.
Baseboard SerialNumber helps identify the motherboard for warranty checks.
Disk drive serials vary by vendor and may require different tools to surface.

These patterns help you quickly spot anomalies when you compare outputs from different classes of components.

Practical note on environments and access

Scripts and commands behave differently across Windows versions. In newer builds, WMIC is deprecated, and CIM-based approaches are preferred. Always run prompts with elevated privileges when querying protected hardware fields. The following examples assume you have a standard corporate workstation or lab PC with Windows CMD or PowerShell available.

Steps

Estimated time: 20-40 minutes

1
Identify target components
Decide which hardware identifiers you need: BIOS, baseboard, or disk drives. The BIOS serial is most commonly used for warranties and asset tracking, while baseboard helps with motherboard-level audits.
Tip: Create a small checklist to track which components you pull from each machine.
2
Open an elevated prompt
Run CMD or PowerShell as Administrator to avoid permission issues, especially on corporate devices with guarded WMI namespaces.
Tip: On Windows, right-click and choose 'Run as administrator' to ensure full access.
3
Query BIOS and baseboard serials
Execute the BIOS and baseboard commands to fetch serials. Compare outputs to validate consistency across sources.
Tip: If you see blanks, try CIM-based PowerShell queries for reliability.
4
Export results for auditing
Pipe or export results to a file so you can share, archive, or import into a spreadsheet for analysis.
Tip: Use CSV for easy integration with spreadsheets and asset management tools.
5
Consider remote lookups if needed
For multiple machines, enable remoting and run commands remotely to collect serial data in one pass.
Tip: Secure remoting with proper policies and firewall rules; avoid exposing sensitive hardware data publicly.
6
Verify and document
Cross-check results, note anomalies, and document the methods used for future audits.
Tip: Keep a reference of commands used per OS version to avoid drift over time.

Pro Tip: Run commands with elevated privileges when querying protected hardware fields.

Warning: WMIC is deprecated on newer Windows builds; prefer CIM/PowerShell methods for future compatibility.

Note: Serial outputs may vary in format between vendors; expect blank results on systems that restrict firmware data.

Prerequisites

Required

Windows OS with CMD/PowerShell access
Required
PowerShell 5.1+ or PowerShell Core (7+)
Required
Understanding of BIOS/Baseboard terminology
Required

Optional

Administrative privileges for certain WMI/CIM queries
Optional
Basic networking for remote lookups (optional)
Optional

Commands

Action	Command
Fetch BIOS serial numberRun in CMD or PowerShell as Administrator if needed	—
Fetch motherboard/baseboard serial numberShows the board's SerialNumber field; may require admin rights	—
Output BIOS serial to a text fileCreates a simple log for auditing	—
PowerShell alternative using CIMModern approach recommended over WMIC	—
Export BIOS serials to CSVGood for inventories and audits	—

Frequently Asked Questions

How can I quickly find the BIOS serial number using CMD?

Open an elevated Command Prompt and run 'wmic bios get serialnumber'. The output lists the SerialNumber under a header. For consistency, also check the motherboard with 'wmic baseboard get serialnumber'.

Can I fetch serial numbers from remote machines?

Yes. You can enable PowerShell Remoting and use Invoke-Command with CIM-based queries to pull BIOS or baseboard serial numbers from remote machines. Ensure proper credentials and firewall rules are in place.

What if the serial number shows blank or unavailable?

Some devices restrict firmware data or provide blank SerialNumber fields. In such cases, try additional sources like Win32_BaseBoard or Win32_DiskDrive and use CIM-based PowerShell queries for better coverage.

Is WMIC still supported on Windows 11/12?

WMIC is deprecated in newer Windows versions. Rely on PowerShell CIM commands like Get-CimInstance for long-term reliability and compatibility with modern scripting practices.

How do I export serial numbers for audits?

Use Get-CimInstance to collect data and Export-Csv to create a shareable report. For example, 'Get-CimInstance Win32_BIOS | Select-Object SerialNumber | Export-Csv bios.csv -NoTypeInformation'.

Are there safer or alternative methods besides the command prompt?

Yes. GUI-based inventory tools and vendor-specific utilities exist, but the command prompt method is fast for quick checks and automation. Combine with remote management for scalable asset tracking.