CompTIA 220-1202 software guide covering Windows symptoms, startup failures, app issues, and boot troubleshooting decisions.
Software-troubleshooting questions on Core 2 reward the technician who can isolate whether the break is in the application, profile, startup path, service, update, or operating system, then choose the smallest supported repair.
| The prompt is usually checking whether you can… | Without making this common miss |
|---|---|
| classify the fault correctly | calling every crash an OS rebuild problem |
| choose a reversible repair first | jumping straight to reinstall, reset, or reimage |
| use the right evidence source | ignoring Event Viewer, startup state, or service status |
| separate app-level failure from profile or OS failure | assuming one broken app means the whole machine is broken |
| Topic | What strong answers usually do |
|---|---|
| app failures | test whether the issue follows the app, the user profile, or the machine |
| startup and boot issues | distinguish no boot, no sign-in, unstable startup, and post-update failures |
| update and driver regressions | prefer rollback or uninstall when the timeline clearly points there |
| services and processes | check whether a dependency, startup type, or blocked process explains the symptom |
| recovery chain | use Safe Mode, clean boot, WinRE, System Restore, or repair tools in a defensible order |
Start with 3.1 Windows Symptoms. It teaches the classification step that makes the rest of Core 2 troubleshooting easier.
Then continue with 3.2 Mobile & Browser Issues for the mobile-app and browser-symptom patterns that students often misclassify.
Then use 3.3 Boot, Update & Connectivity for the failure-mode questions where the exact symptom type matters more than the tool name.
Finally use 3.4 Recovery Order when the issue is no longer just classification, but deciding which repair step should come first.
| If the question says… | Strongest first reading |
|---|---|
| only one application fails for one user | app or profile path first |
| many apps or Windows shell fail after a patch | update or OS repair path |
| problem starts immediately after new driver or software install | rollback or uninstall before bigger repair |
| machine boots but is unstable after sign-in | startup item, service, or profile path |
| boot chain is broken | WinRE and targeted startup repair, not routine in-session tools |
| Trap | Better reading |
|---|---|
| reinstalling the app first | test profile, cache, service, permission, and compatibility clues first |
| using System Restore for every symptom | reserve it for a credible system-state rollback case |
| running deep boot repair when the user can sign in normally | stay in the app, service, or profile lane |
| assuming update issues always require full reset | rollback and uninstall often fit better first |