Windows 11 Start Menu, Taskbar or File Explorer Not Responding: Complete Fix Guide

What is actually broken when Start, the taskbar or File Explorer stop responding

In Windows 11, the Start menu, the taskbar, the desktop icons and File Explorer windows are all drawn by one program called explorer.exe, plus a few helper components that load inside it. When one of those pieces hangs or crashes, several things freeze together, which is why a dead Start button and an unresponsive taskbar so often show up at the same time. The good news is that this makes the problem easier to fix than it looks: most cases come down to a stuck shell process, a damaged system file, a broken app package, or a third-party add-on loaded into Explorer.

The symptoms people search for are all variations of the same thing: "Start menu not working Windows 11", "taskbar not responding", "File Explorer not responding", "explorer.exe keeps crashing", a taskbar that is blank or missing, a Start button that clicks but opens nothing, a search box that will not accept typing, or a desktop where right-clicking freezes everything for ten seconds. This guide treats them as one family and gives you a tested order of attack, from a ten-second restart of the shell up to creating a fresh test user account to prove whether your profile or Windows itself is at fault.

Everything below can be done without reinstalling Windows and without losing files. Where a step changes something (re-registering apps, resetting a profile component), the guide says what it changes and how to undo it. If you only want the fastest path, use the quick-fix box above. If that does not work, use the symptom table in the next section to jump to the right method.

Symptom to fix decision table

Match what you see to the row below and go straight to the method listed. If you cannot tell, start with Method 1 (restart Explorer) and work down in order, because each method is cheaper and safer than the one after it. The table is also designed to be printed and kept near the office help desk.

One more branch worth knowing about: if the whole computer is freezing and not just the shell (the mouse stops, the fan spins up, the disk light stays on), you are probably dealing with a hardware or driver cause rather than an Explorer problem. In that case our guide on why a computer freezes randomly is the better starting point, and the section on hard cases later in this article explains how to tell the two apart in under a minute.

Before you start: five minutes of safety and information gathering

Before changing anything, save open work if the screen still allows it, write down when the problem started, and note whether a Windows update, a new driver or a new program arrived just before. That single detail often points straight to the fix and saves an hour of trial and error.

If you can still reach the desktop even briefly, do these four things now:

1. Save your work and close what you can. If a document will not save because Explorer is frozen, use Alt+Tab to reach the app directly and save with Ctrl+S.
2. Open Task Manager with Ctrl+Shift+Esc. This shortcut works even when the Start menu and taskbar are dead, because Task Manager does not depend on the taskbar.
3. Look at the Performance tab. If CPU, Memory or Disk is pinned near 100 percent, the shell may only be starved of resources. Note which one.
4. Check your version. Press Windows + R, type winver, press Enter. Write down the version and build, because several fixes below depend on the monthly update level. If your PC is still on an old Windows 11 release, read our Windows 11 25H2 update guide too, since old releases lose security and bug fixes.

If the Start menu and taskbar are completely dead and you cannot click anything, you can still do almost every step in this guide with the keyboard. The shortcuts that keep working are Ctrl+Shift+Esc (Task Manager), Windows + R (Run box), Ctrl+Alt+Delete (security screen), and Windows + X (power user menu, which sometimes survives when Start does not). Part of the skill in this kind of repair is learning to stay on those keys instead of hunting with the mouse.

Method 1: restart Windows Explorer (30 seconds, fixes the majority of one-off freezes)

Open Task Manager with Ctrl+Shift+Esc, find Windows Explorer in the Processes tab, right-click it and choose Restart. The taskbar will disappear for a few seconds and come back, and a one-off hang is usually gone. This does not close your apps or lose your work, because only the shell is restarted, not the programs running on top of it.

Step by step

1. Press Ctrl+Shift+Esc. If Task Manager opens in its compact form, select More details at the bottom.
2. On the Processes tab, scroll to Windows Explorer under Apps or Windows processes. If you have a File Explorer window open, it appears there too; the entry that restarts the taskbar is the same program.
3. Right-click it and select Restart. Wait about five seconds.
4. If Windows Explorer is not in the list at all, the shell is not running. Select Run new task in the top bar (in Windows 11 22H2 and later the button sits near the top right), type explorer.exe, tick Create this task with administrative privileges and press OK.

