File Explorer not responding — freezing when you click a folder, hanging for 30 seconds before showing contents, or crashing and restarting when you navigate certain locations — is a particularly disruptive problem because Explorer is the foundation for navigating Windows. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
The fastest triage: does it freeze everywhere, or only in specific locations? If it only freezes when you open a specific folder (like a network share, an external drive, or a folder with thousands of files): the problem is loading that specific location’s contents, not Explorer itself. If it freezes everywhere, including the Desktop and basic local folders: Explorer’s shell has a broader problem.
Restart Windows Explorer — the immediate fix
When Explorer is frozen: Ctrl+Shift+Esc → Task Manager → find “Windows Explorer” in the list → right-click → Restart. This terminates and relaunches Explorer in one step without losing files you have open (they close, but no data is lost). After restarting, Explorer usually works normally again. If it freezes again within a few minutes of restarting: the underlying cause is still present, and restarting is only a temporary fix.
Quick Access and Recent Files
Windows Explorer’s Quick Access panel loads thumbnails and metadata for recently accessed files on every launch. If Quick Access contains files from a disconnected network share, a removed USB drive, or a path that no longer exists: Explorer waits for those locations to time out before loading, creating 10–30 second hangs specifically on startup or when clicking the Home/Quick Access section.
Right-click each pinned item in Quick Access → Remove from Quick Access for any that point to locations you no longer use. Also: File Explorer Options → General → “Open File Explorer to:” → change from “Quick Access” to “This PC.” This makes Explorer open directly to drives rather than loading the recent files panel. Quick Access can stay populated; it just won’t load on every Explorer launch.
Shell extensions — the hidden cause
Third-party shell extensions (context menu items, thumbnail providers, file preview handlers) run inside the Explorer process. When one of these extensions is buggy or outdated: it crashes Explorer’s shell, which either freezes or terminates and restarts the entire Explorer process.
Telltale signs: Explorer crashes specifically when right-clicking files or folders, when previewing specific file types in the preview pane, or when navigating to folders containing specific file formats (RAW images, video files, 3D models).
ShellExView (NirSoft, free) lists every registered shell extension with its status. Sort by Company → disable all non-Microsoft entries → right-click on the desktop to test. If Explorer stops freezing: re-enable extensions in groups of 3–4, testing after each group, until the responsible extension is identified. Removing or updating that extension permanently fixes the issue.
Thumbnail generation and previews
Explorer generates thumbnails for images and videos as you browse. When a folder contains thousands of high-resolution images, RAW photos, or large video files: thumbnail generation can overwhelm Explorer and cause it to appear frozen. The actual work is happening — it just takes long enough that Explorer becomes temporarily unresponsive.
Test: disable thumbnails. View → Options → Change folder and search options → View tab → check “Always show icons, never thumbnails.” After applying: navigate to the previously-freezing folder. If it now loads instantly: thumbnail generation was the bottleneck. This is a workaround — the underlying issue is usually a slow drive or a specific file type where the thumbnail provider is inefficient.
Corrupted system files
Explorer is a system component. Corrupted Windows system files cause Explorer to malfunction in ways that look like software bugs:
sfc /scannowAdministrator Command Prompt. If SFC reports repairs: the corruption was fixed. Restart and test. If SFC finds errors it can’t fix: DISM first → then SFC:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowNetwork locations and mapped drives
If Explorer freezes when navigating “This PC” or when waiting for the folder tree to populate: disconnected mapped drives are a very common cause. Explorer tries to contact each mapped drive location before finishing the display, and each unavailable drive adds 5–30 seconds of timeout. This happens particularly when a work laptop is used at home and corporate mapped drives aren’t reachable.
Remove mapped drives that are no longer in use: right-click in File Explorer → Disconnect Network Drive → remove the relevant drives. If you need them for work but they’re unavailable at home: the drives persist but the timeout on unavailability is the cost. The workaround: don’t use “This PC” view — navigate directly via the address bar to locations you know are available.
Registry corruption affecting Explorer
Win + R → regedit → HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorer → look for any keys with unusual or malformed values. Specifically: “ShellState” and “Bags” keys store Explorer window state and sometimes accumulate corrupted data. Deleting the “Bags” key (Explorer recreates it automatically) often resolves persistent Explorer configuration issues including freezing.
For a cleaner approach: create a new Windows user account → log in as the new user → test File Explorer. If it works without freezing: the issue is specific to the original user’s profile. The SFC/DISM approach repairs system files; the new user test confirms whether user-profile data is the problem.
Our guide on Windows 11 disk usage covers the disk I/O and indexing causes that slow Explorer when navigating large directories. For the shell extension conflicts that affect right-click menus alongside Explorer stability, our context menu guide covers ShellExView usage in depth. Microsoft’s File Explorer troubleshooting covers the Windows Explorer process isolation setting that runs shell extensions in a separate process, preventing a crashed extension from taking down the entire Explorer session.
File Explorer crashes on specific folder types
Explorer crashes when entering specific folders: the crash is triggered by Explorer trying to load something in that folder — usually a corrupted file, a file type with a broken preview handler, or a folder with a problematic desktop.ini customisation.
Test: hold Shift while clicking on the folder → this bypasses some shell extension hooks. If the folder now opens: a shell extension for a file type in that folder is causing the crash. Identify which file type by the folder’s contents. Use ShellExView to disable the thumbnail provider or context menu handler for that file type.
For a folder that crashes Explorer no matter how you access it: open a Command Prompt → navigate to the parent directory using cd → list the folder’s contents with dir foldername → without loading Explorer’s visual layer, you can identify and delete or move the problematic file.
Windows Search indexing conflict
The Windows Search indexer runs in the background and accesses files Explorer is also trying to show. When the indexer is actively building or rebuilding its index (after a Windows update, after adding many new files): both the indexer and Explorer compete for disk access, causing Explorer to appear frozen while waiting for disk reads.
Check: Task Manager → Services tab → look for “WSearch” → if it’s consuming high CPU or disk: the indexer is active. This state is temporary — once indexing completes, Explorer performance returns to normal. If this happens consistently: Control Panel → Indexing Options → Modify → reduce the indexed locations to only what you actually search (remove large data drives, leave only Documents and Desktop). Fewer indexed locations = faster indexing and less Explorer competition.
Antivirus real-time scanning
File Explorer accesses files as you navigate. Antivirus real-time scanning intercepts these accesses to scan files before Explorer reads them. When scanning large files (database files, VM images, archive files) or many small files rapidly: the scan hold lock prevents Explorer from completing its read, causing the folder to hang.
Add frequently-accessed large folders (development directories, media libraries, VM storage folders) to the antivirus exclusion list. This prevents real-time scanning of those locations while still scanning files when they’re first created or changed. The security tradeoff is acceptable for locations containing files you’ve already verified are safe.
File Explorer options and view preferences
View → Options → Change folder and search options → multiple settings here affect performance:
- Search tab: “When searching non-indexed locations, include compressed files” — disabling this reduces search overhead in large folders
- View tab: “Show pop-up description for folder and desktop items” — pop-ups require metadata loading; disabling reduces the number of operations per navigation
- General tab: “Show recently used files in Quick Access” and “Show frequently used folders in Quick Access” — disabling both prevents the usage tracking that occasionally causes Quick Access loads to hang
External drives and sleep spinup
Explorer pauses when a drive it’s navigating or needs to read from is spinning up from sleep. External HDDs typically spin down after 10–15 minutes of inactivity. When Explorer accesses a folder on such a drive after the spindown: it waits 5–15 seconds for the drive to spin back up to operating speed. This looks like Explorer freezing but is actually normal drive spinup behaviour.
Options: use the drive’s power management software to increase its spindown threshold (keeping it active longer), or switch to an SSD-based external drive (no spinup delay). The Disk Management console shows drive status — “Sleeping” confirms the spinup scenario. Clicking elsewhere while waiting (don’t close Explorer) and the folder usually loads normally once the drive is at full speed.
Windows 11 File Explorer vs old Explorer
Windows 11 introduced a redesigned File Explorer (tabs support, redesigned toolbar). Some older shell extensions and third-party file manager tools don’t fully support the new Explorer. If Explorer freezes only after upgrading to Windows 11 or after a major feature update: a shell extension that was compatible with Windows 10’s Explorer may be incompatible with Windows 11’s version.
ShellExView → sort by company → look for extensions installed at the same time as or before the Explorer problems started. Third-party file compression tools (7-Zip, WinRAR), cloud storage integrations (OneDrive, Dropbox, Google Drive), and file sync tools are the most common sources of Windows 11 Explorer incompatibility because they hook into Explorer’s shell at multiple layers.
OneDrive sync and Explorer freeze
OneDrive’s “Files on Demand” feature shows cloud-only files in Explorer without downloading them. When Explorer generates thumbnails or reads metadata for cloud-only files: each file requires a network request. On slow connections or when many cloud-only files are in the same folder: this creates the characteristic Explorer freeze that appears every time you navigate to that folder.
Options: right-click the OneDrive folder → “Always keep on this device” for folders you access frequently (downloads them all locally, eliminating the per-file network requests). Or: in OneDrive settings → disable “Files On-Demand” entirely (makes OneDrive behave like it did before, downloading everything to local storage). The tradeoff is storage space vs Explorer speed in cloud-heavy folder structures.
Running Explorer in a separate process
By default, all Explorer windows run in the same process. When one Explorer window’s shell extension crashes: it takes all open Explorer windows down with it. File Explorer Options → View tab → check “Launch folder windows in a separate process.” This creates a new process for each new Explorer window. Slightly higher memory usage but a crashing extension in one window doesn’t affect other open windows — significantly improves crash isolation.
For machines that regularly have Explorer issues: enabling “Launch folder windows in a separate process” is worth doing preventatively even before issues appear. It’s in the View tab of Folder Options and has essentially no downside on modern machines with 8+ GB RAM. The crash isolation it provides is genuinely useful when shell extensions from various installed software accumulate over years.
The practical order for File Explorer freezing: restart Explorer from Task Manager (immediate relief) → check Quick Access for stale network paths → disable thumbnails to confirm or rule out thumbnail generation → use ShellExView to identify shell extension conflicts → SFC/DISM for system file corruption. Each step takes under 5 minutes except ShellExView (which may take 15–20 minutes to binary-search through extensions). The majority of Explorer freezing is resolved by steps 1–3; the extension investigation is for persistent problems where those steps give temporary relief but the freeze returns.
One more situation worth calling out: File Explorer that was working fine and suddenly started freezing after installing new software — particularly compression tools, image viewers, file sync utilities, or development tools — almost certainly has a new shell extension as the culprit. The timing correlation is the most useful diagnostic clue available and is more informative than any settings investigation. Use ShellExView, sort by Date Modified, and look at what was added on the day the problems started. Disabling that specific extension (not all extensions) is usually a 60-second fix once the cause is identified by date correlation. Related: Windows 11 File Explorer Slow.
