CompTIA A+ Core 2 220-1202Domain 3 Original Course Notes
3.0 Software Troubleshooting
Concise printable notes for Core 2 software troubleshooting objectives: Windows OS symptoms, mobile OS and app issues, mobile security and app behavior, and PC security issues. Use these notes to connect scenario clues to the safest, least disruptive troubleshooting path.

How to use these notes: Read every symptom as evidence. Ask what changed, determine scope, start with low-risk fixes, protect user data, and verify the original workflow before moving to more disruptive repair steps.
Troubleshooting Pattern
Identify the symptom, determine scope, check recent changes, apply the least disruptive fix, test the original workflow, and document the result.
Identify the symptom, determine scope, check recent changes, apply the least disruptive fix, test the original workflow, and document the result.
Security Pattern
Verify the source, avoid scareware clicks, use trusted tools, protect data, restore safely, and escalate when trust cannot be reestablished.
Verify the source, avoid scareware clicks, use trusted tools, protect data, restore safely, and escalate when trust cannot be reestablished.
Notes:
3.1 Windows OS IssuesCore 2 Domain 3
3.1 - Troubleshoot Windows OS Issues
Start with the symptom
- Windows symptoms often overlap, so gather evidence before choosing a fix.
- Common clues include BSOD, degraded performance, boot issues, shutdowns, services not starting, app crashes, low memory, USB warnings, instability, missing OS, slow profile loading, and time drift.
- Use recent changes, Event Viewer, Task Manager, Device Manager, startup settings, logs, and update history to narrow the cause.
Stability and Startup
- BSODs often point to drivers, hardware, memory, storage, firmware, or system corruption.
- Boot issues can involve boot order, boot records, missing system files, failed updates, disk errors, or external devices.
- Frequent shutdowns may indicate overheating, power problems, failing hardware, malware, or OS protection behavior.
Performance and Memory
- Slow performance can come from startup apps, low RAM, disk pressure, malware, updates, drivers, or resource-heavy processes.
- Low memory warnings require checking RAM usage, running apps, page file behavior, startup items, and whether an app has a memory leak.
- Use Task Manager and Resource Monitor before reinstalling software or replacing hardware.
Apps, Services, Devices
- Apps can crash because of bugs, compatibility, corrupted files, permissions, missing dependencies, or bad updates.
- Services may fail due to disabled startup type, dependency failure, account/password issues, corruption, or policy.
- USB warnings may point to driver issues, power limits, cable/port problems, or controller problems.
Scenario pattern: Do not reinstall first. Prove whether the issue is hardware, driver, update, app, service, profile, storage, or system-file related.
Notes:
3.1 Windows Tools and CluesCore 2 Domain 3
3.1 - Windows Troubleshooting Tools
Choose tools based on evidence
- Task Manager shows processes, startup apps, CPU, memory, disk, network, and user sessions.
- Event Viewer helps identify recurring service, driver, application, update, and shutdown errors.
- Device Manager shows hardware status, drivers, disabled devices, and USB/controller warnings.
- Recovery tools help when Windows will not boot or system files are damaged.
Common Repairs
- Restart to clear temporary states when appropriate.
- Update, roll back, reinstall, or disable drivers based on timing and evidence.
- Use System Restore, Startup Repair, Safe Mode, SFC, DISM, or recovery media when the scenario points there.
- Check disk health and file-system errors when storage symptoms appear.
Profiles and Time
- Slow profile loading may involve roaming profiles, network paths, corrupted profiles, logon scripts, group policy, or storage delays.
- Time drift can affect authentication, certificates, updates, and domain access.
- Check time zone, time service, CMOS battery, NTP settings, and domain synchronization.
Verification
- After each change, test the original symptom instead of assuming success.
- Document what was changed, what evidence supported it, and whether the issue returned after reboot.
| Symptom | Likely Evidence | First Places to Check |
|---|---|---|
| BSOD | Stop code, recent driver, dump/log | Event Viewer, drivers, RAM, storage |
| Slow PC | High CPU/RAM/disk | Task Manager, startup, malware scan |
| Service fails | Error code, dependency, account | Services console, Event Viewer |
| Missing OS | Boot error | Boot order, drive health, recovery tools |
Notes:
3.2 Mobile OS and App IssuesCore 2 Domain 3
3.2 - Troubleshoot Mobile OS and Application Issues
Scope app versus device
- Determine whether one app, many apps, or the whole device is affected.
- Common app symptoms include failure to launch, freezing, crashing, hanging, slow response, update failure, install failure, cache problems, and app or server problems.
- Common device symptoms include OS update failure, battery drain, random reboots, connectivity issues, and autorotate failure.
App Won't Launch or Crashes
- Force close and reopen the app, restart the device, update the app, and check storage/network conditions.
- Reinstall only after protecting local or unsynced data.
- Check compatibility, permissions, server status, and whether other users have the same issue.
Update and Install Problems
- Failed updates can involve storage, network quality, app store cache, account state, payment requirements, restrictions, or server problems.
- Failed installs can involve compatibility, MDM restrictions, insufficient storage, untrusted sources, or blocked app stores.
- Use official app stores and approved catalogs.
Performance and Resources
- Slow apps may be affected by CPU, memory, storage, cache, background apps, weak networks, outdated versions, or server issues.
- Clear cache carefully, close unused apps, restart, update, and test on another network when needed.
Scenario pattern: Start with low-risk actions: close, restart, update, check storage, check network, verify permissions, then reinstall or reset only when needed.
Notes:
3.2 Mobile Device SymptomsCore 2 Domain 3
3.2 - Mobile Device Symptom Matching
Use settings and reports
- Mobile troubleshooting uses built-in reports: battery usage, storage, data usage, app permissions, network settings, and OS update status.
- Ask what changed: app update, OS update, new accessory, new network, new case, physical damage, or account change.
Battery and Reboots
- Battery drain can come from weak cellular signal, aging battery, Wi-Fi/Bluetooth/GPS/NFC, background apps, high-use apps, or heat.
- Random reboots may be normal occasionally, but repeated reboots require checking updates, battery health, overheating, hardware damage, and crash logs.
Connectivity and Sensors
- Wi-Fi, Bluetooth, NFC, and cellular issues can involve disabled radios, range, credentials, compatibility, pairing, carrier issues, VPN/proxy/DNS, or hardware faults.
- Autorotate problems can involve rotation lock, app support, sensor issues, or the need to restart the app/device.
OS Updates
- Mobile OS updates need storage, power, compatible hardware, stable network access, and update-server availability.
- Try a reliable network, free storage, restart, verify restrictions, and retry later if servers are busy.
| Symptom | Likely Check | Least Disruptive Step |
|---|---|---|
| Battery drains fast | Battery usage, signal, background apps | Disable unneeded radios/apps |
| No Bluetooth | Pairing mode, saved device, restart | Forget and re-pair |
| NFC not working | NFC enabled, compatibility | Verify setting/device support |
| Autorotate stuck | Rotation lock, app support | Disable lock/restart app |
Notes:
3.3 Mobile Security IssuesCore 2 Domain 3
3.3 - Troubleshoot Mobile Security and App Behavior
Trust starts with the source
- Unofficial app stores, sideloaded APKs, unknown links, fake update prompts, and third-party downloads increase risk.
- Developer Mode, USB debugging, root access, jailbreak status, and custom firmware change the security posture of the device.
- Managed devices must follow approved app lists and MDM policy.
Suspicious Apps
- Malicious or spoofed apps may imitate legitimate apps while requesting excessive permissions.
- Review developer identity, source, reviews, install history, permissions, behavior, and recent changes.
- Remove suspicious apps and reinstall only from official stores or approved catalogs.
Behavior Clues
- High network traffic, high battery usage, slow response, ads, redirects, fake security warnings, missing features, and unexpected app behavior may indicate unwanted software.
- Use built-in data and battery reports before making destructive changes.
- Run trusted mobile security scans when activity is unexplained.
Data Exposure
- Leaked files or data require checking both the device and connected cloud accounts.
- Review recent sign-ins, connected devices, sharing settings, recovery options, saved passwords, and account activity.
- Change exposed passwords from a trusted device and enable MFA where possible.
Scenario pattern: Source plus permissions plus behavior equals trust level. If any part is suspicious, investigate before trusting the app or device.
Notes:
3.3 Mobile Security ResponseCore 2 Domain 3
3.3 - Mobile Security Response Workflow
Protect device, data, and accounts
- Do not install apps from pop-ups, texts, unknown websites, or fake warnings.
- Remove suspicious apps, revoke risky permissions, update OS/apps, and scan with trusted tools.
- Factory reset is appropriate when the device cannot be trusted, but protect data first when safe.
Common Matches
- APK or unofficial store: verify source, remove risk, disable unknown-source settings.
- Developer Mode unexpected: check USB debugging, trusted computers, recent installs.
- Rooted/jailbroken: restore official software or block managed access according to policy.
- Fake warning: close it, verify through trusted settings, scan if clicked.
Connectivity and Usage
- No internet may be Wi-Fi, cellular, VPN, proxy, DNS, carrier, account, SIM, OS bug, or malware.
- High data use may be normal sync or a malicious background process.
- Compare one app, all apps, one device, and other users to scope the problem.
Verify and Document
- After removal, confirm ads, warnings, data spikes, redirects, or app behavior stopped.
- Document app source, permissions, actions taken, accounts reviewed, and remaining risk.
| Clue | Think | Action |
|---|---|---|
| Fake cleaner prompt | Scareware | Do not install; verify through settings |
| Simple app uses lots of data | Suspicious background activity | Review usage, remove, scan |
| Photos leaked | Device and cloud exposure | Clean device, check accounts |
| Root/jailbreak detected | Controls bypassed | Follow policy; restore/re-enroll |
Notes:
3.4 PC Security IssuesCore 2 Domain 3
3.4 - Troubleshoot PC Security Issues
Verify before trusting
- PC security issues often look like regular support problems: slow performance, no network, alerts, pop-ups, blocked updates, redirects, changed files, or browser lag.
- Verify alert source before clicking or installing anything.
- Use trusted tools, official update paths, and known good backups.
Alerts and Scareware
- Desktop alerts may be real security notifications or deceptive browser notifications.
- False antivirus alerts use logos, urgency, fake scans, payment pressure, and professional language.
- Open trusted security tools directly instead of clicking alert buttons.
Files and Updates
- Altered files may be renamed, hidden, encrypted, deleted, inaccessible, or permission-modified.
- Ransomware indicators require protecting data, preserving evidence, and using approved recovery steps.
- OS update failures may involve network access, firewall/filtering/proxy, storage, bandwidth, policy, corrupted components, or malware.
Browser Symptoms
- Browser pop-ups, certificate warnings, redirection, and poor performance require careful isolation.
- Check extensions, notifications, homepage/search, proxy, DNS, VPN, cache/cookies, updates, and malware.
- Try another browser to separate browser-specific issues from system-wide issues.
Scenario pattern: Identify the symptom, verify the source, determine scope, use trusted tools, protect data, restore safely when needed, verify, and document.
Notes:
3.4 PC Security DecisionsCore 2 Domain 3
3.4 - PC Security Decision Points
Know when to restore
- Restoring or rebuilding is not always first, but it may be the safest answer when trust cannot be restored.
- Use a known good backup created before the incident.
- Do not restore infected files or sync damaged files over clean cloud copies.
Certificate Warnings
- Certificate warnings mean website identity cannot be verified.
- Check URL, issued-to name, issuer, expiration date, certificate chain, and system time.
- Do not proceed on sensitive sites when the warning cannot be explained.
Browser Redirection
- Redirection means the user tries to visit one site but lands somewhere else.
- Review extensions, homepage, search provider, site permissions, proxy, DNS, hosts file, startup apps, and scheduled tasks.
- Persistent redirects after cleanup may require restore or rebuild.
Browser Performance
- Slow browsers can be caused by outdated versions, many tabs, cache/cookies, extensions, resource pressure, malware, or network issues.
- Use Task Manager for CPU, RAM, disk, GPU, and network evidence.
- Clear cache and cookies carefully because cookies may sign users out.
| Symptom | Do First | Escalate When |
|---|---|---|
| Fake alert | Close, verify source, scan | User installed/clicked or threats persist |
| Certificate warning | Check URL/details/time | Mismatch persists on sensitive site |
| Redirects | Check browser and DNS/proxy | Returns after trusted cleanup |
| Altered files | Protect data/evidence | Ransomware or sensitive data involved |
Notes:
Domain 3 Rapid ReviewCore 2 Domain 3
Rapid Review Checklist
3.1 Windows OS Issues
- Match BSOD, boot, shutdown, service, app, memory, USB, instability, profile, and time symptoms to likely causes.
- Use Task Manager, Event Viewer, Device Manager, recovery tools, SFC/DISM, Safe Mode, and update/driver history.
- Start with evidence and least disruptive repairs before reinstalling or replacing hardware.
3.2 Mobile OS and App Issues
- Scope one app, many apps, or whole device.
- Check updates, storage, network, permissions, cache, server status, app compatibility, battery reports, data reports, and sensor/radio settings.
- Protect user data before reinstall, reset, or destructive cleanup.
3.3 Mobile Security and App Behavior
- Verify app source, developer, permissions, install history, Developer Mode, root/jailbreak, custom firmware, and MDM policy.
- Investigate high data, ads, fake warnings, slow response, connectivity failures, unexpected behavior, and leaked data.
- Remove suspicious apps, use trusted scans, check cloud accounts, change passwords, and escalate sensitive exposure.
3.4 PC Security Issues
- Verify alerts, avoid scareware clicks, and use trusted tools.
- Investigate malware impact on network access, updates, files, browsers, DNS/proxy, extensions, and certificates.
- Protect files and backups; restore or rebuild only when necessary and safe.
Exam moves: Identify the symptom, scope the issue, verify the source, apply the least disruptive safe fix, protect data, use trusted tools, verify the original workflow, and document.
Notes:
These notes are an original study aid for the Brotocol Joe Core 2 curriculum.