How to Fix the Windows Taskbar Not Working
The fastest fix for a Windows taskbar that is frozen or not responding is to restart the Windows Explorer process: press Ctrl plus Shift plus Esc, find Windows Explorer in Task Manager, right-click it, and select Restart. Windows Explorer draws the taskbar, so reloading that one process clears the large majority of freezes in seconds, without a reboot. If a restart does not hold, sign out and back in, install any pending Windows updates, then re-register the taskbar with PowerShell. A taskbar that breaks for one account only points to a corrupted user profile.
A Windows taskbar that is not working most often results from the Windows Explorer process hanging, since that process draws and controls the taskbar. Other frequent causes include a recent Windows update, a corrupted user profile, an auto-hide or full-screen setting that hides it, corrupted system files, and a third-party shell tool that conflicts with the Windows shell. This guide lists the exact causes first, then gives fixes ordered from the fastest and most common to creating a new user profile. Apply them in order and test the taskbar after each one, because a single cause usually accounts for the failure.
Why Is My Taskbar Not Working?
A non-working taskbar comes from a stalled process, a bad update, a damaged profile, or a setting or tool that hides or breaks the Windows shell. The four most common causes are below, ordered from most to least likely.
A taskbar broken for every account points to a Windows update or corrupted system files, while one broken for a single account points to a corrupted profile. The fixes below address each cause in order.
How Do You Fix a Taskbar That Is Not Working?
Work through these fixes in order and test the taskbar after each step. The first three resolve most cases in minutes.
- Restart Windows Explorer. Press Ctrl plus Shift plus Esc, find Windows Explorer in the Processes tab, right-click it, and select Restart. The taskbar disappears and reloads in a second. If it is not listed, choose Run new task from the File menu and start explorer.exe.
- Sign out and back in. Open the Start menu (or press Ctrl plus Alt plus Delete) and sign out. Signing back in rebuilds the whole shell from scratch and clears a stuck taskbar that a process restart did not, without a full reboot.
- Install pending Windows updates. Open Settings, Windows Update, and install every pending update. Microsoft fixed an explorer.exe sign-in freeze on 24H2 and 25H2 in the May 2026 update KB5089549, so a current build is the permanent fix for an update-caused taskbar bug.
- Re-register the taskbar with PowerShell. Open an elevated PowerShell, paste Get-AppxPackage -AllUsers Microsoft.Windows.ShellExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}, press Enter, then restart Windows Explorer. This reinstalls the shell component for your account.
- Check auto-hide and full-screen apps. Go to Settings, Personalization, Taskbar, Taskbar behaviors, and clear Automatically hide the taskbar. Close any full-screen game or video player, since a full-screen app that does not release the display cleanly can leave the taskbar hidden.
- Test a new user profile. Open Settings, Accounts, Other users, add a new local account, and give it administrator rights. Sign in to it. A working taskbar in the new account confirms the original profile is corrupted, so move your files across.
Run System File Checker and DISM
Repairing corrupt system files with System File Checker and DISM restores a taskbar broken by damaged shell files, which also break the Start menu and tray together. DISM repairs the component store that System File Checker relies on, so it runs first.
- Open Command Prompt or Windows Terminal as administrator.
- Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.
- Run sfc /scannow to repair protected system files.
- Restart the computer.
- Test the taskbar, the Start menu, and the system tray after the restart.
The full procedure, including reading CBS.log and running the tools from the Recovery environment, is in the guide to repair corrupt system files with SFC and DISM. When the taskbar fault comes with the PC failing to shut down or restart cleanly, the steps to fix a PC that will not shut down address the related shell and power problems.
Uninstall a Recent Windows Update That Broke the Taskbar
Uninstalling a recent Windows update reverses a faulty quality update that broke taskbar features such as search or the clock, when a newer fix is not yet available. Windows keeps recent updates available for removal through Update history.

- Open Settings, then Windows Update, then Update history.
- Click Uninstall updates at the bottom of the page.
- Identify the most recent quality update by its install date and KB number.
- Click Uninstall next to that update and restart the computer.
- Pause updates for one week so the same faulty update does not reinstall at once.
A corrected version usually follows within days. Microsoft has repeatedly shipped a fix in the next cumulative update, as it did with KB5089549 in May 2026, so check for and install updates again before rolling back permanently. The full process is in the guide to fix Windows Update errors.
Disable Conflicting Shell Software
Disabling third-party shell software removes the conflict that causes a customized taskbar to freeze or fail after a Windows update. Tools that replace the Start menu or taskbar hook into the Windows shell and can break it when Windows changes.

