Windows Troubleshooting Intro
This lesson introduces the core Windows troubleshooting mindset for help desk and entry-level IT support. You will learn which built-in tools to reach for first, what they are best at, and how to think through a Windows problem without jumping straight into random fixes.
What this lesson covers
- How to think like Windows support instead of guessing
- Which Windows tool fits which problem
- Why symptoms and root causes are not the same thing
- How to verify before and after you make a change
Core idea
In Windows troubleshooting, the first win is usually not the fix. The first win is finding the right place to look.
That usually means checking process state, service state, logs, devices, or network details before changing settings.
Windows Troubleshooting Flow
Teach the learner to use this sequence every time.
Task Manager
Use this when a PC is slow, frozen, or an app is not responding.
- See CPU, memory, disk, and network use
- Find apps or processes consuming resources
- Check startup impact on boot performance
Services
Use this when a Windows feature or background function is not working.
- See whether a service is running or stopped
- Check startup type
- Restart only after you have a reason
Event Viewer
Use this when something failed and you need actual evidence.
- Check Application and System logs
- Look for error timing that matches the symptom
- Use it to support—not replace—other checks
Device Manager
Use this when hardware is missing, broken, or not recognized correctly.
- Check adapters, storage, audio, USB, display, and more
- Look for warning icons and driver issues
- Confirm whether Windows sees the device at all
Command Prompt Networking
Use this when internet, local network, or name resolution is failing.
Settings + Control Panel
Use these for visible configuration checks, but do not stop there.
- Network settings
- Programs and features
- Update status
- User and device settings
How a Support Tech Should Think
User report: “My computer is really slow today.”
Symptom
The user feels slowness. That is not yet the cause.
Best first tool
Open Task Manager to see CPU, memory, disk, and process usage.
Possible cause
A stuck process, full memory usage, heavy disk activity, or startup overload.
Correct habit
Gather evidence first, then decide whether to close an app, reboot, disable startup items, or escalate.
Quick Windows Tool-to-Problem Map
Micro-Quiz
Score at least 75% to unlock the next lesson.