ANAVEM
Languagefr
Fix SMB Network Folder Refresh Issues – Windows 10/11 Server 2026
Fix GuideSMB_CACHE_DELAYSMB File Sharing

Fix SMB Network Folder Refresh Issues – Windows 10/11 Server 2026

Network shared folders not updating immediately due to SMB caching and offline files. Disable caching and adjust SMB client settings to force real-time folder refresh.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
March 18, 2026 12 min 0
SMB_CACHE_DELAYSMB File Sharing 5 methods 12 min
Instant Solution

The fastest fix is to disable SMB client caching using PowerShell. Run Set-SmbClientConfiguration -DirectoryCacheLifetime 0 -FileInfoCacheLifetime 0 as administrator to force immediate folder refresh without caching delays.

Understanding SMB Network Folder Refresh Issues

Network shared folder refresh problems are among the most common complaints in enterprise Windows environments. When users create, delete, or modify files on SMB shares, these changes may not appear immediately in File Explorer, causing confusion and workflow disruptions. The issue stems from Windows' aggressive caching mechanisms designed to optimize network performance, particularly the SMB client metadata cache and Offline Files feature.

The SMB Network Redirector, introduced in SMB v2.0, caches directory listings and file metadata to reduce network traffic between clients and servers. While this improves performance over slow connections, it can cause significant delays in folder refresh operations. By default, Windows maintains directory cache entries for 10 seconds and file information cache for similar periods, meaning new files may not appear until these cache intervals expire.

This comprehensive guide addresses the root causes of SMB folder refresh delays and provides proven solutions ranging from simple PowerShell commands to advanced registry modifications. Each method targets different aspects of the caching system, allowing administrators to choose the most appropriate solution based on their network environment and performance requirements.

Related: Microsoft confirms ongoing Windows 11 File Explorer flash

Related: KB5078938 — March 2026 Security Update for Windows 10

Related: Fix Windows 11 Context Menu Show More Options – File

Related: How to Add or Remove OneDrive from File Explorer Navigation

Diagnostic

Symptoms

  • New files in network folders take 3-4 minutes to appear in File Explorer
  • Manual refresh with F5 key doesn't show new files immediately
  • Files accessible via direct UNC path but not visible in folder view
  • Deleted files still appear in folder listing for several minutes
  • Renamed or moved files show old names or locations temporarily
  • Multiple users report inconsistent folder contents on shared drives
Analysis

Root Causes

  • SMB client metadata caching enabled with default 10-second refresh intervals
  • Offline Files feature caching network folder contents locally
  • DirectoryCacheLifetime and FileInfoCacheLifetime registry values set too high
  • Network Redirector component optimizing for slow connections
  • Shared folder caching mode set to automatic or manual instead of disabled
  • Large number of files causing SMB cache overflow and delayed updates
Resolution Methods

Solutions

01

Disable SMB Client Caching via PowerShell

This method disables SMB metadata caching on the client side to force immediate folder refresh.

  1. Open PowerShell as Administrator by right-clicking Start button and selecting Windows PowerShell (Admin)
  2. Check current SMB caching settings:
    Get-SmbClientConfiguration | Select-Object DirectoryCacheLifetime, FileInfoCacheLifetime, FileNotFoundCacheLifetime
  3. Note the current values (default is usually 10 seconds for DirectoryCacheLifetime)
  4. Disable directory and file info caching:
    Set-SmbClientConfiguration -DirectoryCacheLifetime 0 -FileInfoCacheLifetime 0 -Confirm:$false
  5. Restart the SMB client service to apply changes:
    Restart-Service -Name lanmanworkstation -Force
  6. Verify the changes took effect:
    Get-SmbClientConfiguration | Select-Object DirectoryCacheLifetime, FileInfoCacheLifetime
Pro tip: Setting cache lifetime to 0 disables caching entirely but may increase network traffic on slow connections.
02

Disable Offline Files on Shared Folders

Configure the server-side shared folder to prevent client-side offline caching.

  1. On the file server, open Server ManagerFile and Storage ServicesShares
  2. Right-click the problematic shared folder and select Properties
  3. Click the Settings tab, then Advanced button
  4. In the Advanced Sharing dialog, click Caching button
  5. Change caching mode to No files or programs from the shared folder are available offline
  6. Click OK to apply changes
  7. Alternatively, use PowerShell on the server:
    Set-SmbShare -Name "YourShareName" -CachingMode None
  8. Verify the setting:
    Get-SmbShare -Name "YourShareName" | Format-List CachingMode
Warning: This affects all users accessing the share and prevents offline access entirely.
03

Disable Offline Files Feature Completely

Disable the Windows Offline Files feature system-wide on client computers.

  1. Open Control PanelSync Center
  2. Click Manage offline files in the left panel
  3. In the Offline Files dialog, click Disable offline files
  4. Click OK and restart the computer when prompted
  5. For domain environments, use Group Policy:
    • Open Group Policy Management Console
    • Navigate to Computer ConfigurationAdministrative TemplatesNetworkOffline Files
    • Enable Allow or Disallow use of the Offline Files feature and set to Disabled
  6. Alternatively, disable via registry:
    Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\CSC" -Name "Start" -Value 4
  7. Restart the computer to apply registry changes
Pro tip: This method provides the most comprehensive solution but removes offline file capabilities entirely.
04

Adjust SMB Client Registry Settings

