In CompTIA A+ 220-1202 (Core 2), Domain 1.0, Objective 1.4, "additional Windows tools" means built-in utilities that go beyond the basics of Settings and Task Manager. These tools help you collect facts, isolate causes, and perform safe maintenance. In practice, techs use them because good troubleshooting starts with evidence, not guesses.
This post covers six tools named in the objective: System Information, Resource Monitor, System Configuration, Disk Cleanup, Disk Defragment (Optimize Drives), and Registry Editor. For each one, you'll learn what it does, when to use it, and how to handle it safely. The focus stays exam-aligned, but the advice also fits real tickets, where you often need to explain what you changed and why.
Treat these tools like a mechanic's gauges. They don't fix the car by themselves, but they tell you what's wrong faster.
System Information (msinfo32.exe), get a full PC snapshot fast
System Information gives a structured report of a Windows PC in one place. It's useful when you need quick, defensible facts: hardware model, BIOS details, drivers, and key software settings. When a user says, "My laptop is slow," this tool helps you answer, "What are we working with?" before you try fixes.
To open it, type System Information in the Start menu search, or press Win + R, type msinfo32, then press Enter.
System Information matters because it bridges the gap between what a user reports and what Windows can confirm. For example, you can verify the exact Windows version and build, check whether Secure Boot is available, confirm installed RAM, and see whether Windows flags any hardware as a problem device. In addition, it records the system's environment, which helps when startup items, services, or drivers might affect stability.
When you escalate a ticket, this tool also protects you from vague notes. "User has a Dell" is weak; "Dell Latitude 5420, BIOS mode UEFI, 16 GB RAM, OS build 22631" is actionable.
What to look at first: Summary, Components, and Software Environment
Start with System Summary. It shows OS name and version, system type (such as x64-based PC), CPU model, installed memory, BIOS version, and BIOS Mode (UEFI vs Legacy). That BIOS mode field often appears in Windows 11 readiness scenarios because UEFI relates to Secure Boot and modern boot methods.
Next, open Components for hardware-focused checks. Problem Devices is a fast way to spot missing drivers or failed hardware. Display helps when you suspect a GPU driver issue. Storage and Network entries help you confirm adapter names and driver versions when troubleshooting disconnects or slow throughput.
Then review Software Environment when symptoms feel "soft," such as long boot times or random app hangs. Services, Startup Programs, and Loaded Modules can hint at conflicts, unwanted add-ons, or security software issues.
How to save and share results without guessing
When you need a record, save it from the menu. Use File > Save to store a full report (NFO format), or File > Export for a text file you can attach to a ticket.
Saving the report reduces back-and-forth. Screenshots often miss context because they capture only one pane at a time. A saved export preserves the full tree of details, so another tech can search it, compare it later, or confirm exactly what you saw.
When you can't reproduce an issue on demand, a saved msinfo32 report becomes your "time capsule" of the system state.
Resource Monitor (resmon.exe), find what's slowing Windows down
Resource Monitor offers a deeper performance view than Task Manager. It breaks activity into four areas: CPU, Memory, Disk, and Network. Each area includes graphs and ranked lists, which makes it easier to connect a symptom to a single process or service.
Open it by searching Resource Monitor in Start, or use Win + R and type resmon, then press Enter. You can also launch it from Task Manager's Performance tab on many systems, but the executable is the exam-friendly route.
This tool shines when the problem sounds like friction: long app launches, constant fan noise, "100% disk," or video calls that freeze. Instead of assuming the cause, you can confirm what resource is saturated. Then you can name the process, check whether it's expected, and choose a safe next step.
One practical habit helps a lot: pay attention to the Image (process name) and the Description column. Process names can be cryptic, while descriptions often reveal the vendor or app. Also, watch for patterns. A single spike is less meaningful than sustained pressure for 30 to 60 seconds.
CPU, Memory, Disk, Network tabs, what the graphs and lists really mean
On CPU, focus on the Processes list and the "highest activity" entries. CPU usage shows which process is consuming time. Services helps when a service host (svchost.exe) looks busy, because it lists the services running under it. If a user reports slow typing, and a background process holds high CPU, you have a strong lead.
On Memory, the key idea is pressure. Hard faults/sec can rise when Windows pages memory to disk.