A user's File Explorer keeps crashing. The technician is troubleshooting and tries the following: - Runs Windows Update - Runs CHKDSK and SFC /scannow - Clears File Explorer history Which of the…

Rolling back Windows updates is a valid troubleshooting step if the problem started immediately after an update, but it's often more drastic than necessary and not the next logical step after the given initial attempts without evidence linking the crash to an update.

Reimaging the computer is a last resort, destructive step that should only be performed after exhausting less intrusive troubleshooting methods and confirming a software issue beyond repair, not as the immediate next action after basic checks.

Persistent application crashes, especially system components like File Explorer, even after basic software troubleshooting (updates, SFC, CHKDSK), can indicate underlying hardware issues, with faulty RAM being a common culprit. Testing the computer's memory (e.g., with Windows Memory Diagnostic) is a crucial diagnostic step to identify if corrupt memory is causing the instability.

Repartitioning the boot drive would erase all data and is a drastic measure typically reserved for severe disk corruption or OS reinstallation, and it is highly unlikely to resolve application crashes caused by other factors like memory issues.