Manually configure SMB caching parameters through registry modification for fine-tuned control.

  1. Open Registry Editor by pressing Win + R, typing regedit, and pressing Enter
  2. Navigate to HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
  3. Create or modify the following DWORD values:
    • DirectoryCacheLifetime: Set to 0 (disables directory caching)
    • FileInfoCacheLifetime: Set to 0 (disables file info caching)
    • FileNotFoundCacheLifetime: Set to 0 (disables negative caching)
  4. Right-click in the right panel → NewDWORD (32-bit) Value
  5. Enter the parameter name and set the value to 0
  6. Repeat for all three parameters
  7. Close Registry Editor and restart the computer
  8. Verify settings using PowerShell:
    Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters" | Select-Object DirectoryCacheLifetime, FileInfoCacheLifetime
Warning: Always backup the registry before making changes. Incorrect modifications can cause system instability.
05

Configure SMB Protocol Version and Optimize Settings

Optimize SMB protocol settings and ensure proper version compatibility for better refresh performance.

  1. Check current SMB protocol versions in use:
    Get-SmbConnection | Select-Object ServerName, Dialect, Encrypted
  2. Verify SMB client configuration:
    Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
  3. Disable SMB1 if still enabled (security risk):
    Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart
  4. Configure advanced SMB client settings:
    Set-SmbClientConfiguration -RequireSecuritySignature $true -EnableSecuritySignature $true -Confirm:$false
  5. Set optimal buffer sizes for network performance:
    Set-SmbClientConfiguration -FileInfoCacheEntriesMax 0 -DirectoryCacheEntriesMax 0 -Confirm:$false
  6. Restart SMB services to apply all changes:
    Restart-Service -Name lanmanworkstation, lanmanserver -Force
  7. Test connectivity and verify SMB version:
    Test-NetConnection -ComputerName "YourFileServer" -Port 445
Pro tip: SMB 3.x provides better performance and security. Ensure both client and server support the same modern SMB version.
Validation

Verification

To confirm the fixes are working properly, perform these verification steps:

  1. Test immediate file visibility by creating a new file on the network share from another computer
  2. Refresh the folder view (F5) and verify the new file appears immediately
  3. Check SMB client settings: Get-SmbClientConfiguration | Select-Object DirectoryCacheLifetime, FileInfoCacheLifetime
  4. Verify offline files status in Control PanelSync CenterManage offline files
  5. Monitor network traffic using Get-SmbConnection to ensure active connections
  6. Test with multiple file operations (create, delete, rename) to confirm consistent behavior
If it still fails

Advanced Troubleshooting

If the above methods didn't resolve the issue, try these advanced troubleshooting steps:

  • Network connectivity issues: Run Test-NetConnection -ComputerName ServerName -Port 445 to verify SMB port accessibility
  • DNS resolution problems: Use IP addresses instead of server names, or flush DNS cache with ipconfig /flushdns
  • Antivirus interference: Temporarily disable real-time scanning on network folders to test if antivirus is causing delays
  • Large folder optimization: For folders with thousands of files, consider using Set-SmbClientConfiguration -DirectoryCacheEntriesMax 1024 instead of 0
  • Event log analysis: Check System and Application logs for SMB-related errors using Event Viewer
  • Network adapter settings: Disable power management on network adapters in Device Manager
  • Reset SMB configuration: Use Reset-SmbClientConfiguration to restore default settings if issues persist

Frequently Asked Questions

Why do new files take several minutes to appear in network folders?+
This delay is caused by SMB client-side caching mechanisms. Windows caches directory listings and file metadata for 10 seconds by default to reduce network traffic. Additionally, the Offline Files feature may cache folder contents locally. When files are created on the server, clients don't immediately refresh their cached view, causing the delay. The file exists and is accessible via direct UNC path, but won't appear in folder listings until the cache expires or is manually cleared.
Does disabling SMB caching affect network performance?+
Yes, disabling SMB caching will increase network traffic as clients must query the server for every folder refresh operation. However, the performance impact is usually minimal on modern networks with adequate bandwidth. For slow or unreliable connections, consider setting cache lifetimes to lower values (1-2 seconds) instead of completely disabling caching. Monitor network utilization after making changes to ensure acceptable performance levels.
Can I apply these fixes through Group Policy for multiple computers?+
Yes, several methods can be deployed via Group Policy. For SMB client settings, use Computer Configuration → Administrative Templates → Network → Lanman Workstation to configure caching parameters. Offline Files can be controlled through Computer Configuration → Administrative Templates → Network → Offline Files. Registry-based solutions can be deployed using Group Policy Preferences → Windows Settings → Registry. PowerShell commands can be executed through startup scripts or scheduled tasks managed by Group Policy.
What's the difference between server-side and client-side caching?+
Server-side caching refers to the shared folder's caching mode setting, which determines whether clients can cache the folder's contents offline. This is configured on the file server and affects all users accessing the share. Client-side caching refers to the SMB client's metadata cache (DirectoryCacheLifetime, FileInfoCacheLifetime) and Offline Files feature on individual workstations. Both can cause refresh delays, but client-side caching is more commonly the culprit for immediate refresh issues.
Will these changes affect other network applications or services?+
The changes primarily affect File Explorer and applications that rely on standard Windows file system APIs for network access. Most applications will benefit from more immediate file visibility. However, some backup software or file synchronization tools that depend on caching for performance optimization might experience increased network usage. Database applications and services typically use direct network connections and won't be affected. Always test changes in a non-production environment first.
Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...