Help Desk to Security

Study guide · Core 2 · Domain 8 · 23% of the Core 2 exam

Software Troubleshooting: the CompTIA A+ objectives in plain English

Domain 8 is the Software Troubleshooting domain of CompTIA A+ Core 2 (220-1202). It covers what to do when the hardware is fine but the software is not: a Windows computer that runs slowly, fails to boot, crashes, or will not update, a computer that shows signs of malware, the ordered procedure for removing that malware, and the matching problems on phones and tablets. At 23 percent of the Core 2 exam, this is one of the largest domains, and it is also the closest match to daily help desk work. Most questions give you a symptom and a little evidence, then ask for the best next step: check simple, reversible causes first.

8.0

What the objectives cover

3.1 Troubleshoot common Windows OS problems

Each Windows symptom points to a first check. Slow performance calls for Task Manager first: look at CPU, memory, and disk use, and review the Startup tab, because too many apps launching at sign in can saturate a healthy machine every morning. Boot failures, where Windows never reaches the sign in screen, point to startup settings, a recent update or driver, or damaged system files. A blue screen is a full system crash with a stop code that hints at the failing driver or component, while a black screen after sign in often means an explorer or display problem rather than a dead computer. Application crashes that repeat in the same program suggest a corrupt install, a bad add in, or a profile problem. A service that fails to start may have a wrong sign in account or a missing dependency. Update problems include updates that fail with an error code, loop on restart, or stall on a progress screen. A corrupt user profile shows up as a temporary profile at sign in, or missing files and settings. The tools match the symptom. Safe Mode starts Windows with minimal drivers and services, so if the problem disappears there, a driver or startup item is likely at fault. The Windows Recovery Environment, or WinRE, is the repair menu you reach when Windows will not boot normally. It holds Startup Repair, which fixes common boot problems automatically, and System Restore, which returns system files and settings to an earlier restore point without touching personal files. Event Viewer records errors by time and source. Reliability Monitor shows a timeline of crashes, failed updates, and installs. From an elevated command prompt, sfc scans protected system files and replaces corrupt copies, and DISM repairs the Windows component store that sfc depends on, so DISM is the deeper repair when sfc cannot fix what it finds.

3.2 Troubleshoot common personal computer security issues

Security problems often look like ordinary annoyances at first, so this objective is about recognizing symptoms as a pattern. Malware symptoms include a computer that suddenly runs slowly, disk activity with no user task running, new toolbars or programs nobody installed, changed home pages or search engines, and security software that will not open or update. Constant pop ups, especially ones that appear when no browser is open, point to adware or a malicious notification permission. Browser redirection, where searches or links land on unfamiliar sites, suggests a hijacked browser setting, a rogue extension, or changed DNS settings. Fake security alerts are a classic social engineering trick: a loud warning page claims the computer is infected and urges the user to call a phone number or install a cleaner, and the alert itself is the scam. Unauthorized software appears when users install free utilities or file sharing tools that bundle extra programs that collect data or open the machine to attack. Certificate warnings need care rather than reflexes. A warning that a certificate is expired, mismatched, or untrusted can mean a harmless site error, a wrong system date and time, or a real attempt to intercept traffic. Teach users to stop and report it instead of clicking through.

3.3 Use best practice procedures for malware removal

Malware removal follows a set order on the exam, and the order protects the network. First, investigate and verify malware symptoms: confirm what the user saw, check running processes and installed programs, and decide whether the behavior is really malware or a bad update or a broken application. Second, quarantine the infected system by disconnecting it from the network, so the malware cannot spread or send data out while you work. Third, disable System Restore in Windows, because restore points can hold copies of the infected files, and a later restore could bring the malware back. Fourth, remediate the infected system: run updated antivirus and antimalware scans, use Safe Mode or a bootable scanner when the malware resists removal, and uninstall the malicious software. Fifth, schedule scans and run updates, setting regular antivirus scans and confirming that definitions and the operating system are fully patched. Sixth, enable System Restore and create a restore point, now that the system is clean. Seventh, educate the end user: explain how the infection likely arrived, such as a phishing link, a fake update prompt, or a bundled download, and what to report next time. Education is a real step, not a courtesy, because the same habits will reinfect a cleaned machine.

3.4 Troubleshoot common mobile OS and application issues

Mobile troubleshooting follows the same logic as Windows, with a stronger role for updates and storage. Apps crashing on launch or mid task often trace to a corrupt app cache, an app version that no longer matches the operating system, or too little free storage, so the usual order is force stop the app, clear its cache, update the app, restart the device, and reinstall the app only if the earlier steps fail. Slow performance across the whole device points to low storage, too many apps syncing in the background, or an update still indexing. Connectivity problems need the connection type named first: Wi-Fi, Bluetooth, or cellular data each fail in different ways. Airplane mode left on, a forgotten network, a VPN app, or an exhausted data plan can all look like a dead connection, and toggling the radio or rejoining the network fixes many of them. Update failures usually come from low storage, low battery, or a weak connection, since most devices require Wi-Fi and a set charge level before an update will start. Battery drain questions ask you to find the cause first: check the battery usage screen for the app at the top, look for constant location use or a weak signal, and confirm whether the drain started right after an app install or an update.