The command line version

If the Task Manager list is unresponsive, open Run (Windows + R) or the Run new task dialog and use this pair. The first command forcibly ends the shell and the second starts it again.

taskkill /f /im explorer.exe
start explorer.exe

If you are typing this in a Command Prompt window, both lines work as written. If you use the Run new task dialog, run cmd first and then type the lines in the black window. After the shell returns, test the Start button, the taskbar and a File Explorer window. If it works and stays working for a day, you may have hit a single hiccup and can stop. If the same freeze returns within hours, the shell is crashing for a reason, and the next methods find it.

Method 2: a real restart, pending updates and Fast Startup

Choose Restart, not Shut down, then install any waiting Windows updates and restart again. Restart performs a full reload of Windows, while Shut down on a PC with Fast Startup enabled saves part of the previous session to disk and brings the same problem back at the next power on. This is the most overlooked fix on the list, because many people shut down every night and assume that is equivalent.

Fast Startup (also called hybrid boot) hibernates the Windows kernel when you choose Shut down so the next boot is quicker. A corrupted shell state, a stuck driver or a half-applied update can survive that cycle indefinitely. Restart bypasses it. So the first test is simple: click Restart (use Alt+F4 on the desktop, or Ctrl+Alt+Delete then the power icon if Start is dead), wait for the sign in screen, and test again.

Install pending updates

Open Settings (Windows + I), then Windows Update, and install everything offered, including optional driver updates that are tied to your graphics or chipset. A pending restart from a previous update is a frequent hidden cause: the files are staged but not yet active, so the shell and its components do not match. If Windows Update itself is stuck or failing, work through our guide on Windows Update stuck or failing first.

Turn off Fast Startup as a test

If the problem returns after every cold boot but disappears after a restart, Fast Startup is the likely culprit. To turn it off:

1. Press Windows + R, type control powercfg.cpl and press Enter.
2. Select Choose what the power buttons do, then Change settings that are currently unavailable.
3. Untick Turn on fast startup (recommended) and save changes.

The same thing from an elevated command prompt is powercfg /h off, which also removes the hibernation file and frees several gigabytes. Booting will be a few seconds slower on a hard drive and barely noticeable on an SSD. You can reverse it later with powercfg /h on.

Rule out low disk space and heavy load

A system drive with almost no free space makes the shell fail in odd ways, because it cannot write caches, thumbnails or search data. Open File Explorer, This PC, and check the C: drive. Under about 10 percent free, free space before anything else. Our computer running slow guide and the how to speed up Windows 11 article list safe ways to reclaim space and stop background programs from starving the desktop.

Method 3: repair system files with SFC and DISM

Open Windows Terminal or Command Prompt as administrator and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, then run sfc /scannow once more. Together they check protected system files and repair the component store that Windows uses as its source of clean copies. Damaged shell files are one of the top three root causes of a dead Start menu, so this step is worth the 20 to 30 minutes.

Microsoft documents DISM as the tool for repairing a Windows image, and notes that sfc /scannow is the quick check and DISM the more extensive one that can repair the component store itself. Use them in that order of strength, but run SFC again after DISM, because SFC relies on the store that DISM just repaired.

Run them in the right order

1. Right-click the Start button (or press Windows + X) and choose Terminal (Admin). If Start is dead, use Task Manager, Run new task, type cmd, tick the administrator box.
2. Run the first scan and wait for it to reach 100 percent:

sfc /scannow

3. Run the image check and repair. These can sit at 20 percent or 62.3 percent for a long time; that is normal, so give them at least 20 minutes before worrying:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

5. Restart, open an administrator terminal again, and run sfc /scannow a second time.

How to read the SFC result

When DISM fails with an error such as 0x800f081f (source files not found) or stops with a long error, the usual causes are no internet access to Windows Update, a damaged update cache, or an interrupted earlier update. Our page on error 0x80073712 explains the related component-store corruption in detail. A practical alternative is to point DISM at an install source: mount a Windows 11 ISO from Microsoft, then run DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess (replace D: with the mounted drive letter, and use the matching edition index if your ISO has several; for example /Source:WIM:D:\sources\install.wim:1). The /LimitAccess switch stops DISM from contacting Windows Update, as Microsoft's repair documentation describes.

