Windows 11's File Explorer has no in-app help button, so "getting help" means picking one of Microsoft's official channels or applying the documented fixes yourself. The fastest route is the built-in Get Help app, which connects to Microsoft support through Settings; the most durable is a Repair or Reset of the File Explorer package, which keeps your personal files in place.
That's the honest shape of this topic. Microsoft retired the old File Explorer help menu years ago. What remains is a scattered set of support apps, command-line repairs, and registry checks that most help pages either skip or bury under generic "restart your PC" advice. The sections below map each route in order of effort, name the exact paths and commands, and flag where the official guidance stops short.
Seven Places Microsoft Still Answers File Explorer Questions
File Explorer ships inside Windows, so its support is folded into the operating system's general help system rather than a dedicated menu. That means five usable routes exist: the Get Help app for scripted troubleshooting, Microsoft Support's website for written step guides, the Feedback Hub for reporting a reproducible bug, the Microsoft Support Community forums for peer answers, and the optional "Contact support" flow inside the Get Help app when self-service fails.
Two more routes sit in the command line. The SFC /scannow and DISM /Online /Cleanup-Image /RestoreHealth pair repairs corrupted system files that File Explorer depends on, and PowerShell's Get-AppxPackage cmdlet lets you inspect or re-register the File Explorer package directly. Neither is a "help" menu, but both resolve problems that no help article can talk you through interactively.
The referral path matters more than people expect. Microsoft's own support documentation routes File Explorer performance complaints to Windows Update first, because a patch released in Windows 11 version 22H2 fixed a known memory leak in explorer.exe. If your build predates that fix, no amount of troubleshooting will outperform installing the update.
Time cost breaks down roughly like this: Get Help takes five to fifteen minutes depending on queue length, the community forums take anywhere from an hour to several days for a reply, and a Repair operation finishes in under two minutes on typical hardware.
Opening Get Help From Settings in Four Numbered Moves
The Get Help app is the single official entry point that can run diagnostics on your machine rather than just describe fixes. Use it before you start poking at PowerShell.
1: Press Windows key + I to open Settings. 2: Select System in the left sidebar, then scroll to Troubleshoot. 3: Choose Other troubleshooters, then click Run next to Windows Store Apps if File Explorer launches blank or crashes. 4: For anything else, open the Get Help app from the Start menu and type "File Explorer" into its search box.
If the Windows Store Apps troubleshooter completes without finding anything, don't treat that as confirmation the problem is elsewhere. It only checks app package registration and cache integrity, not shell extensions or group policy.
When Get Help's scripted answers run dry, the same app offers a contact option. Choose your product area, describe the issue in one sentence, and pick either chat or callback. Callback slots fill faster than chat queues during weekday mornings in North America, according to Microsoft's own support page notes, though availability varies by region.
The failure case worth knowing: Get Help sometimes fails to launch on systems where the Microsoft Store is itself broken. If the app opens to a blank window, run wsreset.exe from the Run dialog to clear the Store cache, then relaunch Get Help.
Which Support Channel Fits Your Problem
Not every File Explorer complaint deserves the same queue. Match the symptom to the channel before you spend time typing a description.
| Symptom | Best channel | Typical response time | Can it run diagnostics? |
|---|---|---|---|
| Explorer crashes or restarts on open | Get Help app | 5β15 minutes | Yes |
| Feature request or reproducible bug | Feedback Hub | No reply; tracked internally | No |
| "How do I show file extensions" | Microsoft Support website | Immediate | No |
| Shell extension conflict after third-party install | Support Community forums | 1 hour to 3 days | No |
| Corrupted system files behind Explorer errors | Command line (SFC/DISM) | Under 30 minutes | Yes, locally |
| Explorer.exe memory growth over days | Windows Update first | Depends on build | No |
The table's verdict line is simple. Self-service wins for anything with a known fix, Get Help wins for symptoms that need machine inspection, and the forums win for conflicts specific to software Microsoft didn't write.
Skip the forums for anything covered by a Windows Update note. Community threads about explorer.exe memory leaks from before the 22H2 patch still rank well in search results, and following their advice wastes hours on a problem Microsoft already closed.
Repair and Reset File Explorer Without Losing Personal Files
This is the highest-yield fix most help pages bury at the bottom. Repair reinstalls the File Explorer package while preserving your files, folders, and most settings; Reset does the same but also clears File Explorer's own state, including quick access pins and folder view preferences.
Reach it through Settings > Apps > Installed apps, scroll to File Explorer, click the three-dot menu, choose Advanced options, then click Repair. Wait for the checkmark, then test by pressing Windows key + E. If the problem persists, return and click Reset; the dialog warns that the app's data will be deleted, which for File Explorer means its recent-files list and customized folder views, not your actual documents.
The Reset path also clears the Quick Access history stored in %AppData%\Microsoft\Windows\Recent\AutomaticDestinations. That folder holds jump list cache files with names like f01b4d95cf55d32a.automaticDestinations-ms; they regenerate on their own, but pinned folders you added manually will need re-pinning.
One edge case trips people up: on domain-joined machines, Reset can fail with error 0x80073CF9 because group policy blocks package re-registration. If you see that code, the fix is on the IT side, not yours.
Run SFC and DISM When the Shell Itself Is Damaged
If File Explorer refuses to launch or the taskbar flickers continuously, package-level repair won't run because the settings app can't reach the shell. Command line is the only way in.
Open Terminal (Admin) from the Win+X menu, then run these in order:
1: DISM /Online /Cleanup-Image /RestoreHealth β repairs the component store that SFC pulls replacement files from. 2: SFC /scannow β scans and replaces corrupted protected system files.
Run DISM first. SFC pulls its repair files from the component store, and if that store is damaged, SFC reports "unable to fix" even when it finds corruption. Microsoft's own support documentation states this ordering explicitly, though many third-party guides still put SFC first.
Neither command touches your personal files, installed programs, or registry settings outside the protected system set. A typical full run of both takes fifteen to forty minutes depending on disk speed and whether the component store needs downloading from Windows Update.
Failure handling: if DISM reports error 0x800f081f, it can't reach the source files. Mount a Windows 11 ISO matching your build, note the drive letter, and re-run with /Source:D:\sources\install.wim /LimitAccess where D is your mounted ISO. If SFC still reports unrepaired files after a clean DISM pass, your best move is an in-place upgrade using that same ISO; it preserves apps and files while replacing the system layer.
Registry and Folder Options Checks That Break Explorer
Some File Explorer failures come from settings rather than corruption, and those need different tools. Two are worth knowing because they're undocumented in most help flows.
First, the NoDesktop and NoFolderOptions values under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer. If either is set to 1, File Explorer hides the View tab's Options button or the desktop icons entirely. This gets flipped by some "optimization" scripts and by malware. Set both to 0 or delete them, then sign out and back in; changes don't apply until the shell reloads.
Second, folder view cache corruption. Open File Explorer > View > Show > Options > View tab, click Reset Folders, and confirm. This clears the per-folder view memory stored in the registry under BagMRU and Bags keys, which is where odd behavior like every folder opening in Details view regardless of your preference gets fixed.
The registry edits carry real risk. Export the key first via right-click > Export, because a mistyped value name in the Policies branch can lock you out of folder options with no visible recovery path other than System Restore.
One region-specific wrinkle: on Windows 11 in S mode, which ships on some budget laptops sold in education channels, the registry editor is blocked entirely. In S mode you cannot apply these fixes at all until you switch out of S mode through the Microsoft Store, a one-way change.
Clear the Quick Access and Recent Files Cache Properly
Quick Access is File Explorer's default landing view, and a corrupted recent-files cache is the single most common cause of Explorer hanging for several seconds on launch. Clearing it isn't as simple as right-clicking and removing items.
The real cache lives in %AppData%\Microsoft\Windows\Recent\AutomaticDestinations and its sibling CustomDestinations. Close all File Explorer windows, open Task Manager, end the Windows Explorer process, then delete the contents of both folders. Restart Explorer via File > Run new task in Task Manager and typing explorer.exe.
Alternatively, use File Explorer > View > Options > General tab > Clear next to "Clear File Explorer history." That button does the same thing through the UI, which is safer for readers uncomfortable in AppData. Both routes remove only the history, never the files it points to.
Expect a few seconds of sluggishness on the first folder open after clearing, because Explorer rebuilds the cache from scratch. That's normal; a persistent delay of more than five seconds per folder points to a network location timing out, not the cache.
What the Feedback Hub Actually Does, and When It Helps
The Feedback Hub sits in the Start menu as a preinstalled app, and its purpose is diagnostic reporting rather than answers. Submitting a File Explorer bug there attaches a trace to your report if you opt in, which Microsoft's engineering teams use to reproduce the issue.
The value for you comes later. If a bug you reported gets fixed, the Feedback Hub sends a notification when the fix ships in a Windows Update, and your report becomes a searchable record. Search the app for "File Explorer" before submitting; a report with 400 upvotes already exists for most common issues, and adding your reproduction steps to an existing thread is more useful than filing a duplicate.
Turnaround is the honest limitation. Feedback Hub is not a support queue. There's no reply expectation, no case number, and no escalation path. Treat it as a bug report form, not a help desk.
The one scenario where it genuinely accelerates a fix: if you can reproduce a crash reliably, capture a trace by checking "Include diagnostic data" and recording the exact steps. Reports with attached traces get triaged faster than text-only descriptions, a point Microsoft states on the Feedback Hub's own help page inside the app.
Protecting File Explorer From the Fixes That Cause More Harm
Running a repair or reset changes state, and not every change is reversible by running the same thing again. Before you start, know what you're giving up.
Repair preserves your pinned items, recent files, and folder view preferences. Reset clears all three. Neither touches personal files in your Documents, Pictures, or other user folders, but both can remove any custom shell extensions installed by third-party tools if those tools hook into explorer.exe.
Create a restore point before registry edits. Type "Create a restore point" in Start, open System Properties > System Protection, and click Create. This takes about a minute and gives you a one-click rollback if a fix makes things worse.
The registry backup path matters for the same reason. Right-click the Explorer key under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies before changing anything, choose Export, and save the .reg file somewhere you'll find it. Importing that file reverses every change in the branch.
If File Explorer still misbehaves after Repair, Reset, SFC, DISM, and the registry checks, the remaining options are an in-place upgrade using a Windows 11 ISO, or a clean install. Both are major operations; consult a local technician if you're uncertain about data backup, since the clean install path erases the system drive.
FAQ
Does Windows 11 still have a Help menu inside File Explorer?
No. The Help menu was removed when File Explorer moved to its current tabbed design, and pressing F1 in File Explorer does nothing in Windows 11. The replacement is the Get Help app, which you reach from Settings > System > Troubleshoot or by searching "Get Help" in Start. Some older third-party guides still reference F1; ignore them.
How long does a File Explorer Repair take, and does it need a restart?
A Repair typically completes in 30 to 90 seconds on a solid-state drive, faster than the reset path because it doesn't clear app data. It usually doesn't require a restart, but if the fix doesn't take effect immediately, sign out and back in to reload the shell. Reset takes slightly longer because it removes the cached state.
Will repairing File Explorer delete my pinned folders or quick access items?
Repair leaves them intact. Reset removes pinned Quick Access items, the recent-files list, and customized folder views, but never your actual files. If those pins matter, use Repair first and only fall back to Reset if the problem persists.
Can I get help with File Explorer offline?
The Get Help app keeps a local cache of previously viewed answers and can run the Windows Store Apps troubleshooter without a connection. The command-line routes (SFC and DISM) also work offline, provided DISM can find repair files locally; otherwise it needs Windows Update or a mounted ISO. Community forums and chat support both require internet.
Why did Microsoft remove the File Explorer help menu?
Microsoft consolidated per-app help into the Get Help app starting with Windows 10, and the File Explorer menu didn't survive that consolidation. The company's stated rationale is centralized diagnostics that can inspect the machine rather than a static help file. No official announcement names File Explorer specifically.
Does the Feedback Hub get me a personal reply from Microsoft?
No. Feedback Hub reports are aggregated and triaged, and you'll only hear back through a notification when a related fix ships in an update. If you need a response, use Get Help's contact option or the Support Community forums instead.
What's the difference between Reset and reinstalling Windows for File Explorer problems?
Reset rebuilds only the File Explorer package and preserves your installed programs and personal files. Reinstalling Windows replaces the entire operating system. Reset solves package-level corruption; it cannot fix a damaged system file layer or a corrupt user profile, which is why SFC and DISM exist as separate tools.
Is it safe to delete the AutomaticDestinations folder contents?
Yes. That folder holds jump list and recent-file caches, not your files, and Windows rebuilds it automatically. Close File Explorer and end the explorer.exe process in Task Manager first so the files aren't locked, then delete the contents. Pinned items regenerate only for folders you've opened recently.