Degraded Performance

Your Windows PC was fine yesterday, but today it boots slow, the mouse stutters, and even opening Settings takes too long, so you need a clear method to fix degraded performance for CompTIA A+ Core 2 (220-1202), Domain 3.0 Software Troubleshooting, Objective 3.1 (Given a scenario, troubleshoot common Windows OS issues: Degraded performance).

In simple terms, degraded performance means the system feels slower than normal, slow startup, lag during basic tasks, apps freezing, or long load times. Sometimes the cause is minor (low disk space or too many startup apps), but other times it points to driver issues, failing storage, or malware.

This guide follows the same flow you should use on the exam and on the job. First, you'll confirm the symptoms and set a baseline, so you don't chase the wrong problem. Next, you'll check quick fixes, then move to deeper checks like resource usage, updates, and disk health. Finally, you'll lock in prevention steps, so the PC stays responsive after the repair.

Define "Slow"

For CompTIA A+ Core 2 (220-1202), Domain 3.0 Software Troubleshooting, Objective 3.1 (Degraded performance), the first skill is simple: describe the slowdown in a way you can test. "It's slow" is a feeling, but good troubleshooting needs clues you can repeat and measure. Think of it like a doctor visit, you want symptoms, timing, and triggers before you pick a treatment.

Start by naming what "slow" looks like on this PC. Then collect a few fast facts (power, storage, user scope) so you don't waste time fixing the wrong thing.

Pin down the symptoms before you change anything

Performance problems often hide behind vague complaints, so translate them into clear, observable signs. Common symptoms include slow startup, slow login, long app launches, browser lag, stuttering audio or video, random freezes, or high fan noise when doing light tasks. Each symptom points you toward a different bottleneck, for example, long boot times often relate to startup apps or disk health, while stuttering media can point to GPU drivers, high CPU, or background updates.

Next, confirm whether the slowdown is system-wide or isolated. A system-wide issue affects most apps and accounts. A narrow issue might only show up in one user profile or one application.

Use quick comparisons that take minutes:

Log in with a second account (or a local test profile) and repeat the same action. If it's fast there, suspect the original profile (startup items, sync tools, roaming profile issues, corrupted user settings).
Try a different app for the same task. If Chrome is slow but Edge is fine, the issue may be extensions or a damaged browser profile.
Check whether the problem follows the data. For example, does video stutter only on one website, or in every player?

Before you change settings, do two fast environmental checks because they explain a lot of "sudden" slowness:

Free storage space: If the system drive is nearly full, Windows has less room for updates, paging, and temp files. As a result, even basic tasks can drag.
Power state: Confirm the PC is plugged in (for laptops) and set to the intended power mode. A battery-saver plan can cap CPU speed and dim performance on purpose.

Treat symptoms like evidence. If you can't describe it clearly, you can't prove you fixed it.

Finally, listen for clues you can't see. A loud fan during idle work often means the CPU or GPU stays busy in the background. In contrast, quiet fans with long load times can hint at slow storage or heavy paging.

Ask about recent changes that often trigger performance drops

After you define the symptom, ask what changed. Timing matters because performance drops often follow a specific event. When a user says, "It started right after…," take that seriously because it narrows your search more than any generic checklist.

Focus on common triggers:

Windows updates: Feature updates, cumulative updates, and pending restarts can shift drivers, re-index files, or run cleanup tasks in the background.
Driver changes: GPU, chipset, storage, and network drivers can affect responsiveness. A bad GPU driver, for example, can cause stutter and UI lag.
New applications: Some apps add startup services, background sync, overlays, or telemetry. Even "light" tools can add up.
Browser extensions: New toolbars, ad blockers, coupon finders, and "PDF helpers" can slow page loads and add CPU spikes.
New printer software: Printer suites sometimes install status monitors and update agents that run all day.
VPN clients: VPNs can slow browsing, add DNS delays, or conflict with other network tools.
New security tools: Real-time scanning, web filters, and endpoint agents can cause heavy disk activity, especially after large downloads.
Recent file downloads: A large ISO, video folder, or archive can trigger antivirus scanning and Windows indexing.

Hardware changes matter too. Ask about new USB devices, external drives, webcams, or docking stations. A failing external drive can stall File Explorer. A dock can introduce driver conflicts, display glitches, or high CPU from a misbehaving device service.

Once you have a clear symptom and a timeframe, then it makes sense to look at logs. Event Viewer helps when you know what you're hunting, such as display driver resets, disk warnings, or service failures that match the moment the slowdown began. Without that anchor, logs become noise and you lose time.

