Chương 3 / 422% của kỳ thi
Software Troubleshooting
Software problems range from a single app that will not launch to a system-wide malware infection. Effective troubleshooting follows a methodical approach: gather symptoms, form a likely hypothesis, test the smallest change first, and verify the fix. This chapter covers diagnosing operating-system failures, application and mobile issues, and the structured process for removing malware safely.
Operating System Issues
When Windows will not boot or behaves erratically, targeted recovery tools help isolate the cause without unnecessary destruction. Safe Mode, System Restore, and firmware checks let a technician narrow the problem to a driver, update, or setting. Starting with the least invasive step preserves data and time.
Use Safe Mode to load minimal drivers
Safe Mode starts Windows with minimal drivers and services, helping determine whether a third-party driver or startup item causes a black screen or crash.
Roll back with System Restore
System Restore reverts system files, drivers, and registry settings to an earlier point while leaving personal files intact.
Check boot order first
For a 'no boot device found' message, verify the firmware boot order and that the drive is detected before assuming corruption.
Target recent changes
When problems start after a driver install or update, roll back that specific change and retest to confirm the cause.
Application Issues
Applications may crash silently, freeze on certain files, or fail after an update. Logs and simple isolation tests reveal the cause faster than guessing. A technician reads the evidence before making broad changes.
Read Event Viewer logs
Event Viewer records application and system errors with timestamps and error codes, revealing the cause of a silent or recurring crash.
Isolate the trigger
If only one large file causes a freeze, test whether that file is corrupt or exceeds available memory before assuming a general fault.
Test the update hypothesis
When an app breaks after a Windows update, uninstall the update or use System Restore and retest to isolate the cause.
Free space for updates
Update failures with low-disk warnings are resolved by freeing storage with Disk Cleanup or removing unneeded files.
Mobile Software Issues
Mobile devices show software problems as crashing apps, battery drain, overheating, or data spikes. Because a factory reset is disruptive, technicians work from least to most drastic. Reviewing per-app usage often pinpoints the culprit quickly.
Clear cache before reinstalling
For a crashing app, force stop it, clear its cache, then update or reinstall before considering a factory reset.
Find battery-draining apps
Fast drain and heat while idle often trace to a misbehaving background app found in battery usage statistics.
Investigate data spikes
An unexplained data-usage spike with unfamiliar apps warrants checking per-app usage, removing unknown apps, and scanning for malware.
Remove sideloaded threats
Excessive ads or unexpected charges after sideloading call for uninstalling the app, scanning, and reviewing permissions.
Security-Related Symptoms
Certain symptoms strongly suggest a security compromise rather than a simple bug. Browser redirects, disabled antivirus, and ransom notes each point to specific threats. Recognizing these signs directs the technician to the correct response.
Recognize browser hijacking
Constant redirects and unfamiliar toolbars indicate a browser hijacker or adware infection, not a hardware fault.
Spot active malware
Pop-ups with no browser open and a mysteriously disabled antivirus strongly indicate a malware infection defending itself.
Identify ransomware
Files with strange extensions plus a payment demand indicate ransomware; recover from clean backups rather than paying.
Investigate high CPU processes
An unknown process at near 100% CPU should be researched, ended, and followed by a malware scan before hardware changes.
The Malware Remediation Process
Removing malware effectively follows an ordered process that contains the threat, cleans it, and prevents reinfection. Skipping steps such as isolation or leaving infected restore points can undo the work. A disciplined sequence produces a genuinely clean system.
Quarantine the system
Disconnect the infected machine from the network to stop the malware from spreading or contacting command-and-control servers.
Disable System Restore during cleanup
Turn off System Restore so infected restore points are purged, preventing reinfection from a saved snapshot.
Scan and remediate
Update and run anti-malware tools to identify and remove the infection before verifying the system is clean.
Re-enable protection after cleaning
Once the system is verified clean, re-enable System Restore and create a fresh known-good restore point.
Kiểm tra kiến thức của bạn
Câu hỏi luyện tập về Software Troubleshooting