Week 11 · lesson
Lesson 3: Windows GUI Tools and Settings
Core path: 42 minutes
Windows has many management surfaces because different tools answer different support questions.
The goal is not to memorize where every icon lives forever. UI locations move. Learn the function and evidence each tool provides.
Task Manager
Use Task Manager to inspect:
- Processes — running applications/processes;
- Performance — CPU, memory, disk, network, GPU/resource trends;
- Startup — startup applications/impact;
- Users — active user sessions;
- Services — service state and related process context.
Microsoft Management Console and administrative tools
| Tool | Technician question |
|---|---|
Event Viewer (eventvwr.msc) | What system/application events were recorded? |
Disk Management (diskmgmt.msc) | What disks, partitions, volumes, and drive letters exist? |
Task Scheduler (taskschd.msc) | Which scheduled tasks exist and when do they run? |
Device Manager (devmgmt.msc) | Which hardware devices/drivers are detected and reporting errors? |
Certificate Manager (certmgr.msc) | Which user certificates/trust objects are present? |
Local Users and Groups (lusrmgr.msc) | Which local users/groups exist and what memberships apply? |
Performance Monitor (perfmon.msc) | What performance counters/trends should be measured? |
Group Policy Editor (gpedit.msc) | Which local policy settings are configured on supported editions? |
Additional Windows tools
| Tool | Purpose |
|---|---|
System Information (msinfo32.exe) | hardware, firmware, OS, component summary |
Resource Monitor (resmon.exe) | detailed CPU, memory, disk, network activity |
System Configuration (msconfig.exe) | startup/boot/service diagnostic configuration |
Disk Cleanup (cleanmgr.exe) | identify/remove supported temporary/system files |
Disk Defragment / Optimize Drives (dfrgui.exe) | storage optimization interface appropriate to drive type |
Registry Editor (regedit.exe) | inspect/edit Windows registry when an approved procedure specifically requires it |
Registry changes can damage the operating environment. This course uses supplied state or disposable VMs for registry work.
Windows settings and Control Panel concepts
Recognize where a technician would look for these functions:
- Internet Options;
- Devices and Printers;
- Programs and Features;
- Network and Sharing Center;
- System;
- Windows Defender Firewall;
- Mail;
- Sound;
- Device Manager;
- Indexing Options;
- Administrative Tools.
File Explorer Options
Technicians may need to:
- show hidden files;
- show or hide file extensions;
- change general/view behavior.
Showing extensions can help distinguish files such as report.pdf.exe from a real PDF filename.
Power Options
Recognize:
- hibernate;
- power plans;
- sleep/suspend;
- standby terminology;
- lid-close behavior;
- fast startup;
- USB selective suspend.
Power settings can create symptoms that look like hardware failure when the system is actually following configured power policy.
Major Settings categories
At A+ depth, know the purpose of:
- Ease of Access / Accessibility;
- Time and Language;
- Update and Security / Windows Update and security settings;
- Personalization;
- Apps;
- Privacy;
- Devices;
- Network and Internet;
- Gaming;
- Accounts.
Names/layout can change between Windows releases. The function is the durable knowledge.
Guided selection
Symptom: new disk detected but missing from File Explorer
Best first GUI tool: Disk Management.
Symptom: one startup app consumes resources after sign-in
Best first GUI tool: Task Manager Startup/Performance.
Symptom: scheduled script runs unexpectedly every night
Best first GUI tool: Task Scheduler.
Symptom: repeated application fault after update
Best first GUI tool: Event Viewer, then application-specific evidence.
Student action
Match 20 fictional support questions to the smallest useful Windows GUI/settings tool.
For each write:
question:
tool/settings surface:
evidence expected:
what the result would NOT prove:
risk if the tool can modify state:
Evidence checkpoint
Professional support is not opening every console. Choose the tool that tests the current hypothesis with the least unnecessary change.
Visual reference
See the system before you troubleshoot it
The evidence-first method stays consistent across platforms even when commands, filesystems, permissions, and administrative tools change.
Use it for: Compare platform-specific administration surfaces without treating one operating system as the universal model.
Read it. Prove it.