For a basic Windows PC audit, open System Information with msinfo32. It shows the Windows build, system model, hardware and software environment. Start with the details you need for the job, such as checking a repair quote or describing a driver problem. Use an additional tool only when you need to answer a more specific question.
Run a Windows PC audit with System Information
- Press Windows + R, enter
msinfo32, and open System Summary. Note the OS version, system model, processor and installed memory. - For a display problem, inspect Components > Display and record the adapter and driver version. If a game asks for a DirectX feature level, follow the DirectX diagnostic guide for the separate GPU check.
- For your own records, save an
.nforeport if you need the full inventory. Reopen it to confirm that it contains the expected details. When sharing with support, send only the requested fields after checking for machine names, paths, account names and other identifying details.
Microsoft documents the System Information command and report formats. You can use /nfo to save a System Information file or /report for text output.
When to check startup entries
If the problem is something opening every time you sign in, use Microsoft Sysinternals Autoruns to inspect startup entries. Record the entry name, publisher and file path. Leave entries enabled while collecting evidence. An unfamiliar entry or a blank publisher field by itself does not identify malware.
Example: document a display problem
Suppose an external display stopped working after an update. Start with three facts from System Information: Windows build, graphics adapter and driver version. Add the monitor and connection type and say whether another cable works. That is more useful to a support technician than a full inventory with no description of the problem.
If you are documenting a problem after an update, keep the date and the symptom beside the driver version. A second report after a repair can help you see which details changed. Store the full reports privately and share a short, relevant excerpt for each support request.
Make a short report for a support ticket
For a display issue, include the Windows build, graphics adapter, driver version and a one-sentence description of the symptom. Attach a cropped image only if it clarifies the issue. If the problem began after an update, note when it started and whether it affects one app or the whole desktop. Keep the full inventory available privately in case the technician asks for more.
Our take: Collect a focused inventory first. A PC audit records the machine’s configuration. For intermittent crashes that may involve RAM, see the memory diagnostic guide. This workflow follows Microsoft documentation and has not been retested on a new Windows installation.
