MSInfo32 (System Information) in Windows: Complete Usage and Troubleshooting Guide

QUICK ANSWER

MSInfo32—shown as System Information in Windows—is a built-in diagnostic utility that displays a detailed snapshot of a computer’s hardware, Windows configuration, drivers, components, and software environment. Press Windows key + R, enter msinfo32, and select OK to open it.

The tool is especially useful when checking computer specifications, investigating driver or hardware conflicts, confirming BIOS and Secure Boot information, or creating an .nfo report for technical support. MSInfo32 reports information but does not change settings, repair Windows, update drivers, or test hardware performance.

What is MSInfo32?

MSInfo32.exe is the executable for the Windows System Information utility. Microsoft describes it as a tool that provides a comprehensive view of hardware, system components, and the software environment on a local computer.

MSInfo32 is included with supported versions of Windows 10, Windows 11, and relevant Windows Server releases. No separate installation is normally required.

Common uses include:

• Identifying the computer manufacturer, model, processor, and installed memory
• Checking the Windows edition, version, and build
• Reviewing BIOS or UEFI details
• Verifying Secure Boot and virtualization-related information
• Finding installed drivers and system services
• Investigating problem devices and hardware-resource conflicts
• Recording system configuration before an upgrade or repair
• Creating diagnostic reports for an administrator, vendor, or support engineer
• Viewing information from another Windows computer when remote access requirements are satisfied

How MSInfo32 works

When MSInfo32 starts, it queries information available through Windows management interfaces and system configuration sources. It organizes the results into categories and presents them as a point-in-time system report.

The main window has three areas:

Area	Purpose
Navigation pane	Selects System Summary, Hardware Resources, Components, or Software Environment
Details pane	Displays the properties and values for the selected category
Find box	Searches the collected information for a word or value

MSInfo32 is primarily a reporting tool. Opening it does not normally modify the system. Its data can nevertheless change after a restart, driver update, hardware change, Windows update, or configuration change.

Information may take time to load

Some categories contain many records, particularly drivers, loaded modules, services, and other software-environment data. MSInfo32 may appear busy while Windows gathers this information. This is not necessarily evidence that the application has stopped responding.

How to open MSInfo32

Method 1: Use the Run dialog

1. Press Windows key + R.
2. Enter:

msinfo32

3. Select OK or press Enter.

Method 2: Use Windows Search

1. Open Start or Search.
2. Search for System Information.
3. Select the System Information application.

If you need information that is accessible only with elevated rights, right-click System Information and select Run as administrator. Administrator rights are not normally required to view the basic local-system summary.

Method 3: Use Command Prompt or PowerShell

Run:

msinfo32

The command opens the graphical System Information application.

Understanding the MSInfo32 categories

System Summary

System Summary provides the most commonly requested information in one location.

Depending on the device and Windows version, it may include:

• Operating system name, version, and build
• System manufacturer and model
• System type and processor
• BIOS version and date
• BIOS mode, such as UEFI or Legacy
• Baseboard manufacturer and product
• Installed and available physical memory
• Windows and system directories
• Boot device
• Locale and time zone
• Secure Boot state
• Virtualization-related properties
• Page-file information

This section is usually the best starting point when checking specifications or preparing a support case.

Some fields may show Not Available, Unsupported, or an unexpected value. MSInfo32 can display only the information exposed by Windows, the device firmware, hardware, and installed drivers.

Hardware Resources

Hardware Resources shows how Windows has assigned low-level resources to devices. Its subcategories can include:

• Conflicts/Sharing
• Direct memory access (DMA)
• Forced Hardware
• Input/output (I/O) ranges
• Interrupt requests (IRQs)
• Memory ranges

Entries under Conflicts/Sharing do not automatically indicate a fault. Modern Windows systems commonly share resources. Treat an entry as relevant only when it corresponds with a malfunctioning device, driver error, or Device Manager warning.

Components

Components contains information about installed or detected hardware-related components, such as:

• Multimedia and audio devices
• Display adapters
• Storage devices and drives
• Printing devices
• Network adapters and protocols
• USB devices
• Input devices
• Problem Devices

The exact categories depend on the Windows version and the hardware present.

The Problem Devices section is useful when investigating a device that Windows cannot start or configure. Confirm any finding in Device Manager, where you can review the device status and error code.

Software Environment

Software Environment reports operating-system components and runtime information. Categories can include:

• System drivers
• Environment variables
• Print jobs
• Network connections
• Running tasks
• Loaded modules
• Services
• Program groups
• Windows Error Reporting information

