Troubleshooting Windows & Mobile OS Issues

A+ Core 2 220-1202 · Software Troubleshooting

By Abu Anns · Last updated 20 November 2026Exam version: 220-1202 (V15, current)

Software Troubleshooting is 23% of Core 2, and it is the most concentrated domain on the exam: just four objectives carry nearly a quarter of the marks, and all four are scenario-based. This guide covers the first two — troubleshooting Windows OS issues and mobile OS and application issues. The companion guide covers security-related troubleshooting on mobile and PC.

Windows OS issues

The blue screen of death (BSOD) is Windows' response to a critical error it cannot recover from. The screen shows a stop code that identifies the fault — common causes include faulty drivers, failing RAM, and hardware problems. The first steps are to note the stop code, check Event Viewer for the corresponding error, and consider recent changes (a new driver or update is the usual suspect). Degraded performance has many causes: a full hard drive, too many startup programs, insufficient RAM, a failing drive, or malware. Check Task Manager first to identify whether CPU, memory, disk, or network is the bottleneck. System instability (random freezes and crashes) often points to failing hardware, overheating, or corrupted system files — sfc /scannow checks the latter.

Boot issues include the system not starting at all (check power and hardware first), booting to a black screen, or looping through restarts. Windows Recovery Environment (WinRE) provides startup repair, system restore, and command-line tools for these situations. Frequent shutdowns can be caused by overheating, a failing power supply, or a scheduled task. Services not starting can prevent applications or features from working — check the Services console for the service's status and startup type, and check Event Viewer for the error. Applications crashing on launch can mean a corrupted installation, a missing dependency, or an incompatibility — reinstalling the application or updating it is the usual fix. No OS found means the boot drive is not detected or the boot files are damaged — check the BIOS boot order, the drive connections, and use WinRE's boot repair tools. Low memory warnings mean the system is running out of RAM — close applications, add RAM, or increase the page file. USB controller resource warnings appear when too many USB devices are connected or a USB device is drawing too much power — disconnect devices and use a powered hub.

Mobile OS and application issues

Mobile troubleshooting follows the same logic as desktop troubleshooting: isolate whether the problem is the app, the OS, or the device. Application fails to launch can be caused by a corrupted app installation, insufficient storage, or an OS incompatibility — force-stop the app, clear its cache, or reinstall it. Application fails to close or crashes often means the app has a bug or the device is low on memory — force-stop it and check for updates. Application fails to update is usually a storage, account, or connectivity problem. Application fails to install can mean insufficient storage, an incompatible OS version, or a problem with the app store account. Slow to respond can be caused by too many background apps, low storage, or an aging battery throttling the CPU. OS fails to update is usually a storage, battery, or connectivity problem — updates typically require Wi-Fi, sufficient charge, and free space.

Battery life issues can be caused by a degraded battery, a power-hungry app, or settings such as high screen brightness and always-on location services. Random reboots can indicate a failing battery, a corrupt OS, or a hardware fault. Connectivity issues with Bluetooth, Wi-Fi, or NFC can be caused by settings (airplane mode, disabled radios), a stale network profile, or hardware damage. Screen does not autorotate is usually a settings problem (rotation lock enabled) or a faulty accelerometer sensor. The general mobile troubleshooting sequence is: restart the device, check for updates, check storage and battery, clear the app cache, and as a last resort, reset the device (after backing up).

A troubleshooting habit worth building

For both Windows and mobile issues, the exam rewards the same discipline: identify the symptom precisely, check the simplest and most common causes first, change one thing at a time, and verify the fix. The "best first step" in a scenario question is almost always the least disruptive check that could explain the symptom — restarting an app before reinstalling it, checking Task Manager before replacing hardware, clearing a cache before resetting a device. When a question describes a symptom you have not seen before, work backwards from the component: which part of the system produces this symptom, and what is the simplest thing that could make that part fail?

Windows Recovery Environment and Safe Mode

When Windows will not start normally, the Windows Recovery Environment (WinRE) is the toolkit. WinRE loads automatically after two or three failed boot attempts, or it can be launched from installation media. It offers Startup Repair (automatically fixes boot problems), System Restore (rolls the system back to an earlier restore point), System Image Recovery (restores from a full system image), and a command prompt for manual repairs (including sfc, chkdsk, and diskpart). Safe Mode is a diagnostic startup that loads Windows with only essential drivers and services — if a problem disappears in Safe Mode, the cause is a driver, a startup program, or a service that does not load in Safe Mode, which narrows the search considerably. Safe Mode with Networking adds network drivers, useful when a fix needs to be downloaded. The exam frequently asks which recovery option to use: System Restore for a problem that started after a recent change, Startup Repair for a boot failure, and Safe Mode for isolating a driver or software conflict.

Mobile resets: soft, hard, and factory

Mobile troubleshooting has its own escalation ladder. A soft reset (restarting the phone) clears temporary glitches and is always the first step. A hard reset (forcing a restart with a button combination when the phone is frozen) is the next step when the phone does not respond. A factory reset wipes the phone back to its out-of-the-box state — it is the last resort for persistent software problems, and it must only be done after backing up the user's data. Before a factory reset, the technician should also check whether the phone is enrolled in an MDM solution or protected by an activation lock (Apple ID or Google account), because a reset phone may require the original account credentials to set up again. The exam tests this escalation order: restart, then update, then clear cache or reinstall the app, then factory reset — never jump straight to the reset.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A Windows PC shows a blue screen of death (BSOD) with a stop code shortly after a new graphics driver was installed. What is the most likely cause and the best first step?

Report an error

Q2.A user's Windows PC displays the message "No OS found" on startup. The PC was working normally yesterday. What should the technician check first?

Report an error

Q3.A Windows computer has become very slow over several weeks. Task Manager shows the disk at 100% utilization, and the drive is nearly full. What is the best first step?

Report an error

Q4.A business application crashes every time it is launched, but all other applications work normally. What is the best first step?

Report an error

Q5.A user reports that a Windows service their application depends on is not running. Where should the technician check the service's status and startup type?

Report an error

Q6.A user's phone app crashes every time it is opened, but other apps work fine. The phone has plenty of free storage. What is the best first step?

Report an error

Q7.A user cannot install a new application on their phone. The phone shows a "not enough storage" message, but the user insists they have space. What should the technician check?

Report an error

Q8.A user's phone screen does not rotate when the phone is turned sideways, but it worked yesterday. What is the most likely cause?

Report an error