A user reports that an enterprise database reporting tool on a Windows 11 workstation consistently crashes upon opening specific reporting modules. What is the correct sequence of troubleshooting steps a technician should follow to identify the faulting component and remediate system dependency corruption using Windows administrative tools?
- 1Inspect the Event Viewer Application log for Event ID 1000 to identify the faulting module name and exception code.
- 2Execute System File Checker (sfc /scannow) in an elevated Command Prompt to scan and repair protected system files.
- 3Execute DISM /Online /Cleanup-Image /RestoreHealth to repair the Windows component store image.
- 4Re-execute System File Checker (sfc /scannow) to replace corrupted operating system files.
Cevap
The correct sequence starts with reviewing Event Viewer Application logs for Event ID 1000 crash details, running System File Checker (sfc /scannow) to repair system files, executing DISM /Online /Cleanup-Image /RestoreHealth if the component store is damaged, and finally re-running sfc /scannow to complete file restoration.
The proper troubleshooting process begins by examining Event Viewer Application logs for Event ID 1000 details to verify if a system module caused the crash. The technician then runs System File Checker () to repair damaged files. If SFC encounters corrupted files it cannot fix due to store corruption, DISM () must be executed to repair the Windows component store. Finally, executing a second time applies the repairs using the restored component store.
Adım Adım Çözüm
Anahtar Kavram
Troubleshooting Application Crashes and Windows System File Repair Sequence