Software troubleshooting

Almost every question in this domain hands you a symptom and asks what the technician should do first or next, so the answer is the least-destructive action the symptom justifies, not the boldest repair. Each of this domain's four objectives opens "Given a scenario, troubleshoot common ... issues" (220-1202 exam objectives), which is the symptom-to-cause-to-fix discipline stated four times over. The A+ troubleshooting method is the job-role habit that carries it, six steps in a settled working order: identify the problem, establish a theory of probable cause, test the theory, establish a plan of action and implement it, verify full functionality and add prevention, then document the findings. Two habits inside the early steps matter on their own: back up the user's data before you change anything, and when a machine shows several faults, work each one separately. The classic wrong answer is jumping to the top of the ladder, reimaging or factory-resetting before you have even reproduced the fault. Software troubleshooting is 23 percent of the 220-1202 exam (published domain weights), and it rewards this discipline over any single command.

Read this page as a map, then follow the three subtopics in order, each owning a different class of symptom. OS & Application Troubleshooting carries the desktop core: Windows that will not boot, a BSOD (blue screen of death), a corrupt user profile, and applications that will not install, open, or stay running, among other Windows OS and application faults, with the Windows Recovery Environment (WinRE) as the single door to every offline repair. Mobile Troubleshooting moves the same discipline onto phones and tablets, where the symptoms are their own (fast battery drain, one dead radio, overheating, a stalled app update, signs of mobile malware, plus the connectivity, permission, storage, and device-management faults that go with them) and remediation climbs an escalation ladder, an analogy rather than CompTIA wording, that tops out at a factory reset. Security Issue Remediation handles the compromised workstation: a hijacked browser, a fake security warning (scareware), a rogue process, or security tools switched off, among other signs of compromise, where the skill is reading the symptom and matching it to its specific fix. Each list here samples what its subtopic covers rather than bounding it. The through-line is one method applied three times, and the routing rule is to name the platform first: a phone or tablet stays with Mobile Troubleshooting even when the fault is a compromise, while a compromised PC belongs to Security Issue Remediation.

Across all three subtopics the exam rewards the same instinct: start with the least invasive, most reversible action that could clear the symptom, and climb only if it fails. On a PC a reboot or a service restart sits below Safe Mode and a driver rollback, which sit below System Restore and targeted repairs such as sfc or chkdsk, which sit below Reset this PC or a full reimage. On a phone a force-stop sits below clearing an app's data, which sits below a factory reset. The partner rule is to size the fix to the symptom's scope: one rogue browser extension earns a browser reset and a pop-up blocker, not a wipe. Reading the symptom before you act is what keeps you from both under-reacting to a real infection and over-reacting to a cosmetic one.