Windows Troubleshooting / Windows 11
Windows Troubleshooting Checklist
Quick answer
Start by defining the symptom, then test the smallest reversible cause: restart once, check storage, check Task Manager, confirm whether another account/app/device has the same problem, and only then use repair tools. If you already know the exact symptom, jump to that guide instead of applying every fix on this page.
Quick diagnosis
If several of these match what you see, you are in the right guide.
- You are not sure which Windows troubleshooting guide fits
- Several things are failing after an update, install, or hardware change
- You want safe first checks before running advanced commands
- You need to decide whether the issue is Windows, an app, the network, or hardware
Possible causes
- Pending restart or update servicing
- Low storage, high memory, or a startup app consuming resources
- A device, driver, or recent install changed the system
- A network, browser, security, or file-specific issue being mistaken for a Windows-wide failure
What you need
- Settings
- Task Manager
- Device Manager
- Windows Security
What this problem usually means
Good Windows troubleshooting is not a giant list of tweaks. It is a sequence: symptom → likely cause → test → result → next action. The goal is to avoid resetting Windows, replacing parts, or installing utilities before you know what failed.
Use this checklist as a router. It links to deeper Practical PC guides when the evidence points to a specific problem.
Before you start
- If files matter, back up important work before running repair commands or uninstalling software.
- Do not install driver boosters, registry cleaners, or DLL fixer tools.
- Write down the exact error message or symptom before changing settings.
- If the PC smells hot, has a swollen battery, clicks loudly, or loses power, stop and check hardware first.
Quick fixes
1. Classify the problem before fixing it
- Ask: is the issue startup, performance, update, app, network, file, display, sound, input, security, or storage?
- Ask whether it affects one app or the whole PC.
- Ask what changed right before it started: update, install, driver, cable, dock, router, account, or hardware.
- Use the PC troubleshooting wizard if the category is still unclear.
2. Restart once, then stop repeating it
Restart can finish Windows servicing and clear a stuck process. If the issue returns immediately, repeating restart is no longer diagnosis. Move to the matching branch below.
Step-by-step troubleshooting
If Windows feels slow
- Check Task Manager. CPU, memory, disk, or network pinned near 100% tells you where to look.
- If memory is high, use high memory usage and the RAM calculator.
- If disk space is low, use free disk space before uninstalling random apps.
- If the wait is before sign-in, use slow boot instead of general performance fixes.
If an app, browser, or file fails
- One Windows app: repair/reset it in Settings, or use Windows apps won't open.
- One PDF: use PDF files won't open and check the file extension lookup.
- Chrome or Edge: choose slow, crashing, or won't open; those are separate failure modes.
- A file will not delete or Explorer freezes: start with the Files guides, not system reset.
If network or Wi-Fi fails
- If other devices fail too, suspect router or ISP before Windows.
- If Wi-Fi is connected but most websites fail, use Wi-Fi connected but no internet.
- If only some sites fail, use some websites won't load.
- Use the Internet Connection Troubleshooter to choose between DNS, router, adapter, and signal issues.
If a device is missing or not detected
- Device Manager with a missing adapter, warning icon, or disabled device is evidence.
- USB devices belong in USB not recognized; drives belong in external drive not showing.
- Sound input/output are separate: use microphone or headphones.
- A second monitor should be checked with Win+P, Display settings, cable, input, and port order.
If there is an error code or recovery screen
- Copy the exact code and use the Windows error code lookup.
- Blue screens should be routed through the BSOD stop code lookup.
- Automatic Repair loops and Safe Mode are recovery paths, not routine performance fixes.
- Do not run destructive disk or boot commands unless the guide explains why and what result to expect.
Where should you start?
Choose an answer. The next question appears below, no account or download required.
Check update status, free space, and restart once. If stuck, use the Windows Update guides.
Disable the new startup item or repair the app. Do not reset Windows yet.
Disconnect the new hardware and retest. If the issue disappears, troubleshoot that device path.
Repair the app, check the file type, or use the matching Software/Files guide.
Test another device and use the network guides before resetting Windows.
Use Device Manager plus a known-good cable/port/device test to separate hardware from settings.
Use Safe Mode, System Restore, or Automatic Repair guidance before changing normal desktop settings.
How to know the problem is fixed
- The original symptom is gone in the same place it failed before.
- A second quick check still works, such as another app, another website, or another restart.
- You can explain what changed and why it fixed the issue.
If the problem continues
If the checklist does not identify the branch, stop changing settings and collect evidence: exact error text, Task Manager numbers, Device Manager state, Windows Update history, and what changed recently. That information makes the next guide or technician visit much more useful.
When this may be hardware failure
Suspect hardware when a problem follows a device, cable, port, battery, drive, or display across software changes. Clicking drives, swollen batteries, burning smells, no power lights, and repeated failures with known-good parts are stronger hardware clues than a single Windows error.
Common mistakes to avoid
- Trying every fix from every category without checking whether it matches the symptom.
- Running registry scripts or driver packs because they promise to repair everything.
- Resetting Windows before backing up files or checking a single-app cause.
- Replacing hardware because one app or browser misbehaves.
Frequently asked questions
Should I run SFC and DISM first?
No. They are reasonable when many Windows components fail or a guide calls for them. For one app, one website, one headset, or one PDF, start with the smaller matching test.
When should I stop troubleshooting?
Stop when data loss, swollen batteries, repeated power failure, disk clicking, or business-critical work is involved. Back up and get help rather than forcing more fixes.
Written by Practical PC editorial team. We write practical Windows and PC troubleshooting guides for home users, students, and office workers. Guides are researched from official documentation and widely observed support patterns, then reviewed for safety and plain language. We do not invent lab tests, certifications, or first-hand repair experience we do not have.