Read the log if it still fails. SFC detail lives in C:\Windows\Logs\CBS\CBS.log, and DISM writes to C:\Windows\Logs\DISM\dism.log. To pull only the SFC lines into a readable file on your desktop, use:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"

Method 4: re-register the Start menu, taskbar and built in apps (PowerShell)

Re-registering the built in app packages tells Windows to reinstall the manifests for Start, search, the shell experience host and the other packaged components without touching your files. It is the most effective fix when the Start button does nothing, the taskbar is blank, or Settings will not open. It is safe, reversible in practice (it only re-adds packages that already exist on disk), and takes two minutes.

The modern Start menu, search and parts of the taskbar are packaged apps. If their registration for your user account breaks, which happens after an interrupted update, a profile migration or an aggressive "cleaner" tool, the shell calls them and nothing appears. The repair is a PowerShell command that walks every package and registers it again.

Run the re-registration

1. Open an administrator PowerShell. From Task Manager, choose Run new task, type powershell, tick the administrator box.
2. Paste this single line and press Enter. Red error text for a few packages is expected and normal, because some packages are in use or already correct:

Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

3. Wait until the prompt returns, restart the PC, and test Start, search and the taskbar.

Narrower fixes if you prefer a smaller hammer

If you want to target only the Start experience, run these two lines. They re-register the shell experience host and the Start menu experience host packages by name pattern:

Get-AppxPackage *Microsoft.Windows.ShellExperienceHost* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
Get-AppxPackage *Microsoft.Windows.StartMenuExperienceHost* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

For Windows search problems, the equivalent for the search host is:

Get-AppxPackage *Microsoft.Windows.Search* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Package names can differ slightly between Windows 11 releases, and Microsoft has moved some shell pieces around across 23H2, 24H2, 25H2 and later releases. If a narrow command returns no matching package, run the full all-packages command above, which does not depend on any single name. After a successful run, also consider that the shell may need a sign out and sign in before the Start menu behaves.

Method 5: test with a new user account, then decide whether to migrate

Create a temporary local administrator account, sign in to it, and check whether Start, the taskbar and File Explorer work. If they do, Windows itself is healthy and the damage is inside your user profile; if they fail in the new account too, the problem is system wide. This five minute test is the most valuable diagnostic in the whole guide, because it halves the list of possible causes immediately.

Create the test account from the keyboard

You can do it without a working Start menu. Open an administrator Command Prompt (Task Manager, Run new task, cmd, administrator box ticked) and run the two lines below. Replace the password with your own temporary one and delete the account when you finish.

net user ShellTest TempPass#2026 /add
net localgroup administrators ShellTest /add

Then sign out (Ctrl+Alt+Delete, Sign out) and choose the ShellTest account. The first sign in takes a minute because Windows builds the profile from scratch. Test the Start button, search, the taskbar clock and a File Explorer window.

Read the result

If your profile is the problem

You have two realistic options. The first is to repair in place: re-register apps (Method 4), disable startup items (Settings, Apps, Startup), and remove suspicious shell extensions. The second is to migrate: copy your data folders (Desktop, Documents, Downloads, Pictures, Music, Videos and the browser profile data you want) from the old profile in C:\Users\YourName to the new account, then reinstall or sign back in to your apps. Do not simply rename the profile folder or edit the registry list of profiles, because a mistake there can leave you locked out of your own data.

Be careful with large migrations, and take a full backup before you begin. If the machine holds years of business email, accounting data or a complex Outlook setup, this is where a technician earns the fee, because a clean migration also means moving mail profiles, saved credentials, printers and licence activations. Our article on data recovery after a Windows update or reinstall describes what can be recovered if a profile move goes wrong.

When you are done testing, remove the temporary account so it does not stay as a hidden administrator:

net user ShellTest /delete

Method 6: File Explorer says "Not Responding" when opening folders, drives or the network

If only File Explorer windows freeze, usually for a specific folder or drive, the cause is almost always something Explorer is waiting on: a disconnected network location, a folder with tens of thousands of files, a preview pane trying to render a damaged file, a slow or failing drive, or a cloud sync placeholder that is trying to download. The fix is to remove the thing Explorer is waiting for, rather than to repair Explorer.

