F5 or right-click and select Refresh, the Windows shell notification queue or folder view cache has stalled. In both Windows 10 and Windows 11, you can resolve this by restarting the explorer.exe shell process in Task Manager, resetting Folder Options and cached view templates (BagMRU and Bags), and isolating unreachable network shares pinned to Quick Access that block local directory change notifications.
Prerequisites and Scope
Before modifying File Explorer settings or clearing view caches, review the following requirements and scope boundaries:
- Supported operating systems: Windows 10 (all supported consumer and enterprise builds, 22H2) and Windows 11 (versions 22H2, 23H2, 24H2, and 25H2).
- Account permissions: Standard user permissions are sufficient to restart File Explorer, reset folder views, and clear Quick Access history. Administrator privileges are required only if you need to adjust Server Message Block (SMB) client directory caching for network shares or run system file repair tools.
- Active file operations: Pause or finish any active file copies, archive extractions, or downloads before restarting the Windows Explorer process, as terminating
explorer.exeabruptly closes open File Explorer windows and cancels in-progress shell transfers. - View customization loss: Resetting folder views restores default sort orders, icon sizes, grouping layouts, and column widths across your profile. Make note of any specialized column layouts you rely on before proceeding.
Isolate Whether the Issue Affects Local Folders or Network Locations
Before changing settings, determine whether the refresh failure is confined to a mapped network drive or affects local storage (such as C:\Users\<username>\Desktop or Documents), and whether an offline network path is stalling local refreshes.
- Open File Explorer (
Win + E) and navigate to a purely local directory that is not synced by cloud storage, such asC:\Tempor a newly created test folder on yourC:drive. - Right-click an empty area inside the folder, select New > Text Document, type a name, and press
Enter. - Delete the text document you just created and observe whether it disappears immediately without pressing
F5. - Examine the left-hand Navigation pane under Quick access (Windows 10 and Windows 11) or Home (Windows 11). Look for any pinned folders that point to a mapped network drive, a NAS device, an SMB share (
\\server\share), or an FTP location.- When Windows cannot reach a network share pinned to Quick Access—for example, when using a work laptop away from the office network or when a home NAS is asleep—File Explorer's background shell thread can hang while polling the offline path. This prevents change notifications (
SHChangeNotify) from updating even local folders.
- When Windows cannot reach a network share pinned to Quick Access—for example, when using a work laptop away from the office network or when a home NAS is asleep—File Explorer's background shell thread can hang while polling the offline path. This prevents change notifications (
- If you see an offline or slow network folder pinned in the navigation pane, right-click it and select Unpin from Quick access.
- If right-clicking the unreachable network shortcut causes File Explorer to freeze before the context menu appears, clear the Quick Access and Recent items cache directly:
- Press
Win + Rto open the Run dialog. - Type
%AppData%\Microsoft\Windows\Recent\AutomaticDestinationsand pressEnter. - Select the file
f01b4d95cf55d32a.automaticDestinations-ms(which stores pinned Quick Access folders) and delete it, or delete all files in%AppData%\Microsoft\Windows\Recentto reset recent items completely.
- Press
Restart the File Explorer Process
If the Windows shell notification handler is stuck in memory for your current sign-in session, restarting the explorer.exe process reinitializes the desktop, taskbar, and directory watcher threads without requiring a full system reboot.
Restart Windows Explorer Using Task Manager
- Press
Ctrl + Shift + Escto open Task Manager. - If Task Manager opens in compact mode (Windows 10), select More details at the bottom of the window.
- On the Processes tab, locate Windows Explorer (listed under the Apps section if File Explorer windows are open, or under Windows processes further down the list).
- Select Windows Explorer, then click Restart (Windows 10, bottom-right corner) or Restart task (Windows 11, top command bar), or right-click Windows Explorer and select Restart.
- Wait two to five seconds while the taskbar and desktop icons briefly disappear and reload.
Alternate Method: Restart File Explorer via Command Prompt or PowerShell
If Task Manager is unresponsive or if restarting the process from the graphical interface causes the taskbar to hang, force-restart the shell from a command prompt:
- Press
Ctrl + Shift + Escto open Task Manager. - Click Run new task (Windows 11 top bar) or File > Run new task (Windows 10 menu bar).
- Type
cmd.exeand pressEnter. - Run the following command to terminate all running instances of the shell and immediately launch a fresh instance:
taskkill /f /im explorer.exe && start explorer.exe - Close the Command Prompt window once your taskbar reappears.
Reset Folder Views and Folder Options to Defaults
When File Explorer fails to refresh across reboots, the cause is often a corrupted folder view state or an exhausted view cache. Windows stores custom view settings for individual folders; if a folder's cached view template becomes damaged, File Explorer may fail to redraw the window when contents change.
Warning: Clicking Reset Folders and Restore Defaults clears your custom view templates (such as Details vs. Large Icons, custom columns, and Group By preferences) across all folders using that folder type template and clears your recent file/folder history in Quick Access.
Reset Folder Options in Windows 11
- Open File Explorer (
Win + E). - On the top command bar, click See more (the three-dot
...menu icon) and select Options to open the Folder Options dialog. - On the General tab:
- Under the Privacy section, click Clear next to Clear File Explorer history.
- Click Restore Defaults at the bottom of the dialog, then click Apply.
- Switch to the View tab:
- Under Folder views, click Reset Folders.
- When prompted with Do you want all folders of this type to match this folder's view settings?, click Yes.
- Click Restore Defaults at the bottom of the View tab.
- In the Advanced settings list on the View tab, scroll down to the Navigation pane section, check Expand to open folder if it is unchecked (Microsoft Q&A community reports indicate that toggling this setting resolves a shell auto-refresh bug in recent Windows 11 builds), and click Apply.
- Switch to the Search tab:
- Click Restore Defaults, then click Apply and OK.
- Restart the Windows Explorer process in Task Manager using the steps in the previous section to commit the clean view state.
Reset Folder Options in Windows 10
- Open File Explorer (
Win + E). - Click the View tab on the top ribbon, then click the Options button on the far right (or select Options > Change folder and search options).
- On the General tab:
- Under Privacy, click Clear next to Clear File Explorer history.
- Click Restore Defaults, then click Apply.
- Switch to the View tab:
- Under Folder views, click Reset Folders and click Yes at the confirmation prompt.
- Click Restore Defaults at the bottom of the window, then click Apply.
- Switch to the Search tab:
- Click Restore Defaults, then click Apply and OK.
- Restart Windows Explorer in Task Manager.
Alternate Method: Clear Corrupted ShellBags View Cache via Command Line
The graphical Reset Folders button resets the template for the currently selected folder type (such as General Items or Pictures), but it does not always purge corrupted per-folder view entries stored in the Windows Registry (BagMRU and Bags, commonly known as ShellBags). Windows maintains a hard limit of 5,000 saved folder views; once this table fills up or becomes corrupted, individual folders stop saving view states or refreshing properly.
Warning: Editing or deleting registry keys incorrectly can cause user profile instability. The commands below modify only the current user's (HKCU) saved folder view layout keys and do not affect system files or personal data. To back up these keys before deleting them, runreg export "HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU" "%UserProfile%\Desktop\BagMRU-backup.reg"andreg export "HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags" "%UserProfile%\Desktop\Bags-backup.reg"in Command Prompt. Double-clicking those.regfiles restores your previous folder views.
- Open Command Prompt (
Win + R, typecmd, and pressEnter). - Run the following commands one at a time to delete the per-folder view cache and restart the Windows shell:
Code:reg delete "HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU" /f reg delete "HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags" /f taskkill /f /im explorer.exe && start explorer.exe - Windows automatically rebuilds clean
BagMRUandBagsregistry keys as soon asexplorer.exerestarts.
Verify That Automatic Refresh Is Working
After restarting File Explorer and resetting your folder views, test the shell notification pipeline across both the Desktop and standard folders:
- Open File Explorer and go to your Documents or Downloads folder.
- Right-click inside the folder, select New > Folder, and confirm that
New folderappears immediately with its name highlighted for editing. - Type
RefreshTestand pressEnter. Confirm the new name displays immediately without pressingF5. - Press the
Deletekey whileRefreshTestis selected. Confirm the folder disappears from the view immediately. - Repeat the same test directly on your Windows Desktop by right-clicking the desktop background, creating a new folder, renaming it, and deleting it.
Troubleshooting Persistent Refresh Failures
If File Explorer still requires a manual F5 refresh after restarting the shell and clearing folder views, match your symptoms to the specific failure modes below.
Symptom: Local Folders Refresh Normally, but Network Shares Do Not Update
If local drives (C:) update immediately when you add or delete files, but mapped network drives or UNC shares (\\server\share) show stale directory listings when files are modified by another user or application, the Windows SMB client metadata cache is holding onto cached directory enumeration data. By default, Microsoft's SMB client caches directory metadata for 10 seconds (DirectoryCacheLifetime) when directory leases are unavailable or not supported by a third-party NAS/Samba server.
Warning: Disabling SMB client directory metadata caching forces your PC to query the remote file server every time a directory is enumerated. While this resolves stale folder views on network shares, it increases SMB network traffic and can slow down browsing in network folders that contain thousands of files. Record your current settings before changing them so you can roll them back if network browsing slows down.
- Right-click the Start button and select Terminal (Admin) or Windows PowerShell (Admin).
- Check your current SMB client cache lifetimes by running:
Get-SmbClientConfiguration | Select-Object DirectoryCacheLifetime, FileInfoCacheLifetime, FileNotFoundCacheLifetime
(By default,DirectoryCacheLifetimeis10,FileInfoCacheLifetimeis10, andFileNotFoundCacheLifetimeis5.) - To disable SMB directory and file metadata caching so network shares reflect changes immediately, run:
Set-SmbClientConfiguration -DirectoryCacheLifetime 0 -FileInfoCacheLifetime 0 -FileNotFoundCacheLifetime 0 -Force
(This cmdlet updates the correspondingREG_DWORDvalues underHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parametersimmediately without requiring a system restart.) - Rollback: If disabling the SMB cache causes noticeable lag when opening large network directories, restore the Windows default cache lifetimes by running the following command in an elevated PowerShell window:
Set-SmbClientConfiguration -DirectoryCacheLifetime 10 -FileInfoCacheLifetime 10 -FileNotFoundCacheLifetime 5 -Force
Symptom: Only Cloud-Synced Folders (OneDrive, Dropbox, iCloud) Fail to Refresh
If folders outside your cloud storage path (C:\Temp) refresh automatically, but your Desktop, Documents, or Pictures folders lag behind or require F5, the cloud sync client's shell icon overlay handler is blocking the thread.
- Check the OneDrive (or third-party sync client) icon in the system tray (notification area). If it shows Syncing... or Processing changes across thousands of small files, shell refresh events in synced folders will queue behind the sync engine.
- Pause syncing temporarily by clicking the OneDrive cloud icon in the system tray, clicking the Help & Settings gear icon, and selecting Pause syncing > 2 hours.
- Test creating and deleting a file in the affected folder. If pausing sync resolves the refresh delay, allow the sync client to finish indexing or uncheck high-churn folders (such as developer build directories) from the sync client's folder backup list.
Symptom: File Explorer Windows Hang or Fail to Refresh When Third-Party Context Menus Are Installed
Third-party shell extensions—such as file archivers, PDF utilities, cloud drives, or version-control overlays like TortoiseGit—run directly inside the explorer.exe process. A poorly coded shell extension can block the main window thread or swallow change notifications. Isolate each window in its own process to prevent background shell hangs:
- Open File Explorer and open Folder Options (See more
...> Options in Windows 11, or View > Options in Windows 10). - Select the View tab.
- Under Advanced settings, scroll down and check Launch folder windows in a separate process.
- Click Apply and OK.
- Rollback: If you want to revert this setting later to conserve a small amount of system memory, return to the View tab in Folder Options, uncheck Launch folder windows in a separate process, and click Apply.
Symptom: System-Wide Shell Corruption Persists Across All User Profiles
If creating a new local Windows user account still results in File Explorer failing to refresh local folders, core Windows shell libraries may be damaged. Repair the component store and system files:
- Right-click the Start button and select Terminal (Admin), Command Prompt (Admin), or Windows PowerShell (Admin).
- Run the Deployment Image Servicing and Management (DISM) tool to repair the Windows component store:
DISM.exe /Online /Cleanup-image /Restorehealth - Once DISM reports that the restore operation completed successfully, run the System File Checker:
sfc /scannow - Restart your computer after the scan completes and test creating, renaming, and deleting a file in File Explorer.