When you click Get Help in File Explorer on Windows 11, you aren't opening a File Explorer manual — you're launching the unified Windows Get Help app, which tries to hand your question to Microsoft's virtual assistant or a live support agent. That matters, because most people clicking the button expect Explorer-specific troubleshooting and get a general support hub instead. The fastest route to actual Explorer help is usually the built-in troubleshooters, the Feedback Hub (Windows key + F), or Microsoft's support site — not the blue Get Help link itself.

You'll find that link in a few places: the File Explorer ribbon's Help section (the ? icon in the top-right of the command bar), inside Settings under System, and in the Get Help app that ships as a Store component. Every one of them lands in the same place. Once you know what's behind the button, the useful question becomes which help channel actually solves which Explorer problem — sluggish folder loads, a crashed taskbar, a missing ribbon, or a mapped drive that won't reconnect.

What the Get Help Button in File Explorer Actually Opens

The ? icon at the right end of the File Explorer command bar launches a packaged app called Get Help (internally, an app with the executable name GetHelp.exe), not a browser page. That app signs you in with your Microsoft account and presents a chat-style interface. Its scope covers Windows broadly, Microsoft 365, Xbox, Surface hardware, and account billing — so the quality of a File Explorer answer depends entirely on how you phrase the first message.

Notably, Get Help does not index your local file system, doesn't read Explorer's error dialogs, and can't see which folder or drive triggered your problem unless you describe it. That limitation is the single biggest reason people come away unimpressed. If you type "file explorer keeps crashing," you'll get generic scripted steps, not a diagnosis of a specific shell extension.

Microsoft has repositioned this app over the life of Windows 11: it replaced the older "Contact Support" app and consolidated several separate support entry points. The app updates through the Microsoft Store independently of Windows feature updates, so its behavior can shift between Patch Tuesdays without any visible change in File Explorer itself.

Practically, treat the button as a doorway to human chat and account-level support rather than a troubleshooting engine. If your question is "why does this one folder take eight seconds to open," you'll do better in the Feedback Hub or with the steps below. If your question is "my Microsoft 365 subscription shows the wrong renewal date," Get Help is genuinely the right tool.

Get Help vs. Windows Troubleshooters vs. Feedback Hub: Which Channel Wins

Three built-in channels compete for the same job, and they differ sharply in what they can actually do. Getting this comparison right saves you ten minutes of clicking around before you've fixed anything.

Channel How to open Best for Can it read your system logs? Typical response time
Get Help app ? icon in Explorer, or Start menu search Account, billing, licensing, live agent escalation No Minutes in chat, hours to days for callback
Settings troubleshooters Settings > System > Troubleshoot > Other troubleshooters Recognized failure patterns (audio, network, Windows Update) Yes, limited Under 2 minutes
Feedback Hub Windows key + F Reporting new Explorer bugs, searching known issues, upvoting Attaches diagnostics with consent No reply; community and engineering triage
Microsoft Support site Browser Step-by-step articles, fix-it tools, known-issue pages No Immediate, self-serve

The verdict splits by problem type. Use a troubleshooter first for anything that looks like a standard failure — Explorer refusing to open at all, network locations timing out, search returning nothing. Use the Feedback Hub when you suspect a bug introduced by a recent update, because the search field there surfaces other people's reports and Microsoft's own acknowledgment notes. Use Get Help only when a person needs to intervene: activation errors, subscription confusion, or a support case you want logged against your account.

One caveat worth knowing: the Settings > System > Troubleshoot path changed in the 22H2 feature update, moving most individual troubleshooters behind an "Other troubleshooters" button. If you follow an older guide that says Settings > Update & Security > Troubleshoot, you're reading Windows 10 instructions — that page doesn't exist in Windows 11. The relocated list is shorter than it used to be, with several troubleshooters retired outright.

Restarting File Explorer When the Ribbon or Taskbar Freezes

This is the fix you'll reach for most often, and the sequence matters because the obvious method sometimes fails when Explorer is truly hung.

