220-1102 Software Troubleshooting Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Disable all startup programs via Task Manager

  Why this is correct

  The Startup tab in Task Manager lists every program configured to launch at logon, along with a measured 'Startup impact' rating. Disabling non-essential entries—such as updaters, preloaders, or third-party utilities—prevents them from consuming CPU, disk, and memory resources during boot, which directly shortens the time to the desktop. This method is reversible and does not remove the software; the program remains available for manual launching later, making it the safest and most effective first step.

• ✗

  Uninstall the most recently installed program

  Why it's wrong here

  This approach presumes that the most recently installed program is responsible for the slow boot, but the problem is often caused by an accumulation of startup entries from many applications over time. The newest software may not even register a startup item, and if it did, disabling that single entry via Task Manager would suffice. Uninstalling a program is disruptive if it is still needed for other tasks, and it should only be considered after identifying the specific culprit through the Startup tab. Therefore, uninstalling is an unnecessarily aggressive and often ineffective reaction.

• ✗

  Run System File Checker (sfc /scannow)

  Why it's wrong here

  Running sfc /scannow launches the System File Checker, which verifies and restores protected system files, such as core Windows executables and Dynamic Link Libraries, by comparing them against cached copies in the Windows component store. This is useful for addressing corruption that can cause crashes, system instability, or OS-level failures, but it does not address the loading of third-party programs at logon. A slow boot with many startup programs is a user-mode autostart issue, not a system-file integrity issue. Since the symptom is clearly related to startup load, sfc /scannow would search for a problem that likely does not exist and would have no effect on boot time.

• ✗

  Perform a clean boot using msconfig

  Why it's wrong here

  A clean boot through msconfig is a diagnostic technique used to temporarily disable all non-Microsoft services and startup items to isolate whether a third-party process is causing a problem. It is not intended as a permanent performance optimization because it also disables services that your hardware drivers, antivirus, or other critical software may require, and the system runs in a 'Selective Startup' state that can interfere with normal functionality. Task Manager's Startup tab is the appropriate tool for permanently managing startup items because it allows granular control without touching service-level dependencies. In contrast, a clean boot is a temporary state meant for troubleshooting, not for everyday use, and it would be overkill and potentially harmful as a permanent fix.

Go deeper

Related to this question