Reproduce the problem and set a baseline

You can't troubleshoot what you can't repeat. First, do a quick reboot. This clears stuck processes, finishes updates, and gives you a clean starting point. After the restart, repeat the user's steps exactly, same app, same file, same website, same dock setup. If you change too many variables, the result stops meaning anything.

While you reproduce the issue, keep Task Manager open (Processes and Performance tabs). You're not trying to run advanced diagnostics yet. Instead, you are building a plain-language baseline: what "normal" looks like on this PC when it sits idle, compared to what happens during the slow action.

A practical baseline includes:

CPU: At idle, it should usually sit low. If it stays high, something runs constantly.
Memory: Watch whether memory use climbs until the system starts paging, which can feel like freezing.
Disk: High disk activity during simple actions can cause long waits. If disk usage stays pinned, suspect updates, indexing, antivirus scans, or storage issues.
Network: Slow browsing plus high network activity can point to sync tools, cloud backups, or a VPN.
GPU: Video stutter or UI lag with high GPU use can hint at driver or hardware acceleration problems.

Write down what you see, even in short notes. For example: "Idle CPU 8 to 12%, disk 2%, memory 70% used, app launch spikes disk to 100% for 45 seconds." Those notes become your comparison point after each change.

A baseline also keeps you honest. If performance improves, you can prove it. If it doesn't, you can stop guessing and move to the next likely cause with confidence.

Windows Tools

For CompTIA A+ Core 2 (220-1202), Domain 3.0 Software Troubleshooting, Objective 3.1 (Given a scenario, troubleshoot common Windows OS issues: Degraded performance), the fastest wins often come from tools already built into Windows. They help you confirm the bottleneck instead of guessing, whether it is CPU load, memory pressure, disk contention, or background network traffic.

Start with the simplest view (Task Manager), then zoom in only when you see a clear signal. This approach saves time because each tool answers a different question, and you can tie your fix to evidence you can repeat after changes.

Task Manager checks that point to the real cause

Task Manager is your first pass because it shows both symptoms and likely culprits. Open it with Ctrl + Shift + Esc, then keep it visible while you reproduce the slowdown. Small spikes are normal, but sustained pressure usually explains the user's complaint.

In the Processes tab, focus on what stays high, not what briefly peaks. First, click the column headers to sort by CPU, Memory, Disk, and Network. Sorting turns noise into a short list of suspects.

Here is what often matters most:

Runaway CPU use: If a process sits high for minutes (not seconds), it can cause stutter, heat, and loud fans. Common causes include browser tabs, video calls, update services, and third-party security tools.
Memory pressure: High memory use is not always bad, but the pattern matters. If memory stays high and the PC pauses during simple actions, Windows may page to disk. That feels like freezing because storage is far slower than RAM.
High disk usage: Look for sustained high disk activity during basic tasks. If the disk column stays busy, app launches and logins drag because everything waits in line.
Unexpected network use: High network traffic can slow browsing and cloud apps. It can also cause CPU spikes if encryption or syncing runs nonstop.

Next, move to the Performance tab to confirm whether the problem is a true bottleneck. The graphs help because they show sustained saturation. For example, a CPU that pins at a high percentage during a simple task points to a compute limit. On the other hand, a disk that stays near 100 percent active time often points to storage contention, not a "slow CPU."

Pay attention to these signs:

Disk active time stays high while transfer speed looks modest. This often means many small reads and writes, not one large copy.
Memory use stays high and the system feels sluggish when switching apps. That often matches paging behavior.
CPU stays high at idle after startup. That points to background tasks, updates, or a stuck service.

The Startup apps tab helps with slow boot and slow login. Too many startup items can create a traffic jam before the user even opens an app. Disable items carefully, and avoid turning off anything you cannot identify. As a rule, keep security tools and core drivers enabled unless you have a clear reason.

A safe workflow is simple:

Record the current enabled startup items (a screenshot works).
Disable one or two high-impact, non-essential items.
Reboot, then measure boot and login behavior again.

Finally, check the Users tab when the complaint is "the whole PC is slow" on a shared system. This view shows resource use by each signed-in user. If one user session runs heavy processes, it can slow everyone else.

Change control matters. When you disable startup items or end tasks, document what you touched so you can reverse it quickly.

Resource Monitor for "who is using the disk and network"

Open Resource Monitor when Task Manager shows high disk or network use but does not make the cause obvious.