This section can be large and may take longer to populate. It is useful for diagnostics, but it is not a complete replacement for Event Viewer, Reliability Monitor, Task Manager, or specialized management tools.

How to find information in MSInfo32

Use the Find what box at the bottom of the window:

1. Enter a term such as Secure Boot, BIOS, processor, or a device name.
2. Select Find.
3. Select Find Next to locate another match.

For predictable results, begin at System Summary or select the category most likely to contain the required property.

How to refresh the displayed information

Use View > Refresh or press F5 to collect the information again.

Refresh the report after making a relevant configuration change. Some changes are not fully reflected until Windows or the affected service has restarted.

How to save an MSInfo32 report

Save a native NFO file

In the graphical interface:

1. Open MSInfo32.
2. Select File > Save.
3. Choose a location and filename.
4. Save the file with the .nfo extension.

An NFO file preserves the structured System Information report and is generally the best format when another Windows administrator needs to examine the report in MSInfo32.

To open it later, start MSInfo32 and select File > Open, or use:

msinfo32 "C:\Reports\ComputerName.nfo"

Use a quoted path when it contains spaces.

Export a text report

To create a more portable, human-readable file:

1. Select File > Export.
2. Choose a location.
3. Save the report as a text file.

A text export is convenient for searching, reviewing in a text editor, or attaching to systems that do not accept NFO files. It does not provide the same structured navigation as an NFO file.

Privacy warning before sharing reports

MSInfo32 reports can contain information such as:

• Computer and Windows account names
• Hardware identifiers and serial-related information
• Network configuration
• Installed software, services, and drivers
• File paths and environment variables
• Organization-specific configuration

Review exported reports before sending them outside your organization. Share them only through an approved secure channel and only with a trusted recipient. Do not publish an unreviewed report on a public forum.

MSInfo32 command-line options

Microsoft documents the following general syntax:

msinfo32 [/pch] [/nfo <path>] [/report <path>] [/computer <computername>] [/showcategories] [/category <categoryID>] [/categories <category-selection>]

The most useful options are:

Option	Function
/nfo <path>	Saves information as an NFO file
/report <path>	Saves information as a text report
/computer <computername>	Opens information for another computer
/showcategories	Displays internal category IDs
/category <categoryID>	Opens MSInfo32 with a specified category selected
/categories <selection>	Limits displayed and saved information to selected categories
/pch	Opens the System History view
/?	Displays command-line help

Create an NFO report

First make sure the destination folder exists, and then run:

msinfo32 /nfo "C:\Reports\SystemInfo.nfo"

If the specified filename does not end in .nfo, Windows automatically appends that extension.

Create a text report

msinfo32 /report "C:\Reports\SystemInfo.txt"

Unlike /nfo, the /report option does not automatically add .txt. Include the extension in the path if you want a text-file extension.

Wait for report generation in a batch file

MSInfo32 is a graphical application. A script may otherwise continue before report generation finishes. In a Command Prompt batch file, use:

start /wait msinfo32.exe /nfo "C:\Reports\SystemInfo.nfo"

The process can take time, especially when the report includes large software-environment categories.

Display category IDs

msinfo32 /showcategories

Category IDs are more suitable than localized category names for scripts used across Windows installations with different display languages.

Export only System Summary

msinfo32 /nfo "C:\Reports\SystemSummary.nfo" /categories +systemsummary

Exclude loaded modules

msinfo32 /categories +all -loadedmodules

Excluding large categories can reduce collection time and report size.

Export hardware-conflict and problem-device information

Microsoft provides the following category-selection example:

msinfo32 /nfo "C:\Reports\Conflicts.nfo" /categories +componentsproblemdevices+resourcesconflicts+resourcesforcedhardware

Category availability can vary. Use /showcategories on the target Windows installation to confirm the valid identifiers.

Viewing information from a remote computer

The /computer option can start System Information for another computer:

msinfo32 /computer PC-NAME

Microsoft permits a computer name, full computer name, IP address, or UNC-style name as the target value. The account running MSInfo32 must have appropriate access to the remote computer.

Remote collection may fail when:

• The target computer is offline or unreachable
• Name resolution is not working
• A firewall blocks required management traffic
• Required Windows management services are unavailable
• The current account lacks remote permissions
• Security policy prevents remote management
• Network segmentation blocks the connection

Do not weaken firewall, authentication, or administrative controls merely to make MSInfo32 remote access work. In managed environments, use the organization’s approved remote-management method. A safer alternative is often to create the report locally on the target computer and transfer it through an approved support channel.

