Microsoft's venerable WMIC command-line tool has been on life support since Windows 10 version 21H1, and its gradual disappearance from new installations is forcing a long-overdue reckoning for PC users who need to identify their motherboard without a screwdriver. A Neowin guide published July 18, 2026, revisits two built-in methods — System Information and a modern PowerShell command — that read firmware-stored hardware details reliably on Windows 11 and Windows 10. The takeaway is clear: it’s time to retire the old wmic baseboard trick and adopt the Get-CimInstance approach, both for accuracy and to avoid the headache of a command that may suddenly fail when you need it most.
The Tools at Your Disposal
Windows has always shipped with ways to peek under the hood, but the motherboard — or “baseboard,” as Windows calls it — is one of those components that often stays hidden unless you know exactly where to look. Two tools sit right in the operating system, ready to spill the board’s secrets: the graphical System Information utility and PowerShell’s CIM cmdlets.
System Information (msinfo32) presents a tree of categories in a classic multi-pane window. Under System Summary, you’ll find BaseBoard Manufacturer, BaseBoard Product, BaseBoard Version, and, occasionally, a serial number. For a desktop you built yourself, this often shows a recognizable brand like ASUS or MSI and the retail model name. For a laptop, you might get an internal code — something like “854A” — that means nothing without the parent system model.
PowerShell offers a leaner alternative that returns just the facts, no GUI overhead. The command Get-CimInstance -ClassName Win32_BaseBoard | Select-Object Manufacturer, Product, Version, SerialNumber pipes the four fields straight into a table. It’s fast, scriptable, and doesn’t require administrator rights. For quick copy-paste into a support chat or compatibility checker, it’s the method of choice. A shorter variant — Get-CimInstance -ClassName Win32_BaseBoard | Select-Object Manufacturer, Product — omits version and serial number when you just need the high-level identity.
Both tools pull data from the computer’s firmware, not from a physical label. That means they can only report what the manufacturer programmed. When the board maker skimped on that programming, you get generic strings like “To Be Filled By O.E.M.” — a sure sign you’ll need the system model, not the board model, for any practical support or upgrade path.
Why WMIC Is No Longer Trustworthy
For two decades, Windows pros reached for wmic baseboard get manufacturer,product,serialnumber,version whenever they needed board details. The command still works on many systems running Windows 10 or 11, but its deprecation is not a rumor. Microsoft officially flagged WMIC as deprecated in Windows 10 version 21H1 (released May 2021) and began removing it from new installs and feature updates over subsequent releases. By now, a fresh Windows 11 24H2 installation may not include WMIC at all. If you’ve been relying on it in scripts or batch files, you’re one update away from a broken workflow.
PowerShell’s CIM commands — Get-CimInstance and its predecessors — are Microsoft’s strategic replacement for the aging WMI infrastructure. They work over the same WMI back-end, so they return identical data, but they’re more efficient, support remote sessions natively, and, critically, aren’t going anywhere. For everyday users, the biggest difference is consistency: a PowerShell command typed into Terminal will produce the same output on a home-built gaming rig, a school-issued laptop, or an enterprise-managed workstation (provided group policy hasn’t locked down PowerShell itself).
The Upgrade That Could Brick Your PC
Knowing your motherboard model isn’t a parlor trick. It’s the key to safe BIOS updates, RAM compatibility checks, and even resale listings. A wrong BIOS flash — say, you downloaded firmware for a close but not identical board revision — can render a PC unbootable. “Do not install a BIOS or UEFI update solely because its motherboard name looks similar,” the Neowin guide warns. “Firmware intended for a different board revision, laptop model, or OEM system can prevent the computer from starting.”
That risk extends to the subtle difference between a board model and a system model. On a custom-built desktop, the BaseBoard Product is your ticket to the manufacturer’s CPU support list and BIOS download page. On a Dell, HP, Lenovo, or Acer prebuilt, the motherboard may be a bespoke design that exists only inside that series. Searching for “Dell 0KX48P” will get you nowhere; what you need is the machine’s full System Model — like “OptiPlex 7080” — plus the BIOS version you’re currently running. That combination appears in System Information under System Manufacturer and System Model, or via Get-CimInstance -ClassName Win32_ComputerSystem | Select-Object Manufacturer, Model.
So while the motherboard’s identity feels foundational, it’s often the wrong target for OEM PC maintenance. Windows distinguishes them clearly: BaseBoard for the physical circuit, System for the finished product. Know which one you need before you start downloading.
How to Use PowerShell and System Information — Step by Step
For those who prefer a clickable path, System Information is the gentlest on-ramp:
- Press Windows + R, type
msinfo32, and hit Enter. - Wait for the System Summary pane to populate.
- Scroll to BaseBoard Manufacturer, BaseBoard Product, and BaseBoard Version.
- (Optional) Note System Manufacturer and System Model if you’re on a prebuilt.
- Use File > Export to save a text report if you need to share details with support — just triple-check the report for serial numbers before posting it online.
PowerShell hands you the data in two commands:
- The full motherboard picture:
powershell Get-CimInstance -ClassName Win32_BaseBoard | Select-Object Manufacturer, Product, Version, SerialNumber - The quick duo for compatibility research:
powershell Get-CimInstance -ClassName Win32_BaseBoard | Select-Object Manufacturer, Product - To save the result directly to your desktop as a text file:
powershell Get-CimInstance -ClassName Win32_BaseBoard | Select-Object Manufacturer, Product, Version, SerialNumber | Out-File "$env:USERPROFILE\Desktop\MotherboardInfo.txt"
All commands run without elevation. If you see “Get-CimInstance is not recognized,” ensure you’re in a PowerShell tab within Terminal — not Command Prompt — or right-click Start and select “Windows PowerShell” on older Windows 10 builds. On a managed device where PowerShell is restricted, fall back to System Information.
When Windows Lies to You
Since Windows pulls motherboard information from firmware, it’s subject to the attention span of the people who programmed that firmware. Common outcomes include:
- “To Be Filled By O.E.M.” The firmware holds a placeholder, not real data. This is frequent on white-box systems and older budget OEMs. If the board is retail, check the physical label between PCIe slots or the original packaging.
- “Default string” or blank The fields are present but unpopulated. Again, a physical inspection is your last resort.
- A cryptic code Laptops and sealed prebuilts often report an internal OEM part number, not a consumer-friendly name. Pair it with the System Model — that’s what the manufacturer’s support site expects.
In all cases, the mismatch isn’t a Windows error; it’s a gap in the PC’s own reporting. Switching to PowerShell won’t conjure missing data, but it will give you the same accurate view that System Information provides, without the noise of deprecated tools.
What to Watch For
As Windows 10 inches toward its end-of-support date in October 2025, many holdouts will finally transition to Windows 11, bringing them face-to-face with the WMIC removal. Microsoft has been clear that PowerShell’s CIM cmdlets are the future; the remaining WMIC installations are vestigial. For IT pros, that means auditing existing deployment scripts. For home users, it’s a reminder to learn Get-CimInstance now, before a critical system problem leaves you fumbling for a command that no longer exists.
The motherboard identifier itself isn’t changing — but the way we retrieve it is. Bookmark the PowerShell method, and next time you’re comparing QVL memory lists or hunting a BIOS update, you’ll have the right string, every time.