Windows command guide
Restart Explorer.exe with PowerShell to Fix Taskbar or Desktop Issues
Windows Explorer is more than the file browser. It also powers major parts of the Windows shell such as the taskbar, desktop, and Start-related interface. When those elements hang, a full reboot is not always necessary. Restarting Explorer can refresh the shell quickly.
This guide is written around the specific symptom-command match for restart explorer shell, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.
Stop-Process -Name explorer -Force; Start-Process explorer.exe
Best place to run it
PowerShell is the right execution context for this page. Even when elevation is not always required, using the right shell prevents syntax mistakes and makes the output easier to trust.
Fast repair workflow
- Start from the exact symptom on this page: The taskbar is unresponsive or blank
- Run the primary line exactly as shown: Stop-Process -Name explorer -Force; Start-Process explorer.exe.
- This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
- Test the original trigger again and compare the result with the problem description on this page.
- Move to the next repair family only after reading the output and deciding what actually changed.
Copyable wrapper script
Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.
$ErrorActionPreference = "Continue"
Write-Host "Run this PowerShell block in the matching shell and read the output carefully."
Write-Host "Starting targeted Windows repair step..."
Stop-Process -Name explorer -Force; Start-Process explorer.exe
Write-Host "`nReview the output above before moving to the next fix."
Verification commands after the repair
These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.
systeminfo
whoami /groups
What problem this command is trying to solve
This command targets a stuck or unstable Windows shell process. It is helpful when the desktop looks frozen, icons stop refreshing, or the taskbar stops responding.
- The taskbar is unresponsive or blank.
- Desktop icons do not refresh correctly.
- File Explorer windows behave strangely while the system is otherwise usable.
How the command works
The first part force-stops the Explorer process. The second part starts explorer.exe again. That cycle reloads the shell without restarting the whole computer.
When it makes sense to run it
Use it when the shell is the problem, not the entire machine. It is faster than rebooting and often enough to recover from a broken taskbar or desktop state.
Before you run this command
- Open the shell that matches Stop-Process -Name explorer -Force; Start-Process explorer.exe before you paste it.
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: the taskbar is unresponsive or blank.
- Read the command once from start to finish so you know whether it scans, resets, or changes a stored setting.
What result to expect
After running Stop-Process -Name explorer -Force; Start-Process explorer.exe, compare the result against the symptom that brought you here. The most useful checkpoint is whether the taskbar is unresponsive or blank becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.
How to verify that it worked
The best verification step after Stop-Process -Name explorer -Force; Start-Process explorer.exe is to repeat the action that previously triggered the problem. If desktop icons do not refresh correctly still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.
Shell and execution context
This command usually does not need a full elevated repair context, but it still works best when you run it in the shell it was written for and read the output carefully.
Before you run it
Open file operations may visually disappear for a moment while Explorer restarts. Save work first if you are in the middle of moving or renaming files.
When this is probably the wrong fix
This is not the right first fix for every random Windows problem. Use it when the symptom and command target on this page clearly line up with what your PC is actually doing.
What to do if it does not help
If Stop-Process -Name explorer -Force; Start-Process explorer.exe does not improve the taskbar is unresponsive or blank, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about the specific Windows behavior described on this page.
Frequently asked questions
Should I use Stop-Process -Name explorer -Force; Start-Process explorer.exe for this exact Windows symptom?
Use it when the behavior on your PC lines up with the repair target on this page: This command targets a stuck or unstable Windows shell process. It is helpful when the desktop looks frozen, icons stop refreshing, or the taskbar stops responding.
What should I check right after Stop-Process -Name explorer -Force; Start-Process explorer.exe?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether the taskbar is unresponsive or blank becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on Stop-Process -Name explorer -Force; Start-Process explorer.exe alone?
This is not the right first fix for every random Windows problem. Use it when the symptom and command target on this page clearly line up with what your PC is actually doing.