Master Windows 11 Troubleshooting with Five Built In Tools

My laptop has never been happier since I learned to treat Windows 11 like a system you can inspect, diagnose, and repair yourself — using five built-in troubleshooting tools that stop most problems before they become a repair-shop bill.

Overview​

Windows 11 ships with a compact toolbox that covers the majority of everyday faults: slow performance, unresponsive apps, driver problems, boot failures, and mysterious errors. Learning to use Task Manager, Event Viewer, System Restore, Device Manager, and the Command Prompt turns hours of guessing into minutes of confident action. These tools are free, fast, and—when used carefully—safer for your privacy than handing your device to a third party.
This article explains what each tool does, how to use it step by step, real-world troubleshooting workflows that combine tools, and the limits and risks you should be aware of before making system changes. Practical tips, concrete commands, and clear decision rules will let you fix most issues yourself while preserving your data and avoiding unnecessary repair costs.

---

Background: Why built-in tools matter​

Built-in troubleshooting tools let you:

• Diagnose what is wrong (logs, error codes, resource usage).
• Test fixes in place (disable a startup app, roll back a driver).
• Recover a working state (restore points, system image).
• Repair core components (system file repair, disk checks).
• Work without shipping your device off or exposing personal files.

Using the system's own tools also keeps control local: you don't need to give strangers remote access to your files, passwords, or sensitive accounts. That’s a meaningful privacy and security advantage.

---

Task Manager — identify the resource hog​

What Task Manager is best for​

Task Manager is your first port of call when Windows is sluggish, an app is frozen, or startup feels slow. It gives a live view of:

• Running processes and apps
• Resource usage (CPU, Memory, Disk, GPU, Network)
• Startup programs that run when Windows boots
• Background services and which ones are consuming resources

Quick checks and actions​

• Press Ctrl + Shift + Esc (or Ctrl + Alt + Del then Task Manager) to open it immediately.
• On the Processes tab, sort by CPU, Memory, or Disk to see the top resource consumers.
• If an app shows Not Responding, select it and click End task to close it without rebooting.
• Open the Startup tab to review programs that auto-start. Disable anything you don’t need at boot.
• Use the Performance tab to monitor CPU, memory, disk, and GPU trends — this helps detect a resource limit or failing hardware symptom.
• For deeper investigation, right‑click a process and select Open file location, Search online, or Properties.

Advanced tips​

• Use Resource Monitor (open from Task Manager’s Performance tab) to see per-thread disk I/O and network activity.
• When multiple processes use high CPU, expand them and check subprocesses (services under svchost.exe). That narrows down the culprit service.
• For slow shutdowns or boots, look for drivers or apps that hang in the Startup tab and update/disable them.

Risks and limits​

Ending system-critical processes can make Windows unstable. Don’t forcibly kill processes you don’t recognize without looking them up. When in doubt, Google the process name on a separate device or put it in a sandbox before acting.

---

Event Viewer — find the error, not the symptom​

Why Event Viewer matters​

Event Viewer is a chronological log of system, application, and security events. It doesn’t fix problems, but it tells you:

• Which service or driver produced an error
• When the error started and how frequently it occurs
• Error codes and textual descriptions that narrow troubleshooting steps

How to use Event Viewer effectively​

• Open Event Viewer (press Windows key, type Event Viewer).
• In Windows Logs, check System and Application for red errors and yellow warnings.
• Filter logs to recent time windows (last 24 hours) and severity to avoid noise.
• Create a Custom View to show only relevant event sources (e.g., Kernel-Power, Application Error).
• Click an event to read the General and Details tabs for error codes and faulting module names.

Practical investigation workflow​

• If a particular app crashes, inspect Application logs for the faulting module and timestamp.
• If the machine unexpectedly restarts, check System logs for Kernel-Power or bugcheck (blue screen) entries.
• Use the event's source and error code to search official Microsoft documentation or manufacturer knowledge bases for targeted fixes.

Tips to avoid overwhelm​

Event Viewer is noisy. Create filters and focus on:

• Event IDs that repeat
• Critical and error-level events that correspond to observed faults
• Events that point to driver files or specific DLLs — those are usually actionable leads

Risks and caveats​

Event Viewer shows what happened, not why. Correlate timestamps with user actions and Task Manager captures. Misinterpreting logs can lead to unnecessary changes.

---

System Restore — rollback without reinstalling​

What System Restore does​

