A+ Core 2 Software Troubleshooting: Symptoms, Causes, First Steps

What does A+ Software Troubleshooting cover?

Software Troubleshooting is domain 3 of Core 2 and carries 23% of the 220-1202 blueprint, behind Operating Systems and Security at 28% each and ahead of Operational Procedures at 21%. All four of its objectives begin "Given a scenario, troubleshoot common." They were checked in CompTIA's 220-1202 objectives document, version 3.0, on November 6, 2026:

The document lists symptoms and stops there. It names no remedy for any of them, and CompTIA notes that its bulleted lists are not exhaustive. So the fixes on this page come from two places. Where a vendor's support page states the steps, the vendor is named. Everywhere else, the first step is the working habit from the troubleshooting methodology guide: find out what changed, test the cheapest theory first, and change one thing at a time. Most of the tools named below are ones 220-1202 lists in objectives 1.4 (Windows tools), 1.5 (command line), and 1.6 (Windows settings).

Windows symptoms (3.1): likely cause and first step

Rows without a named vendor are theories to test, not rules. A clock that is wrong again after every power-off is a different symptom: the Core 1 objectives treat it as hardware, and the hardware and network troubleshooting guide covers it with the "bootable device not found" checks.

Microsoft's order for a repeating stop error. Microsoft says that in most cases the restart resolves the problem and no further action is needed. If Windows restarts frequently with the same stop code, its basic steps run in this order: remove any new hardware, start the PC in safe mode, check Device Manager for devices marked with an exclamation point and update, disable, or uninstall them, check for sufficient free space on the drive (Microsoft suggests keeping 10% to 15% free), install the latest Windows updates, and only then restore Windows from a restore point or another recovery option. The order moves from the least disruptive step to the most disruptive one. An answer that reinstalls Windows before anyone has asked about new hardware is usually too early.

System files. Microsoft's repair guidance says to run DISM before the System File Checker, then sfc /scannow, which scans all protected system files and replaces corrupted files with a cached copy. If SFC reports that it could not perform the requested operation, Microsoft's next step is to run the scan in safe mode. The Windows command-line guide covers sfc and chkdsk and when each one fits, and the Windows tools and settings guide covers the consoles in the table.

This domain has 167 Software Troubleshooting questions in full A+ prep, each with an explanation, so you can practice choosing the first step for symptoms like these.

Mobile OS and app symptoms (3.2): what to try, in what order

Apple's page for an app that stops responding, closes unexpectedly, or will not open gives the steps in a set order: close and reopen the app, restart the device, check for an app update and then an OS update, and last, delete the app and redownload it. Apple warns that deleting an app might lose data that was stored in it, which is why it comes last. The reasoning is the same as on Windows. When a stem asks what to do first about one misbehaving app, start with the step that costs the user nothing, not a factory reset.

Setting up these radios, pairing, and sync is Core 1 material in the Mobile Devices guide. Core 2 picks up when they stop working.

Mobile security symptoms (3.3): ordinary fault or malicious app?

Objective 3.3 has two lists. The first is security concerns, the conditions that make a malicious app more likely:

• Application source and unofficial application stores. Google says Play Protect runs a safety check on apps from the Google Play Store before you download them, and checks the device for potentially harmful apps from other sources. An app installed from a link in a message did not come through the store's check.
• Developer mode. A setting meant for building and testing software. On a user's phone, ask why it is on.
• Root access or jailbreak. Apple says jailbreaking bypasses security features and can cause security vulnerabilities, instability, shortened battery life, unreliable voice and data, disruption of services, and an inability to apply future software updates.
• Unauthorized or malicious applications, including application spoofing. A spoofed app imitates a legitimate one to get installed and trusted.

The second list is symptoms. Several also have an ordinary explanation, so the scenario's details decide.

On Android, Google says Play Protect is on by default but can be turned off, and that when it finds a potentially harmful app it might send a notification, disable the app until you uninstall it, or remove the app automatically. In a scenario, checking that Play Protect is still on is a reasonable early step. Preventive controls such as screen locks, OS and application updates, remote wipe, and MDM policy belong to objective 2.8, mapped in the Core 2 security guide.

When two answers both look defensible on questions like these, the explanation matters more than the score. In full A+ prep, AI Rescue can explain why the choice you made was wrong and put the idea in simpler terms.

PC security symptoms (3.4): what each one suggests

Microsoft's guidance on tech support scams gives a fact worth memorizing: real error messages from Microsoft never include a phone number to call. A full-screen warning with a number is the false alert the objective describes. On ransomware, Microsoft relays the FBI's recommendation not to pay, because payment does not guarantee the data comes back.

Once malware is the confirmed explanation, the procedure is no longer a judgment call. Objective 2.6 gives ten steps in a fixed order, and the malware removal steps guide explains each one. The browser settings that prevent many of these symptoms, such as the pop-up blocker and extensions from trusted sources, are objective 2.11.

The four symptom lists are short enough to memorize, and the 69 Software Troubleshooting flashcards in full A+ prep are sorted into this domain for that kind of recall.

Three scenarios, worked from symptom to first step

These are original and simplified. Cover the answer and decide the first step.

1. Blue screens after a new webcam. A Windows 11 PC has shown a stop error three times since Tuesday, always when it wakes from sleep. The user plugged in a new webcam on Monday. First step: record the stop code and unplug the webcam, since new hardware is the first item in Microsoft's order. If the errors stop, look in Device Manager for the webcam's driver. Restoring Windows is the last step in that order, not the first.

2. A phone that burns through its data plan. An Android phone reaches its data limit in ten days and shows full-screen ads on the home screen. Last week the user installed a "battery saver" from a link in a text message. First step: remove that app, then confirm Play Protect is turned on. The app came from outside the official store, and a high number of ads is on the 3.3 symptom list. A factory reset would also remove it, but it erases the user's data and comes much later. Compare this with a phone whose data ran out after photo backup was turned on: same notification, ordinary cause, and the fix is to limit that sync to Wi-Fi.

3. A warning that fills the browser. A user reports a full-screen message saying the PC is infected, with a phone number and a loud alarm. The mouse will not close it. First step: do not call the number. Close the browser with Alt+F4, or restart the PC if that fails. Then check whether anything was installed or whether anyone was given remote access. If so, the ten malware removal steps apply, ending with educating the user about what the fake alert looked like.

How should you practice Software Troubleshooting?

Cover the "First step" column in each table and answer from the symptom alone, then explain why the more drastic choice is wrong. On a Windows PC you are allowed to change, open Event Viewer, Task Manager's Services tab, and the date and time settings so the names in the tables match something you have seen. On your own phone, find the storage screen and the rotation lock.

The free A+ practice questions include ten Core 2 scenarios for a quick check, and the free A+ study plan can focus on Core 2 with this domain at its official weight. If your accuracy here stays lower than in the other Core 2 domains, Weak Spot in full A+ prep drills your lowest domain five questions at a time. The rest of the A+ library is in the A+ guides hub.