Check 1: turn off the preview and details panes

In File Explorer, open the View menu, then Show, and switch off Preview pane and Details pane. A corrupt PDF, video or Office file can freeze the preview handler every time you click it. Then choose Options, View, and tick Always show icons, never thumbnails as a test. If the freezes stop, a thumbnail or preview handler is at fault; keep thumbnails off until the offending file or add-on is found.

Check 2: remove dead network drives and shortcuts

When a mapped drive or a pinned network location is offline, Explorer can wait for a timeout of many seconds every time it refreshes the navigation pane. In This PC, right-click any mapped drive marked with a red X and choose Disconnect. From the command line, net use lists mappings and net use Z: /delete removes one. Also remove stale entries from Quick access and the Network section that point to machines that no longer exist. If your problem is a flaky connection to a NAS or a company server, test with the drive disconnected for a day.

Check 3: clear the Explorer history and reset folder view settings

In File Explorer, select the three dots, Options, and under Privacy select Clear next to "Clear File Explorer history". Then use Restore Defaults on the General and View tabs. This removes bad remembered view settings. To reset the saved view for every folder, close all Explorer windows and run this in a command prompt, then restart Explorer:

reg delete "HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags" /f
reg delete "HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU" /f
taskkill /f /im explorer.exe & start explorer.exe

These keys store only per-folder view preferences (icon size, sort column, window position). They are rebuilt automatically, but export them first with reg export if you prefer a safety copy, as the guidance on common Windows 11 problems also suggests for registry edits in general.

Check 4: huge folders and cloud placeholders

A single folder containing 50,000 or more files, especially photos or log files, can lock the window for a minute while Explorer reads thumbnails and metadata. Split it into subfolders, or sort by name and switch the layout to Details to cut the work. On OneDrive or other sync folders, files marked as "online only" can freeze Explorer when an app or a preview tries to read them. Right-click the folder, choose Always keep on this device only for what you need, or pause sync for a test.

Check 5: the drive itself

If the freezes happen with one drive only, especially an external or older internal disk, suspect the drive. Clicking sounds, a very slow copy, or the disk showing 100 percent active time in Task Manager with tiny transfer speeds are classic signs. Run chkdsk C: /scan (read-only online scan) and, for a mechanical drive, back up immediately. If the drive disappears or is not detected, our guide on a hard drive not detected covers the next steps, and a failing drive is where data recovery rather than repair is the right path.

Method 7: Start search is blank, will not type, or File Explorer search hangs

When the search box shows nothing, never finds files, or freezes as you type, restart the Windows Search service, re-register the search package from Method 4, and rebuild the search index from Indexing Options. The index can become bloated or damaged, and rebuilding it is slow but safe.

Restart the Windows Search service

Open an administrator command prompt and run:

net stop wsearch
net start wsearch

Or press Windows + R, type services.msc, find Windows Search, confirm that its startup type is Automatic (Delayed Start), and select Restart.

Rebuild the index

1. Press Windows + R, type control /name Microsoft.IndexingOptions, press Enter.
2. Select Advanced, then Rebuild under Troubleshooting, and confirm.
3. Leave the PC powered on and idle for a few hours. Search results fill in gradually, and the indexing may use noticeable CPU and disk meanwhile.

If the index will not rebuild, or the search service keeps stopping, the index database itself may be damaged. With the Windows Search service stopped, delete the database file at C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb and start the service again; Windows creates a new one. This file holds only the search catalog, not your documents.

Also run the built in troubleshooter: Settings, System, Troubleshoot, Other troubleshooters, then Search and Indexing. Choose the options that match your symptom (for example "Files don't appear in search results" or "Search or indexing is using a high amount of CPU"). It is not magical, but it catches a stopped service or a bad permission on the index folder quickly.

Finally, remember the Start menu web search box. If the search box is slow because it tries to reach online services, turning off web results is a policy or registry choice that Microsoft has changed across releases; treat any registry tweak you find online as a temporary experiment, test it on one PC, and verify that it still works after the next feature update.

