Msinfo32 Can’t Collect Information: Fixes

If System Information (msinfo32) says it “can’t collect information,” the WMI (Windows Management Instrumentation) service is usually stopped or corrupted, or the tool lacks the permissions to query system data. Restarting the WMI service, running msinfo32 as administrator, or repairing the WMI repository resolves the issue in most cases.

What msinfo32 Does and Why It Fails

System Information (msinfo32.exe) is a built-in Windows utility that displays a snapshot of your hardware, software, and system components. It gathers data from multiple sources, including the registry, the file system, and crucially, WMI. WMI is a framework that standardizes how Windows and third-party apps expose management data. When msinfo32 cannot collect information, it typically means the WMI service (Winmgmt) is not running, the WMI repository is corrupted, or a permissions issue blocks access to the data.

The error can appear as a dialog box saying “Can’t collect information” or the left pane may be partially populated with missing details under categories like Components or Software Environment. The failure is rarely caused by msinfo32 itself; it is almost always an underlying system service or repository problem.

Quick Fixes to Try First

Before diving into deeper repairs, try these simple steps. They resolve a surprising number of cases.

• Restart the WMI service: Press Win + R, type services.msc, and press Enter. Find Windows Management Instrumentation, right-click it, and select Restart. If the service is stopped, click Start.
• Run msinfo32 as administrator: Right-click the Start button, select Run, type msinfo32, and press Ctrl + Shift + Enter to launch it with elevated privileges. Some WMI queries require admin rights.
• Check if the service is disabled: In services.msc, double-click the WMI service and ensure the Startup type is Automatic. If it is disabled, set it to Automatic and start it.
• Reboot the PC: A simple restart can restart the WMI service and clear temporary glitches.

If the error persists, the WMI repository may be corrupted, or a third-party application may be interfering with WMI.

Repair the WMI Repository

The WMI repository is a database that stores WMI class definitions and instance data. Corruption can occur after a failed update, a disk error, or an improper shutdown. Windows provides built-in commands to check and rebuild it.

1. Open an elevated Command Prompt (Run as administrator).
2. Run winmgmt /verifyrepository to check the repository’s consistency. If it returns “WMI repository is consistent,” corruption is not the issue.
3. If the verification fails, run winmgmt /salvagerepository to attempt a repair. This command rebuilds the repository from existing data.
4. If salvage fails, run winmgmt /resetrepository to reset the repository to its default state. This will delete all WMI data, including custom settings from third-party apps. After the reset, you may need to reinstall or reconfigure those apps.

After running any of these commands, restart the PC and try msinfo32 again. Note that /resetrepository is a last resort because it removes all custom WMI data.

Check for WMI Service Dependencies

WMI depends on the RPC (Remote Procedure Call) service and the DCOM Server Process Launcher. If either of these is stopped or disabled, WMI will fail to start. To verify:

1. Open services.msc.
2. Locate Remote Procedure Call (RPC) and DCOM Server Process Launcher. Both should be running and set to Automatic.
3. If they are not, start them and set their startup type to Automatic.

Also, check if any security software or a group policy is blocking WMI. Some endpoint protection tools can restrict WMI queries. Temporarily disabling such software (if safe) can help isolate the cause.

Run System File Checker and DISM

Corrupted system files can also break msinfo32. The System File Checker (SFC) and Deployment Imaging Service and Management Tool (DISM) can repair them.

1. Open an elevated Command Prompt.
2. Run sfc /scannow. This may take 10-15 minutes. If it finds integrity violations, it will attempt to repair them.
3. If SFC does not fix the issue, run DISM /Online /Cleanup-Image /RestoreHealth. This repairs the Windows image that SFC relies on. After DISM completes, run sfc /scannow again.

These commands are safe and do not affect personal files.

Alternative Ways to Get System Information

If msinfo32 still fails, you can still obtain the same data through other built-in tools. They are not exact replacements but cover most common needs.

• System Settings: Go to Settings > System > About to see basic device specs (processor, RAM, device ID).
• Task Manager: Open Task Manager (Ctrl+Shift+Esc) and go to the Performance tab for real-time CPU, memory, disk, and GPU usage.
• Command-line tools: Use systeminfo in Command Prompt to get a text summary of OS, RAM, and network info.
• Device Manager: For hardware details, open Device Manager (devmgmt.msc) and expand categories like Display adapters or Network adapters.
• DirectX Diagnostic Tool: Run dxdiag to get detailed graphics and sound information.

These alternatives may not show every detail msinfo32 does, but they cover the most requested items.

Frequently Asked Questions

Why does msinfo32 say “Can’t collect information” on every startup?

If the error appears every time, it indicates a persistent issue, usually a stopped WMI service or a corrupted repository. Follow the steps above: restart WMI, verify the repository, and if needed, reset it. Also check that the WMI service startup type is Automatic.

Does running msinfo32 as administrator fix the issue?

Sometimes. Some WMI queries require elevated privileges, especially when accessing data from other user accounts or protected system components. If you are not running as administrator, right-click the Start button and choose “Run as administrator” or press Ctrl+Shift+Enter when launching msinfo32.

Can I use msinfo32 to export a report if it can’t collect information?

No. If msinfo32 cannot collect information, it cannot generate a complete report. You might be able to export a partial report, but it will be missing data. Fix the underlying issue first, then export.

Is it safe to reset the WMI repository?

Resetting the repository is generally safe but will remove all WMI data, including custom settings from third-party applications. Those applications may need to be reinstalled or reconfigured. It is a last-resort step after other repairs fail.

Will a Windows update fix msinfo32 errors?

Sometimes. Microsoft regularly patches WMI and system components. Check Windows Update for pending updates and install them. However, if the issue is caused by a corrupted repository, an update alone may not fix it.

Related

• Mouse Keeps Double Clicking? Fixes That Work
• ChromeOS Desktop Widgets: Why It’s a Game Changer
• VLC Hide Controls: How to Turn Them Off