3.5 Troubleshoot common mobile OS and application security issues

Mobile security issues come from what an app is allowed to do, not from a broken setting. Excessive permissions are the first check: a flashlight app that asks for contacts, messages, microphone, and precise location is asking for far more than its job needs, and the fix is to deny the extra permissions or remove the app. Location tracking deserves its own review, because apps can record or share location in the background after a user granted the permission once without noticing. Switch apps to approximate location, or to permission only while in use, when full access is not needed. Sideloading means installing an app from outside the official store, by direct file on Android or through alternate stores and profiles. It bypasses store review, so a sideloaded app carries a higher malware risk even when it looks normal. Jailbreaking on Apple devices and rooting on Android devices remove the protections that limit what apps can reach. A jailbroken or rooted device can run unsigned code, often cannot update cleanly, and is a poor candidate for work data, so many organizations block such devices. Fake apps copy the name, icon, and screenshots of a popular app to trick users into installing a copy that serves ads or steals sign ins. Check the developer name, download counts, and whether the link came from the real vendor site.

EX

Worked example

Domain 8: Software TroubleshootingTroubleshoot slow Windows performance8-01

A Windows laptop is usable after sign in, but opening apps takes several minutes during the first half hour of the day. Task Manager shows high disk and CPU use, and the Startup tab lists several nonessential chat, gaming, and updater apps set to launch at sign in. What is the best first step?

Correct answer: A. Disable the nonessential startup apps, restart the laptop, and compare performance

Too many startup apps can saturate disk and CPU right after sign in. Disabling nonessential startup items is a reversible first step, and a restart shows whether performance improves.

Why the other options are wrong

AZ

Acronyms and terms in this domain

TermWhat it means
BSODBlue Screen of Death, a full Windows crash screen showing a stop code
WinREWindows Recovery Environment, the repair menu used when Windows will not boot
SFCSystem File Checker, the tool that scans and replaces corrupt protected system files
DISMDeployment Image Servicing and Management, the tool that repairs the Windows component store
Restore pointA saved snapshot of system files and settings that System Restore can return to
QuarantineIsolating an infected system or file so it cannot spread or send data
SideloadingInstalling a mobile app from outside the official app store, bypassing store review
RootingRemoving Android system restrictions to gain full control, which also removes built in protections
Safe ModeA Windows startup mode that loads minimal drivers and services for troubleshooting
Reliability MonitorA Windows timeline of crashes, installs, and update results
HD

Where the help desk meets this domain

You meet this domain in the most common tickets on the board. A user says the computer is slow every morning, and you open Task Manager, find chat and updater apps launching at sign in, disable the ones the job does not need, and ask the user to compare the next morning. A laptop that blue screens twice a week becomes a Reliability Monitor exercise: the timeline shows the crashes started the day a driver updated, so you roll that driver back instead of guessing at hardware. A profile that loads as temporary, a service that will not start after a password change, an update that fails on the same error code for a week, each is objective 3.1 with a person waiting. The winning habit is the one the exam rewards: gather the log or timeline first, and try the reversible fix.

The security and mobile objectives arrive just as often. A user forwards a loud warning that claims their computer is locked and gives a phone number to call, and your job is to recognize a fake security alert, keep them from calling, close the page safely, and scan the machine. A browser that keeps landing on strange search pages leads you to rogue extensions and bundled software, and a cleaned machine leads to the last malware removal step, a short explanation of how it got in. Phones bring the mobile half: an app that crashes after an update, a battery that dies by noon because one app holds location all day, a tablet that will not update until storage is freed. None of these tickets uses the exam vocabulary, but all of them test the same judgment.

!

Traps to watch for

The malware removal order is the most tested trap in this domain, because the wrong choices usually list the right steps in the wrong sequence. Quarantine comes before remediation, not after a first scan on the network, because a connected infected machine can spread or leak data while you work. System Restore is disabled before cleaning and enabled again only after the system is clean, with a fresh restore point created at that later step. A choice that creates a restore point before remediation, or skips quarantine, will be wrong even if every tool it names is legitimate. Education of the end user is the final step, so any sequence that ends at scanning or patching is incomplete. When a question asks for the next step, find where you are in the sequence from the stem, then pick the step that follows it.

A second set of traps swaps similar tools. Safe Mode, System Restore, Startup Repair, and WinRE are related but not interchangeable: WinRE is the environment, Startup Repair fixes boot problems inside it, System Restore rolls settings back to a point in time, and Safe Mode is a minimal way to start Windows for diagnosis. SFC and DISM have an order too, since SFC relies on the component store that DISM repairs, so a failed SFC repair points to DISM rather than to a reinstall. Blue and black screens test different instincts: a blue screen gives you a stop code to research, while a black screen after sign in points first to display or profile causes. On mobile questions, watch for choices that jump to a factory reset before cache, updates, permissions, and battery usage were checked. The exam favors the least disruptive step that matches the evidence.

Now try it. The 3 free sample questions for this domain are in practice mode, with full explanations.

Practice Domain 8 questions
All trainingsDomain 9 guide