Method 8: find the third-party add-on that crashes explorer.exe (clean boot, Event Viewer, ShellExView)

If explorer.exe crashes repeatedly, especially when you right-click, open a folder or plug in a device, the cause is usually a third-party DLL loaded into the shell: a context menu extension, a cloud storage overlay, an archive tool, a graphics driver component, or an old security product. A clean boot proves it, and the Event Viewer faulting module names the culprit.

Step 1: read the crash record in Event Viewer

Every Explorer crash leaves a record. Press Windows + R, type eventvwr.msc, open Windows Logs, Application, and use Filter Current Log for Event level Error. Look for entries where the source is Application Error and the faulting application is explorer.exe. The text shows a line like "Faulting module name: SomeVendor.dll". That name is your lead.

The same information can be pulled from PowerShell in one go. This lists the last 20 Explorer crash events with the module that failed:

Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='Application Error'} -MaxEvents 200 |
  Where-Object { $_.Message -like '*explorer.exe*' } |
  Select-Object -First 20 TimeCreated, @{n='Detail';e={($_.Message -split "`n")[0..6] -join ' | '}}

The exception code is also informative. 0xc0000005 is an access violation (a program touched memory it should not), which points to a buggy add-on or, less often, failing RAM. 0xc0000409 is a stack buffer overrun, again a software defect. Neither is proof of a virus, but if you also see unknown programs, a hijacked browser or strange pop-ups, run the checks in our complete virus removal guide.

Step 2: run a clean boot to prove a third-party cause

1. Press Windows + R, type msconfig, press Enter.
2. On the Services tab, tick Hide all Microsoft services, then select Disable all.
3. Open the Startup tab, select Open Task Manager, and disable every startup item there.
4. Click OK and restart. The desktop will look bare; that is expected.
5. Use the PC normally for 20 to 30 minutes, doing what used to trigger the freeze.

If the problem is gone, a third-party service or startup program is responsible. Re-enable them in halves: turn on half of the services, restart, test, and repeat on whichever half brings the problem back. With 40 items you find the culprit in about six restarts. When you finish, return to Normal startup in msconfig, or you will keep running without your security software and sync clients.

Step 3: inspect shell extensions with ShellExView

ShellExView is a free utility from NirSoft that lists every shell extension (context menu items, property sheet handlers, preview handlers) with its vendor. Download it only from the NirSoft site itself, never from a download aggregator. Open it, sort by Company, and use Options, Hide All Microsoft Extensions so that only third-party items remain. Disable the suspicious ones in bulk, restart Explorer (Method 1), and test. If the freeze stops, re-enable them one at a time until it returns. Do not delete anything; disabling is reversible, and a note of what you changed makes the rollback easy.

A few common offenders, listed as categories rather than accusations: old archive and compression utilities, cloud storage clients with "overlay" icons, backup suites, PDF tools that add preview handlers, graphics control panel menus, and screenshot or clipboard utilities. Vendor names change and so do bugs, so use the faulting module name from Event Viewer as the evidence and the update status of the program as the first fix.

The context menu variant in Windows 11

Windows 11 introduced the shorter right-click menu, with "Show more options" for legacy entries. Freezes on right-click often come from the legacy section, where old extensions load. That is another reason to look at the extension list. Avoid the popular registry hack that forces the old full menu back permanently unless you need it for work, because it loads exactly those older handlers every time.

Method 9: the problem began right after a Windows update

If Start, the taskbar or Explorer broke immediately after a cumulative update, check Windows Update history for the update number, install any newer update that supersedes it, and as a last resort uninstall that specific update. Microsoft occasionally ships a monthly update that breaks part of the shell for a subset of devices, then repairs it with an out of band fix or the next month's release, and the support documentation for each update lists known issues.

Find which update arrived

1. Open Settings, Windows Update, Update history. Note the KB number and date of the latest quality update.
2. Compare the date with when the problem started. If they match, the update is a strong suspect.
3. Search the KB number on Microsoft's support site and read the Known issues section at the bottom. Microsoft lists acknowledged problems and the workaround there.

The same list is available from PowerShell, which also works if the Settings app will not open:

Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10
wmic qfe list brief /format:table

Install a fix before removing anything

