comptia-a-plus-core2/labs/TRB-1-windows-os-issues-lab.md

Lab TRB-1: Windows OS Troubleshooting Evidence

Domain:

• 3.0 Software Troubleshooting

Works on:

• Windows
• Linux comparison optional

Goal

Practice gathering evidence for Windows OS symptoms without making risky changes.

Part 1: Resource Check

Windows:

taskmgr
perfmon /rel
eventvwr.msc

Record:

• Highest CPU process:
• Highest memory process:
• One Reliability Monitor event:
• One Windows log you opened:

Part 2: System Repair Commands

Do not interrupt these commands if you run them.

sfc /verifyonly
DISM /Online /Cleanup-Image /CheckHealth
chkdsk

Record:

• SFC result:
• DISM result:
• CHKDSK result:

Part 3: Startup and Services

Open:

• Task Manager > Startup apps
• Services console

Record:

• One enabled startup app:
• One stopped service:
• Whether the stopped service appears normal or suspicious:

Part 4: Scenario Practice

Match the next step:

1. Windows says no OS found.
2. A service fails to start after boot.
3. A system blue-screens after a driver update.
4. A user reports the PC is slow after login.
5. The clock keeps drifting.

What You Should Learn

• Troubleshooting starts with symptoms and evidence.
• Event Viewer and Reliability Monitor help build a timeline.
• SFC, DISM, and CHKDSK support repair decisions.
• Startup apps, services, drivers, storage, and time settings are common Windows issue areas.