Windows 11 File Explorer Keeps Restarting can look like a single error, but the right repair depends on which layer failed. Explorer or taskbar repeatedly disappears and returns while opening folders. This walkthrough narrows the fault using three plausible branches, starting with observations that do not modify data, account credentials or firmware. The instructions are intended as a decision path, not proof that any particular component is defective.
Recognize the problem and define its scope
Windows error numbers frequently identify the failing subsystem, not the root cause. Keep the exact build, KB or driver version in your notes, and distinguish an isolated application failure from a system-wide one. Record the exact wording, affected version, timestamp and the operation that failed. Note whether the issue began after an update, a change in hardware, a new connection or an account change. If the failure appears on only one device or one user account, that difference is often more useful than repeating the error message in a search engine.
Before choosing an advanced repair, collect these observations: (1) the outcome of “test an empty local folder”; (2) whether “turn off preview pane temporarily” changes anything; and (3) whether the original symptom persists after a safe retry. Keep a short log of the action and outcome. A result that changes only one variable is easier to interpret than multiple simultaneous resets.
Before you change anything
Important: Do not delete user profile folders before backing them up. Where the workflow involves backups, passwords, encryption, drive partitions, system software or data migrations, confirm a usable recovery path first. If this is a managed device or production service, coordinate changes with its owner. Never paste tokens, cookies, private logs or serial numbers into public troubleshooting posts.
Use the following interactive instructions in order. The Beginner tab contains low-risk checks; the Advanced tab is for administrators or experienced users who can interpret logs and reverse configuration changes. Stop when the original operation is working and the validation test passes.
Step-by-Step Troubleshooting
Begin with safe, reversible checks; use advanced diagnostics only when the evidence indicates that branch. Preserve backups and original settings.
Test an empty local folder
Test an empty local folder. This is a low-risk check for third-party shell extension crash. Before proceeding, note whether the original failure appears with the same message and conditions. If this test changes the behavior, repeat the same operation once to distinguish a stable change from a transient result. Avoid making an unrelated setting change during this comparison.
Turn off preview pane temporarily
Turn off preview pane temporarily. This is a low-risk check for thumbnail or preview handler fault. Before proceeding, note whether the original failure appears with the same message and conditions. If this test changes the behavior, repeat the same operation once to distinguish a stable change from a transient result. Avoid making an unrelated setting change during this comparison.
Restart explorer.exe from Task Manager
Restart explorer.exe from Task Manager. This is a low-risk check for damaged user profile. Before proceeding, note whether the original failure appears with the same message and conditions. If this test changes the behavior, repeat the same operation once to distinguish a stable change from a transient result. Avoid making an unrelated setting change during this comparison.
Check if another Windows account is affected
Check if another Windows account is affected. This is a low-risk check for third-party shell extension crash. Before proceeding, note whether the original failure appears with the same message and conditions. If this test changes the behavior, repeat the same operation once to distinguish a stable change from a transient result. Avoid making an unrelated setting change during this comparison.
Read explorer.exe faulting module in Event Viewer
Read explorer.exe faulting module in Event Viewer. Use this diagnostic only when earlier evidence implicates third-party shell extension crash, and only with appropriate administrative access. Record the command or setting, original value, timestamp and outcome; redact sensitive log material. If the result does not support the suspected cause, stop rather than adding unrelated fixes. For production services, run the procedure in an approved maintenance window or staging environment.
Optional read-only diagnostic example. Review the target environment before running; it does not perform a repair.
Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion,OsBuildNumberCorrelate Reliability Monitor crashes
Correlate Reliability Monitor crashes. Use this diagnostic only when earlier evidence implicates thumbnail or preview handler fault, and only with appropriate administrative access. Record the command or setting, original value, timestamp and outcome; redact sensitive log material. If the result does not support the suspected cause, stop rather than adding unrelated fixes. For production services, run the procedure in an approved maintenance window or staging environment.
Temporarily isolate non-Microsoft shell extensions
Temporarily isolate non-Microsoft shell extensions. Use this diagnostic only when earlier evidence implicates damaged user profile, and only with appropriate administrative access. Record the command or setting, original value, timestamp and outcome; redact sensitive log material. If the result does not support the suspected cause, stop rather than adding unrelated fixes. For production services, run the procedure in an approved maintenance window or staging environment.
Repair system files only if evidence supports it
Repair system files only if evidence supports it. Use this diagnostic only when earlier evidence implicates third-party shell extension crash, and only with appropriate administrative access. Record the command or setting, original value, timestamp and outcome; redact sensitive log material. If the result does not support the suspected cause, stop rather than adding unrelated fixes. For production services, run the procedure in an approved maintenance window or staging environment.
Which cause best matches the evidence?
Use the original behavior and each controlled test to decide which branch deserves attention. These are hypotheses—not automatic diagnoses—and more than one can be present.
| Possible cause | Evidence to look for | Next safe check |
|---|---|---|
| Third-party shell extension crash | The fault changes when you isolate this specific condition, or the related log or device state identifies it. | Turn off preview pane temporarily |
| Thumbnail or preview handler fault | The fault changes when you isolate this specific condition, or the related log or device state identifies it. | Restart explorer.exe from Task Manager |
| Damaged user profile | The fault changes when you isolate this specific condition, or the related log or device state identifies it. | Read explorer.exe faulting module in Event Viewer |
For example, a result that changes after restart explorer.exe from task manager points toward a different path from one that fails identically on every supported device. Do not select a repair based only on a coincidental reboot, cache clear or temporary service recovery; repeat the original operation after isolating the suspected cause.
Understanding the three failure paths
Third-party shell extension crash
Investigate this branch when the initial test suggests third-party shell extension crash. Start by test an empty local folder, then turn off preview pane temporarily. If those two checks show a repeatable difference, read explorer.exe faulting module in event viewer can help confirm which component or configuration is involved. Keep the investigation limited to the affected environment: a failure isolated to one profile, disk, account or network path should not trigger a system-wide reset.
Thumbnail or preview handler fault
Investigate this branch when the initial test suggests thumbnail or preview handler fault. Start by restart explorer.exe from task manager, then check if another windows account is affected. If those two checks show a repeatable difference, correlate reliability monitor crashes can help confirm which component or configuration is involved. Keep the investigation limited to the affected environment: a failure isolated to one profile, disk, account or network path should not trigger a system-wide reset.
Damaged user profile
Investigate this branch when the initial test suggests damaged user profile. Start by turn off preview pane temporarily, then check if another windows account is affected. If those two checks show a repeatable difference, temporarily isolate non-microsoft shell extensions can help confirm which component or configuration is involved. Keep the investigation limited to the affected environment: a failure isolated to one profile, disk, account or network path should not trigger a system-wide reset.
Read the test results before choosing a repair
| Observation | What it suggests | Reasonable next action |
|---|---|---|
| The original task now works | A tested change may have removed the blocker, but the condition could have been temporary. | Check if another Windows account is affected; retest the original operation. |
| The failure is unchanged | The first suspected cause is not yet supported by evidence. | Read explorer.exe faulting module in Event Viewer and compare a different branch. |
| The failure affects another device or account | A shared service, network or account policy may be involved. | Temporarily isolate non-Microsoft shell extensions; check official service guidance. |
| Data integrity or security is at risk | Repeated writes, bypasses or resets could increase damage. | Pause changes, preserve backups and escalate with redacted diagnostics. |
How to verify the repair
Expected result: Explorer stays responsive across repeated navigation and restart. Run the same operation that originally failed, not only a nearby health test. Where appropriate, repeat it once after a normal restart or reconnection. Check the relevant event log, application status, output file, transaction state or device reading for fresh errors. A successful login or a green dashboard is not sufficient if the original operation still fails.
Rollback and when to seek help
If a new symptom appears after a configuration change, reverse only that change and repeat the baseline test. Preserve the original error text, the software or firmware version, the three diagnostic results and any redacted log excerpts. If the safe steps do not help, the next evidence-based investigation is repair system files only if evidence supports it. For hardware faults, ongoing disk corruption, account lockouts or public-facing server incidents, seek authorized vendor or administrator support rather than looping through resets.
Solution Checklist
Frequently asked questions
Does Windows 11 File Explorer Keeps Restarting always mean the same fault?
No. The message can be produced by third-party shell extension crash, thumbnail or preview handler fault, or damaged user profile. Use the specific affected operation and a second controlled check before deciding which path applies.
Can I skip directly to the advanced steps?
Not recommended. Begin with test an empty local folder. Advanced steps such as correlate reliability monitor crashes are useful only when earlier evidence points there; many require elevated permissions or careful change tracking.
When is it safe to consider the issue resolved?
Explorer stays responsive across repeated navigation and restart. Ideally the successful result persists across normal use and the earlier error does not reappear.
Official documentation and related guidance
For supported versions, exact menu names and vendor-approved recovery procedures, consult Microsoft Windows Support. These references are starting points for version-specific instructions, not a claim that this particular repair was tested on every affected model.
Browse additional Windows solutions on PRBLEM. If another error appears during the same operation, search its exact text separately rather than assuming the messages are interchangeable.