Run Check for updates again. If the issue was acknowledged, a corrective update may already be available, sometimes delivered silently through Known Issue Rollback, which Microsoft uses to switch off a problematic change without a full uninstall. Restart after installing, because Known Issue Rollback needs a restart to apply.

Uninstall the update (only if nothing else works)

1. Settings, Windows Update, Update history, Uninstall updates.
2. Select the latest quality update by KB number and choose Uninstall.
3. Restart. Then pause updates for a week, in Windows Update, to give Microsoft time to publish a fix.

From a command line, the same removal is wusa /uninstall /kb:5000000 where you replace the number with the real KB. Be aware that you leave the PC without that month's security fixes until you reinstall a newer update, so keep the pause short and set a calendar reminder. Never leave a computer permanently on a blocked update. If the system will not start at all after the update, use our guide for Windows that will not boot after an update, and if a stop screen appears, see the blue screen fix guide.

Cannot reach the desktop at all? Use Windows Recovery

If the shell is too broken to sign in, force the recovery menu: power the PC on and hold the power button to switch it off as soon as the Windows logo appears, three times in a row. On the third start Windows opens the Recovery Environment. Choose Troubleshoot, Advanced options, Uninstall Updates, then Uninstall latest quality update. The other options there (System Restore, Startup Settings for Safe Mode) are covered in the hard-case section below.

Taskbar specific problems: blank, missing, wrong place or icons that will not respond

A taskbar that is blank, hidden or missing icons is usually the shell not finishing its startup, a hidden or auto-hide setting, a display scaling glitch after waking from sleep, or damaged taskbar data. Restart Explorer first, then check the settings and the clock. These cases look dramatic but have small causes.

• Taskbar vanished after waking a laptop or changing monitors. Press Windows + P and cycle display modes, or unplug the extra monitor and restart Explorer. Display changes can leave the bar on a screen that no longer exists.
• Taskbar hides itself. Right-click an empty area of the taskbar, open Taskbar settings, Taskbar behaviors, and untick Automatically hide the taskbar. Auto-hide with a frozen shell looks like a missing bar.
• Clock, volume or network icons are missing or dead. Restart Explorer, then toggle the system icons in Settings, Personalization, Taskbar, System tray icons. A broken tray often points to the shell experience package, so re-register it (Method 4).
• Taskbar buttons ignore clicks but the Start menu works. Close and reopen the problem apps, then check for a full screen app or an overlay (game recorders, screen capture tools, remote desktop clients) that grabs focus. Quit them from Task Manager as a test.
• Everything on the taskbar works but is extremely slow to respond. The cause is almost always load: check CPU, memory and disk in Task Manager, and see whether a security scan, a sync client or the indexer is running. Wait it out or pause them.
• Clock shows the wrong time or the calendar flyout does not open. Open Settings, Time and language, Date and time, and use Sync now. A broken time sync is a surprising cause of flyout errors and of sign in problems for cloud services.

If none of those apply, reset the taskbar data for your account. First close all windows. Then, in an administrator command prompt, run the following. It deletes the cached pin and layout data, which Windows rebuilds, so you will need to re-pin your favorite apps afterwards. Take a note of your pinned apps first.

taskkill /f /im explorer.exe
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Taskband" /f
start explorer.exe

The Taskband key stores pinned items and their order. Deleting it is a documented, widely used reset; nothing else is affected. If the taskbar stays blank even after this, return to the new account test, because the cause is then in the profile or the system.

Real troubleshooting for hard cases: Safe Mode, drivers, memory, malware and the repair install

When the basic methods fail, narrow the problem with a Safe Mode test, then rule out the display driver, bad memory, malware and a damaged Windows image, in that order. The last resort that keeps your files is an in-place repair install, and the final resort is Reset this PC. Work through this ladder from top to bottom and stop at the first step that fixes it.

Rung 1: Safe Mode with Networking

Safe Mode starts Windows with minimal drivers and no third-party startup items. Press Windows + R, type msconfig, open the Boot tab, tick Safe boot, choose Network, and restart. If Start and Explorer work normally in Safe Mode, the cause is a driver or a third-party program, which sends you back to Method 8 and to the driver step below. If they fail even in Safe Mode, the damage is in Windows itself. Untick Safe boot afterwards, or the PC keeps starting in it.