System Restore snapshots critical system files, installed drivers, and the registry so you can roll Windows back to an earlier point without touching personal files. It’s a fast recovery method when a recent app or driver update breaks the system.

Enabling and using System Restore​

• System Restore is often disabled by default. To enable it:
• Open Control Panel → System and Security → System → System protection (or search “Create a restore point”).
• Select the system drive (usually C and click Configure.
• Turn on system protection and choose the amount of disk space for restore points.
• Click Create to make a manual restore point before risky changes.
• To restore:
• Open System Restore from the same System Protection dialog or boot into Advanced Startup > Troubleshoot > Advanced Options > System Restore.
• Choose a restore point from before the problem occurred and follow prompts.

When to use System Restore​

• After a bad driver update
• After installing software that corrupts system behavior
• Before attempting invasive changes (large updates, customizing system folders)

Strengths and limitations​

• System Restore is fast and usually fixes configuration and driver mistakes.
• It doesn’t replace a full backup — personal files are not covered.
• Restore can’t always undo firmware or major Windows feature updates; it focuses on system files and drivers.
• Restores are irreversible once started; let the process complete uninterrupted.

Good practices​

• Create a manual restore point before trying untrusted drivers, beta software, or significant registry edits.
• Complement System Restore with a scheduled full-image backup for critical systems and data.

---

Device Manager — fix hardware and driver problems​

What Device Manager shows​

Device Manager lists all hardware and drivers and indicates issues with a yellow exclamation mark. It’s the canonical place to diagnose device-level problems: ports not working, cameras missing, audio failures, and driver conflicts.

Core Device Manager actions​

• Open Device Manager (press Windows key, type Device Manager).
• Look for devices with a warning triangle. Expand categories to find the offending hardware.
• Right-click a device and choose:
• Update driver — search automatically or browse local driver files.
• Disable device — temporarily stop a device if it causes instability.
• Uninstall device — remove a driver so Windows can re-detect and reinstall it.
• Properties → Driver → Roll Back Driver to revert a recent update.

Practical driver troubleshooting flow​

• If a device recently stopped working, check Driver date and version then Roll Back if available.
• If Roll Back is not available, choose Update driver and let Windows search automatically; if that fails, download the driver from the device manufacturer and use Browse my computer to install it.
• If a device remains unknown, use Scan for hardware changes after uninstalling or disable power management features that may suspend USB devices.

Advanced repair steps​

• Use the View menu to show hidden devices — ghosted drivers can cause conflicts.
• For audio issues, check the sound device properties and ensure correct output device is selected in Windows Settings.
• If a NIC fails after sleep/resume, toggle “Allow the computer to turn off this device to save power” in device power management.

Risks and precautions​

Installing drivers from untrusted sources risks malware and system instability. Always prefer manufacturer-signed drivers or Windows Update. When testing unsigned drivers, create a restore point first.

---

Command Prompt — rescue, repair, and recover​

Why Command Prompt still matters​

Command Prompt (and its sibling PowerShell) gives text-based access to repair commands that are invaluable when the GUI fails. It’s the last-resort tool for boot problems, corrupt system files, and disk errors.

Essential commands (safe and widely used)​

• System File Checker: sfc /scannow
• Scans and repairs missing/corrupt system files.
• DISM health repair: DISM /Online /Cleanup-Image /RestoreHealth
• Fixes the Windows component store so sfc can complete repairs.
• Disk check: chkdsk C: /f /r
• Locates and attempts recovery of bad sectors and fixes filesystem errors (often requires reboot).
• Boot repair (from Recovery Environment):
• bootrec /fixmbr
• bootrec /fixboot
• bootrec /scanos
• bootrec /rebuildbcd

When to run these commands​

• If sfc /scannow reports corrupt files but can’t fix them, run DISM first then rerun sfc.
• If the system won’t boot or shows a boot manager error, use the Windows Recovery Environment (WinRE) and run bootrec and startup repair.
• If SMART or repeated disk errors occur, chkdsk can repair filesystem structures but failing physical drives should be replaced.

Safe step-by-step recovery routine (GUI fails)​

• Boot to WinRE (hold Shift while choosing Restart, or use recovery options).
• Choose Troubleshoot → Advanced options → Command Prompt.
• Run chkdsk on the system volume: chkdsk C: /f /r
• Run DISM: DISM /Online /Cleanup-Image /RestoreHealth
• Run sfc: sfc /scannow
• If boot errors persist, run the bootrec sequence.

Data-first approach​

If disk errors suggest imminent hardware failure, use the Command Prompt to quickly copy essential files to an external drive (robocopy or xcopy), then perform image backups before attempting repairs.

Risks and safety measures​

Command-line operations can cause data loss if mistyped. Always:

• Type commands carefully and verify flags.
• Back up critical data before running repair commands that might alter partitions or rewrite boot sectors.
• When in doubt, create a drive image first.

---

Combining tools in real-world scenarios​

Scenario 1 — Laptop is slow after installing new app​

• Open Task Manager to spot resource spikes and kill the offending process.
• Disable the app in Startup if it autostarts.
• If crashes or repeated errors occur, check Event Viewer for application errors and faulting modules.
• If the app changed system files, use System Restore to roll back to before installation.

Scenario 2 — Sound or camera stopped working after update​

• Use Device Manager to check for warnings; roll back the driver or reinstall using the manufacturer's driver.
• If driver updates fail repeatedly, create a System Restore point, uninstall the device, and reboot to let Windows re-detect it.
• Check Event Viewer for device-specific errors (driver install failures).

Scenario 3 — Windows won’t boot after update​

• Boot into WinRE and use Startup Repair.
• If Startup Repair fails, use the Command Prompt: run chkdsk, DISM, then sfc.
• If the bootloader is corrupted, run bootrec commands.
• If all else fails, restore to a System Restore point or recover files and reinstall Windows.

---

Preventive maintenance — reduce the number of repairs​

• Enable System Restore and create manual restore points before risky changes.
• Schedule regular full-image backups or use cloud backup for critical files.
• Keep drivers updated from the manufacturer, but avoid automatically installing unsigned drivers.
• Use Task Manager’s Startup tab to limit background apps that slow boot and waste resources.
• Check Event Viewer periodically for recurring warnings—small issues often precede bigger failures.
• Run sfc and DISM quarterly to maintain system file health.

---

When to stop and seek professional help​

Built-in tools resolve most software and driver issues, but there are times to consult a professional:

• Repeated hardware faults (SMART warnings or repeated bad sectors) signal physical drive failure.
• Complex firmware updates (BIOS/UEFI) that go wrong can brick a motherboard; these are risky without experience.
• If malware has deep hooks in the OS and you can’t confidently clean or rebuild without losing data.
• Electrical or physical damage (liquid spills, crushed ports) that require part replacement.

If a repair shop is required, prepare before you hand over the device:

• Back up and encrypt sensitive data.
• Remove accounts or change passwords after recovery.
• Ask for a detailed scope of work and diagnosis steps before authorizing repairs.

---

Limitations, risks, and best practices​

• Built-in tools are powerful but not infallible. They can mask failing hardware and sometimes only provide temporary relief.
• Misapplied fixes (incorrect registry edits, unsigned driver installs) can make recovery harder.
• System Restore does not replace backups — always pair restore points with full-image backups for critical systems.
• Command-line repairs can alter boot records and partitions; verify commands and ensure backups exist.
• When using online troubleshooting guides, prioritize manufacturer and Microsoft documentation to avoid incorrect steps.

---

Final recommendations and checklist​

• Learn three commands: sfc /scannow, DISM /Online /Cleanup-Image /RestoreHealth, and chkdsk C: /f /r.
• Keep System Restore enabled and create a restore point before risky changes.
• Use Task Manager and Resource Monitor to spot immediate resource hogs.
• Inspect Event Viewer only for correlated timestamps and repeat events; use filters.
• Use Device Manager to roll back drivers before installing new ones from unknown sources.
• When in doubt, back up then experiment; the cost of a backup is always lower than data loss.

---

Conclusion
Mastering the five built-in Windows troubleshooting tools — Task Manager, Event Viewer, System Restore, Device Manager, and Command Prompt — puts troubleshooting power back in your hands. These tools stop most common issues quickly, protect your privacy, and reduce the need to pay for repairs. With methodical use, a few safety precautions, and a consistent backup strategy, most Windows 11 problems are manageable at home. The key is to act deliberately: gather evidence (Task Manager and Event Viewer), test low-risk fixes (disable startup items, roll back drivers), and escalate to full repairs (sfc, DISM, chkdsk, or System Restore) only after backing up essential data. This workflow saves time, money, and the headaches of handing your device over when the solution is often just a few diagnostic steps away.

---

Source: Pocket-lint I use these 5 Windows troubleshooting tools to avoid paying for repairs