Windows Troubleshooting Flowcharts

CompTIA A+ Core 2 - Interactive Learning Tool

CompTIA Troubleshooting Methodology

The CompTIA A+ troubleshooting methodology is a systematic 6-step process used to diagnose and resolve IT issues efficiently.

1
Identify the Problem
Gather information from users and system. Ask open-ended questions. Document symptoms. Determine if changes occurred recently. Use inquiry process: what, when, where, who, how. Replicate the problem if possible.
2
Establish a Theory of Probable Cause
Question the obvious. Consider multiple approaches. Start with simple solutions first. Research knowledge bases, vendor documentation, and online resources. Develop hypotheses based on symptoms.
3
Test the Theory to Determine Cause
Test your theory. If confirmed, determine next steps to resolve. If theory is not confirmed, re-establish new theory or escalate. Use safe mode, diagnostic tools, and isolate variables.
4
Establish a Plan of Action
Create action plan with steps to resolve. Consider corporate policies and impact to users. Get approval if needed. Backup data before making changes. Have rollback plan ready.
5
Verify Full System Functionality
Test the fix thoroughly. Verify the original problem is resolved and no new issues appeared. Test related functionality. Have user verify fix if possible. Implement preventive measures.
6
Document Findings, Actions, and Outcomes
Create detailed documentation. Record symptoms, solutions, and lessons learned. Update knowledge base. Document configuration changes. Include date, time, and technician name.

Interactive Troubleshooting Flowcharts

Select a problem type to begin the interactive troubleshooting flowchart:

Boot Failures

BSOD, boot loops, black screen

Slow Performance

System lag, high resource usage

Application Crashes

Programs freezing or closing

Network Issues

No connectivity, slow internet

Printing Problems

Printer offline, print queue issues

Display Issues

No display, distorted graphics

Audio Problems

No sound, distorted audio

Windows Update Failures

Update errors, rollback issues

Windows Recovery Tools Reference

Comprehensive guide to Windows recovery and diagnostic tools:

Safe Mode

Access: Advanced Startup > Troubleshoot > Startup Settings
When to Use:
  • Removing problematic drivers or software
  • Troubleshooting startup issues
  • Malware removal
  • System file corruption diagnosis

Windows Recovery Environment (WinRE)

Access: Settings > Update & Security > Recovery > Restart now
When to Use:
  • System won't boot normally
  • Access to advanced troubleshooting tools
  • Command prompt access when GUI fails
  • Startup repair and system restore

System Restore

Access: Control Panel > Recovery > Open System Restore
When to Use:
  • Recent software installation caused issues
  • Windows updates failed
  • System instability after changes
  • Driver conflicts

Startup Repair

Access: WinRE > Troubleshoot > Advanced options > Startup Repair
When to Use:
  • Boot configuration data (BCD) corruption
  • Missing or damaged system files
  • Master boot record (MBR) issues
  • Boot sector problems

Reset This PC

Access: Settings > Update & Security > Recovery > Reset this PC
When to Use:
  • Persistent malware infections
  • Severe system corruption
  • Performance issues after other fixes fail
  • Preparing PC for new user

System File Checker (SFC)

Command: sfc /scannow
When to Use:
  • Suspected system file corruption
  • Random crashes or errors
  • Before running DISM
  • After malware removal

DISM (Deployment Image Servicing)

Command: DISM /Online /Cleanup-Image /RestoreHealth
When to Use:
  • SFC unable to repair files
  • Windows image corruption
  • Component store issues
  • Before running SFC

Recovery Drive

Access: Control Panel > Create a recovery drive
When to Use:
  • Hard drive failure prevention
  • Boot from external media needed
  • Reinstalling Windows
  • Emergency recovery scenarios

Event Viewer

Access: eventvwr.msc or Windows Logs
When to Use:
  • Investigating application crashes
  • Diagnosing system errors
  • Security audit review
  • Hardware failure detection

Command Prompt (Recovery)

Access: WinRE > Troubleshoot > Command Prompt
When to Use:
  • Bootrec commands for boot issues
  • Diskpart for disk management
  • File operations when GUI unavailable
  • Registry edits (regedit)

Last Known Good Configuration

Access: F8 during boot (older Windows versions)
When to Use:
  • Recent driver installation caused boot issues
  • Configuration changes prevent booting
  • Note: Deprecated in Windows 10/11
  • Use System Restore instead

Performance Monitor

Access: perfmon.msc
When to Use:
  • Diagnosing performance bottlenecks
  • Monitoring resource usage over time
  • Identifying memory leaks
  • Disk I/O analysis

Troubleshooting Scenario Simulator

Practice real-world troubleshooting scenarios. Follow the flowchart to solve each problem:

Event Viewer Demo

Learn to interpret Windows Event Viewer logs. Filter by severity level to focus on specific issues:

Filter by Level:

Event Viewer Tips

  • Error (Red): Critical issues requiring immediate attention - application crashes, service failures, hardware errors
  • Warning (Yellow): Potential problems - disk space low, driver issues, performance degradation
  • Information (Blue): Normal operations - successful operations, service starts, routine events
  • Event ID: Unique identifier for troubleshooting - search Microsoft knowledge base
  • Source: Application or service that logged the event
  • Common Logs: Application (app errors), System (Windows/driver), Security (audit events)

Troubleshooting Knowledge Quiz

Test your Windows troubleshooting knowledge with 10 CompTIA A+ style questions:

Course Home