Master Windows 10 Hardware Checks: Built-in Tools for Diagnostics & Upgrades

Windows 10 gives you more ways than ever to inspect the hardware and software under the hood — from the quick, user-friendly Settings > About panel to deep, exportable inventories created by System Information (msinfo32), dxdiag, PowerShell, and classic command-line tools — and knowing which method to use matters when you’re preparing for upgrades, troubleshooting, or sharing a support-ready system report.

Background​

Modern Windows systems are complex stacks of firmware, drivers, and device-specific components. A seemingly minor mismatch — an outdated GPU driver, a missing UEFI setting, a misreported BIOS string — can be the root cause of performance problems, compatibility errors, or blocked upgrades. Windows 10 ships with multiple built-in tools to inspect this stack: the Settings “About” page, System Information (msinfo32), the DirectX Diagnostic Tool (dxdiag), Task Manager and Device Manager, PowerShell (Get-ComputerInfo), and the Command Prompt (systeminfo). Each tool emphasizes different data points and workflows, and the right choice depends on whether you need a high-level check, a support-ready text dump, or an automated inventory for dozens of machines.
Microsoft has also set a firm timetable for Windows 10’s lifecycle: Windows 10 reaches end of support on October 14, 2025, after which most consumer devices will no longer receive security or feature updates unless enrolled in the Extended Security Updates (ESU) program. For users who need more time, Microsoft is offering a consumer ESU path that provides critical security updates beyond the 2025 deadline. Plan upgrades, backups, and compatibility checks now to avoid service interruptions or security exposure. (support.microsoft.com)

---

Overview: which tool to use and why​

• Settings > System > About — quick and readable summary for casual checks (CPU, RAM, Windows edition and build).
• System Information (msinfo32) — deep, structured inventory including firmware, installed drivers, motherboard strings, and exportable reports.
• DirectX Diagnostic Tool (dxdiag) — concise GPU/audio snapshot and common support dump used by game developers and GPU vendors.
• PowerShell (Get-ComputerInfo) — scriptable, filterable output ideal for automation and remote inventory.
• Command Prompt (systeminfo) — classic CLI snapshot, useful for quick captures and minimal scripting.
• Task Manager & Device Manager — live telemetry and per-device driver control for immediate troubleshooting and driver rollbacks.

Each tool is appropriate for different workflows: use Settings for a fast check, msinfo32 or dxdiag for support-ready exports, and PowerShell or systeminfo for automation and batch reporting.

---

How to get a quick snapshot: Settings > About​

The fastest place to check essential specs is Settings > System > About. The page displays the processor model, installed RAM, system architecture (32-bit/64-bit), Windows edition (Home/Pro), the installed Windows version and OS build, and basic device model information. The page also now surfaces cards highlighting memory type, graphics, and storage capacity in a readable layout. For quick copy/paste to a support ticket, use the Copy button on the About page to place the details into the clipboard.
Why use Settings:

• Best for non-technical users who only need CPU, RAM, and OS build.
• Fast, readable, and safe to share.

Why not rely on Settings alone:

• It omits firmware details, precise driver versions, and motherboard or slot-level memory information needed for advanced troubleshooting.

---

Deep-dive inventory: System Information (msinfo32)​

What msinfo32 shows​

System Information (msinfo32) is the most comprehensive built-in profiler in Windows 10. It aggregates:

• System Summary: full processor name, number of cores/sockets, total physical memory, firmware type and version (UEFI/BIOS), system model and vendor strings.
• Hardware Resources: IRQs, DMA, memory-mapped I/O ranges.
• Components: display adapters and drivers, storage controllers and disks, network adapters and MACs.
• Software Environment: running services, environment variables, installed drivers.
  It also includes a search box for fast lookups. (learn.microsoft.com)

How to open and export a report​

• Press Windows, type msinfo32, and press Enter.
• Choose System Summary (for everything) or expand Components for targeted details (Display, Storage, etc.).
• File > Export, choose a filename like "Windows10_Hardware_Specs.txt", and save.

The exported report is plain text and is ideal for attaching to support tickets or archiving; however, treat exported files as moderately sensitive because they can include serial numbers and network identifiers. Many vendors and OEM support pages instruct users to generate msinfo32 reports before opening a support case. (nvidia.custhelp.com)

Strengths and limitations​

• Strengths: Comprehensive, hierarchical view; exportable; no third-party tools required.
• Limitations: Some OEM-specific values may be missing; running as Administrator improves accuracy for driver caches and firmware reads.

---

Fast graphics & audio snapshot: DirectX Diagnostic Tool (dxdiag)​

