File Explorer in Windows 11 leans on two repair systems that most people never separate: the Windows 11 22H2-and-later tabbed shell (File Explorer Gallery and tabs arrived in 22H2, September 2022, per Microsoft's Windows 11 update history) and the older COM-based explorer.exe process underneath it. "Get help" here means picking the right one to reset. The most common real fault β€” Explorer opening to Quick Access instead of This PC, or refusing to remember window size β€” is a folder-options setting, not corruption, and it's fixed in about 40 seconds without any repair tool.

Why File Explorer Misbehaves Differently in the 22H2 Tabbed Shell

Windows 11's File Explorer is not one program anymore. The tabbed window you see since version 22H2 is a XAML host process wrapping the classic explorer.exe frame, and Microsoft's own Windows release health notes have documented explorer.exe crashes tied to third-party shell extensions after feature updates. That split matters because it changes which repair tool works. Resetting the modern shell clears tab and Gallery state; resetting explorer.exe clears the COM handlers that draw context menus and folder views.

The first failure pattern to know: a crash that returns your taskbar but not your desktop means explorer.exe died while the XAML host survived. Press Ctrl+Shift+Esc, find Windows Explorer in Task Manager, and choose Restart β€” that relaunches the shell without a reboot and takes roughly 5 seconds on an SSD. This is the single most useful keystroke sequence in the whole article.

The second pattern is the opposite: windows that open but freeze on "Working on it…" when you click a network path. That's usually a stalled shell extension (cloud sync clients are the classic culprit), not the tab engine. Restarting explorer.exe won't fix it for long; disabling the extension will.

A third pattern only appears on Windows 11 SE, the education-only edition Microsoft ships on school devices. SE blocks some shell customizations by policy, so folder-option toggles that work on Home and Pro may be greyed out. If you're on a school-managed machine, the fix lives with your IT admin, not in Settings.

The Quick Access Reset That Fixes Four Complaints in 40 Seconds

Windows 11 changed the default: File Explorer now opens to Home (formerly Quick Access), listing Recent files and Favorites. Four complaints trace to this one setting β€” Explorer "forgetting" your last folder, the Home view loading slowly on a network, pinned folders vanishing, and recent files you'd rather not display. All four live under the same Options dialog.

Here's the sequence, in the exact on-screen order:

1: Open File Explorer (Win+E) and click the three-dot See more menu at the top right, then Options. 2: In the General tab, find Open File Explorer to: and switch the dropdown from Home to This PC. 3: Under Privacy, untick Show recently used files in Quick access and Show frequently used folders in Quick access if you want Home empty. 4: Click Clear next to Clear File Explorer history, then Apply. 5: Return to the View tab and click Reset Folders, then Reset on the confirmation.

If the Options dialog itself won't open or the Apply button does nothing, a policy is blocking it. Check gpedit.msc under User Configuration β†’ Administrative Templates β†’ Windows Components β†’ File Explorer for any "Turn off" entries set to Enabled; on Home edition, gpedit isn't available, so check the same policy strings in the registry under HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer instead. Fixing policy first, then repeating steps 1–5, resolves it.

Restarting Explorer.exe From Task Manager Without Losing Your Session

Restarting the shell is the highest-value, lowest-risk repair in Windows 11, and it costs you nothing but open File Explorer windows. Your browser, documents, and apps keep running. The shell redraws the taskbar, Start, and desktop in a few seconds.

Do it this way. Press Ctrl+Shift+Esc to open Task Manager. On the Processes tab, scroll to Windows Explorer (it may show as Windows Explorer with a folder icon). Right-click it and choose Restart. If the entry is missing entirely β€” which happens when the shell has crashed and not auto-recovered β€” click Run new task at the top, type explorer.exe, and press Enter.

Version detail that trips people up: Windows 11 22H2's Task Manager still lists the classic process name. The redesigned Task Manager that arrived with the 23H2 feature updates (rolled out from late 2023) groups it under Windows processes and adds an efficiency-mode column, so the right-click menu wording differs slightly. Both versions accept the same Run new task fallback.

If explorer.exe restarts and dies again within a minute, stop restarting it. That loop points to a bad shell extension or a corrupted user profile, and the next two sections address each.

Using the Built-In Get Help App and Windows Troubleshooter for Explorer Faults

Microsoft ships a Get Help app (search "Get Help" in Start) that runs automated diagnostics and can connect you to support. It's genuinely useful for one specific job: confirming whether a File Explorer fault is a known, Microsoft-acknowledged issue with a published workaround. It is not a repair tool in itself, and it won't rebuild your shell.

The older Windows Troubleshooter path still exists and is faster for permission errors. Go to Settings β†’ System β†’ Troubleshoot β†’ Other troubleshooters, and run Windows Store Apps (it covers shell components on some builds) or Network and Internet if the fault only appears on mapped drives. Windows 11 23H2 consolidated these under "Other troubleshooters," so the exact label you see depends on your build, which you can confirm in Settings β†’ System β†’ About.

Timing note worth knowing: Microsoft's release health dashboard has, in past feature updates, listed File Explorer hangs as "known issues" with a stated fix window measured in weeks, not hours. If Get Help tells you your build is affected, waiting for the monthly Patch Tuesday cumulative update is often faster than any manual repair. Patch Tuesday falls on the second Tuesday of each month, which in 2026 lands on November 10 β€” two days before this article's reference date.

If neither tool finds anything, the fault is local to your profile, and the next sections cover that.

Clearing Explorer State Through the AppData Folders Nobody Mentions

File Explorer caches its view state in three user-profile locations, and clearing them fixes thumbnail corruption, wrong folder templates, and column layouts that snap back to defaults. None of these live in Settings, which is why most guides skip them.

The paths, opened by pasting into the File Explorer address bar:

%APPDATA%\Microsoft\Windows\Recent β€” the automatic-destinations and recent-items jump lists. %LOCALAPPDATA%\Microsoft\Windows\Explorer β€” thumbnail cache and icon cache files, named thumbcache_.db and iconcache_.db. %APPDATA%\Microsoft\Windows\Shell β€” the Bags and BagMRU keys that store per-folder window size, view, and sort order.

Close all File Explorer windows first. Then delete the contents of Recent and the thumbcache/iconcache files. Deleting BagMRU resets every folder's remembered view β€” including the sizes you deliberately set β€” so do this only when layouts misbehave, and expect to re-set your preferred column widths afterward. Windows rebuilds the caches on next launch; thumbnail regeneration on a large photo library can take several minutes.

This is where Windows 11 differs from Windows 10: the 22H2 shell stores tab-session state alongside these caches, so a full AppData purge also closes your restored tabs on next launch. That's harmless but surprising if you rely on restore-on-startup. No reboot is needed for the cache deletions; a sign-out is enough if a file is locked.

Running SFC and DISM to Repair Corrupted Explorer Components

When explorer.exe crashes on launch or File Explorer refuses to open at all, the cause can be a corrupted system file rather than a setting. Two Microsoft-shipped command-line tools handle this, and they must run in the right order.

Open Terminal (Admin) β€” right-click Start, choose Terminal (Admin), or search "Terminal," right-click, and Run as administrator. Then:

1: Run sfc /scannow and let it finish. It typically takes 5–15 minutes and reports whether it found and repaired corruption. 2: Run DISM /Online /Cleanup-Image /RestoreHealth. This repairs the component store SFC reads from, and it can take 10–30 minutes depending on your connection, because it may pull replacement files from Windows Update. 3: Reboot, then run sfc /scannow once more to confirm a clean result.

Order matters. Running SFC before DISM on a machine with a damaged component store produces false "unable to fix" results, a failure case that sends people down dead ends. If DISM itself fails with error 0x800f081f, it can't reach Windows Update for source files; Microsoft's documented workaround is pointing DISM at installation media with the /Source: switch.

SFC won't touch third-party shell extensions or your user-profile settings, so a clean scan plus a still-broken Explorer means the fault is above the system-file layer. That's normal, not a failed repair.

Safe Mode and a Clean Boot: Isolating Third-Party Shell Extensions

Third-party shell extensions β€” the handlers that add right-click menu entries β€” are the most common cause of Explorer hangs that survive every built-in repair. Windows 11 lets you test this without uninstalling anything, two ways.

Safe Mode loads Windows with minimal drivers and no third-party shell extensions. Hold Shift while clicking Restart from the Power menu, then choose Troubleshoot β†’ Advanced options β†’ Startup Settings β†’ Restart, and press 4 for Safe Mode. If Explorer behaves perfectly there, an extension is the culprit.

Clean Boot is finer-grained and keeps you in normal Windows. Run msconfig, go to the Services tab, tick Hide all Microsoft services, then click Disable all, and reboot. Re-enable services in halves to find the offender. This is Microsoft's own documented procedure for isolating background-service conflicts.

Once you suspect extensions, audit them with Autoruns from Microsoft Sysinternals, filtering to the Explorer tab. Disable entries in batches; each toggle is reversible, so you never lose a working setup to a guess. Cloud-storage clients and "right-click tools" utilities dominate the offender list in practice. The verification path: re-enable one extension at a time and open a folder after each.

Rebuilding the Shell With a New User Profile as the Last Local Fix

If a fresh explorer.exe, clean system files, and a clean boot all fail, the fault is bound to your user profile. Windows 11 lets you test this in about 10 minutes without deleting anything. Create a new local account in Settings β†’ Accounts β†’ Other users β†’ Add account, sign in, and open File Explorer there.

If Explorer works under the new profile, your old profile's shell registry keys are damaged. The durable fix is migrating: copy your files from C:\Users<oldname> to the new profile and make the new account your daily driver. The quick-and-dirty fix is renaming the Shell and ShellNoRoam registry keys under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer after exporting a backup β€” Windows rebuilds them on next sign-in.

Don't skip the export. Use regedit's File β†’ Export on the Explorer key first; a bad rename can leave you with no taskbar, and the import restores it. This is the riskiest step in the article, and it's the one to attempt only after the earlier, safer fixes have failed.

Home vs Pro vs SE: The Folder-Options Features You Can't Toggle

The repair set changes by edition, and knowing which features are missing saves you hunting for toggles that don't exist. Here's how the common Explorer controls compare across Windows 11 editions as of the 23H2 feature set.

Feature Home Pro SE Where it lives
Open File Explorer to This PC Yes Yes Yes (may be policy-locked) Folder Options β†’ General
Group policy editor (gpedit.msc) No Yes No Run dialog
BitLocker drive unlock in Explorer No Yes No Right-click drive
Hyper-V virtual disk mounting No Yes No Disk Management
Clear thumbnail cache via Disk Cleanup Yes Yes Yes Disk Cleanup applet
Folder Options dialog itself Yes Yes Policy-dependent See more menu

The practical verdict: on Home, skip any guide that begins "open gpedit" β€” you'll need the registry path instead. On SE, confirm with IT before touching Folder Options, since the dialog can be locked by device policy. On Pro, everything in this article is available as written.

FAQ

Does resetting File Explorer delete my files?

No. Every repair in this article touches settings, caches, and system files, never your documents. The one step with side effects is deleting the BagMRU registry keys or the Shell folder, which resets remembered window sizes and sort orders β€” cosmetic, not data loss. If you follow the AppData section, expect to re-set your preferred column widths afterward.

Why does File Explorer keep opening to Home even after I change it to This PC?

A group policy or a synced setting is overriding your choice. Check the registry key HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer for a "Launch To" or "NoRecentDocsHistory" value set by a management tool, and check that OneDrive isn't re-syncing folder settings. On managed work machines, the policy usually wins, and only your IT admin can change it.

Is sfc /scannow safe to run, and how long does it take?

It's a Microsoft-shipped repair tool and safe to run repeatedly; it changes system files only when it finds corruption. Expect 5–15 minutes for SFC and 10–30 minutes for DISM, with DISM sometimes faster if your component store is already healthy. If SFC reports "unable to fix," run DISM first and then repeat SFC β€” the order matters.

Can I fix Explorer without Safe Mode?

Yes, in most cases. Restarting explorer.exe from Task Manager, resetting Folder Options, clearing the AppData caches, and a Clean Boot will isolate or fix the majority of faults. Safe Mode is the escalation step when those fail and you need to prove a third-party driver or extension is involved.

What's the difference between restarting Explorer and rebooting Windows?

Restarting explorer.exe relaunches only the shell β€” taskbar, desktop, Start, and File Explorer windows β€” in about 5 seconds while your apps keep running. A reboot also reloads drivers and services, so it fixes more but costs minutes. Reach for the shell restart first; reboot only when the shell restart loops.

Will a Windows 11 feature update fix my Explorer bug?

Sometimes, and it's worth checking. Microsoft's release health dashboard lists acknowledged File Explorer issues with a stated fix window, often the next monthly cumulative update. Since Patch Tuesday falls on the second Tuesday of each month, waiting for it can beat manual repair if Get Help confirms your build is affected.

Does Windows 11 SE have the same Explorer repair tools?

SE shares the built-in tools β€” SFC, DISM, Task Manager, Safe Mode β€” but restricts several shell customizations by policy, including some Folder Options entries. Confirm with the device administrator before changing policy-controlled settings, because school-managed devices often revert unauthorized changes at next sign-in.

How do I know whether the fault is Explorer or a shell extension?

Restart explorer.exe and watch how long it survives. If it dies within a minute of restarting, suspect an extension; if it survives but one folder type hangs, suspect a cached view or a cloud-sync handler. Clean Boot settles the question: perfect behavior in a clean boot points at an extension every time.