CompTIA A+ Core 2 exam objective 3.2 asks you to troubleshoot common Windows OS issues — the real-world messes that make users call IT. This matters because on the 220-1202 exam, you will be given a scenario where a Windows machine is behaving badly, and you must choose the correct first step to diagnose and resolve it. Getting this wrong can cost you the question, but more importantly, knowing how to troubleshoot correctly is the difference between being a user who panics and a professional who fixes.
Jump to a section
A simple way to picture Troubleshooting Windows OS Issues
A house painter arrives at a job to find the homeowner furious. The living room wall is streaked, the paint is peeling in the bathroom, and the kitchen ceiling has a water stain the painter didn't cause. The painter doesn't panic. Instead, they put down their brush and start a methodical walk-through. They check the prep work: was the old paint sanded? They look at the primer: was it the right type for the bathroom's humidity? They sniff for mould behind the peeling spot. They ask the homeowner: 'Did you turn on the bathroom fan after the last shower?' The painter isn't trying to paint yet. They are gathering clues. Once they find the root cause — a leaking pipe in the ceiling — they don't slap paint over it. They call a plumber. Only after the pipe is fixed and the wall dried do they patch, prime, and repaint. The homeowner sees the mess and wants it gone fast. The pro knows that fast means fixing the cause, not just the symptom.
This is exactly what an IT pro does when a Windows machine has the Blue Screen of Death, or a laptop won't connect to Wi-Fi, or an application crashes every time you open it. The user sees a broken screen. The tech sees a chain of clues leading back to a driver conflict, a corrupted system file, or a misconfigured setting. The tech doesn't start by reinstalling Windows. They start with methodical investigation — asking questions, checking logs, testing one thing at a time. The painter's comeback is a calm, step-by-step fix that lasts. The IT pro's comeback is a stable, running system.
Troubleshooting Windows OS issues is the systematic process of identifying, isolating, and resolving problems that prevent Windows from operating correctly. For a beginner, think of it as detective work: you have a crime scene (the broken computer), witnesses (the user), evidence (error messages, logs), and you need to find the culprit (the root cause). The whole point of troubleshooting is to fix the problem permanently, not just mask the symptoms.
Before you can troubleshoot, you need to know the common types of Windows issues you will face. These include:
Blue Screen of Death (BSOD): a full-system crash that displays a blue error screen with a stop code. This usually points to a hardware driver problem, faulty RAM, or a corrupted system file.
Slow performance: the computer takes ages to boot, open applications, or respond to clicks. This can be caused by too many startup programs, low disk space, malware, or failing hardware.
Application crashes: a specific program (like Word or Chrome) stops working and may show an error message. This could be due to a corrupt installation, incompatible version, or missing system files.
Network connectivity issues: the computer cannot connect to the internet or a local network. This might involve faulty drivers, misconfigured IP settings, or a dead network adapter.
Startup and boot failures: the computer gets stuck on a black screen, shows a 'Boot Device Not Found' error, or loops during the Windows logo. This often means the bootloader is corrupted, a system file is missing, or the hard drive is failing.
Driver problems: Windows cannot control a hardware component (like a printer, graphics card, or Wi-Fi adapter) because the driver software is missing, outdated, or incompatible.
Malware and viruses: malicious software causing pop-ups, slow performance, or data theft. Antivirus scans and malware removal tools are the primary response.
User account and permission issues: a user cannot log in, or they get 'Access Denied' messages. This might be a forgotten password, a locked account, or incorrect file permissions.
Update failures: Windows Update hangs, fails to install, or causes problems after installation. This can be due to corrupt update files, insufficient disk space, or a conflicting third-party application.
The core of troubleshooting is a methodical framework often called the 'troubleshooting methodology'. It is a step-by-step process that ensures you do not skip critical checks. The classic CompTIA 6-step process is: 1. Identify the problem: gather information from the user, ask questions ('What were you doing when it crashed?', 'Did you install anything new?'), and document the symptoms. 2. Establish a theory of probable cause: based on the symptoms, think of the most likely reasons. For a BSOD, a common theory is a bad driver or failing RAM. 3. Test the theory: run tests to confirm or rule out your theory. This could be checking Event Viewer logs, running a memory diagnostic, or updating a driver. 4. Establish a plan of action: decide what fix to try first. The safest, least invasive fix is usually attempted first (e.g., restart the computer before reinstalling Windows). 5. Implement the fix: apply the solution you chose. 6. Verify full system functionality: make sure the original problem is resolved and that nothing new broke. Also, document what you did and what the root cause was.
This framework is not optional. On the 220-1202 exam, the 'correct answer' often hinges on knowing which step comes next. For example, a question might describe a user who gets a 'file is corrupted' error after installing a new app. The wrong answer might be 'immediately run a full antivirus scan'. The correct answer is 'gather more information from the user about when the error started' because you must identify the problem first.
Common tools you will use include:
Event Viewer: a built-in Windows tool that logs system, application, and security events. It is the number one place to find detailed error codes and timestamps.
Task Manager: shows running processes, CPU and memory usage. Great for spotting a program that is using too many resources.
Safe Mode: a stripped-down version of Windows that loads only essential drivers. Booting into Safe Mode helps isolate whether a third-party driver or startup program is causing the issue.
System File Checker (SFC): a command-line tool that scans for and repairs corrupted Windows system files.
System Restore: rolls back system files, settings, and programs to an earlier point in time without affecting personal files.
CHKDSK (Check Disk): scans the hard drive for file system errors and bad sectors.
MSConfig (System Configuration): a tool to manage startup programs and boot options.
Windows Memory Diagnostic: tests RAM for errors.
Malwarebytes or Windows Defender: tools for detecting and removing malware.
Each of these tools has a specific purpose. Knowing when to use which is critical for the exam. For instance, if a user reports that an error started after a recent Windows Update, the logical first step is to check if Safe Mode works, then use System Restore to undo the update.
Identify the problem
Ask the user detailed questions: What happened exactly? When did it start? Did you install anything new or change any settings? Document the symptoms, error messages, and any recent changes. This step prevents you from wasting time on wrong theories.
Establish a theory of probable cause
Based on the symptoms, think of the most likely root causes. For example, a BSOD with a 'MEMORY_MANAGEMENT' stop code points to a RAM issue. A slow boot points to too many startup programs or a dying hard drive. List your top one or two theories.
Test the theory
Use the appropriate tool or test to confirm or rule out your theory. For RAM issues, run Windows Memory Diagnostic. For corruption, run SFC /scannow. For startup issues, boot into Safe Mode. If the test confirms your theory, move on. If not, go back to step 2.
Establish a plan of action
Decide what fix to apply first, starting with the least invasive and safest option. For example, if a driver is suspected, update the driver before reinstalling the operating system. If a recent update caused the issue, use System Restore before resetting the PC.
Implement the fix
Apply the solution you chose in step 4. This could involve running a command, uninstalling software, rolling back a driver, or replacing hardware. Work methodically to avoid introducing new problems.
Verify full system functionality
After the fix, confirm that the original problem is gone. Also test other related functions to ensure nothing else broke. For example, after fixing a network adapter driver, make sure the user can still connect to printers and shared drives. Finally, document the issue, the root cause, and the resolution.
Imagine you are the only IT support person for a small accounting firm with 30 employees. It is a Tuesday morning, and a frantic call comes in from Sarah in payroll. Her Windows 11 PC is stuck in a boot loop: it starts booting, shows the Windows logo, then restarts. She has payroll reports due by noon. The partner walks by and asks, 'Is it fixed yet?'
Your job is not to guess. Your job is to follow a methodical process.
First, you ask Sarah detailed questions: 'Did it start happening after you installed anything? Did Windows update last night? Did you turn it off normally yesterday?' Sarah says it was fine yesterday, she installed a new accounting software plugin, and then Windows prompted a restart. She clicked restart, and since then, it has been looping.
You now have a theory: the new plugin is incompatible with the current Windows version or a system file got corrupted during the update. You need to test. You boot the PC into Safe Mode. To do this, you interrupt the boot process three times by holding the power button during the Windows logo. On the third attempt, Windows Recovery Environment (WinRE) appears. From there, you go to Troubleshoot > Advanced Options > Startup Settings > Restart, then press 4 for Safe Mode.
The PC boots successfully into Safe Mode with only essential drivers. This tells you the problem is likely caused by a third-party driver or startup application. You then open MSConfig, go to the Services tab, check 'Hide all Microsoft services', and disable all third-party services. You also go to the Startup tab and disable the new plugin from loading at startup. You restart normally. The PC boots fine. You then re-enable services one by one to isolate the culprit. You find the new accounting plugin service is the problem. You uninstall it and inform the vendor.
Next steps: you run Windows Update to ensure no pending updates are corrupted. You also run SFC /scannow to check system file integrity. You verify the payroll software works. Sarah is back online by 10:30 AM. You document the entire process in a ticket, noting the fix and the root cause (incompatible plugin service).
Later that week, another user reports a Blue Screen of Death with a stop code 'PAGE_FAULT_IN_NONPAGED_AREA'. You check Event Viewer and see repeated memory errors. You run Windows Memory Diagnostic, which finds faulty RAM. You order a replacement stick. The problem disappears.
These scenarios show the real rhythm of troubleshooting. You do not have to know every answer instantly. You need a deliberate process, a toolkit of built-in utilities, and the discipline to test one variable at a time.
The 220-1202 exam tests troubleshooting in two main ways. First, they give you a scenario and ask, 'What is the MOST likely cause of this issue?' Second, they ask, 'Which tool should the technician use to resolve this problem?' The third common pattern is 'What is the NEXT step the technician should take?'
Concepts they love to test:
The order of the CompTIA troubleshooting methodology. They will try to trick you into jumping to a fix before identifying the problem. Always look for the step that involves gathering more information first.
Safe Mode: knowing what it is, how to enter it (using power button interrupts or F8 on older systems), and what its limitations are. They love to ask, 'Which mode should a technician use to load only essential drivers?' Answer: Safe Mode.
System Restore vs. Backup and Restore: System Restore only affects system files and registry settings, not user files. A common trap is asking about restoring a deleted document. System Restore will not help. That requires Backup and Restore or a previous version of the file.
Event Viewer: specifically, the 'System' and 'Application' logs. They test that the 'Error' level events are the ones to look at. A question might say, 'A user reports intermittent crashes. Where should the technician look first?' Answer: Event Viewer.
CHKDSK and SFC: knowing which command repairs system files (SFC /scannow) and which scans the file system and disk for errors (chkdsk /f or chkdsk /r). Exam questions often swap these roles.
Boot errors: 'Bootmgr is missing', 'Invalid boot device', 'NTLDR is missing' (older systems). They test that these usually require a Startup Repair from the Windows Recovery Environment or rebuilding the BCD (Boot Configuration Data).
Blue Screen of Death stop codes: you do not need to memorise every code, but they expect you to recognise common ones like 'MEMORY_MANAGEMENT' (RAM issue), 'PAGE_FAULT_IN_NONPAGED_AREA' (usually faulty RAM or driver), and 'IRQL_NOT_LESS_OR_EQUAL' (bad driver).
Common traps:
Trap 1: The user says, 'My computer is slow.' The correct first step is to open Task Manager and check resource usage, not to immediately reinstall Windows.
Trap 2: 'A user cannot connect to Wi-Fi.' The first step is to check if the wireless adapter is enabled and has the correct SSID and password, not to go straight to updating the driver.
Trap 3: 'Windows Update is stuck at 50%.' The answer is rarely 'wait longer'. The correct approach is to run the Windows Update Troubleshooter or stop the Windows Update service and clear the SoftwareDistribution folder.
Trap 4: Confusing 'System Configuration' (MSConfig) with 'System Information' (msinfo32). MSConfig manages boot and startup settings; System Information shows hardware and software details.
Key definitions to memorise:
BSOD: Blue Screen of Death, a critical system error.
Event Viewer: logs system, security, and application events.
Safe Mode: minimalist boot environment with only essential drivers.
System File Checker (SFC): repairs corrupted system files.
CHKDSK: checks disk integrity and repairs file system errors.
System Restore: reverts system files and settings to a restore point.
Boot Configuration Data (BCD): firmware-independent boot configuration database.
WinRE: Windows Recovery Environment, a recovery toolset.
The CompTIA six-step troubleshooting methodology starts with identifying the problem, not jumping to a solution.
Safe Mode loads only essential drivers and is the primary way to isolate whether a third-party driver or startup application is causing an issue.
Event Viewer is the central log repository for system problems; always check the 'System' and 'Application' logs for error events.
System Restore affects only system files and registry settings, not personal user files—never use it to recover a deleted document.
The SFC /scannow command repairs corrupted Windows system files, while CHKDSK /f checks the file system for logical errors.
A Blue Screen of Death stop code is a crucial clue; write it down before doing anything else to narrow down the cause.
Slow performance is most often diagnosed first by opening Task Manager to check CPU, memory, and disk usage, not by running an antivirus scan.
Windows Update issues can often be resolved by stopping the Windows Update service and deleting the SoftwareDistribution folder.
The Boot Configuration Data (BCD) stores boot configuration; if the system cannot boot, you may need to rebuild it from the Windows Recovery Environment.
Documenting every step of your troubleshooting process is important for knowledge sharing and for demonstrating a methodical approach.
These come up on the exam all the time. Here's how to tell them apart.
System File Checker (SFC)
Scans and repairs corrupted Windows system files like .dll and .sys files.
Run from Command Prompt as 'sfc /scannow'.
Does not check the physical hard disk for bad sectors.
Check Disk (CHKDSK)
Scans the file system for logical errors and checks the disk for bad sectors.
Run from Command Prompt as 'chkdsk /f' or 'chkdsk /r'.
Can detect and mark bad sectors on the hard drive.
System Restore
Rolls back system files, registry settings, and installed programs.
Does not affect user personal files like documents or photos.
Uses restore points created automatically or manually.
Backup and Restore (Windows 7)
Creates full backups of user files and system images.
Can restore individual files or entire system images.
Used primarily for disaster recovery.
Safe Mode
Loads only essential drivers and services needed to start Windows.
Used to isolate problems caused by third-party drivers or applications.
No network access (unless Safe Mode with Networking is chosen).
Normal Mode
Loads all drivers and startup programs configured by the user.
Normal operation for everyday use.
Full network and peripheral functionality.
Event Viewer
Logs system, security, and application events with timestamps and error codes.
Used for historical analysis of errors and warnings.
Does not show real-time resource usage.
Task Manager
Shows real-time performance metrics like CPU, memory, disk, and network usage.
Used to identify resource-hogging processes.
Provides ability to end tasks or processes.
Windows Update Troubleshooter
Automated tool that scans for common update problems and fixes them.
Easy for beginners: launched from Settings > Update & Security > Troubleshoot.
May not fix complex corruption issues.
Manual SoftwareDistribution Reset
Requires stopping the Windows Update service and deleting the SoftwareDistribution folder manually.
More thorough: clears the entire update download cache.
Administrator privileges needed.
Mistake
If a computer has a Blue Screen of Death, the first thing to do is reinstall Windows.
Correct
The first step is to record the stop code, then check Event Viewer for details, and then use diagnostic tools like Windows Memory Diagnostic or CHKDSK based on the code.
Reinstalling Windows is a last resort because it is time-consuming and may not fix a hardware problem like faulty RAM. Beginners often panic and think a fresh install will solve everything, but it is overkill when the cause is a single corrupt driver.
Mistake
System Restore can recover personal files that were accidentally deleted.
Correct
System Restore only rolls back system files, registry settings, and installed programs. It does not touch user documents, photos, or other personal files.
The word 'Restore' confuses people. They think it is a backup tool. In reality, Windows has separate tools like File History or Backup and Restore for file recovery. Beginners often try System Restore when they have missing documents and wonder why it did not bring them back.
Mistake
Running an antivirus scan is always the correct first step when a computer is slow.
Correct
An antivirus scan is appropriate if malware is suspected, but slowness is often caused by too many startup programs, low disk space, or a failing hard drive. The correct first step is to open Task Manager to check CPU, memory, and disk usage.
Malware is a boogeyman for beginners. Any unexplained behaviour is blamed on a virus. This leads them to skip basic diagnostics and waste time on full scans that do not address the actual problem.
Mistake
If Windows Update is stuck, the only solution is to wait for it to finish.
Correct
If the update is stuck for more than a few hours, you should run the Windows Update Troubleshooter, stop the Windows Update service, clear the SoftwareDistribution folder, or use System Restore to undo the update.
Waiting is passive and often futile because the update process may have hung due to corrupt files. Beginners do not know that there are built-in tools to manually reset the update components.
Mistake
The SFC command and CHKDSK command do the same thing.
Correct
SFC (System File Checker) scans and repairs corrupted Windows system files. CHKDSK (Check Disk) scans the file system for errors and checks the physical disk for bad sectors.
Both are command-line tools that seem to 'fix things', so beginners lump them together. Exam questions specifically test the distinction: SFC is for system files, CHKDSK is for the file system and disk hardware.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Write down the exact stop code and search for it in Event Viewer under Windows Logs > System. Look for error events that occurred at the same time as the crash. This will give you more detail. If you need a quick check, boot into Safe Mode to rule out third-party drivers.
Interrupt the boot process three times by pressing and holding the power button during the Windows logo. On the third restart, Windows Recovery Environment (WinRE) will load. From there, go to Troubleshoot > Advanced Options > Startup Settings > Restart, then press 4 for Safe Mode or 5 for Safe Mode with Networking.
SFC (System File Checker) scans and repairs corrupted Windows system files. CHKDSK (Check Disk) scans the file system for logical errors and checks the physical disk for bad sectors. You use SFC when a system file is likely corrupted (e.g., missing DLL errors). You use CHKDSK when you suspect hard drive issues (e.g., slow performance, file corruption).
No. Before running a virus scan, open Task Manager (Ctrl+Shift+Esc) and check the Processes tab. Look for any program using an unusually high percentage of CPU, memory, or disk. This often reveals the real cause, such as a runaway application, too many startup programs, or a failing hard drive.
System Restore might help if the corruption is related to system files that the profile depends on, but it does not directly fix user profiles. For user profile issues, the best solution is to create a new user profile and move the user's data to it.
First, run the Windows Update Troubleshooter from Settings > Update & Security > Troubleshoot. If that doesn't work, stop the Windows Update service, rename the SoftwareDistribution folder (C:\Windows\SoftwareDistribution), and then restart the service. This clears the download cache and forces a fresh download.
This error means the Boot Manager file is corrupt or missing. To fix it, boot from a Windows installation media, go to Repair your computer > Troubleshoot > Advanced Options > Command Prompt. Then run Bootrec /fixmbr, Bootrec /fixboot, and Bootrec /rebuildbcd in sequence.
You've finished Troubleshooting Windows OS Issues. Continue through the 220-1202 study guide to build a complete picture of the exam.
Done with this chapter?