Windows Troubleshooting

Restart File Explorer in Windows 11 with Task Manager or PowerShell

Md Fakharuddin

Md Fakharuddin

— 2 min read
Share

Restarting explorer.exe can help recover an unresponsive File Explorer, taskbar, or desktop shell. It does not reset folder preferences, clear every cache, repair Windows, or undo registry settings.

Finish any Explorer copy, move, extraction, or rename operation first. Restarting the process can interrupt those operations and close Explorer windows. Save important work and record any error before proceeding.

Try Task Manager First

Press Ctrl + Shift + Esc, locate Windows Explorer, and choose Restart from its context menu or the available task control. The taskbar and desktop may disappear briefly while the shell returns.

If Explorer is absent, use Task Manager's Run new task, enter explorer.exe, and start it normally. Do not select administrative privileges merely to relaunch your desktop. Microsoft describes this approach in its blank-screen troubleshooting guidance.

A full Windows restart is another option after saving work if the problem extends beyond the shell.

Restart Explorer from PowerShell

Use an ordinary PowerShell window inside the affected user's interactive desktop session. Do not use this example from a remote management session or elevate it to affect other users.

This example selects Explorer processes in the same session as the PowerShell process:

$explorerSessionId = (Get-Process -Id $PID).SessionId
$explorerProcesses = Get-Process -Name explorer -ErrorAction SilentlyContinue |
    Where-Object { $_.SessionId -eq $explorerSessionId }

$explorerProcesses | Select-Object Id, ProcessName, SessionId

Review the listed processes and ensure you have finished relevant file operations. Then, in the same PowerShell window:

$explorerProcesses | Stop-Process -Force
Start-Process explorer.exe

Stop-Process -Force terminates the selected processes without giving their Explorer windows a normal opportunity to finish work. Start-Process requests a new Explorer instance. Windows may also restart the shell automatically, and the exact behavior can vary with process/session configuration.

Microsoft documents Get-Process and Stop-Process. Do not replace the selection with a broad elevated process-kill command when you only intend to recover your own desktop.

What Should Happen

The shell may disappear briefly and return. Open Win + E and test the folder or context-menu action that previously failed.

Other independent applications normally remain open, but it is too strong to promise that every unsaved operation is unaffected. Explorer hosts file operations and shell extensions; interruption can have consequences.

There is no universal ten-second deadline. If the desktop does not return, read the error, inspect Task Manager, and try Run new task > explorer.exe. Do not repeatedly terminate processes or disable security software because the restart did not work.

Restarting Is Not Resetting Settings

Restarting reloads a process. It does not restore default folder views, reset Quick Access/Home history, reset file associations, or delete user customizations.

If the issue is a particular preference, change that preference through File Explorer Options or Settings. Keep a record of the original value. Do not delete broad registry keys or install a shell-modification utility merely to recover a hung window.

If the Problem Returns

Record whether it happens in one folder, on a network location, with a particular file type, or after installing an application or update.

  • One location is slow: Check whether a disconnected network path, cloud provider, removable drive, or problematic file is involved.
  • Right-clicking triggers a hang: Investigate the relevant application's shell integration. Update it or use its supported configuration/removal method, changing one component at a time.
  • Crashes affect Windows more broadly: Check updates, errors, storage health, and system repair guidance rather than repeatedly restarting Explorer.
  • Only one account is affected: Compare its configuration and software before concluding the entire profile is corrupt. Creating a new account is a diagnostic or migration decision, not an automatic first repair.
  • There are signs of infection: Use a supported security scan; an Explorer crash alone does not establish malware.

For suspected system-component corruption, follow Microsoft's repair workflow, normally DISM RestoreHealth followed by SFC after successful completion, using an elevated terminal for those repairs. These tools are separate from restarting Explorer.

Microsoft's File Explorer troubleshooting guide provides further steps. Test the original failing action after each justified change so that temporary recovery is not mistaken for a permanent fix.

Read more