- Open Settings, then Apps, then Installed apps.
- Identify any Start menu or taskbar customization tool.
- Select the tool and click Uninstall, or disable it in its own settings.
- Open Task Manager, Startup apps, and disable any remaining shell add-on at boot.
- Restart the computer and test the taskbar without the third-party tool.
A taskbar that breaks immediately after installing or updating a customization tool confirms the conflict. Reinstall a version that is compatible with your Windows build only after confirming the default taskbar works.
Taskbar Symptoms and Likely Causes
| Symptom | Most Likely Cause | First Fix to Try |
|---|---|---|
| Taskbar frozen, clicks do nothing | Hung Windows Explorer | Restart Windows Explorer |
| Taskbar frozen right after sign-in | Known 24H2 or 25H2 update bug | Install pending updates (KB5089549) |
| Taskbar missing entirely | Auto-hide stuck or a full-screen app | Turn off auto-hide, exit full screen |
| Search or clock broken after update | Faulty Windows update | Uninstall the recent update |
| Taskbar broken for one account only | Corrupted user profile | Create a new user profile |
| Start menu and tray also broken | Corrupted system files | Run DISM then SFC |
Last Thoughts on a Taskbar That Is Not Working
A Windows taskbar that is not working is fixed by matching the symptom to its cause and applying targeted changes in order. Restarting Windows Explorer clears the large majority of freezes in seconds, and signing out and back in handles most of the rest. Installing pending updates resolves the confirmed 24H2 and 25H2 explorer.exe sign-in freeze that Microsoft patched in May 2026, while re-registering the taskbar, repairing system files, and creating a new profile handle the deeper causes.
The pattern that matters is scope: a taskbar broken for every account points to an update or corrupted system files, while one broken for a single account points to a corrupted profile. A taskbar fault is one of the documented common PC problems, and the same shell that draws the taskbar also draws the Start menu and tray, so a fix here often restores all three at once.
Key Takeaways:
- Restart Windows Explorer first; the process draws the taskbar and reloading it clears most freezes in seconds.
- If a restart does not hold, sign out and back in to rebuild the whole shell without a full reboot.
- Install pending Windows updates; KB5089549 (May 2026) fixed the explorer.exe sign-in freeze on 24H2 and 25H2.
- Re-register the taskbar with PowerShell when a restart and sign-out both fail.
- A taskbar missing entirely is usually auto-hide or a full-screen app, not a fault; turn off auto-hide and exit full screen.
- A taskbar broken for one account only means a corrupted profile, so create and test a new administrator account.
Frequently Asked Questions (FAQs)
How do I fix a frozen Windows taskbar?
Press Ctrl plus Shift plus Esc to open Task Manager, find Windows Explorer in the Processes tab, right-click it, and select Restart. This reloads the taskbar in seconds and clears the large majority of freezes without a reboot.
Why is my taskbar frozen and not responding to clicks?
An unresponsive taskbar almost always means the Windows Explorer process has hung, because that process draws the taskbar. Restart Windows Explorer in Task Manager first. If that fails, sign out and back in, then re-register the taskbar with PowerShell.
My taskbar froze right after sign-in on Windows 11. Is it a known bug?
Yes. Microsoft confirmed a Windows 11 bug on 24H2 and 25H2 where explorer.exe froze right after sign-in, leaving the taskbar and tray unresponsive. The May 2026 update KB5089549 fixes it, so installing the latest cumulative update is the permanent fix.
How do I get my taskbar back if it disappeared entirely?
Check whether auto-hide is on under Settings, Personalization, Taskbar, Taskbar behaviors, and turn it off. Confirm you are not in a full-screen app, then press the Windows key. If it is still missing, open Task Manager, choose Run new task, and start explorer.exe.
Does signing out and back in fix a broken taskbar?
Often yes. Signing out ends your session and rebuilds the shell from scratch on the next sign-in, which clears a stuck taskbar that a process restart did not. It is faster than a full reboot and is the second fix to try after restarting Windows Explorer.
Will a new user profile fix taskbar problems?
It will if the cause is a corrupted profile. Create a new administrator account and sign in. A taskbar that works in the new account confirms the original profile is damaged, and moving your files to the new account resolves it.


