Core 2 · 23% exam weight

Software Troubleshooting: a practical CompTIA A+ guide

Application failures, browser behavior, malware symptoms, and OS instability. Learn the mental models, common failure modes, and evidence-based troubleshooting steps.

220-1202V15 objectives4 deep-dive sections
How to use this guide: Read one section, explain the concept in your own words, then walk through each support case without looking at the suggested diagnostic path. A strong tech tests a hypothesis before replacing parts.

01. Start with change and scope

Ask when the failure began, whether other users or devices are affected, and what changed. If one app fails after an update, isolate that app and its dependencies before blaming network hardware. If every app fails, consider shared resources, OS components, storage or malware.

02. Browser and connectivity errors

A site that fails only in a normal browser profile but loads in a private window suggests an extension, cache, cookies, or profile settings. A hostname failure with working direct-IP connections points toward DNS. Certificate warnings require careful clock, certificate-chain and interception checks; do not teach users to bypass warnings.

03. Recover safely

Use logs, documented rollback paths, compatibility checks, known-good test users, and Safe Mode when needed. Blue screens shortly after a driver update can justify driver rollback; repeated storage errors justify backup and disk-health review. Reinstall only when lower-risk methods fail and data has been protected.

04. Malware symptoms and response

Unexpected redirects, fake alerts, browser extensions and disabled security controls may indicate potentially unwanted software or malware. Follow incident handling and approved scans; preserve evidence. A suspicious symptom is evidence to investigate, not proof of a specific infection.

Apply the lesson: real support cases

Support case 1

A browser extension update coincides with redirects; private mode works. Disable suspect extensions and verify before reinstalling the OS.

Support case 2

One employee’s line-of-business app stops after a patch while colleagues remain unaffected. Compare client version, event logs and per-user configuration.

Exam-day decision rule: Use “what changed?” and “who else?” before choosing a repair.
Practice this material →

These are original explanatory notes aligned to the named exam domains; review the current official objectives for exact scope. The mock exam is practice only and is not scored on CompTIA's scale.