A technician is troubleshooting a Windows 11 workstation where a critical line-of-business… — CompTIA A+ (Core 1 & Core 2)

A technician is troubleshooting a Windows 11 workstation where a critical line-of-business application crashes immediately upon opening. Event Viewer records Event ID 1000 in the Application log, specifying ntdll.dll as the faulting module. Hardware diagnostics for memory and storage report no errors. Which of the following commands should the technician execute FIRST from an elevated command prompt to verify and repair corrupted system files?

sfc /scannowAnswer
B
chkdsk C: /r
C
Perform a clean reinstallation of the Windows operating system
D
Open Disk Management and extend the system partition volume

Answer

The technician should execute sfc /scannow from an elevated command prompt to repair corrupted system files.

Executing sfc /scannow is the standard non-destructive troubleshooting step to repair corrupted system files when Event Viewer indicates a core Windows library like ntdll.dll is the faulting module.

Step-by-Step Solution

Analyze Event Viewer logs

Identify Event ID 1000 indicating an application crash caused by a corrupted core system library (ntdll.dll).

Event ID 1000 logs application crashes along with the faulting application path and faulting module.

Select the appropriate non-destructive command-line utility

Choose System File Checker (sfc /scannow) to inspect Windows system files.

Since ntdll.dll is an essential Windows component, System File Checker compares current system files against cached, known-good versions.

Execute the repair command

System File Checker replaces damaged system binaries without altering user data or requiring OS reinstallation.

This isolates and resolves OS system file corruption efficiently.

Key Concept

Using System File Checker (sfc /scannow) to resolve Windows application crashes caused by corrupted system binaries.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic