'Sir, which model is your computer?' — support calls crawl when the answer is a guess. Three tools already on or in this guide's method each produce a proper specification file in a minute. Send the file, and the conversation starts at the solution.
Describing a PC over the phone fails in predictable ways: "i5, 16 GB" says nothing about the motherboard, BIOS version, RAM part numbers or driver dates — the details that actually decide a repair or an upgrade. The professional habit is to send a report: a text file the machine writes about itself. This page builds you three of them — the complete msinfo32 export, the dxdiag save that support desks ask for by name, and the compact CPU-Z report from the video's tool — and tells you honestly which file fits which conversation.
The three reports between them answer every specification question a technician, seller or buyer can ask — each takes about a minute to produce.
msinfo32, Enterpc-report.txt and save it where you can find itThis single file covers hardware, motherboard and BIOS, every device with its driver version, and the software environment. If a technician is allowed only one attachment, it is this one. (Use Export, not Save — Save's .nfo format opens only inside System Information.)
dxdiag, Enter, and let it loadWhen a fault involves the screen, video or audio, support desks ask for this file by name. It answers "which driver, from when" — the question behind half of all display problems — without a long phone conversation.
This is the file to send a seller when valuing a PC, or to attach when asking "which RAM should I buy?" — it contains exactly the part numbers and models the other side needs, and nothing they do not.
A report plus two honest lines beats a long story:
Selling instead? Send the CPU-Z report and the msinfo32 summary with the invoice if you have it. Buyers trust files written by the machine itself far more than photographs of stickers.
Save today's reports in a folder named with the date, somewhere you keep important documents. After every upgrade or repair, save a fresh set. Months later, when something changes and you ask "what was different before?", you will have the answer in writing instead of from memory — and if you ever sell the machine, its complete, dated specification history is the best listing you could write.
The CPU-Z check behind the neatest report — processor, board, RAM and graphics read live in the full video.
▶️ Watch Full VideoThe msinfo32 export (File, then Export, saved as .txt). It is the most complete single document: hardware summary, motherboard and BIOS, every component with its driver, and the software environment. A technician can answer most questions from that one file; add the dxdiag save only when the problem is about display or sound.
No — that is exactly what Save All Information produces: every display and sound device, driver file and version on the system, in plain text. Do not edit or trim it; the size is the point, and support desks read it with their own tools. Just attach and send.
Yes. Msinfo32 and dxdiag are built into Windows and work fully offline, and the ZIP version of CPU-Z runs from a pen drive without installing or connecting. Reports are written locally as text files — you only need a connection at the moment you choose to send one.