1: Press Ctrl + Shift + Esc to open Task Manager directly, bypassing the Ctrl + Alt + Delete screen. 2: If Task Manager opens in compact view, click More details at the bottom. 3: On the Processes tab, scroll to Windows Explorer — it sits under Apps, not Background processes. 4: Right-click it and choose Restart. The taskbar and desktop icons will blink out for two to five seconds, then return. 5: If Restart is greyed out, choose End task instead, then click File > Run new task, type explorer.exe, and press Enter.

Restarting the shell process does not close your open File Explorer windows' contents destructively — but unsaved work in apps launched from Explorer stays open, since only the shell process restarts. What it does clear is the thumbnail cache in memory and any stuck shell extension handlers, which is why it fixes the "folder opens but shows nothing" symptom so reliably.

Failure handling: if Explorer restarts and immediately hangs again, a third-party shell extension is the likely culprit. Right-click your Start button, open Terminal (Admin), and run Get-AppxPackage Microsoft.Windows.Explorer | Reset-AppxPackage to reset the package. If that returns an error, run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth, which repair the underlying system image. Neither command touches your personal files.

Running the Built-In Troubleshooters That Still Exist in Windows 11

Windows 11's troubleshooter list has quietly shrunk. As of the 23H2 and 24H2 branches, the surviving automatic troubleshooters include Network and Internet, Playing Audio, Printer, Windows Update, Bluetooth, Camera, Keyboard, Program Compatibility, and Video Playback. There is no dedicated File Explorer troubleshooter — a gap Microsoft has never filled, which is why the Get Help button feels like the only official door.

