How to Restart Windows Explorer Without Rebooting the PC

Updated: October 2026

The taskbar stops responding, the tray icons freeze, and the user asks if they should reboot. They usually don't need to. Here's how to restart Windows Explorer locally or on a remote PC, what the restart fixes, and what to check when Explorer keeps crashing anyway.

What Restarting Windows Explorer Does

Explorer.exe is the Windows shell. It draws the taskbar, the desktop, the system tray and every File Explorer window. When it hangs, the PC underneath is usually fine. Apps keep running and network drives stay mapped. Only the shell has stopped listening.

Restarting Explorer kills that one process and starts a fresh copy. The taskbar blinks out for a second or two and comes back. Nothing else closes, with one exception: any open File Explorer window goes with it, including a copy or move running in that window. Ask the user before you do it mid-transfer.

It also reloads shell settings. Taskbar tweaks and some registry edits under the Explorer keys apply after a restart, without a sign-out.

On Windows 11, not everything that looks like the shell lives in explorer.exe. The Start menu runs as StartMenuExperienceHost.exe, Search as SearchHost.exe, and notifications and quick settings in ShellExperienceHost.exe. If Start is the part that's frozen, restart that process instead.

How to Restart Windows Explorer From Task Manager

This is the fastest route when you're at the keyboard.

1. Press Ctrl+Shift+Esc to open Task Manager.
2. On the Processes tab, find Windows Explorer. Typing "explorer" in the search box at the top finds it faster.
3. Right-click it and choose Restart.

If the taskbar is gone and the screen is black apart from the cursor, Explorer isn't running at all. There's nothing to restart. In Task Manager, choose Run new task, type explorer.exe and press Enter.

Britec09's walkthrough covers the Task Manager route and the repair steps that come after it when File Explorer keeps freezing.

Restart Explorer.exe From the Command Line

The command line works when Task Manager won't open, and it's the version you can script.

In Command Prompt:

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

In PowerShell:

code
Stop-Process -Name explorer -Force

On a default install, Windows starts a new shell by itself after the PowerShell line. Winlogon watches the shell process and relaunches it when it dies. If the taskbar doesn't come back within a few seconds, run Start-Process explorer. Our list of PowerShell commands covers more of these one-liners.

On a shared Remote Desktop host, every signed-in user has their own explorer.exe. taskkill /im explorer.exe without a filter restarts the shell for all of them. Add /fi "USERNAME eq DOMAIN\user" to hit one session.

Restart Windows Explorer on a Remote PC

The user calls, the taskbar is frozen, and you're not there. You can end their Explorer from your own machine:

code
taskkill /s PC-042 /fi "USERNAME eq CONTOSO\jdoe" /im explorer.exe

Microsoft's taskkill reference notes two things that matter here. Remote kills are always forced, with or without /f. And the STATUS filter doesn't work on a remote system, so you can't target only "not responding" processes. Filter by user instead.

Don't follow it with a remote start explorer.exe. That launches the shell under your session, not the user's. Let Winlogon bring it back on the user's side. It's the same restart-on-exit behavior from the section above.

PowerShell remoting does the same job:

code
Invoke-Command -ComputerName PC-042 {
  Get-Process explorer -IncludeUserName |
    Where-Object UserName -eq 'CONTOSO\jdoe' |
    Stop-Process -Force
}

OpenFrame can run either line as a script on the user's device, so a frozen taskbar doesn't need a remote session to fix.

Restart Explorer, Sign Out or Reboot?

Each step clears more and costs the user more. Pick the smallest one that fixes the problem.

Group membership rides on the logon token, so only a fresh sign-in picks it up. No shell restart changes that. The same goes for drives mapped by a logon script or Group Policy.

When One Restart Isn't Enough

Restarting Explorer once a month is housekeeping. Restarting it daily is a symptom. This r/sysadmin thread from a Windows 11 rollout lists the small shell faults a restart clears, and the replies show how normal the habit has become.

When it keeps coming back, find out why. Start with the Application log in Event Viewer. Event 1000 (Application Error) records each crash, and event 1002 (Application Hang) records each freeze. In a 1000 event, read the Faulting module name line. If it's a third-party DLL, you've probably found your culprit: a cloud sync overlay, an old preview handler, a context-menu add-in. If it's a Windows file such as ucrtbase.dll, suspect the image instead. Reliability Monitor (perfmon /rel) shows the same crashes on a timeline, which makes patterns easy to spot.

How to Find the Cause, Cheapest Check First

Work down the list and stop when the crashes stop.

1. Read the faulting module. Event 1000 often names the DLL. Update or remove the software it belongs to.
2. Disable shell extensions. NirSoft's ShellExView lists every context-menu handler, overlay and preview handler, and it can hide Microsoft's. Disable the rest in halves until Explorer holds.
3. Repair Windows files. Run sfc /scannow, then DISM if sfc can't fix what it finds. Our DISM RestoreHealth guide walks through it.
4. Test a new profile. If a fresh user account is stable, the fault lives in the old profile. If a new account crashes too, it's the machine or the image.
5. Clean boot. Microsoft's clean boot steps disable non-Microsoft services and startup apps, then re-enable them in halves until the crash returns.

Updates can break the shell across a fleet at once. When one admin rolled Windows 11 25H2 out to 150 endpoints in October 2025, six came back without a taskbar. The top reply was DISM RestoreHealth. The next one added sfc and a reboot.

If something else looks wrong while you're in Task Manager, such as one service host eating a whole core, our guide to svchost.exe explains how to tell which service is behind it.

Restart First, Then Ask Why

Restarting Windows Explorer takes seconds from Task Manager, one line from the command prompt, and one filtered taskkill from across the network. Warn the user about open File Explorer windows before you do it. If you're restarting the same PC's shell every week, read event 1000 and go down the list.

When the crashes take down the whole PC rather than the shell, our blue screen of death guide is the next read.