Rung 2: the display driver

Explorer draws everything through the graphics driver, and a corrupt or mismatched driver can freeze or crash the shell, especially after a feature update. Update from the manufacturer (Intel, AMD, NVIDIA, or the laptop maker), or roll back in Device Manager, Display adapters, Properties, Driver, Roll Back Driver. For a clean install, use the vendor's installer with the clean installation option. See our guide to updating drivers safely. Hybrid laptops with two graphics chips are the most sensitive, so update both the integrated and the dedicated driver together.

Rung 3: memory and disk health

Random access violations in explorer.exe, in many different modules, are a classic signature of failing RAM or a failing drive. Run Windows Memory Diagnostic (Windows + R, mdsched.exe, restart now) and let it finish a full pass. For deeper testing, a bootable tool such as MemTest86 run for several passes is more reliable. For the disk, open an administrator terminal and run:

chkdsk C: /scan
wmic diskdrive get model,status
Get-PhysicalDisk | Select FriendlyName, HealthStatus, OperationalStatus

A status other than Healthy or OK, or reallocated sector warnings in a SMART tool, mean you should back up now and plan to replace the drive.

Rung 4: malware and unwanted software

Browser hijackers and "system optimizers" are known to inject into Explorer. Run a full Microsoft Defender scan and an offline scan (Windows Security, Virus and threat protection, Scan options, Microsoft Defender Antivirus (offline scan)). If the shell problem started right after installing a free download, uninstall it in Settings, Apps. Our virus removal guide goes deeper.

Rung 5: in-place repair install (keeps files and apps)

An in-place repair reinstalls Windows over itself, replacing every system file and the component store while keeping your files, apps and most settings. It fixes nearly every system level shell problem that SFC and DISM cannot. The method:

1. Download the Windows 11 ISO from Microsoft's official download page (never from third party sites).
2. Double click the ISO in File Explorer to mount it, then run setup.exe from the mounted drive while signed in to Windows normally. If Explorer is too broken to browse, run mountvol or use PowerShell: Mount-DiskImage -ImagePath "C:\Users\You\Downloads\Win11.iso", then start the setup program from the new drive letter.
3. Choose to keep personal files and apps, accept the defaults, and let it run. Expect 45 to 90 minutes and several restarts.

Match the language and edition of your installed Windows, and install the same or newer release than the one you run now. Disconnect unneeded USB devices first, make a backup, and keep the PC plugged in. This is a real operation, so if the computer is a business machine you depend on, consider letting a technician do it.

Rung 6: Reset this PC

Settings, System, Recovery, Reset this PC, with Keep my files, reinstalls Windows and removes apps and settings. It is the final software option, and it should only follow a full backup, because while it is designed to keep files, a failure midway can be messy. Afterwards you need to reinstall your programs and licences. See our guide on how to factory reset a laptop for the differences between the options.

Special case: black screen with a cursor, or Explorer never starts after sign in

If you sign in and see only a wallpaper or a black screen with a movable mouse, the shell did not start. Press Ctrl+Shift+Esc, choose Run new task, type explorer.exe and press Enter; if it works, the real problem is a startup item or a damaged shell registration that stops Explorer from launching on its own.

Check the Winlogon shell value, which tells Windows what program to start as the shell. Malware and badly written tools sometimes change it. In an administrator command prompt run:

reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v Shell

The expected data is explorer.exe. Anything else, especially a path to an unknown program, is a red flag and should be investigated before you change it back. If you need to correct it, use:

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v Shell /t REG_SZ /d explorer.exe /f

If the black screen appears only on a laptop with an external monitor, test with the external monitor unplugged. If it appears only after a long idle, disable hybrid graphics power saving in the vendor control panel. If you are stuck at a spinning wheel before sign in, that is the boot stage, not the shell, and the right guides are the boot problem article and our article about freezing computers.

Printable checklist: fix a frozen Start menu, taskbar or File Explorer in order

Work down this list top to bottom and tick each box as you go; stop as soon as the problem is gone, and write down what fixed it. The order goes from the fastest and safest step to the heaviest, so you never use a big repair when a small one would do. Print the page or copy the list into your notes.

