Microsoft’s support documentation treats DISM and System File Checker as the built-in repair sequence for Windows system corruption: run DISM first, then run sfc /scannow. That order is important. SFC draws on the local Windows component store for replacement files, so repairing that store first gives SFC a better chance of completing a real repair rather than merely reporting damage it cannot fix.
This guide deliberately starts with the least disruptive steps. Restarting Explorer does not delete documents, installed apps, or taskbar pins. DISM and SFC do not reinstall Windows. Save any open work first, then work through the checks in order.
Confirm that the shell is the part that froze
A taskbar problem can look worse than it is. If the mouse still moves, open apps still respond, and Ctrl + Alt + Delete works, Windows itself is likely still running. The trouble is more likely in the desktop shell: the part of Windows that presents the taskbar, Start menu, notification area, desktop icons, and many File Explorer interactions.
Press Ctrl + Shift + Esc to open Task Manager. This shortcut works even when clicking the taskbar does not. If it fails, press Ctrl + Alt + Delete and choose Task Manager from the security screen.
In Task Manager, stay on the Processes page and look under Windows processes for Windows Explorer. Do not confuse it with a File Explorer window or an unrelated process that happens to have “Explorer” in its name. On a typical Windows desktop, the Explorer process is the one restoring the visible desktop shell.
Before restarting it, look briefly at the CPU, Memory, Disk, and Network columns. An app consuming sustained CPU or disk activity may be making the whole PC sluggish, but it does not prove that the app caused the taskbar failure. The useful distinction is simple: if only the taskbar, Start menu, and desktop shell are unresponsive, restart Explorer; if all programs stop responding and storage activity is pegged, give Windows a minute to recover or restart the computer normally.
If Task Manager shows Windows Explorer as Not responding, or the taskbar has stopped accepting clicks while programs are still usable, proceed to restart it.
Restart Windows Explorer without restarting the PC
Select Windows Explorer in Task Manager, then choose Restart. In Windows 11, the Restart button may appear near the top of the Task Manager window after selecting the process; right-clicking the process also exposes the option. In Windows 10, right-clicking Windows Explorer and choosing Restart is usually the most direct route.
For a few seconds, the desktop, taskbar, system tray, and open File Explorer windows may disappear. This is expected. Windows launches the shell again and redraws those parts of the interface. Your open applications should remain running, although any File Explorer windows may refresh or close.
Microsoft’s Windows troubleshooting documentation uses the same underlying recovery method when a shell-related display issue requires Explorer to be stopped and started again. The practical reason is that Explorer is more than a file-browsing application on a standard Windows desktop: it hosts the taskbar and desktop session as well.
If Windows Explorer is missing from Task Manager, or Restart does not restore the taskbar, start it manually:
- In Task Manager, select Run new task. In some Windows 11 versions, this is a button in the upper-right corner; in older Task Manager layouts, use File > Run new task.
- Type
explorer.exe. - Select OK.
The taskbar and desktop should return within moments. If they do, use the PC normally for a while. A one-off Explorer stall after a long uptime, a display change, or a misbehaving File Explorer window may never recur. Repeated freezes deserve a deeper check rather than a cycle of restarting Explorer every day.
Restart Windows, then test the taskbar before changing settings
If Explorer starts again but freezes later in the same session, restart Windows rather than immediately changing registry settings, reinstalling taskbar utilities, or running random PowerShell commands copied from forums. A normal restart clears the active user session and reloads the shell, drivers, and startup programs in a controlled order.
When the taskbar is not clickable, you can still restart from Task Manager. Press Ctrl + Shift + Esc, choose Run new task, type the following command, and select OK:
shutdown /r /t 0
This restarts the PC immediately. Save work first: the command closes programs as part of the restart process.
After signing in again, test the actual failure points rather than assuming the repair worked because the taskbar is visible. Open Start, click a pinned taskbar app, right-click a taskbar icon, open the notification area, and press Windows + E to start File Explorer. If these actions work normally after one or two restarts, do not escalate to more invasive repairs.
If the taskbar locks up only after a particular utility launches, check Task Manager’s Startup apps section. Microsoft documents Task Manager as a supported place to disable startup applications. Temporarily disable only a nonessential, recognizable third-party item that you can re-enable later, restart, and test again. Common candidates include taskbar customization tools, shell extensions, RGB utilities, peripheral suites, overlay software, and third-party security agents.
Do not disable Microsoft services indiscriminately. A clean boot can be useful for persistent conflicts, but Microsoft cautions that System Configuration is a powerful troubleshooting tool and should be handled carefully. For most home users, a targeted startup-app test is a safer first diagnostic step.
Repair the Windows image with DISM, then run SFC
When Explorer and the taskbar repeatedly fail alongside other symptoms—File Explorer hangs, Start is unreliable, Settings crashes, or Windows updates fail—check for damaged Windows components. Microsoft Support’s current instructions for Windows 10 and Windows 11 use DISM before SFC.
Open an elevated Command Prompt:
- Press
Ctrl+Shift+Escto open Task Manager. - Select Run new task.
- Type
cmd. - Check Create this task with administrative privileges.
- Select OK, then approve the User Account Control prompt if Windows shows one.
Run this command first:
DISM.exe /Online /Cleanup-Image /RestoreHealth
/Online tells DISM to work on the Windows installation currently running on the PC. /RestoreHealth checks the component store and attempts repair. Microsoft says this can take several minutes; the percentage indicator can appear stuck for a while, especially at lower percentages. Leave the window open and avoid shutting down the PC while DISM is working.
On a normally configured consumer PC, DISM may use Windows Update as its repair source. That means a working internet connection and access to Microsoft Update can matter. In managed business environments, Windows Update access may be blocked by policy or redirected through enterprise update infrastructure; a DISM failure in that situation is evidence to check the organization’s servicing policy, not a reason to download an arbitrary “repair DLL” or unofficial Windows image.
When DISM reports that the restore operation completed successfully, run:
sfc /scannow
SFC checks protected Windows system files and replaces damaged copies where possible. Wait for Verification 100% complete before closing the window. Then restart Windows and test the taskbar again.
The order should remain DISM, then SFC. Running SFC first is unlikely to damage anything, but it can leave a problem unresolved if the component store from which it needs to repair files is itself corrupt.
Read the results before taking a bigger step
A successful DISM and SFC run does not prove that every taskbar problem came from corruption. It establishes that Windows’ servicing image and protected system files passed repair checks. If the taskbar remains unstable afterward, the remaining suspects shift toward a startup conflict, a profile-specific problem, a recent driver or software change, or a Windows issue requiring an update or rollback.
Use the command results to decide what to do next:
- If DISM completes successfully and SFC reports no integrity violations, restart Explorer once more and focus on recently installed startup software or shell-altering utilities.
- If SFC reports that it found and repaired corrupt files, restart Windows before judging the result; the repaired files may not be active until the next boot.
- If DISM cannot find source files or fails because Windows Update is unavailable, do not substitute files from a different Windows version. The repair source must match the installed Windows release, language, and servicing level closely enough to provide valid components.
- If the whole PC freezes, restarts unexpectedly, or reports disk errors, treat this as broader stability troubleshooting rather than a taskbar-only fault.
Windows 10 users should also account for support status. Microsoft ended free Windows Update security fixes and technical support for Windows 10 on October 14, 2025. The Explorer, DISM, and SFC steps still apply to an existing Windows 10 installation, but they do not restore ongoing security servicing. A recurring shell failure on an unsupported Windows 10 PC is a stronger reason to plan a supported Windows 11 deployment or use an applicable extended-support arrangement.
Avoid a reset until the basic evidence points there
A taskbar freeze alone does not justify resetting Windows, deleting the Explorer cache, re-registering every built-in app package, or editing the registry. Those measures are frequently suggested online because they are dramatic, not because they identify the cause. They can create new variables and make an intermittent problem harder to trace.
If restarting Explorer, restarting Windows, disabling a suspected third-party startup item, DISM, and SFC do not stabilize the system, use Microsoft’s recovery options in escalating order. Back up important files first. If the failure began immediately after a Windows update, software installation, or driver change, rollback or uninstalling that specific change is more informative than a blind reset.
For most Windows 11 and Windows 10 taskbar failures, the concrete first response remains small: restart Windows Explorer, reboot once if needed, and use DISM followed by SFC only when the problem is recurring or accompanied by wider shell instability.