Start With a Restart to Fix File Explorer Not Responding in Australia
Restart Windows Explorer through Task Manager first. That single move fixes the freeze in most cases because it reloads the shell process cleanly without touching your files. If it stops responding again within minutes, reboot the PC, then run DISM followed by SFC to check for corrupted system files. Cache clearing and shell extension checks come next if the freezing keeps coming back.
TL;DR:
Clearing the File Explorer caches and rebuilding the search index can fix freezing issues caused by corrupted cache data or a bloated search database.
Restarting Windows Explorer from Task Manager or performing a full system reboot often solves simple shell process freezes, with reboots needed when multiple instances are affected.
Disabling third-party shell extensions and running a clean boot can identify and eliminate faulty software causing context menu or search-related crashes.
Running DISM and SFC in the correct order repairs corrupted system files that can lead to unresponsive Explorer, especially after failed updates or malware infections.
Persistent freezing despite software fixes may indicate hardware faults or deep system corruption, necessitating professional diagnosis and possibly in-person repair services.
Table of Contents
Quick fixes: restart Windows Explorer and reboot your PC
A frozen File Explorer is almost always a shell process problem, not a hardware one, which is why restarting it works so often. Stopping and restarting explorer.exe fully reloads the shell and clears whatever internal state got stuck, rather than just closing a window and hoping the same fault doesn’t reappear, according to HowToGeek.
Here’s the order to work through:
Open Task Manager (Ctrl+Shift+Esc).
Find “Windows Explorer” in the Processes list.
Right click it and select Restart.
Wait a few seconds for your taskbar and desktop icons to reappear.
If Task Manager itself feels sluggish or Explorer won’t respond to the restart command, open a Command Prompt and run taskkill /f /im explorer.exe, followed by start explorer.exe. This forces the process to end and relaunches it fresh.
Choose a full reboot instead when multiple Explorer windows are frozen at once, or when the crash keeps repeating within the same session. A restart from Task Manager fixes a single stuck instance. A full reboot clears memory leaks, stuck drivers, and background services that a shell restart can’t reach. You’ll know it’s worked when folders open instantly, the taskbar responds to clicks, and right-clicking a file shows the context menu without delay.
Clear File Explorer caches and rebuild the search index
Three caches cause a disproportionate share of freezing complaints: Quick Access history, thumbnails, and icons. Clearing them takes a few minutes and often solves problems that look far more serious than they are.
Open File Explorer, go to the three-dot menu or Options, then General, and click “Clear” under Privacy to wipe Quick Access history.
Use Disk Cleanup (search for it in the Start menu) and tick “Thumbnails” to clear that cache in one pass.
Delete the iconcache files manually if icons look broken or Explorer stutters when scrolling folders, forcing Windows to rebuild them from scratch.
Pro Tip: Thumbnails will load a little slower for the first browse or two after clearing the cache. That’s Windows rebuilding them in the background, not a sign something’s gone wrong.
If the freezing happens specifically when you search for files, the problem is likely a bloated or corrupted search index rather than the shell itself. Go to Control Panel, then Indexing Options, then Advanced, and click Rebuild. Depending on how many files you have, a rebuild can take anywhere from a few minutes to several hours, so start it before you step away rather than expecting an instant result. Practitioners have also found that clearing thumbnail and icon caches resolves crashes that survive even after a full system file repair, which makes it worth doing early rather than as a last resort.
Disable third-party shell extensions and try a clean boot
If Explorer crashes specifically when you right-click a file or folder, a third-party context menu handler is a common culprit. Tools you’ve installed over the years, cloud sync clients, archive utilities, old antivirus software, all hook into that right-click menu, and a broken one can freeze the entire shell.
Download ShellExView, a free diagnostic tool that lists every context menu handler installed on your PC.
Sort by “Company” and disable everything that isn’t from Microsoft, working in small groups rather than all at once.
Restart Explorer after each group and test the right-click menu.
Once you find the culprit, leave it disabled or uninstall the software it belongs to.
Disabling extensions in groups rather than individually saves time when there are dozens installed, and re-enabling unaffected groups afterwards means you don’t lose functionality you actually wanted, a method backed by Microsoft Q&A troubleshooting guidance.
If that doesn’t isolate it, run a clean boot: open msconfig, select “Selective startup,” untick “Load startup items,” then go to Services and tick “Hide all Microsoft services” before disabling everything left. Reboot, test Explorer, then reintroduce items in batches. Never disable anything listed as a Microsoft service. Once you find the offender, re-enable everything else.
Run DISM and SFC to repair system files
Corrupted system files are a well documented cause of Explorer becoming unresponsive, and Microsoft’s own guidance is specific about the order to run repairs in. Run DISM first, because it repairs the underlying Windows image that SFC then relies on to fix individual files. Running SFC first, on a damaged image, often produces the same errors again.
Open an elevated Command Prompt and run these in order:
DISM.exe /Online /Cleanup-image /Restorehealth, then wait for it to finish (this can take 10 to 20 minutes).
sfc /scannow, which scans and replaces damaged system files.
You’ll see one of three outcomes: no integrity violations found, violations found and repaired, or violations found that couldn’t be repaired. That third result usually means booting into Safe Mode and running SFC again, or using System Restore to roll back to a point before the fault appeared, a sequence Microsoft recommends directly for exactly this symptom. If you end up contacting support, note the exact wording of any error and how long each scan took.
Check mapped drives and external devices for timeouts
If Explorer freezes specifically when you open “This PC” or expand a network location, the fault is likely outside Windows altogether. A mapped drive that’s connected but unreachable, say your NAS was rebooting, or your Wi-Fi dropped, forces Explorer to wait for a network timeout before it gives up.
Watch for a pause lasting around half a minute when opening This PC or expanding a mapped drive, which points to a mapped share Explorer can’t reach, a known Windows behaviour.
Disconnect mapped drives by running net use * /delete in Command Prompt, or right-click the drive under This PC and select Disconnect.
Test Explorer immediately after disconnecting. If it opens instantly, the mapped drive was the cause.
Unplug external USB drives temporarily and retest; a failing external drive can hang Explorer the same way a bad network share does.
Update your NAS firmware or refresh saved network credentials if the mapped drive keeps dropping out.
Check for Windows updates and known Explorer bugs
Sometimes the fault isn’t yours to fix at all. Microsoft occasionally ships a cumulative update that breaks Explorer for a subset of devices, and the fix is simply installing the follow-up patch.
Go to Settings, then Windows Update, and install anything pending, including optional driver updates.
Check Device Manager for outdated display or network adapter drivers, since both interact heavily with Explorer’s rendering and network browsing.
Microsoft documented one such case where a cumulative update, tracked as KB5072911, caused Explorer and other XAML-based apps to fail on some devices, later resolved by KB5095093.
If you installed an update right before the freezing started, uninstall it under Settings, Windows Update, Update History, “Uninstall updates,” and wait for Microsoft’s fix rather than reinstalling immediately.
Create a new user profile to test for corruption
If you’ve cleared caches, disabled extensions, and run every repair command with no luck, the corruption might sit inside your specific Windows user profile rather than the system itself. Every account has its own registry hive and settings folder, and either can develop faults that a system-wide repair simply can’t touch.
Create a new local account through Settings, then Accounts, then “Other users,” and add a new account. Sign into it and open File Explorer straight away. If it runs smoothly with no freezing, the fault lives in your original profile’s settings, not in Windows itself.
That narrows your options considerably. You can migrate your files, browser bookmarks, and desktop shortcuts across to the new profile and adopt it permanently, which is tedious but guaranteed to work. Or you can try repairing the old profile by resetting specific folders, like Explorer’s saved window layouts and taskbar pins, though this is hit and miss. Many users find it faster to just move house digitally rather than chase down exactly which setting went bad.
If the new profile freezes too, you’ve just ruled out user-specific corruption entirely, which is useful information in its own right. It tells you the fault sits somewhere in Windows itself, a driver, a shell extension not tied to any one account, or damaged system files. That’s your cue to go back to DISM and SFC, or move on to checking your disk for physical or file system faults.
Check disk and file system integrity with chkdsk
A failing hard drive or a corrupted file system table can make Explorer stall every time it tries to read folder contents, and no amount of cache clearing will fix that. This is the check worth running if freezing started suddenly, especially alongside other odd symptoms like files disappearing or folders that won’t rename.
Open an elevated Command Prompt and run chkdsk C: /f /r. The /f flag fixes file system errors, and /r locates bad sectors and recovers readable information from them. Because your system drive is in active use, Windows will ask to schedule the scan for the next restart rather than running it live. Confirm, then reboot.
The scan runs in five stages and can take anywhere from a few minutes to well over an hour, depending on drive size and how many errors it finds. Don’t interrupt it. If chkdsk reports and fixes errors, that’s a strong sign your file system, not Explorer itself, was the actual source of the freezing. If it reports bad sectors specifically, that’s a hardware warning sign worth taking seriously. A drive throwing bad sectors tends to get worse, not better, and it’s worth backing up important files immediately regardless of whether Explorer starts behaving normally afterwards.
You can also run chkdsk without the /f /r flags first, as a read-only check, if you just want to see the current state of the drive without committing to a scheduled repair scan.
Examine Event Viewer logs for specific errors
If the freezing keeps returning despite every fix so far, Event Viewer will usually tell you exactly what’s failing at the moment Explorer hangs, rather than leaving you guessing.
Open Event Viewer by searching for it in the Start menu, then expand Windows Logs and click Application. Look for red “Error” entries timestamped close to when Explorer last froze or crashed. The Source column often names the exact component at fault, whether that’s Explorer itself, a specific driver, or a background service. Click any relevant entry and check the General tab for the full error description and an event ID number.
That event ID is worth writing down or searching separately, since specific IDs point to specific causes: a particular ID might indicate a driver conflict, another might point to disk errors, and another might flag a corrupted application data file. Also check the System log, under the same Windows Logs section, for hardware or driver level errors that wouldn’t show up under Application.
If you’re planning to ask for help, whether from a forum or a technician, screenshot the exact error message, the Source, and the Event ID rather than describing it from memory. It’s the single most useful piece of diagnostic information you can hand over, and it often cuts a support conversation from twenty minutes down to two.
When to stop DIY and call a technician
If Explorer keeps crashing after all of the above, if SFC or DISM report errors they can’t fix, or if chkdsk flags bad sectors, it’s time to call in a professional rather than keep guessing. Those are signs of a hardware fault or deep corruption that risks losing files if you push on regardless.
A technician runs hardware diagnostics, checks your network and NAS setup in person, and performs offline repairs safely, backing up your data first. Before a visit, back up anything important, and write down the exact error text, when it happens, and any recent changes you made to the PC.
NextGen IT: on-site help for Explorer problems that won’t quit
If you’ve worked through every step above and Explorer is still freezing, that’s usually a sign of something a screen share or forum post can’t fully diagnose, whether it’s failing hardware, a driver conflict specific to your machine, or malware sitting deeper than a scan catches. Professional technicians can visit your home to diagnose and fix persistent Explorer freezing issues in person, often with a pay-if-fixed guarantee.
Our computer and laptop repair visits cover exactly this kind of persistent fault: hardware diagnostics, malware removal, driver conflicts, and system repairs that go beyond what DISM and SFC can reach on their own. If the freezing traces back to a flaky network connection or an unreachable NAS, we can sort your Wi-Fi and connectivity setup at the same visit. And if scam software or malware is behind the instability, our scam protection and cyber security service checks for and removes it properly, rather than papering over the symptom.
Before we arrive, have three things ready: a backup of anything irreplaceable, a note of the exact error messages you’ve seen, and a rough idea of when the freezing happens, on startup, when opening specific folders, or after certain updates. That’s usually enough for us to diagnose and fix it in a single visit. If you’re in Brisbane, Logan, Ipswich, or Redlands and ready to book, get in touch through our Brisbane computer repair page or the closest service area to you.
Sources
FAQ
Why does my File Explorer keep freezing?
The most common causes are a stuck explorer.exe process, corrupted thumbnail or icon caches, a bad shell extension, or an unreachable mapped network drive. Corrupted system files are also a frequent cause, which is why Microsoft recommends running DISM then SFC as a standard diagnostic step.
How do you restart Windows Explorer?
Open Task Manager with Ctrl+Shift+Esc, find “Windows Explorer” in the process list, right-click it, and choose Restart. This reloads the shell process cleanly and clears most temporary freezes within seconds.
How do I clear the cache in File Explorer?
Open File Explorer Options and click “Clear” under Privacy to wipe Quick Access history, then use Disk Cleanup to remove the thumbnail cache. Clearing these caches often restores stability when Explorer has been freezing or crashing intermittently.
Why is File Explorer not opening files?
This usually points to a corrupted file association, a stuck background process, or a shell extension interfering with the file type you’re trying to open. Try restarting Explorer first, then check for conflicting extensions with a tool like ShellExView if the problem is specific to certain file types.
Should I update my BIOS if Explorer keeps crashing?
A BIOS update rarely fixes an Explorer freezing issue directly, since BIOS controls hardware initialisation, not the Windows shell. Only update it if you’ve confirmed a specific hardware compatibility issue, and always back up your data first, since a failed BIOS update carries real risk.
When should I call a technician instead of troubleshooting further?
Call a technician if Explorer keeps crashing after DISM, SFC, and chkdsk, or if you suspect failing hardware. NextGen IT offers on-site visits across Brisbane, Logan, Ipswich, and Redlands under a No Fix, No Fee guarantee, so you only pay once the problem is actually resolved.
Recommended
Comments