CompTIA 220-1202 operating systems guide covering Windows features, file systems, accounts, and recovery decisions.
Core 2 operating-systems questions are rarely about memorizing a command in isolation. They are usually about identifying the right Windows boundary first: edition, tool, startup state, profile state, disk state, or recovery path.
| The prompt is usually checking whether you can… | Without making this common miss |
|---|---|
| choose the right Windows tool for the symptom | jumping straight to reset or reinstall |
| separate edition limits from misconfiguration | assuming every Windows feature exists on every edition |
| distinguish startup failure from profile or app failure | treating every login problem like a boot problem |
| pick the least disruptive recovery path | using WinRE or Reset this PC too early |
| Topic | What strong answers usually do |
|---|---|
| editions and feature fit | keep BitLocker, Group Policy, Hyper-V, and RDP host boundaries straight |
| admin tools | choose the tool that matches the layer: Event Viewer, Services, Task Manager, Disk Management, Device Manager, Settings, or Control Panel |
| accounts and profiles | separate local account, Microsoft account, domain account, and damaged user profile behavior |
| filesystems and storage | recognize where NTFS behavior, encryption, compression, quotas, and permissions matter |
| recovery tools | use Safe Mode, WinRE, rollback, restore, repair, then reset in that order unless the prompt forces something broader |
Start with 1.1 Windows Recovery. It covers the Windows-first support decisions that create most of the real separation on Core 2.
Then continue with 1.2 Apps & Cloud Tools for the deployment and non-Windows support boundaries that CompTIA still expects.
Then use 1.3 Filesystems & Accounts when the issue is really about mapped drives, VPN paths, domain join behavior, filesystems, or Windows client settings.
Finally use 1.4 Settings & Sharing for the control-panel and Settings decisions that look small on the exam but still decide the right answer.
| If the question says… | Strongest first reading |
|---|---|
| user signs in but only that profile is broken | profile or app issue, not full OS failure |
| system will not boot after update or driver change | Safe Mode or WinRE, then rollback or uninstall |
| Windows files look corrupted | DISM plus sfc, not random registry edits |
| feature is missing on one machine but present on another | edition, license, or policy boundary |
| disk or partition issue blocks startup or access | Disk Management, filesystem, BitLocker, or WinRE command tools |
| Trap | Better reading |
|---|---|
using Reset this PC as the first fix |
start with rollback, repair, restore, or Safe Mode if the stem still allows a reversible path |
| treating any login issue as a domain issue | check whether the failure is local profile, credentials, domain reachability, or policy |
| confusing feature availability with configuration failure | confirm edition fit before changing settings that may not exist |
| memorizing tools without layer awareness | ask whether the problem is process, service, startup, storage, driver, or profile |
DISM and sfc.