Finding your Windows 11 serial number from the Command Prompt is one of those tiny but essential skills every Windows user should have — it saves time when checking warranty status, filing support tickets, or preparing for repairs — and you can do it in seconds without third‑party tools.
Background
Modern Windows installations store multiple identifiers: a hardware serial number baked into the BIOS/UEFI, a system product/service tag, and — separately — a Windows product key or
digital license used for activation. Each identifier has a different role: the BIOS/UEFI serial or manufacturer “service tag” helps vendors match warranty and support records; the Windows product key or digital license proves software entitlement. Knowing which value you need and how to pull it quickly from the system can convert what’s usually a panicked search under a laptop into a one‑minute task. This article walks through the quickest command‑line methods, explains
what each value is and
why they sometimes differ (or appear blank), flags security and privacy considerations, and explains the near‑term change every user and helpdesk should expect: the legacy WMIC tool is being phased out and PowerShell/CIM is the supported replacement.
Quick summary: the commands that work now
- To retrieve a machine serial number (BIOS/UEFI):
- Command Prompt (legacy WMIC): wmic bios get serialnumber.
- PowerShell (recommended and future‑proof): (Get‑CimInstance -ClassName Win32_BIOS).SerialNumber.
- To retrieve the system/product identifying number (service tag):
- Command Prompt: wmic csproduct get identifyingnumber.
- PowerShell: Get‑CimInstance -ClassName Win32_ComputerSystemProduct | Select‑Object IdentifyingNumber.
- To retrieve an embedded Windows product key (if present in firmware):
- Command Prompt: wmic path softwareLicensingService get OA3xOriginalProductKey.
- PowerShell: (Get‑CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey or (Get‑WmiObject -Query 'SELECT OA3xOriginalProductKey FROM SoftwareLicensingService').OA3xOriginalProductKey.
Note: WMIC has been the most commonly quoted command in quick‑help articles and forum replies, but that tool is deprecated and being removed from newer Windows releases — use PowerShell/CIM where possible for longer‑term compatibility.
Why the difference between serial number, service tag, product key, and digital license matters
Serial number vs. service tag vs. product key — what each one is
- Serial number (BIOS/UEFI) — a hardware identifier that the manufacturer writes into the system firmware. Useful for warranty lookups and verifying the device model. This is what wmic bios get serialnumber reports (or the PowerShell equivalent).
- Service tag / IdentifyingNumber — OEMs often expose a separate product or service tag via WMI; vendors like Dell, HP, Lenovo use this to index support pages and driver downloads. Tools that pull Win32_ComputerSystemProduct.IdentifyingNumber return this value.
- Windows product key (25‑character key) — the software key used for activation when a retail or OEM product key is embedded in firmware. The OA3xOriginalProductKey field is where many OEM‑preinstalled systems store that key. Not all devices have it.
- Digital license (digital entitlement) — a different activation mechanism where Windows ties activation to hardware or a Microsoft account instead of exposing a 25‑character key. If you have a digital license (most modern preinstalled or upgraded systems do), commands that print a firmware product key may return nothing or NULL.
Common confusions and why commands sometimes return “blank” or “NULL”
- Many modern systems activate via digital license; the product key may not be present in firmware, so the OA3xOriginalProductKey query returns nothing. This is expected behavior and does not mean your copy of Windows isn’t genuine.
- Upgrades from old Windows versions or volume licensing (KMS) for corporate machines often mean there is no retail/OEM key in firmware. In managed environments, product keys are handled by corporate activation servers and the above queries will fail to show a simple 25‑character key.
- Some consumer devices bundle a separate physical sticker or documentation with a key; if you can’t get one out of the OS, check the packaging or vendor account.
Step‑by‑step: find the serial number and product key (with safe alternatives)
Below are concise, copy‑ready steps you can run immediately. Use
PowerShell where shown for a future‑proof method.
Option A — Quick: Command Prompt (works now on many systems)
- Click Start and type cmd.
- Right‑click Command Prompt and choose Run as administrator.
- To show the BIOS serial number, type:
wmic bios get serialnumber
Your serial will appear under SerialNumber.
- To show the system identifying number (service tag), type:
wmic csproduct get identifyingnumber
That prints the OEM service tag if the vendor provides one.
- To attempt to show the embedded Windows product key, type:
wmic path softwareLicensingService get OA3xOriginalProductKey
If the field is populated you’ll see the 25‑character key; otherwise you may get blank/NULL.
Security note: don’t paste or publish product keys; treat them like passwords.
Option B — Recommended: PowerShell (modern and supported)
- Press Start, type PowerShell (or Windows Terminal), right‑click and Run as administrator.
- BIOS serial number:
(Get‑CimInstance -ClassName Win32_BIOS).SerialNumber
This is the supported, scriptable equivalent and works on all current Windows builds.
- System identifying number / service tag:
Get‑CimInstance -ClassName Win32_ComputerSystemProduct | Select‑Object IdentifyingNumber
Use this for vendor service tags and product IDs.
- Product key (if present in firmware):
(Get‑CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey
If the system uses a digital license, this will often return nothing — that’s normal.
Option C — GUI alternatives (no command line)
- System Information: Win + R → msinfo32 → check System Summary for BIOS/SKU/Serial fields.
- Settings and Activation: Settings → System → Activation will show activation state and sometimes link a Microsoft account‑tied digital license that removes the need for an explicit key.
What to do when the command returns nothing or “NOT FOUND”
- If serial or identifyingnumber returns blank: your firmware may not expose the value (common for some custom builds or motherboards), or the vendor may store the information elsewhere. Boot into UEFI/BIOS — many systems list the serial or service tag there — or check the physical sticker on the chassis.
- If OA3xOriginalProductKey returns blank: you likely have a digital license. Sign in with the Microsoft account used on the device and check Settings → Activation; Windows will often reactivate automatically after reinstall.
- If you’re in a corporate environment and the machine is domain‑joined or KMS‑activated, contact IT: volume licensing makes the product key retrieval methods above irrelevant for activation purposes.
WMIC is being retired — what that means for help desks and power users
WMIC (the Windows Management Instrumentation Command‑line tool) has long been the shortcut quoted in countless help articles and videos. Microsoft has deprecated the WMIC utility and is removing it from newer Windows images; it will not be included by default in Windows 11 releases moving forward and may be removed during upgrades on many devices. Administrators should migrate scripts and documentation to PowerShell/CIM (Get‑CimInstance / Get‑WmiObject) to avoid breakage. Practical implications:
- If you find a machine where wmic returns “‘wmic’ is not recognized…”, use PowerShell instead. (Get‑CimInstance Win32_BIOS).SerialNumber delivers the same value and is supported.
- If you maintain automation (SCCM, scripts, inventory tools), convert WMIC calls to CIM/PowerShell equivalents. Microsoft’s guidance and release notes explicitly advise this migration.
Security and privacy: treat serials and keys carefully
- Serial numbers and service tags are usually safe to share with vendor support, but avoid posting them publicly. Attackers have used hardware IDs to craft social‑engineering or warranty‑fraud scams in the past.
- Product keys are effectively software licenses and should never be posted publicly. If someone asks for your product key in a forum, refuse — legitimate support channels will never ask you to post keys in public threads.
- Avoid untrusted third‑party tools that promise to “recover” keys; free utilities vary widely in safety. Prefer built‑in methods (PowerShell/CIM, msinfo32, or vendor support pages). If you must use a utility, choose well‑known tools with good reputations and scan executables before running them.
Troubleshooting activation and serial/SKU mismatches
- Error codes like 0xC004F050 or 0xC004F069 typically indicate a mismatch between installed edition and product key or an invalid/blocked key. The Activation Troubleshooter in Settings is the first recommended step. If that doesn't help, verify the license type (Retail vs OEM vs Volume) and the edition installed.
- If you replaced the motherboard, OEM licenses often do not transfer; retail licenses can be moved but may require contacting Microsoft activation support or using the Activation Troubleshooter with a Microsoft account linked to your digital license.
- If the product key you retrieved from firmware doesn’t work for activation, it might be an OEM-specific key tied to a different SKU or edition. Confirm edition match (Home vs Pro vs Enterprise) before attempting to activate.
For IT admins: inventory and automation tips
- Use PowerShell and CIM for bulk inventory. Example to export serial and service tag for many machines:
- Get‑CimInstance -ClassName Win32_BIOS | Select‑Object PSComputerName, SerialNumber
- Get‑CimInstance -ClassName Win32_ComputerSystemProduct | Select‑Object PSComputerName, IdentifyingNumber
Save results to CSV for asset databases.
- Avoid Win32_Product for mass queries: it can trigger Windows Installer repair behavior on certain systems — use other inventory classes where possible. That gotchas list appears in many admin discussions.
- Update deployment and management scripts off WMIC. Microsoft has documented the WMIC removal timeline; converting to Get‑CimInstance or other programmatic WMI APIs avoids future breakage.
Best practices: store and manage identifiers safely
- Store product keys in encrypted password managers (dedicated notes), not plaintext files. For corporate assets, keep serials and tags in an asset management system with role‑based access.
- Link your Microsoft account to your device’s digital license where supported — this makes recovery and reactivation much easier after hardware repairs. Settings → System → Activation shows linking options.
- When buying or selling hardware, record the BIOS serial, service tag, and any original installation media or key documentation. If you plan to move a retail license to a different machine, document the transfer steps and deauthorize the old device first.
Practical checklist — copy, paste, run
- Open PowerShell as Administrator.
- Run: (Get‑CimInstance -ClassName Win32_BIOS).SerialNumber — copy it to your asset record.
- Run: Get‑CimInstance -ClassName Win32_ComputerSystemProduct | Select‑Object IdentifyingNumber — copy service tag if present.
- Run: (Get‑CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey — if you get a 25‑character key, store it securely; if blank, document that the device uses a digital license.
Risks, limitations and when to escalate
- Some vendor devices deliberately do not expose serials via WMI; hardware stickers or UEFI screens may be the only source. If you can’t get a serial via software, document where you looked and escalate to vendor support.
- WMIC commands shown in older guides will eventually stop working on default Windows images. If a script relies on WMIC, it must be updated — leaving it unaddressed will cause automation failures on upgraded systems.
- Third‑party recovery tools can expose sensitive data or include unwanted telemetry/advertising. Use them only after vetting and ideally within a controlled environment.
Final analysis: strengths and risks of the Command Prompt approach
The command‑line approach is fast, scriptable, and works without extra software — its biggest strength is universality: administrators and advanced users can pull identifiers on nearly any machine with a couple of keystrokes. The built‑in WMI interface provides consistent fields that vendors and Microsoft use for device and licensing workflows.
However, there are clear risks and limitations:
- The traditional WMIC tool is being removed, so documentation must shift to PowerShell/CIM to remain reliable. Failure to migrate will create friction in helpdesk and automation.
- Many modern activations use digital licenses; that makes the product key field empty by design, which can confuse users who expect a visible 25‑character key. Guides that don’t explain digital licenses risk sending users down the wrong troubleshooting path.
- Exposing product keys or serials publicly is a privacy and security risk; emphasize secure storage and restricted sharing when teaching others.
Conclusion
Finding the serial number, service tag, or embedded product key from Windows 11 is straightforward and safe when you use built‑in tools and follow a few basic privacy rules. The simple commands shown in this article — especially the PowerShell, CIM‑based methods — will work across contemporary Windows builds and are the recommended, future‑proof approach. Remember: WMIC commands commonly quoted in older tutorials still work on many machines today, but the utility is being phased out; converting scripts and helpdesk steps to PowerShell now prevents future breakage and keeps your processes dependable. Keep these short commands handy for your own checklist, and store any keys or identifiers in encrypted, access‑controlled systems so they’re ready when warranty, support, or reinstallation time comes.
Source: Techloy
VIDEO: How to find your Windows 11 serial number using Command Prompt