For Explorer-adjacent failures, the useful ones are Network and Internet (for mapped drives and network locations that won't open) and Windows Update (for Explorer components that failed to install). The Search and Indexing troubleshooter, which existed in Windows 10, was folded into the general search settings page; you now rebuild the index manually under Settings > Privacy & security > Searching Windows > Advanced Indexing Options.

Run each from Settings > System > Troubleshoot > Other troubleshooters and click Run beside the entry. The tool logs results to the Reliability Monitor — type "reliability" into Start and open View reliability history to see what it changed. That log is the single most underused diagnostic in Windows 11 and will tell you whether a fix actually applied or just reported success.

If a troubleshooter reports "Troubleshooting couldn't identify the problem," that isn't a dead end. It means the tool found no matching signature in its rules database. Note the timestamp and move to the Feedback Hub search, where you can look for reports posted in the same week — a strong signal that a recent update, not your machine, is at fault.

Finding Real Answers in the Feedback Hub With Windows Key + F

The Feedback Hub (Windows key + F) is where Explorer bugs actually get acknowledged. It has two halves: Feedback for reporting and searching, and Announcements for Microsoft's own posts. The search box at the top searches existing reports, and results show an upvote count and a status label — "Acknowledged," "In progress," "Fixed," or "Needs more info."

That status label is the payoff. When Microsoft's engineering teams confirm an Explorer regression, they tag the feedback item and often post a workaround in the comments. Searching terms like "explorer slow folder," "explorer crash right click," or "explorer ribbon missing" surfaces those threads faster than any web search, because the reports are dated and tied to specific Windows builds.

To report your own issue, click Give feedback, choose Problem or Suggestion, and describe it with the build number visible under Settings > System > About. You can attach a replay of your actions if you enable the recording option — this captures the exact click sequence and is genuinely useful to engineers, though it will record whatever is on screen, so close anything sensitive first.

Two caveats: you need to be signed in with a Microsoft account, and the hub does not notify you when an item you reported is fixed. Check back manually or watch the Announcements tab around monthly Patch Tuesday releases, when fix lists are posted.

Command-Line Repairs When Get Help Can't Diagnose the Problem

When the graphical channels run dry, four commands cover most Explorer corruption. Run them in an elevated Terminal, one at a time, and note the output — each reports what it found and fixed.

sfc /scannow — scans protected system files and replaces corrupted ones from a cached copy. Takes five to fifteen minutes and reports "did not find any integrity violations" when clean. DISM /Online /Cleanup-Image /RestoreHealth — repairs the component store that sfc draws from. Run this before sfc if sfc itself fails with error 0x800f081f. Get-AppxPackage Microsoft.Windows.Explorer | Reset-AppxPackage — resets the Explorer package to its default state without touching user data. Useful when the ribbon or navigation pane is missing entirely. chkdsk C: /scan — read-only volume check; add /f only after a reboot if errors are found, since it needs exclusive access.

The order matters: DISM first, then sfc, then the package reset. Running sfc against a broken component store is the most common reason people report "sfc found corrupt files but couldn't fix them" — the error is about the repair source, not your PC.

If all four come back clean and Explorer still misbehaves, create a new local administrator account and test there. A fresh profile isolates the problem to your user hive, which points at a corrupted shell registry key or a per-user setting rather than Windows itself. Migrating to the new profile is tedious but conclusive.

Known Explorer Bugs and Their Status as of Late 2026

File Explorer has accumulated a recognizable set of recurring defects across the Windows 11 lifecycle, and knowing which are acknowledged saves you from chasing phantom fixes.

The most-reported class involves the address bar and tab bar becoming slow to respond after waking from sleep, particularly on laptops with hybrid graphics. Another persistent complaint is the "Working on it" spinner appearing for several seconds when opening folders containing large numbers of video files, traced to thumbnail generation rather than file access. A third is right-click context menu lag on systems with many third-party shell extensions installed — the Windows 11 compact menu added a "Show more options" layer that re-invokes the legacy menu, doubling the extension load.

Microsoft's acknowledgment status for these shifts month to month, and the reference date for this article is November 12, 2026 — verify current status in the Feedback Hub's search rather than trusting a fixed list, since fix rollouts depend on your build and channel. What stays stable is the diagnostic approach: check the Feedback Hub first, then the Windows release health page on Microsoft's support site, then the reliability history on your own machine.

A version-specific note worth carrying: Windows 11 24H2 moved Explorer's tab handling into a separate process, which changed the failure mode when a tab crashes — the whole window no longer dies, but a single tab can go blank and need closing manually. If you're on 23H2 and reading a 24H2 workaround, the steps may not apply.

Reconnecting Mapped Drives and Network Locations Explorer Can't See

Network locations are where Explorer help requests cluster, because the failure is often outside Windows entirely. Explorer shows a red X on a mapped drive when the SMB session drops, but the drive letter persists in the registry and reconnects on next logon — usually.

Three fixes cover most cases. First, clear stale credentials: open Credential Manager from Start, choose Windows Credentials, and remove any entries for the server's hostname or IP. Explorer caches old passwords and will retry them silently, producing "access denied" errors that look like permissions problems.

Second, check that network discovery and file and printer sharing are enabled under Settings > Network & internet > Advanced network settings > Advanced sharing settings. Windows 11 defaults these off on networks it classifies as Public, and a misclassified home network is the single most common cause of "I can't see the other PC."

Third, if the drive maps but disconnects after sleep, open an elevated Terminal and run net use Z: \server\share /persistent:yes with your actual letter and path — the /persistent flag writes the mapping to your profile so it survives reboots. For NAS devices using SMB1 (common on older hardware), you may need to enable the SMB 1.0/CIFS client under Settings > Apps > Optional features > More Windows features — but only do that on a trusted LAN, since SMB1 is deprecated for security reasons.

Performance Tuning: Folder Options Most Users Never Open

Explorer's default settings favor visual richness over speed, and four toggles in File Explorer Options (accessible via the three-dot menu > Options) change folder-open latency measurably.

Under the General tab, set "Open File Explorer to" to This PC rather than Quick access — Quick access queries recent-file history on every launch, which stalls on machines with network drives in the recent list. Under the View tab, uncheck Show pop-up descriptions for folder and desktop items and Show preview handlers in preview pane; both trigger background parsing. In the same dialog, click Apply to Folders after adjusting a folder's view so the settings propagate.

The bigger win is thumbnail caching. If you browse folders of high-resolution images or video, Explorer generates thumbnails on demand and stores them in a database under your user profile. Clearing it — Disk Cleanup > Thumbnails, or deleting %LocalAppData%\Microsoft\Windows\Explorer\thumbcache_*.db while Explorer is closed — forces a clean rebuild that often resolves the endless spinner. It also costs you a slow first browse while the cache regenerates, so do it when you're not in a hurry.

If Explorer still feels heavy, check what's loaded at startup: Task Manager > Startup apps, and disable anything you don't recognize. Third-party thumbnail handlers for PDFs and RAW images are frequent offenders, and removing the associated app removes the handler.

FAQ

Does the Get Help button in File Explorer cost anything to use?

No — the Get Help app and its chat assistant are free for anyone running Windows 11, and chatting with the virtual assistant costs nothing and requires no subscription. Live-agent escalation is also free for Windows support itself; you'd only pay if the issue turns out to be a Microsoft 365 billing matter tied to a paid plan. Microsoft's consumer support policy states Windows support is included with the license, so there's no per-incident charge.

Why does Get Help only show me generic answers instead of fixing my Explorer problem?

Get Help is a chat front end, not a diagnostic engine — it cannot read your event logs, Explorer version, or the folder that failed, so it replies with scripted steps drawn from a general knowledge base. That's a deliberate design limit, not a bug, and it's why the tool works better for account and billing questions than for crash diagnosis. For system-specific faults, the Feedback Hub's search and the reliability monitor give you evidence the chat app never sees.

Is there a dedicated File Explorer troubleshooter in Windows 11?

No. Microsoft has never shipped a File Explorer-specific automatic troubleshooter in Windows 11, and the old Windows 10 Search and Indexing troubleshooter was removed rather than ported. The closest surviving tools are Network and Internet (for mapped drives) and Windows Update (for failed Explorer component installs), both reached through Settings > System > Troubleshoot > Other troubleshooters. For Explorer itself, the practical equivalents are the shell restart and the Appx package reset.

What's the difference between restarting File Explorer and resetting its package?

Restarting kills and relaunches the explorer.exe shell process, which clears in-memory state and stuck extension handlers in about two to five seconds without affecting installed settings. Resetting the package runs Reset-AppxPackage against Microsoft.Windows.Explorer, which restores the app's default configuration files and registry entries — heavier, slower, and occasionally needed when the ribbon or navigation pane is missing entirely. Try restart first; reset only if restart doesn't stick.

Can a corrupted user profile cause Explorer to crash even after running sfc and DISM?

Yes, and it's an underdiagnosed cause. System file repairs operate on Windows itself, not on your per-user registry hive, where Explorer's folder-view settings,Quick access history, and shell extension registrations live. Creating a second local administrator account and testing there takes about three minutes and conclusively separates profile corruption from system corruption — if Explorer behaves in the new profile, the fault is in your user hive, and migrating is the durable fix.

How long should I wait for a Feedback Hub report to get a fix?

There's no guaranteed timeline, and Microsoft doesn't commit to one for consumer reports. Acknowledged Explorer regressions typically appear in the release health notes within days to weeks of broad reporting, and fixes ship with monthly cumulative updates or the next feature update depending on severity. Check the Announcements tab after each Patch Tuesday rather than watching your individual report, which won't notify you when it's resolved.

Why does Explorer show a red X on a mapped drive that still works when I click it?

The red X reflects a failed status check at the moment Explorer painted the icon, usually because the SMB session was idle and had dropped. Clicking the drive forces a fresh connection, which succeeds, so the icon was stale rather than the mapping being broken. Setting the mapping as persistent with net use /persistent:yes and clearing stale Credential Manager entries reduces how often the false warning appears.