220-1102 Question 206
Single answerUpdates/patchesA small accounting office uses several Windows 11 PCs. After the monthly security updates were installed on one workstation, a critical line-of-business application began crashing immediately at launch. The user needs the application restored as quickly as possible, but the company also wants to maintain good security practices. What should the technician do FIRST?
- A
Uninstall the most recently installed update on the affected workstation, verify the application works, and then defer that update temporarily while the issue is investigated
- B
Disable Windows Update permanently on the workstation so no future patches can interfere with the application
- C
Perform a full operating system reinstall to remove all recent changes and return the PC to a stable state
- D
Update the workstation's wallpaper and user profile settings to force the application to rebuild its configuration
Show answer and explanation
Correct answer: A
Explanation
The best first action is to remove the specific recently installed update that appears to have caused the issue, confirm the application launches correctly, and then temporarily defer or pause that update while researching a long-term fix. In real support environments, technicians should use the least disruptive corrective action first. This aligns with standard Windows troubleshooting practices for problematic updates and with security best practices: restore functionality, document the issue, and avoid unnecessarily broad actions such as disabling updates permanently. Microsoft documents methods for viewing update history, uninstalling quality updates, and pausing updates in Windows settings. From an A+ Core 2 perspective, the key concept is balancing business continuity with patch management by rolling back a problematic patch when necessary rather than abandoning update management entirely.
- A. Correct.
Correct. When a business application fails immediately after a recent patch cycle, the most appropriate first step is to identify and roll back the specific update that likely introduced the issue, then confirm functionality. This is a practical troubleshooting step that restores service quickly while limiting exposure. Temporarily pausing or deferring the problematic update is more appropriate than disabling patching entirely, because it supports continued security management while the vendor or IT staff investigates compatibility.
- B. Incorrect.
Incorrect. Permanently disabling Windows Update is not a good security practice and creates significant risk by leaving the system unpatched against future vulnerabilities. A technician might choose this if focused only on short-term application stability, but CompTIA expects balancing usability with security. Temporary deferral of a known problematic update is acceptable; permanent disabling is not.
- C. Incorrect.
Incorrect. A full OS reinstall is far too disruptive and should not be the first response to a likely patch compatibility issue. Reinstallation increases downtime and may not even solve the problem if the same update is later reapplied. A technician might pick this when thinking about returning to a known-good state, but targeted rollback is the faster and more appropriate troubleshooting step.
- D. Incorrect.
Incorrect. Changing wallpaper or profile settings has no meaningful relationship to post-update application crashes. This distractor reflects random or non-causal troubleshooting rather than evidence-based action. An app crashing immediately after patch installation points toward update compatibility, application repair, or vendor guidance, not cosmetic user settings.