The DirectX Diagnostic Tool is the standard quick-report for graphics and audio troubleshooting. It displays system manufacturer, model, processor, memory, DirectX version, and — on the Display tab — GPU name, vendor, driver version, and display modes. Use Save All Information to create a compact dxdiag.txt file that vendors often request. Intel, NVIDIA, and game support teams routinely ask for dxdiag outputs when diagnosing video or sound issues. (intel.com)
Step-by-step:

• Press Windows + R, type dxdiag, press Enter.
• (Optional) Click “Run 64-bit DxDiag” if prompted.
• Click Save All Information, choose a folder, and save the .txt file.

When to use dxdiag:

• Report GPU driver problems, DirectX errors, or audio device conflicts.
• Provide a compact, standard text file to game publishers and GPU vendors. (intel.com)

---

Power users and sysadmins: PowerShell’s Get-ComputerInfo​

PowerShell’s Get-ComputerInfo is a scriptable, filterable way to retrieve dozens — often hundreds — of system properties, ideal for automation and inventory workflows. The cmdlet was introduced in PowerShell 5.1 and returns a structured object that can be filtered with the -Property parameter or exported to text, CSV, or JSON. Example commands:

• Full dump: Get-ComputerInfo
• BIOS-only: Get-ComputerInfo -Property "bios*"
• Export to file: Get-ComputerInfo | Out-File -FilePath C:\Temp\computer-info.txt -Encoding utf8

Third-party documentation and PowerShell guides recommend Get-ComputerInfo for bulk inventory because it’s automatable across machines using remoting or management tooling. Note the cmdlet can return vendor-neutral properties; some OEM-specific details may still require vendor tools or msinfo32. (pdq.com)

When to choose PowerShell over msinfo32​

• You need repeatable, scriptable output for dozens or hundreds of devices.
• You want to filter properties, integrate with CSV/JSON pipelines, or remotely query multiple endpoints.
• You prefer a programmatic approach for asset management or automated audits. (pdq.com)

---

Command Prompt: systeminfo​

systeminfo is a simple, script-friendly CLI utility that returns OS name, architecture, install date, BIOS mode (UEFI vs BIOS), installed memory, hotfix list, and more. It’s particularly useful for quick command-line captures and legacy scripts. Example:

• Run as admin: systeminfo
• Save to CSV: systeminfo /fo CSV > C:\Temp\systeminfo.csv

Use systeminfo when you need a classic command-line snapshot or when PowerShell isn’t an option.

---

Live telemetry and device control: Task Manager & Device Manager​

Task Manager’s Performance tab shows real-time CPU, GPU, memory, and disk usage. Since Windows 10 build 18963, Task Manager can also display GPU temperature, but this is subject to constraints:

• GPU temperature display requires a dedicated GPU (discrete card).
• The GPU driver must implement WDDM 2.4 or later for Task Manager to read temperatures.
• Temperature is shown in Celsius and will not appear for many integrated GPUs or older drivers. (howtogeek.com)

Device Manager lists installed hardware by category and is the place to inspect or roll back drivers, view device IDs, and troubleshoot driver conflicts. Use Device Manager when you suspect a specific driver is causing instability or device failures.

---

BIOS/UEFI, TPM, and Windows 11 compatibility checks​

System Information and Windows Security > Device Security expose firmware details such as UEFI vs legacy BIOS, Secure Boot state, and TPM presence/version. These values matter if you plan to upgrade to Windows 11: the OS requires UEFI with Secure Boot and TPM 2.0 on most supported upgrades, and Microsoft offers tools (PC Health Check) to verify upgrade eligibility. If your PC lacks TPM 2.0 or Secure Boot, a firmware update or a BIOS setting change may enable these features — but behavior varies by vendor and model. For formal compatibility checks and upgrade planning, cross-reference msinfo32 findings with Microsoft’s Windows 11 requirements. (learn.microsoft.com)

---

Exporting and sharing reports — practical steps and privacy warnings​

Exported system reports are excellent for technical support and inventory, but they can contain sensitive identifiers:

• Serial numbers, BIOS strings, and motherboard IDs.
• MAC addresses and network adapter names in some reports.
• Installed software lists and driver versions.

Best practices:

• Scrub or redact serial numbers and MACs before sharing publicly.
• Share exports only with trusted support channels or via secure ticketing systems.
• Use msinfo32’s export or dxdiag’s Save All Information to create the canonical files vendors expect.

---

Practical checklists and step-by-step sequences​

Quick checklist: determine if your PC is ready for Windows 11 (one-minute check)​

• Open Settings > System > About and confirm CPU and RAM.
• Run msinfo32 and check System Summary for UEFI Firmware and Secure Boot State.
• In msinfo32 or Windows Security, verify TPM is present and version is 2.0.
• Run the PC Health Check tool to confirm Microsoft’s compatibility result. (learn.microsoft.com)

Create a full troubleshooting packet (recommended for support contacts)​

