Every BIOS download page, CPU compatibility list and RAM guide starts with the same question: what motherboard do I have? Windows 11 can answer it in under a minute. AMD’s own support documentation on identifying a motherboard tells owners to look at the System Summary page in Windows and says, “On the System Summary page, check the Baseboard Manufacturer, Baseboard Product, and BIOS Version/Date entries for information about the system motherboard.”
That advice still holds, but a lot of older guides now steer readers wrong. The most popular trick on the web, the wmic baseboard get product command, no longer works on current Windows 11 builds. Microsoft removed the WMIC utility from Windows 11 version 24H2 and later, and Windows 11 24H2 Home and Pro stopped receiving updates on October 13, 2026. Windows 11 version 26H2 is now the broadly available release, so any tutorial you follow today should work there.
This tutorial walks through 13 steps, takes about 25 minutes, and ends with a PowerShell script that saves a full hardware report to your desktop. You will find your motherboard model, chipset, socket and BIOS version with four independent methods, then use that information to download the right manual and plan a safe BIOS update without guessing. Every method below was chosen because it works on Windows 11 26H2 and 25H2 without extra downloads, except where we say otherwise.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Why Your Exact Motherboard Model Matters
“Gigabyte board” or “an ASUS board” is not an answer. Manufacturers sell dozens of boards under similar names, and a BIOS file built for one will not flash onto its sibling. The exact model name, plus the hardware revision when one exists, decides which BIOS file, which driver bundle and which manual belong to your machine.
Firmware is also moving faster than many owners realize. On October 13, 2026, GIGABYTE expanded BIOS support for future LGA1700 processors across its full Z790, B760 and H610 lineups, covering both DDR4 and DDR5 versions. That update means an older board can accept a newer processor, but only if you flash the matching BIOS for your exact model. Pick the wrong file and the best case is an error message. The worst case is a bricked board.
Knowing the model also protects your wallet. Before you buy a new GPU, an NVMe drive or a RAM kit, you need to know how many M.2 slots the board has, which memory standard it supports and how many DIMM slots sit free. Retailers publish compatibility tables by board name, not by “the thing in my case.” One reported item to keep in mind: an October 22, 2026 report says ASUS, GIGABYTE and MSI told sales channels to expect fourth-quarter motherboard price increases of 5% to 10%. The manufacturers have not confirmed that, but it is one more reason to check what you already own before you buy a replacement.
Support work benefits as well. When a forum asks “what is your motherboard and BIOS version,” a screenshot of System Information answers both. If your PC will not post and you need to recover it, the board name tells you whether it has a dedicated flash button. Boards with that feature let you update the BIOS without a CPU installed, which is how owners rescue a new processor that an old firmware cannot recognize.
Finally, there is the security angle. Firmware bugs and weak boot settings get patched through BIOS releases, and those releases are model-specific. You cannot patch what you cannot name. Spending five minutes on identification is the cheapest maintenance task you will do this year.
Prerequisites and Tools You Need
You do not need to open the case for most of this tutorial. A working Windows 11 install and a few built-in tools cover the first nine steps. Here is the checklist, with the versions that matter.
- Windows 11 version 26H2 or 25H2. Microsoft recommends moving to 25H2 or 26H2, and the commands below were written for those builds. Windows 11 24H2 Home and Pro ended updates on October 13, 2026, so update first if you are still there. Per BleepingComputer’s report on the 24H2 cutoff, Enterprise and Education editions have a longer runway.
- Windows PowerShell 5.1 (built in) or PowerShell 7.x. Either one runs every command in this guide. You do not need to install anything.
- Administrator access. Optional for most steps, required for the Secure Boot check in the final script.
- CPU-Z, latest version. A free utility from CPUID that reads the Mainboard tab. Optional but useful as a cross-check.
- HWiNFO, latest version. A free system information tool. Optional, and a good second opinion on the chipset name.
- A phone or camera. Photographing the board label saves you from retyping long model names.
- A flashlight and a Phillips screwdriver. Only needed for the physical inspection in Step 10.
Budget about 25 minutes. The software steps take roughly 10 minutes, the manual and BIOS lookup another 10, and the compatibility check the rest. If you run a laptop, a prebuilt desktop from Dell, HP or Lenovo, or a virtual machine, read the pitfalls section first, because the answers look different there.
One more preparation step costs nothing: create a plain text file called my-board.txt on your desktop. You will paste five values into it as you go: board manufacturer, board model, board revision, chipset and BIOS version with date. That small file becomes your reference every time you shop for parts or open a support ticket.
Which Method Should You Use? A Quick Comparison
There are six realistic ways to answer “what motherboard do I have.” They differ in speed, accuracy and the situations where they fail. Use this table to pick a starting point, then work through the steps in order if the first method returns something odd.
| Method | Time | Shows chipset | Shows BIOS version | Works if Windows will not boot |
|---|---|---|---|---|
| System Information (msinfo32) | 1 min | No dedicated field | Yes | No |
| PowerShell CIM query | 2 min | No | Yes | No |
| Command Prompt (systeminfo, dxdiag) | 2 min | No | Yes | No |
| CPU-Z or HWiNFO | 3 min | Yes | Yes | No |
| UEFI firmware screen | 5 min | Often | Yes | Yes |
| Physical inspection or box label | 10 min | Yes | No | Yes |
The pattern is simple. Software methods are fast but cannot see the chipset name reliably, because Windows exposes the board model and not the chipset marketing label. For that you either decode the model name (covered next) or use a third-party tool. Methods that read the firmware screen or the physical board work even when the operating system is gone, which is why the last two steps matter for broken machines.
How to Read a Motherboard Name Before You Start
Board names look like noise, but they follow a grammar. Learn it once and you can pull the chipset, tier and revision out of nearly any model string. Take a name such as “Z790 AORUS ELITE AX” from the GIGABYTE Z790 family. The first token is the chipset, the middle words are the product line and tier, and the suffix flags features such as built-in Wi-Fi.
| Part of the name | Example | What it tells you |
|---|---|---|
| Chipset code | Z790, B760, H610, X870E | Platform generation, overclocking support and lane count |
| Product line | AORUS, ROG Strix, MAG, TUF | Brand tier and styling |
| Tier word | ELITE, ULTRA, PRO | Relative feature level inside the line |
| Feature suffix | AX, WIFI, D4 | Wi-Fi card, or DDR4 versus DDR5 variant |
| Form factor tag | ITX, M-ATX, mATX | Physical size, slot count and case fit |
| Revision | Rev 1.0, V14 | Hardware change that can affect BIOS files |
A fresh example shows the grammar at work. COLORFUL’s iGame X870E ULTRA-S V14 was reportedly launched on October 20, 2026 at a stated price of CNY 1,899 (roughly US$265). You can read the chipset (X870E), the line (iGame), the tier (ULTRA-S) and a revision tag (V14) straight off the name without opening a spec sheet. Treat the price as reported, not confirmed.
Two warnings apply. First, the chipset letter alone does not tell you the socket. Intel Z790, B760 and H610 boards, for example, all belong to the LGA1700 generation, but you must confirm that on the product page. Second, DDR4 and DDR5 versions of the same chipset exist, so a “D4” suffix or a spec line matters. If you plan a platform change, a head-to-head like B850 versus X870 versus X870E on AM5 shows how much the chipset tier changes lanes and features.
Keep one more idea in mind: the name Windows reports is whatever the manufacturer wrote into the firmware. Most of the time it matches the retail name. On prebuilt PCs it often does not, and you will see an internal part code instead. The troubleshooting section covers that case.
Steps 1 to 3: Check Your Motherboard With System Information
Microsoft System Information is the fastest answer to “what motherboard do I have” on Windows 11, and it needs no download. The tool is included with Windows, runs as msinfo32.exe, and carries no separate price or edition. Start here, and only move on if it returns a placeholder.
Step 1: Open System Information. Press the Windows key plus R to open the Run box, type msinfo32 and press Enter. The System Information window opens on the System Summary page. If you see a long tree on the left, that is normal. Stay on the top item.
Step 2: Read the board fields. Scroll the right-hand pane until you find these rows: System Manufacturer, System Model, BaseBoard Manufacturer, BaseBoard Product, and BIOS Version/Date. On a custom-built desktop, the BaseBoard Manufacturer and BaseBoard Product rows are the ones that name your motherboard. On a prebuilt, the System rows name the whole computer and the BaseBoard rows may name an internal part.
Example System Summary (illustrative sample, your values will differ)
OS Name Microsoft Windows 11 Pro
System Manufacturer Gigabyte Technology Co., Ltd.
System Model Z790 AORUS ELITE AX
BIOS Version/Date American Megatrends International, LLC. F10, 3/12/2025
BIOS Mode UEFI
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
BaseBoard Product Z790 AORUS ELITE AX
BaseBoard Version x.xStep 3: Record the BIOS version and date. Copy the full BIOS Version/Date line into your notes file. The version string, such as “F10” in the sample above, is what you compare against the manufacturer’s download page later. Also write down the BIOS Mode line. Windows labels the field “BIOS,” but modern boards use UEFI, and “BIOS Mode” tells you which one you have. Secure Boot and some storage features require UEFI mode.
Be aware of one limit. According to Microsoft guidance, System Information cannot show hardware details when you run it in Safe Mode, where it falls back to system component and software environment data. If the hardware rows look empty, boot normally and try again. Also note that there is no dedicated chipset row. The chipset comes from the name decoding you just learned or from Step 7.
If the BaseBoard Product row reads something generic, jump ahead to the troubleshooting table. If it shows a clean model, paste it into your notes and carry on. You now have the answer most people need, and the remaining steps verify it and extend it.
Steps 4 to 6: Query the Board With PowerShell and Command Prompt
Graphical tools are fine for one PC. Commands are better when you want copyable text, a second opinion or a script. Windows 11 still ships everything you need, but the old WMIC tool is gone, so the syntax changed.
Step 4: Understand why WMIC fails. If you type wmic baseboard get product,manufacturer in a current Windows 11 build, you will get an error saying the command is not recognized. Microsoft’s own notice on the removal of WMIC from Windows confirms that only the command-line utility is gone. The underlying Windows Management Instrumentation platform still works, and Microsoft points scripts toward PowerShell CIM cmdlets as the replacement. Note that the linked page appears in German for some visitors, but the product names and commands are the same in every language.
Step 5: Run the PowerShell CIM query. Open the Start menu, type PowerShell, right-click Windows PowerShell and choose Run as administrator. Administrator rights are not strictly required for this query, but they avoid surprises later. Paste the two commands below.
Get-CimInstance -ClassName Win32_BaseBoard | Select-Object Manufacturer, Product, Version, SerialNumber
Get-CimInstance -ClassName Win32_BIOS | Select-Object Manufacturer, SMBIOSBIOSVersion, ReleaseDateThe first command reads the Win32_BaseBoard class, which Microsoft describes as representing a baseboard, also known as a motherboard or system board. The second reads the BIOS class. Here is what sample output looks like.
Manufacturer Product Version SerialNumber
------------ ------- ------- ------------
Gigabyte Technology Co., Ltd. Z790 AORUS ELITE AX x.x Default string
Manufacturer SMBIOSBIOSVersion ReleaseDate
------------ ----------------- -----------
American Megatrends International... F10 3/12/2025 12:00:00 AMThe Product column is your motherboard model. Do not worry if the SerialNumber says “Default string” or “None.” Many consumer boards never write a real serial into firmware, and the physical sticker holds the true number.
Step 6: Use Command Prompt as a cross-check. Two built-in commands give a second view. The systeminfo command prints the system manufacturer, system model and BIOS version, and you can filter it so only those lines appear. The DirectX diagnostic tool can write the same details to a text file.
systeminfo | findstr /i /c:"System Manufacturer" /c:"System Model" /c:"BIOS Version"
dxdiag /t "%USERPROFILE%\Desktop\dxdiag.txt"Open dxdiag.txt after a few seconds and look at the System Information block near the top. If System Model and the BaseBoard Product from Step 2 agree, you have a confirmed answer. If they differ, you probably have a prebuilt PC, which is common and explained in the troubleshooting section. Add whichever name matches the manufacturer’s website to your notes.
Steps 7 and 8: Confirm the Chipset With CPU-Z and HWiNFO
Windows reports the board model, but it rarely reports the chipset in a form you can read. Third-party tools fill that gap by reading the hardware directly. They also catch the occasional case where the firmware strings are wrong or generic. Use both tools below if you can, because a mismatch between them is itself a useful clue.
Step 7: Read the Mainboard tab in CPU-Z. Download the latest CPU-Z from the CPUID website, install it or run the portable ZIP, and open the Mainboard tab. You will see the board manufacturer, the model, the chipset and southbridge names, and a BIOS block with brand, version and date. Photograph or copy the Chipset line, since this is the value Windows itself cannot give you cleanly. Match the BIOS version here against Step 3. If the two agree, firmware reporting is healthy.
While CPU-Z is open, flip to the CPU tab for a moment. The socket line and the package name there help you confirm what the board physically supports. If you later undervolt or tune the processor, the same tab is your baseline, and a guide on how to check CPU temperature pairs well with the notes you are collecting.
Step 8: Cross-check with HWiNFO. Download the latest HWiNFO, choose the portable or installer build, and start it in Summary-only mode if the sensors window feels noisy. The summary window has a Motherboard panel listing the board model, chipset, BIOS date and version, and whether the firmware booted in UEFI mode. It also lists the slots HWiNFO can see, which helps when you are counting free DIMM positions.
Compare three sources now: System Information, CPU-Z and HWiNFO. In the usual case all three show the same model and BIOS. When they differ, the likely causes are a prebuilt with a custom firmware string, a recently flashed BIOS that Windows cached before a reboot, or a board that a vendor rebranded for an OEM. Trust the version that matches an actual product page on the manufacturer’s site, and note the discrepancy in your file.
A short privacy note belongs here as well. Utilities that read hardware identifiers can display serial numbers, and screenshots posted to forums can leak them. Before you share a CPU-Z or HWiNFO capture publicly, blur any serial number or product key field. The model name and BIOS version are all a helper needs.
Steps 9 and 10: Read the UEFI Screen and Inspect the Board
Software methods fail the moment Windows will not start, or when you suspect the operating system is reporting stale data. The firmware itself and the physical board are the ground truth. AMD’s support documentation makes the same point, noting that “Details about the motherboard manufacturer, chipset, and BIOS version are also available in the system BIOS.”
Step 9: Open the UEFI firmware screen. The fastest route on a PC that boots is through Windows. Open Settings, choose System, then Recovery, find Advanced startup and select Restart now. After the blue menu appears, pick Troubleshoot, then Advanced options, then UEFI Firmware Settings. If Windows will not boot at all, restart and tap the setup key as the logo appears. The key is commonly Delete or F2, but it depends on the manufacturer, so check the splash screen or the manual.
Once inside, look for a page called Main, System Information or Overview. Boards usually show the model name, the BIOS version and date, the installed CPU and the memory capacity on that first screen. Some also show the chipset or the Intel Management Engine version. Take a photo of it with your phone. Do not change any setting while you are there, and exit with the discard option unless you intended to edit something. If you do trigger a bad setting by accident, a guide on how to clear CMOS and reset the BIOS gets the board back to defaults.
Step 10: Inspect the board and check the paperwork. When even the firmware screen is out of reach, you read the hardware. Shut the PC down, switch off the power supply, unplug the cable and press the power button once to drain residual charge. Touch the bare metal of the case to discharge static, then open the side panel. The model name is printed on the board itself, usually between the PCIe slots, beside the RAM sockets or near the CPU socket. A large graphics card can hide the text, so use your phone camera with the flash on rather than pulling the card.
Look for the hardware revision too. It appears as “REV 1.0,” “REV 1.1” or a similar tag, and sometimes as a sticker on the board or the retail box. Some manufacturers publish separate BIOS files for different revisions, so a model name alone is not always enough. Boxes, receipts and order histories are the lazy shortcuts here. If you bought through a retailer, the order page often lists the exact model, and the box usually prints the chipset on the front.
A few practical cautions apply to every inspection. Do not pull RAM or cables unless you have a reason. Do not use compressed air at full blast on fans, which can spin them past their rating. And keep screws in a magnetic tray so one does not slip behind the board. If the PC is under warranty and a seal covers the case, check the warranty terms before you open anything.
Step 11: Identify the Chipset, Socket and Slot Layout
You now hold a model name. Step 11 turns that into the parts of the spec that drive upgrade decisions: chipset, CPU socket, memory standard, storage slots and PCIe layout. This is the step most tutorials skip, and it is where most upgrade mistakes begin.
Start with the motherboard chipset. Read it from the model name (the first token on most consumer boards), then confirm it in CPU-Z or on the manufacturer’s product page. The chipset sets the platform’s feature ceiling, including how many fast storage lanes the board offers and whether the CPU can be overclocked. Do not confuse the chipset with the CPU. The same board can run several processor generations only if the socket is shared and the BIOS has the right microcode.
| Spec to find | Where to read it | Why it matters |
|---|---|---|
| Chipset | Model name, CPU-Z Mainboard tab, product page | Sets feature ceiling and overclocking support |
| CPU socket | Product page, CPU-Z CPU tab | Decides which processors physically fit |
| Memory type | Product page, Win32_PhysicalMemory output | DDR4 and DDR5 are not interchangeable |
| DIMM slots and max capacity | Manual, the report script in this guide | Caps how much RAM you can add |
| M.2 slots and speeds | Manual, specification table | Some slots share lanes with SATA ports |
| PCIe slot layout | Manual, board diagram | A second card may run at reduced width |
| BIOS version needed for a CPU | CPU support list on the vendor site | Newer processors need a newer BIOS first |
Socket confusion causes expensive errors. On the Intel side, the Z790, B760 and H610 families covered by GIGABYTE’s October 2026 announcement all use the same LGA1700 socket, which is why one BIOS announcement could cover all three. On the AMD side, the AM5 generation has its own chipset tiers. The PowerShell report in the next section prints a socket label from Win32_Processor, but some Intel boards report an internal designation instead of the LGA name, so the product page remains the final word.
A word on rumors, since forum posts blur them with facts. Reports say that more than 20 Z990 model names appeared in an Eurasian Economic Union database on October 21, 2026, and one outlet linked them to a possible next Intel desktop platform. That is rumor. No Z990 board is on sale, and no official specification exists. Plan your upgrade around boards you can actually buy.
Steps 12 and 13: Find the Manual, BIOS and Compatibility Lists
With the model in your notes, the last two steps turn identification into action. Step 12 gets you the official manual and BIOS page. Step 13 checks that the part you want to add will actually work.
Step 12: Open the manufacturer’s support page for your exact model. Search the manufacturer’s own site, not a driver aggregator, for the board name. Every major vendor keeps a support page per board with tabs for manuals, BIOS, drivers and compatibility lists. ASUS shows what this looks like, since its BIOS and firmware page for the Pro WS W680-ACE is specific to that one board. BIOS updates are model-specific, so compare the BIOS Version/Date you recorded in Windows with what the manufacturer lists for your exact board.
That example proves a point: BIOS releases are per board, not per brand. ASUS also issued model-specific updates dated October 14, 2026 for other products, reportedly BIOS 316 for the B3408 and BIOS 343 for the RC71L. None of those files would help a different board. Match your BIOS Version/Date value from Step 3 to the list. If your installed version is the newest, stop. If it is several releases behind, read the release notes between your version and the latest, because they list fixed issues and added CPU support.
Download the PDF manual while you are there. It holds the block diagram, the M.2 and SATA sharing rules, the front-panel header pinout and the BIOS menu map. Save it next to your notes file. If the vendor lists multiple hardware revisions, pick the one that matches the label from Step 10. When you decide to flash, follow a careful routine such as this walkthrough on how to update your BIOS, which covers power protection and recovery options.
Step 13: Check compatibility before you buy anything. Use three lists from the vendor page. The CPU support list shows which processors work and the minimum BIOS each one needs. The memory qualified vendor list (QVL) names tested RAM kits. The storage notes in the manual explain which M.2 slot runs at full speed and which ones share bandwidth. Work through them in that order.
- CPU upgrade: confirm the socket matches, then confirm your installed BIOS is at or above the minimum version listed for that processor. If not, flash first and install the CPU second.
- RAM upgrade: confirm DDR4 or DDR5, count free slots, and check the maximum capacity. Mixing kits is allowed on paper but often forces lower speeds.
- NVMe upgrade: check the slot generation and whether it disables a SATA port. Before you move data, run through how to check SSD health on the drive you are replacing.
- GPU upgrade: confirm slot clearance and power connectors, and check that a second M.2 drive will not drop the GPU slot to a lower width.
If a compatibility entry says “BIOS F-something or later required,” that means your notes file earns its keep. The installed BIOS version you recorded in Step 3 is the number you compare against it. Skipping the comparison is the single most common cause of a new CPU that will not post.
Complete Working Project: A Motherboard Report Script
Doing the steps by hand once is fine. Repeating them every time a friend asks for help, or whenever you need to check motherboard model details on a second PC, is tedious. The script below pulls the board, BIOS, firmware mode, CPU, memory, GPU and storage details in a single run, then saves both a readable text file and a JSON file to your desktop. It uses only built-in Windows 11 cmdlets, so there is nothing to install.
The script
Save the following as board-report.ps1 in any folder. It reads the same Win32 classes you used in Step 5 and adds memory slot counts, the DIMM list and a Secure Boot check. The Secure Boot call needs an administrator window on a UEFI system, and the script falls back to a readable message if it cannot run.
param(
[string]$OutDir = [Environment]::GetFolderPath("Desktop")
)
$board = Get-CimInstance -ClassName Win32_BaseBoard
$bios = Get-CimInstance -ClassName Win32_BIOS
$sys = Get-CimInstance -ClassName Win32_ComputerSystem
$cpu = Get-CimInstance -ClassName Win32_Processor | Select-Object -First 1
$array = Get-CimInstance -ClassName Win32_PhysicalMemoryArray | Select-Object -First 1
$dimms = Get-CimInstance -ClassName Win32_PhysicalMemory
$gpus = Get-CimInstance -ClassName Win32_VideoController
$os = Get-CimInstance -ClassName Win32_OperatingSystem
$ramType = @{
24 = "DDR3"
26 = "DDR4"
34 = "DDR5"
35 = "LPDDR5"
}
$fwType = (Get-ComputerInfo -Property BiosFirmwareType).BiosFirmwareType
$secureBoot = try {
Confirm-SecureBootUEFI -ErrorAction Stop
} catch {
"Unknown (needs admin and UEFI)"
}
$memory = foreach ($d in $dimms) {
[pscustomobject]@{
Slot = $d.DeviceLocator
SizeGB = [math]::Round($d.Capacity / 1GB)
Type = $ramType[[int]$d.SMBIOSMemoryType]
RatedMHz = $d.Speed
RunningMHz = $d.ConfiguredClockSpeed
PartNumber = "$($d.PartNumber)".Trim()
}
}
$disks = foreach ($p in Get-PhysicalDisk) {
[pscustomobject]@{
Name = $p.FriendlyName
Media = $p.MediaType
Bus = $p.BusType
SizeGB = [math]::Round($p.Size / 1GB)
}
}
$maxGB = [math]::Round($array.MaxCapacityEx / 1MB)
$report = [ordered]@{
GeneratedOn = (Get-Date).ToString("yyyy-MM-dd HH:mm")
Windows = "$($os.Caption) build $($os.BuildNumber)"
SystemMaker = $sys.Manufacturer
SystemModel = $sys.Model
BoardMaker = $board.Manufacturer
BoardModel = $board.Product
BoardRevision = $board.Version
BoardSerial = $board.SerialNumber
BiosVendor = $bios.Manufacturer
BiosVersion = $bios.SMBIOSBIOSVersion
BiosDate = $bios.ReleaseDate.ToString("yyyy-MM-dd")
FirmwareMode = "$fwType"
SecureBoot = "$secureBoot"
Cpu = $cpu.Name.Trim()
CpuSocket = $cpu.SocketDesignation
MemorySlotsTotal = $array.MemoryDevices
MemorySlotsUsed = @($dimms).Count
MemoryMaxGB = $maxGB
Memory = $memory
Gpu = @($gpus | ForEach-Object { $_.Name })
Storage = $disks
}
$jsonPath = Join-Path $OutDir "board-report.json"
$txtPath = Join-Path $OutDir "board-report.txt"
$report | ConvertTo-Json -Depth 5 | Set-Content -Path $jsonPath -Encoding UTF8
$lines = @(
"Board: $($report.BoardMaker) $($report.BoardModel) (rev $($report.BoardRevision))"
"System: $($report.SystemMaker) $($report.SystemModel)"
"BIOS: $($report.BiosVendor) $($report.BiosVersion) dated $($report.BiosDate)"
"Mode: $($report.FirmwareMode), Secure Boot: $($report.SecureBoot)"
"CPU: $($report.Cpu) (socket label $($report.CpuSocket))"
"RAM slots: $($report.MemorySlotsUsed) of $($report.MemorySlotsTotal) used, board maximum $($report.MemoryMaxGB) GB"
)
foreach ($m in $memory) {
$lines += " DIMM $($m.Slot): $($m.SizeGB) GB $($m.Type), rated $($m.RatedMHz) MHz, running $($m.RunningMHz) MHz, part $($m.PartNumber)"
}
foreach ($g in $report.Gpu) {
$lines += "GPU: $g"
}
foreach ($d in $disks) {
$lines += "Disk: $($d.Name), $($d.SizeGB) GB, $($d.Media), $($d.Bus)"
}
$lines | Set-Content -Path $txtPath -Encoding UTF8
$lines
Write-Host ""
Write-Host "Saved: $txtPath"
Write-Host "Saved: $jsonPath"Run it and read the output
Open an elevated PowerShell window in the folder that holds the file and run the command below. The execution policy flag applies to this one run only and does not change your system setting.
powershell -ExecutionPolicy Bypass -File .\board-report.ps1On a typical desktop you should see output shaped like the sample below. This is an illustrative sample, so your board, CPU and memory values will differ.
Board: Gigabyte Technology Co., Ltd. Z790 AORUS ELITE AX (rev x.x)
System: Gigabyte Technology Co., Ltd. Z790 AORUS ELITE AX
BIOS: American Megatrends International, LLC. F10 dated 2025-03-12
Mode: Uefi, Secure Boot: True
CPU: Intel(R) Core(TM) i7-13700K (socket label U3E1)
RAM slots: 2 of 4 used, board maximum 192 GB
DIMM DIMM_A1: 16 GB DDR5, rated 5600 MHz, running 5600 MHz, part F5-5600J3636C16G
DIMM DIMM_B1: 16 GB DDR5, rated 5600 MHz, running 5600 MHz, part F5-5600J3636C16G
GPU: NVIDIA GeForce RTX 5070
Disk: Samsung SSD 990 PRO 2TB, 1863 GB, SSD, NVMe
Saved: C:\Users\you\Desktop\board-report.txt
Saved: C:\Users\you\Desktop\board-report.jsonRead the report from the top. The Board line is the model to search for on the vendor site. The BIOS line is the value to compare against the download list. The Mode line should say Uefi and show Secure Boot as True on a healthy Windows 11 machine. The RAM line tells you whether you have free slots, and the DIMM lines show whether memory runs at its rated speed. A running speed below the rated one usually means an XMP or EXPO profile is off in the firmware. Once the report is done, a quick pass through how to check GPU temperature rounds out a basic health snapshot of the machine.
Keep the JSON file. It is machine readable, so you can diff two reports taken before and after a BIOS update and see exactly what changed. Attach the text version to a support ticket and the helper gets everything they need on the first reply.
Common Pitfalls When You Identify a Motherboard
Most people who ask what motherboard do I have run into the same traps, and the traps are rarely technical. They come from reading the wrong field, trusting an outdated tutorial or skipping a verification step. These are the seven mistakes that trip up the most people, in rough order of how often they cost real money or time.
- Copying a WMIC command from an old guide. It looks authoritative, it appears in thousands of posts, and it fails on Windows 11 24H2 and later. Use
Get-CimInstanceinstead, and when a guide still teaches WMIC, check its publish date before you trust anything else it says. - Confusing the system model with the board model. On a Dell, HP or Lenovo desktop, the System Model row names the whole PC. The BaseBoard Product row may be an internal code that no retailer sells. Search the OEM’s support site with the system model or serial, not the board code.
- Treating the chipset as the socket. A chipset name such as B760 or X870E tells you the platform tier. The socket tells you which processor physically fits. Always confirm both on the product page.
- Ignoring the hardware revision. Two boards with the same name but different revisions can need different BIOS files. A sticker or silkscreen tag such as “REV 1.1” settles it. Photograph it during Step 10 while the case is open.
- Downloading BIOS files from aggregator sites. Third-party mirrors often host stale or mislabeled files. Get firmware only from the board maker’s support page for your exact model, and read the release notes before flashing.
- Running the tools in the wrong environment. Safe Mode hides hardware details from System Information. A virtual machine reports virtual hardware and says nothing about the host board. A remote desktop session into a different PC shows that PC’s board, not yours.
- Relying on a screenshot from last year. The BIOS version changes after every flash, sometimes through Windows Update on managed laptops. Re-run the checks before you compare against a CPU support list.
A related trap deserves its own mention: laptops. A laptop has a motherboard, but it is rarely a separate retail product, and manufacturers seldom publish it by name. For a laptop, the System Model and the product number on the bottom label are the identifiers that matter. BIOS and driver downloads are tied to that model, and the guesswork about “which board” does not help you.
Handhelds and mini PCs behave like laptops as well. If your device is a gaming handheld or a small-form-factor box with a soldered board, treat the product name as the board name. The OEM’s support page for that exact product is where its firmware and drivers live, and the internal board code rarely helps you there.
Troubleshooting: 12 Problems and Fixes
When a step returns something strange, find the symptom in this table first. Each fix is the smallest change that usually works.
| Symptom | Likely cause | Fix |
|---|---|---|
| “wmic is not recognized as an internal or external command” | WMIC was removed from Windows 11 24H2 and later | Use Get-CimInstance -ClassName Win32_BaseBoard in PowerShell |
| BaseBoard Product reads “To Be Filled By O.E.M.” or “Default string” | The board maker never wrote a name into firmware | Read the model in CPU-Z, the UEFI screen or the board silkscreen |
| BaseBoard rows are blank in System Information | Safe Mode is active, or WMI data is unavailable | Reboot normally and reopen msinfo32 |
| Get-CimInstance returns “Access denied” or “Invalid namespace” | Standard user window, or a damaged WMI repository | Open PowerShell as administrator, then run winmgmt /verifyrepository |
| “Running scripts is disabled on this system” | PowerShell execution policy blocks local scripts | Run powershell -ExecutionPolicy Bypass -File .\board-report.ps1 |
| Secure Boot shows “Unknown (needs admin and UEFI)” | No admin rights, or the PC boots in legacy mode | Rerun as administrator and check that FirmwareMode says Uefi |
| System Model and BaseBoard Product disagree | Prebuilt or OEM PC with an internal board code | Use the system model and serial on the OEM’s support site |
| Report shows “Virtual Machine” or a hypervisor name | You are inside a VM, so no physical board is visible | Run the tools on the host operating system |
| CPU-Z and System Information show different BIOS versions | A pending reboot after a recent BIOS flash | Restart fully, then read both again |
| Vendor page lists several revisions of your board | Hardware revisions use separate BIOS files | Match the REV label printed on the board or box |
| dxdiag.txt is empty or missing | The export has not finished, or the path is blocked | Wait a minute, then save to a folder you own, such as Documents |
| Desktop save path fails in the script | The Desktop folder is redirected to a cloud sync folder | Pass -OutDir C:\Temp when you run the script |
If the WMI repair command reports an inconsistent repository, run winmgmt /salvagerepository from an elevated prompt and try again. That fixes most cases where the CIM cmdlets fail on an otherwise healthy install. Reserve any deeper repair for the situation where nothing else works, because it touches system management data.
One more scenario is worth planning for: the PC reports the right board, but the vendor page offers no matching download. That usually means the board belongs to an OEM-only line. In that case the OEM’s support portal, searched by serial number, is the only trustworthy source for BIOS files. Do not flash a retail-board BIOS onto an OEM variant, even when the names look similar. The firmware checks will often reject it, and the ones that do not can leave the PC unbootable.
Advanced Tips for Power Users and IT Admins
Once the basics work, a few extensions turn a one-off lookup into a repeatable inventory habit. These tips suit anyone who manages several PCs, builds machines for friends or tracks firmware across upgrades.
Audit many PCs at once. The same CIM classes work remotely over WinRM. Put one hostname per line in pcs.txt and run the loop below from an admin account that has remote management rights. The result is a CSV you can sort by board model or BIOS version.
$results = foreach ($pc in Get-Content .\pcs.txt) {
$b = Get-CimInstance -ComputerName $pc -ClassName Win32_BaseBoard
$v = Get-CimInstance -ComputerName $pc -ClassName Win32_BIOS
[pscustomobject]@{
PC = $pc
BoardMaker = $b.Manufacturer
BoardModel = $b.Product
BiosVersion = $v.SMBIOSBIOSVersion
}
}
$results | Export-Csv -Path .\boards.csv -NoTypeInformationDiff before and after a BIOS update. Run the report script before you flash and again after. The JSON files compare cleanly, and you can see the new BIOS date, any changed memory speed and any reset of firmware mode in one pass. This also catches the quiet side effect where a flash resets XMP or EXPO and drops memory to its default speed.
Compare-Object (Get-Content .\before.json) (Get-Content .\after.json)List physical slots. The Win32_SystemSlot class reports the slots that firmware advertises, including their designation and whether each is in use. It is not always accurate on consumer boards, but it can confirm how many PCIe and M.2 positions the vendor declared. Treat it as a hint and verify against the manual diagram.
Get-CimInstance -ClassName Win32_SystemSlot | Select-Object SlotDesignation, CurrentUsage, MaxDataWidthUse Linux when Windows is out of reach. A live USB of any mainstream distribution can read the same firmware tables. The commands below print the baseboard record, the BIOS version and the board name without touching the installed system. That makes a live USB a clean choice for a dead Windows install.
sudo dmidecode -t baseboard
sudo dmidecode -s bios-version
cat /sys/class/dmi/id/board_nameRecord a BIOS changelog. Keep a short text file or a spreadsheet row for each PC with the board model, the BIOS version, the date you flashed it and the reason. Six months later, when a game crashes or a USB port misbehaves, that history tells you whether a firmware change lines up with the problem. Store the vendor’s release notes next to it.
Check hash values when the vendor publishes them. Some manufacturers list a checksum beside each BIOS download. Run Get-FileHash on the file you downloaded and compare. A mismatch means a bad download, and flashing a corrupted file is the fastest way to a dead board.
The takeaway: a motherboard model is one lookup that unlocks everything else. Check it once, save it with the BIOS version and revision, and rerun the script after any firmware change. If you keep going down the maintenance path, the hardware how-to guides cover temperatures, storage health, memory tuning and more.
Frequently Asked Questions
What motherboard do I have, and how do I find out without opening the case?
Press Windows key plus R, type msinfo32 and read the BaseBoard Manufacturer and BaseBoard Product rows on the System Summary page. Those two values name your board on most custom-built desktops. If they read as generic text, run the PowerShell command from Step 5 or open CPU-Z and check the Mainboard tab.
Why does the wmic baseboard command not work on Windows 11?
Microsoft removed the WMIC command-line utility from Windows 11 version 24H2 and later, and it is no longer available as an optional feature. The underlying WMI platform still works, so the replacement is the Get-CimInstance cmdlet in PowerShell. The query in Step 5 returns the same manufacturer and product values.
How do I check my motherboard chipset on Windows 11?
System Information has no dedicated chipset row, so use one of two routes. Read the chipset code from the start of the board model (for example Z790 or B760) and confirm it on the manufacturer’s product page. Or open the Mainboard tab in CPU-Z, or the Motherboard panel in HWiNFO, which list the chipset directly.
How can I find my motherboard model if the PC will not boot into Windows?
Enter the UEFI setup screen with the setup key shown at startup, commonly Delete or F2, and read the main information page. If the screen is unreachable, power down, open the case and read the model printed on the board itself. A Linux live USB with dmidecode is a third option that needs no case access.
Is a laptop’s motherboard model the same as the laptop model?
In practice yes. Laptop boards are rarely sold separately, and manufacturers tie BIOS and driver downloads to the laptop’s system model or product number. Use the System Model value from System Information plus the serial number on the bottom label when you search the maker’s support page.
Should I update my BIOS once I know my motherboard?
Not automatically. Update when the release notes fix a problem you have, or when a new processor or memory kit needs a newer version, as with GIGABYTE’s October 2026 LGA1700 support expansion. If everything works and the notes offer nothing you need, leaving a stable BIOS alone is a sound choice.
Can I find my motherboard model on Linux or macOS?
On Linux, sudo dmidecode -t baseboard and cat /sys/class/dmi/id/board_name print the board details. On a Mac, the logic board is not a swappable retail part, so About This Mac and the model identifier are the information you need for support and compatibility.
