Courseiva
Software Troubleshooting →hardMultiple Choice

220-1102 Software Troubleshooting Practice Question

A user reports that a 64-bit application on Windows 10 Pro crashes immediately upon launch with the error '0x80004005 - Unspecified error'. The technician has already reinstalled the application and verified that all Windows updates are current. Which built-in tool should the technician use NEXT to check for system file corruption?

⚠ Common exam trap

A common mix-up: candidates confuse a generic error code like 0x80004005 with a hardware issue, leading them to choose Windows Memory Diagnostic, when the error is actually a software corruption problem that SFC is designed to resolve.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

System File Checker (SFC)

The error 0x80004005 is a generic COM error often caused by system file corruption. Since the application has been reinstalled and Windows updates are current, the next logical step is to use System File Checker (SFC) to scan and repair protected system files. SFC is the built-in tool specifically designed for this purpose.

Answer analysis

Option-by-option breakdown

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

  • ✓

    System File Checker (SFC)

    Why this is correct

    System File Checker (SFC) is the correct first repair step because the generic 0x80004005 error often indicates corrupted or missing protected system files. Running 'sfc /scannow' from an elevated command prompt verifies the integrity of system files and replaces damaged versions using cached copies in the Windows component store.

  • ✗

    Windows Memory Diagnostic

    Why it's wrong here

    Windows Memory Diagnostic targets physical RAM faults, which typically manifest as access violations like 0xc0000005, random application crashes, or bugchecks (BSOD) — not the generic 0x80004005 HRESULT. Because this error is commonly a file-corruption symptom rather than a hardware memory failure, running a memory test would unlikely resolve the crash and would delay the correct repair.

  • ✗

    Event Viewer

    Why it's wrong here

    Event Viewer would provide granular crash details such as the faulting module and exception code, but it only records evidence of the failure; it cannot repair the underlying file corruption. Since the technician already has the 0x80004005 error code, reading more logs is a diagnostic delay rather than a corrective action, so it is not the best next step.

  • ✗

    Reliability Monitor

    Why it's wrong here

    Reliability Monitor aggregates system stability events over time, showing a history of crashes including the failing application, but it is a retrospective reporting tool without any repair capability. It cannot replace or repair corrupted system files; SFC is the dedicated utility for that specific remediation, making Reliability Monitor inappropriate as the immediate next action.

Go deeper

Related to this question

About these practice questions

Courseiva writes every 220-1102 question from scratch — 925 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This 220-1102 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1102 exam.