• Open msinfo32 → File > Export → save as MsInfo_Report.txt. (Include System Summary and Components > Display.)
• Press Windows + R → dxdiag → Save All Information → DxDiag.txt.
• Open PowerShell (Admin) → Get-ComputerInfo | Out-File C:\Temp\computer-info.txt.
• Compress the three files and attach them to your vendor/IT ticket after scrubbing serials or MAC addresses. (intel.com)

---

Critical analysis — strengths, shortfalls, and security trade-offs​

Windows’ built-in tools are powerful and generally sufficient for most use cases, but each has trade-offs worth noting.
Strengths

• No third-party installs: All tools ship with the OS, reducing the risk of external executables or added telemetry.
• Exportability: msinfo32, dxdiag, and PowerShell all support saving human-readable or machine-friendly dumps for archiving or automation.
• Multiple interfaces: GUI, CLI, and programmatic access cover every user profile from novice to enterprise admin.

Limitations and risks

• Partial data: Settings > About intentionally provides a high-level view and can hide critical driver or firmware details needed for diagnosis. Relying solely on it can mislead a troubleshooting effort.
• Vendor fields may be absent: msinfo32 depends on OEM-provided SMBIOS strings; some custom or older builds may not report every field, leading to gaps for motherboard serials or per-slot memory details. When vendor-specific introspection is needed, OEM utilities may still be required.
• Privacy of exports: Exported reports contain identifiers. Sending them to public forums or unclear email addresses can expose hardware serials tied to warranty and inventory systems. Treat exported files like account-level data.
• ESU and life-cycle complexity: Windows 10’s end-of-support timeline is firm (October 14, 2025), but enrollment options for consumer ESU and vendor support windows can be regionally inconsistent. Verify enrollment options in Windows Update or Microsoft account prompts rather than relying on third-party reports. If you choose ESU, understand it covers only security updates, not feature updates or expanded vendor support. (support.microsoft.com)

Caution on unverifiable claims

• Any published claims about consumer pricing, enrollment fees, or limited offers for ESU can vary by region and over time; verify terms in your Microsoft account’s Windows Update or the official Microsoft lifecycle pages before making purchasing decisions. (support.microsoft.com)

---

Advanced tips and troubleshooting traps​

• Run msinfo32 and dxdiag as Administrator when possible to reduce stale or cached results; this improves access to driver caches and firmware queries.
• If Task Manager doesn’t show GPU temperature, confirm you have a discrete GPU and a driver implementing WDDM 2.4+; otherwise use vendor tools (NVIDIA/AMD) or third-party monitors such as HWiNFO, HWMonitor, or Core Temp for CPU temperatures. The GPU temperature readout is provided in Celsius only and requires modern driver support. (howtogeek.com)
• For automation across a fleet, prefer PowerShell’s Get-ComputerInfo or CIM/WMI-based queries and output to CSV/JSON. Store outputs in a secure internal repository and redact personal identifiers when necessary. (pdq.com)
• When planning for Windows 11, use msinfo32 to confirm firmware mode and TPM, but always cross-check with the PC Health Check app and Microsoft’s published requirements — CPU lists are long and change over time, and the Health Check tool reflects Microsoft’s final compatibility decisions. (learn.microsoft.com)

---

Recommended workflow for end users and IT teams​

• Casual check: Settings > System > About for CPU, RAM, Windows edition and build.
• Support-ready single-PC export: msinfo32 export + dxdiag save.
• Fleet inventory or automation: PowerShell Get-ComputerInfo scripts with Out-File or Export-Csv.
• Thermal or live performance issues: Task Manager Performance + vendor monitoring tools (for CPU temps).
• Upgrade readiness: msinfo32 for UEFI/TPM, then PC Health Check for Windows 11 compatibility; plan ESU if replacement or upgrade isn’t immediate. (pdq.com)

---

Conclusion​

Windows 10 includes a robust toolbox for inspecting and exporting your PC’s full specifications — from the simple Settings summary for quick checks to msinfo32 and dxdiag for support-ready snapshots, and PowerShell for automation at scale. These built-in methods remove the need for third-party profilers in most scenarios, but understanding the strengths and limits of each tool is essential: Settings is fast but shallow, msinfo32 is deep but can contain sensitive identifiers, dxdiag is the standard for graphics/audio troubleshooting, and PowerShell is ideal for repeatable inventories. With Windows 10’s support window closing on October 14, 2025, using these tools now to verify hardware, firmware, and TPM status is a practical first step in planning upgrades, enrolling in ESU where appropriate, or replacing aging devices. Responsible handling of exported reports — scrubbing serials and sharing only with trusted channels — completes a secure and effective troubleshooting workflow.

---

Source: Windows Central How to check your PC's full specifications on Windows 10