Practical uses and benefits

Check a computer’s specifications

System Summary can quickly identify the processor, memory, model, system type, and Windows build without installing third-party inventory software.

For total disk capacity and free space, File Explorer, Disk Management, or PowerShell may provide a clearer view than the summary page.

Confirm BIOS and UEFI information

MSInfo32 can show the BIOS version/date and BIOS mode. This is useful when preparing for a firmware update or checking whether Windows is using UEFI.

Always obtain firmware updates from the computer or motherboard manufacturer. Do not determine firmware compatibility from a version number alone.

Check Secure Boot state

Look for Secure Boot State in System Summary.

Possible values may include:

• On — Secure Boot is enabled
• Off — The system supports it, but it is not currently enabled
• Unsupported — Windows does not detect supported Secure Boot operation
• A missing or unavailable value — Firmware, system mode, permissions, or platform reporting may prevent detection

Do not change UEFI settings without understanding the effect on BitLocker, operating-system boot, device compatibility, and organizational security policy. Record or suspend BitLocker protection as directed by your organization before firmware changes that could trigger recovery.

Diagnose device and driver issues

Review:

• Components > Problem Devices
• Software Environment > System Drivers
• Hardware Resources > Conflicts/Sharing

Then verify the result in Device Manager and the relevant event logs. An MSInfo32 entry identifies configuration data; it does not by itself prove that a driver is defective.

Create a baseline before changes

Save an NFO report before:

• Updating BIOS or firmware
• Replacing hardware
• Installing a major driver
• Performing a Windows feature update
• Troubleshooting an intermittent issue

A second report taken afterward can help an administrator identify configuration differences. MSInfo32 does not provide a complete built-in comparison workflow, so external comparison or management tooling may be required.

Improve support requests

A structured report gives support staff more context than a screenshot of one settings page. It can reduce repeated questions about the operating-system build, system model, firmware, memory, drivers, and detected components.

What MSInfo32 cannot do

MSInfo32 has important limitations:

• It does not repair Windows or hardware.
• It does not update BIOS, Windows, or device drivers.
• It is not a malware scanner.
• It does not test CPU, memory, disk, or graphics performance.
• It does not provide a complete health assessment.
• It does not replace Device Manager, Event Viewer, Reliability Monitor, Performance Monitor, or vendor diagnostics.
• Most information is a snapshot rather than continuous monitoring.
• Firmware or driver reporting can be missing, stale, or inaccurate.
• Remote access depends on permissions, services, network configuration, and security policy.
• An empty category does not necessarily mean that the corresponding component or activity does not exist.

Use MSInfo32 as evidence within a broader diagnostic process, not as the sole basis for replacing hardware or making security-sensitive changes.

Troubleshooting MSInfo32

MSInfo32 does not open

Try these steps in order:

1. Press Windows key + R and run msinfo32.
2. Search for System Information from Start.
3. Restart Windows and try again.
4. Install pending Windows updates approved for the device.
5. On a managed computer, check whether application-control policy is preventing the utility from running.
6. If Windows components may be damaged, have an administrator use the organization’s approved Windows repair procedure.

Do not download a replacement msinfo32.exe from an unofficial website.

The window opens but remains blank or says it cannot collect information

Possible causes include a temporary management-service problem, damaged Windows components, insufficient access, or an unusually slow category query.

Try:

1. Wait several minutes, particularly on a heavily loaded system.
2. Close and reopen MSInfo32.
3. Restart Windows.
4. Run it as an administrator if elevated access is appropriate.
5. Test whether a limited report succeeds:

msinfo32 /nfo "C:\Reports\Summary.nfo" /categories +systemsummary

6. Check Event Viewer and the health of Windows Management Instrumentation if the problem continues.

Rebuilding or resetting the WMI repository can affect management applications and should not be used as a routine first step. It should be performed only after proper diagnosis and according to Microsoft-supported procedures.

The report command creates no file

Check the following:

• The destination folder already exists.
• The current account has permission to write there.
• The file is not open or locked by another application.
• The path is surrounded by quotation marks if it contains spaces.
• Security software or controlled-folder protection is not blocking the write.
• The command has been given enough time to finish.
• The output filename includes .txt when using /report.

Test with a simple writable location:

msinfo32 /report "%USERPROFILE%\Desktop\SystemInfo.txt"

In a script, use start /wait when later commands depend on the report being complete.

An NFO file will not open

