Study CompTIA 220-1202 Service, Update, and Recovery Order: key concepts, common traps, and exam decision cues.
Many Core 2 troubleshooting misses happen because the candidate picks the right broad topic but the wrong order. This lesson is about sequencing: service check, update rollback, Safe Mode, repair, restore, reset, or reimage.
Rollback: Reversing a recent driver, patch, or change that is the likely cause of the new problem.
Reimage: Rebuilding the system from a known image, a much more disruptive action than targeted rollback or repair.
The exam usually wants you to:
| If the prompt says… | Strongest first move |
|---|---|
| issue started right after a driver or feature update | rollback or uninstall update before broader recovery |
| one service does not start but Windows still runs | service state, dependency, and logs before OS rebuild |
| system files may be damaged | targeted repair tools before reset |
| only one app or profile is affected | stay narrow and avoid full OS recovery |
| mobile app or OS update fails | check storage, compatibility, source, connectivity, and OS state before device wipe |
flowchart LR
A["Classify app, service, update, or system issue"] --> B["Use the narrowest fix that fits"]
B --> C["Rollback or targeted repair if recent change exists"]
C --> D["Safe Mode, restore, or WinRE if normal path is blocked"]
D --> E["Reset, reimage, or wipe only when smaller fixes are no longer enough"]
| Symptom | Better reading |
|---|---|
| service fails after a recent change | dependency, permissions, service startup mode, or the change itself |
| OS update failure with no other compromise clues | update path, storage, support, or policy first |
| OS update failure with fake warnings, altered files, or redirects | possible security issue, not just patching trouble |
| mobile update fails on low storage or unstable network | narrower mobile support path before full reset |
| Trap | Better reading |
|---|---|
| using reimage or factory reset as the first answer | Core 2 usually rewards narrower rollback and repair steps first |
| treating a single failed service as total OS collapse | stay in the service lane if the rest of the system is alive |
| restoring the whole OS for one broken user profile | contain the fix to the profile or app if the clue allows it |
| wiping a mobile device before checking app source, storage, or connectivity | keep mobile recovery proportional to the evidence |
A Windows system becomes unstable after a patch, but the user can still reach Safe Mode and recent logs show one service failing at startup. Which answer best fits Core 2?
Correct answer: B. The evidence still supports a narrower recovery path. Core 2 usually wants rollback and targeted service investigation before reimage.