Introduction
Windows includes several built-in tools for viewing hardware specifications and system information. This article covers CMD, PowerShell, System Information, and DxDiag for checking the CPU, RAM, BIOS, motherboard, disks, graphics adapter, and overall system details.
01 — General System Information
Run systeminfo in Command Prompt to view detailed Windows and hardware configuration information.
systeminfoThe output includes information such as the Windows version, system model, BIOS details, installed RAM, and network adapter configuration.
02 — View CPU Information
Run the following PowerShell command to view the processor name, manufacturer, core count, logical processor count, and reported maximum clock speed.
Get-CimInstance Win32_Processor |
Select-Object Name, Manufacturer, NumberOfCores, NumberOfLogicalProcessors, MaxClockSpeed03 — View RAM Information
The following command lists the physical memory modules and their manufacturer, part number, capacity, and speed.
Get-CimInstance Win32_PhysicalMemory |
Select-Object Manufacturer, PartNumber, Capacity, Speed04 — Motherboard and BIOS
Use CIM classes to view motherboard and BIOS information without relying on the deprecated WMIC command-line utility.
Get-CimInstance Win32_BaseBoard
Get-CimInstance Win32_BIOSWMIC is deprecated and has been removed from newer Windows releases. Use CIM/PowerShell for new scripts and commands.
05 — Disk Information
Check the available physical disks, their media type, size, and health status.
Get-PhysicalDisk |
Select-Object FriendlyName, MediaType, Size, HealthStatus06 — Graphics Adapter
Use the video-controller CIM class to view the graphics-adapter name, driver version, and reported adapter memory.
Get-CimInstance Win32_VideoController |
Select-Object Name, DriverVersion, AdapterRAM07 — Use DxDiag
Run DxDiag to open the DirectX Diagnostic Tool.
dxdiagSystem
Shows Windows, system, processor, memory, BIOS, and DirectX information.
Display
Shows graphics-adapter and display-driver details.
Sound and Input
Shows detected audio devices and input devices such as keyboard and mouse.
To save a text report, run the following command. Ensure that the destination folder exists and is writable.
dxdiag /t C:\Temp\dxdiag.txt08 — System Information
Open the graphical System Information utility for a detailed, categorized view of hardware resources, components, and the software environment.
msinfo32| Tool | Best use | Interface |
|---|---|---|
| systeminfo | General Windows and system configuration | Command Prompt |
| DxDiag | DirectX, graphics, audio, and input diagnostics | Graphical utility and text export |
| msinfo32 | Detailed, categorized system inventory | Graphical utility |
Best Practices
- Use CIM/PowerShell instead of WMIC for new automation and scripts.
- Run PowerShell with appropriate permissions when a command needs access to protected system information.
- Save DxDiag output when collecting information for support or troubleshooting.
- Compare hardware reports with the manufacturer documentation when planning an upgrade.
Troubleshooting
A command is not recognized
Run CMD or PowerShell as appropriate, verify the command spelling, and confirm that the required Windows component is available.
Hardware information is missing
Update the relevant device driver and compare the result with System Information or the hardware manufacturer documentation.
DxDiag cannot write its report
Confirm that the destination folder exists and that the current user can write to it.
Frequently Asked Questions
Should I use WMIC for new hardware inventory scripts?
No. WMIC is deprecated; use CIM cmdlets in PowerShell for new work.
Which tool is best for graphics and DirectX troubleshooting?
Use DxDiag because it focuses on DirectX, display, sound, and input information.
Why do the reported RAM values require conversion?
Some CIM properties report capacity in bytes, so convert the value to MB or GB when preparing a readable report.
Conclusion
Use systeminfo for a quick general view, CIM cmdlets in PowerShell for structured hardware queries, DxDiag for DirectX and multimedia diagnostics, and msinfo32 for a detailed graphical inventory. Prefer CIM/PowerShell over WMIC in current Windows environments.