Three realistic scenarios (illustrative)

The cases below are realistic illustrations, not real client files, and are meant to show how the methods combine and how long each takes. Numbers are typical ranges seen in this kind of repair.

Scenario 1: the dead Start button after a Tuesday update

A home user in Montreal installs the monthly update overnight. In the morning the Start button does nothing and the search box is blank, though File Explorer opens. Restarting Explorer helps for ten minutes, then it fails again. The user runs SFC (it reports repaired files) and DISM (25 minutes), restarts, and still has a dead Start. The PowerShell re-registration from Method 4 finishes in two minutes and, after a restart, Start and search return. Total time: about 55 minutes, no data touched. Lesson: the files were repaired but the per-user registration was not, so both steps were needed.

Scenario 2: File Explorer freezes for 20 seconds whenever a folder opens

A small accounting office has a laptop where every folder opens with a long "Not Responding" pause. The Event Viewer shows no crash, so it is a hang rather than a failure. The preview pane is on and the PC has two mapped network drives to a server that was retired months ago. The technician disconnects the dead drives and turns off the preview pane, and the freezes disappear immediately. Time: 15 minutes. Lesson: an Explorer hang is often Explorer waiting on something that no longer exists.

Scenario 3: explorer.exe crashes on every right-click

A designer's workstation closes all folders when she right-clicks a file. Event Viewer shows 14 crashes in a week, each naming the same DLL from a cloud storage and screenshot utility. A clean boot makes the problem vanish, and ShellExView confirms the extension. Updating the utility to its latest release stops the crashes for good. Time: 40 minutes. Lesson: the faulting module name is worth the two minutes it takes to read.

What this costs in Canadian dollars: DIY versus paying a technician

The software methods in this guide cost nothing but time, typically 30 to 90 minutes. Paying a technician is reasonable when the PC holds business data, when the fixes loop without success, or when the cause is hardware, and a remote session is the least expensive way to get expert help.

Parts prices change often, so treat the SSD row as an indication rather than a quote. The point of the table is the order of escalation: software first, then a short expert session, and hardware only when the evidence says so. A repair that keeps recurring is a reason to look at the whole machine, not to keep paying for the same fix.

How to stop it from coming back

Keep Windows and your graphics driver current, restart weekly instead of only shutting down, keep at least 15 percent of the system drive free, limit shell add-ons to ones you need, and keep a recent backup so that a repair is never a gamble. Most shell problems we see are the combination of a long uptime, an old driver and a full disk.

• Restart the PC at least once a week, and use Restart rather than Shut down if Fast Startup is on.
• Create a restore point before installing large programs or drivers (search for Create a restore point, then Create).
• Remove "registry cleaner" and "PC booster" programs. They add risk and rarely any speed.
• Install shell-integrated tools sparingly, and update them when Windows gets a feature update.
• Keep a second admin account, or know the recovery shortcuts in this guide, so a damaged profile never locks you out.
• Back up files automatically. See automated backups for small businesses.

When to call a professional

Call a technician when the shell keeps crashing after Methods 1 to 5, when the PC holds data you cannot lose, when Event Viewer or health checks point to failing hardware, or when you are asked to run a repair install or reset and are not comfortable doing it. Stopping early costs less than a failed reset.

IT Cares has provided remote and on-site IT support in Quebec and across Canada since 2014. A technician connects to your PC with your permission, reads the Event Viewer evidence, applies the right fix in front of you, and explains what went wrong so it does not return. A standard Expert Consultation is 119.99 $ CAD for 60 minutes. Call 1 (888) 711-9428 or book a session online. For a wider overview of Windows 11 trouble spots, see our Windows 11 tips and problems guide.

Frequently asked questions

Related guides

• Windows 11 tips and common problems guide
• Computer freezing randomly: causes and fixes
• How to speed up Windows 11
• Windows Update stuck or failing: how to fix it
• Windows will not boot after an update
• Fix a blue screen in Windows 11
• How to update drivers safely
• Error 0x80073712 component store fix
• Virus removal complete guide
• Automated backups for small businesses

Sources and official references

Last verified: October 1, 2026

• Microsoft Learn: Repair a Windows Image (DISM /RestoreHealth, sfc /scannow)