Confirm that:

• The file was created with MSInfo32 rather than simply renamed from another format.
• The transfer or download completed successfully.
• The file is not zero bytes or visibly truncated.
• The file came from a trusted source.
• You are opening it through File > Open in System Information.

If the sender can reproduce the report, ask for a text export as an alternative.

Remote computer information cannot be collected

Verify:

• The target name or IP address is correct.
• The target is powered on and reachable.
• Your account has the necessary remote rights.
• Required management services are operating.
• Approved firewall rules permit the connection.
• The devices are in an appropriate trusted administrative environment.

If organizational policy blocks remote collection, generate the report locally on the target computer instead of bypassing the policy.

Information appears incorrect or outdated

Press F5 to refresh, then restart Windows if the relevant hardware, driver, or firmware has recently changed. Compare the result with:

• Settings > System > About
• Device Manager
• Disk Management
• Windows Update history
• The device manufacturer’s support utility
• UEFI or BIOS setup
• PowerShell or approved asset-management tools

When sources disagree, investigate how each value is obtained instead of assuming that MSInfo32 is always authoritative.

FAQ

Frequently asked questions

Is MSInfo32 safe to run?

Yes. MSInfo32 is a Microsoft-provided Windows reporting utility, and opening it normally does not change system settings. Reports may contain sensitive configuration data, however, so review them before sharing.

Do I need administrator rights to use MSInfo32?

Basic information about the local computer is normally available without elevation. Administrator or delegated rights may be necessary for some protected information and remote-computer access.

Where is MSInfo32.exe located?

The standard executable is normally located in the Windows system directory, commonly:

C:\Windows\System32\msinfo32.exe

Use Windows Search or the Run dialog rather than downloading the executable from another website.

What is an NFO file?

An NFO file created by MSInfo32 is a structured System Information report that can be reopened in the System Information utility. The .nfo extension is also used by unrelated text-based files, so not every NFO file is an MSInfo32 report.

What is the difference between MSInfo32 and Systeminfo?

msinfo32 opens the graphical System Information tool and can create detailed structured reports. systeminfo is a command-line utility that produces a more concise text-oriented summary suitable for terminals and many scripts.

What is the difference between MSInfo32 and Device Manager?

MSInfo32 reports broad system, hardware-resource, component, driver, and software-environment information. Device Manager focuses on hardware devices and their drivers and provides management actions such as viewing device status, updating drivers, disabling devices, and uninstalling devices.

Can MSInfo32 show the Windows product key?

MSInfo32 may show general Windows installation and licensing-related properties, but it should not be relied upon to retrieve the complete product key. Modern Windows activation may use a digital license or firmware-embedded key that is not displayed there.

Can MSInfo32 display CPU or GPU temperatures?

No. MSInfo32 is not a sensor-monitoring utility and normally does not provide real-time CPU or GPU temperatures. Use manufacturer-supported hardware-monitoring or diagnostic tools when temperature data is required.

Can MSInfo32 tell me whether a computer is healthy?

Not by itself. It can reveal useful configuration details and possible problem devices, but it does not run comprehensive hardware, malware, performance, or file-system tests.

How often should an IT team collect MSInfo32 reports?

Collect a report when troubleshooting, documenting a build, or recording the system before and after a significant change. For continuous inventory or monitoring, use approved endpoint-management and asset-management tools instead.

FINAL RECOMMENDATION / CONCLUSION

Use MSInfo32 as the first diagnostic snapshot when you need detailed Windows configuration information. Start with System Summary, review Problem Devices and relevant driver or hardware-resource sections, and save an NFO report when technical support needs the full structured data.

Treat the report as sensitive, verify important findings with the appropriate specialized tool, and remember that MSInfo32 identifies configuration—it does not repair problems. For scripting or support collection, use /nfo or /report, quote paths containing spaces, and use start /wait in Command Prompt scripts when subsequent steps must wait for report generation.

 

#MSInfo32 #SystemInformation #Windows11 #Windows10 #WindowsServer #WindowsTroubleshooting #SystemDiagnostics #NFOFile #HardwareInformation #DriverTroubleshooting #BIOS #UEFI #SecureBoot #ProblemDevices #ITSupport #WindowsCommands #SystemAdministration #ComputerSpecifications #TechnicalSupport #WindowsTools

SOURCES

• Microsoft Learn: MSInfo32 command, syntax, parameters, and supported Windows versions
• Microsoft Learn: System Information overview
• Microsoft: Download Windows 11—using System Information to identify system type