Fix Windows 11/10 Icon Cache issues
—
If File Explorer, the Start menu, or other parts of your Windows interface are showing blank labels or solid color blocks instead of text, the fastest fix is almost never a virus scan or a reinstall — it is rebuilding a corrupted icon cache or simply restarting the Explorer process, both of which take under two minutes and touch none of your files. The counterintuitive part: this exact symptom made headlines in 2017 because of one specific antivirus conflict during the Windows 10 Creators Update, but today the same blank-text bug almost never has anything to do with security software at all.
Jake found out about this the expensive way. A customer dropped off a laptop that had just finished a Windows update overnight, and when Jake opened File Explorer to check the drive for a repair estimate, every folder in the window showed empty gray rectangles where the file names should have been. He couldn't read a single label, couldn't tell the customer what was on the drive, and the customer — already anxious about a slow PC — got up and said he'd "just take it somewhere else." That's a diagnostic fee Jake never collected, gone in under five minutes because a text label wouldn't render.
The good news is that Jake's shop has since turned this into a two-minute check instead of a lost customer, because the cause is almost always one of a short list of things, and none of them require wiping the drive he was just asked to look at. Below is that list, sorted the same way Jake now works through it — fastest and most likely first.
Which of these is happening to you?
"Blank text" is not one bug, it's a symptom with several distinct causes, and matching what you're actually seeing to the right cause saves you from trying seven fixes when one would have done it. Use the table below to jump to the section that matches your screen.
| What you're seeing | Likely cause | Jump to |
|---|---|---|
| Some file names blank, others fine, icons sometimes generic | Corrupted icon cache | Fix it |
| Just started this session, was fine yesterday | Stuck Explorer.exe process | Fix it |
| Whole desktop looks flat, colors changed, not just Explorer | High Contrast mode enabled | Fix it |
| Started after a monitor change or GPU driver update | Graphics driver mismatch | Fix it |
| Started right after installing a Windows feature update | Security software conflict | Fix it |
| Cache rebuild didn't help, problem is widespread | Corrupted system files | Fix it |
| Only happens under one Windows sign-in, other accounts fine | Corrupted user profile | Fix it |
Cause 1: A corrupted icon cache (most common)
Windows doesn't redraw every file icon and label from scratch each time you open a folder. It keeps a database of pre-rendered icons called the icon cache, stored per-user, so browsing feels instant. When that database gets partially written — usually because a feature update, a crash, or a forced shutdown interrupted it mid-write — some entries come back blank while others render fine. This is the single most common cause of the "some names show, some don't" pattern, and it's the first thing worth trying because it never touches a personal file.
Windows 11: rebuild the icon cache
Open the Run box first — press Win + R, which opens a small dialog for typing a command directly instead of hunting through menus. Type cmd and hold Ctrl + Shift + Enter to launch Command Prompt as administrator, then run:
taskkill /f /im explorer.exe
Your desktop and taskbar will vanish for a moment — that's expected. Then run:
ie4uinit.exe -show
That command forces Windows to discard the current icon database and rebuild it fresh the next time Explorer starts. Finally, type explorer.exe and press Enter to bring the shell back. The rebuild happens automatically as you browse; the first folder or two may render slightly slower than usual while it repopulates.
Windows 10: the same steps, same commands
These steps are the same on both. The icon cache mechanism didn't change between Windows 10 and 11, so the identical taskkill, ie4uinit.exe -show, and explorer.exe sequence above works without modification on a Windows 10 machine.
✅ Why this is the one to try first
It's the only fix on this page that directly targets the exact database responsible for icon and label rendering, it takes under a minute, and it cannot delete or damage anything you own. Every other fix below is for when this one doesn't hold.
Cause 2: Explorer.exe got stuck mid-render
Explorer.exe is the single process behind your desktop, taskbar, Start menu, and every File Explorer window. It occasionally gets into a state where it's technically running but has stopped repainting parts of its own windows correctly, and a restart alone clears it, with no cache rebuild needed.
🙋♂️ Jake's Reality Check
"Won't killing Explorer.exe close everything the customer had open?"
No. Explorer.exe only controls the desktop shell and File Explorer windows. A browser, a document in Word, a game — those are separate processes and keep running untouched.
To restart it without the command line: open Task Manager with Ctrl + Shift + Esc, find Windows Explorer in the Processes list, right-click it, and choose Restart. On Windows 11's redesigned Task Manager the entry sits near the top; on Windows 10 it's alphabetical, so scroll to the W's. If it doesn't bring labels back within a few seconds, move on to the icon cache rebuild above rather than restarting repeatedly.
Cause 3: High Contrast mode switched on by accident
This one gets mistaken for a rendering bug most often, because it doesn't look like an accessibility setting — it looks like the whole interface broke. High Contrast swaps your entire theme for a stripped-down high-visibility palette, and on some color combinations, unfamiliar text can genuinely look like it's missing.
It's usually triggered by Left Alt + Left Shift + Print Screen, easy to hit by accident on a cramped laptop keyboard; pressing it again toggles it back off. To turn it off through Settings: Windows 11 is Settings > Accessibility > Contrast themes, set to None; Windows 10 is Settings > Ease of Access > High contrast, toggled off. Same setting, Microsoft just renamed and relocated the section.
Cause 4: A graphics driver behind or mismatched with Windows
File Explorer's window is composited by the Desktop Window Manager, the same GPU-accelerated layer responsible for the taskbar, window shadows, and transparency effects across the whole desktop. If the graphics driver is old, was left mid-update, or doesn't match what a recent Windows update expects, any DWM-composited surface, File Explorer's text included, can render incorrectly, flicker, or drop out entirely.
Update the driver from where Windows itself checks first: Settings > Windows Update > Advanced options > Optional updates > Driver updates on Windows 11, or Settings > Update & Security > Windows Update > View optional updates on Windows 10. If nothing shows there, go directly to the GPU maker's own site, Intel, AMD, or NVIDIA, since their driver packages are usually newer than what Windows Update offers.
⚠️ What this actually breaks
A driver reinstall briefly blacks out the screen while it reloads, which is normal, but don't do this mid-download or mid-task-that-you-can't-restart. On a laptop, plug in the charger first — an interrupted reinstall can leave the display worse than when you started.
Cause 5: Security software fighting with Explorer
This is the cause that made this exact page famous nearly a decade ago, and it's worth telling honestly because it's the clearest example of how one very specific bug can shape years of search traffic long after it stopped mattering.
🕐 What changed since we first wrote this
- Then: when we first covered this in April 2017, the Windows 10 Creators Update had a documented, Microsoft-acknowledged issue where an out-of-date Comodo Internet Security or Comodo Cloud Antivirus install caused exactly this symptom — icons and text failing to render across the interface. The fix at the time was to update Comodo to its latest version before or after installing the Creators Update.
- Now: that specific Comodo bug was tied to one feature update from 2017 and is not the shape this problem takes today. The general lesson held up, though — security software that hooks deeply into how Windows draws file information can still cause this same symptom with any vendor, if the product is out of date relative to a recent Windows update.
- What that means for you: don't assume you're safe just because you don't run Comodo. Any real-time protection product worth updating to its latest version, or briefly disabling to test, before you consider anything more drastic.
To test whether your security software is the cause, update it to the latest version first, that alone resolves it in most cases, exactly as it did in 2017. If the problem persists, briefly disable real-time protection through the product's own interface (not Windows Security, since third-party antivirus usually needs to be turned off from its own app) and see if labels come back immediately. If they do, you've confirmed the cause; turn protection back on and update the software rather than leaving it disabled.
Ethan's take on this one is blunt: "If your antivirus is old enough to still be fighting with a Windows update, it's probably also old enough that it's not catching what it should be catching. Update it for the security, and the blank text clears up as a side effect, not the other way around." Jake's shop treats every visit like this as a two-for-one, the customer walks out with the display fixed and a security product actually current for once.
Cause 6: Corrupted system files
If the icon cache rebuild didn't hold and the problem shows up in more places than just Explorer, menus, dialog boxes, Settings pages, the underlying system files Windows uses to draw its own interface may themselves be damaged. Open Command Prompt as administrator (Win + X, then Terminal (Admin) on Windows 11, or right-click Start and choose Command Prompt (Admin) on Windows 10) and run, in order:
DISM.exe /Online /Cleanup-Image /RestoreHealth
This checks the Windows component store against a known-good copy and repairs mismatches. It needs internet and can take ten to twenty minutes; let it finish uninterrupted. Once done, run:
sfc /scannow
This scans your actual system files against the now-repaired component store. Restart once both finish, whether or not either reported fixing something, since a restart is what applies most of the staged repairs.
How to tell if DISM and SFC actually found anything
Both commands print a short verdict when they finish. SFC reports one of three outcomes: no integrity violations found, meaning this wasn't the cause; violations found and repaired, meaning it likely was; or violations found that it could not fix, which means DISM needs to run again first so SFC has a clean component store to repair from. If you see that third message, run DISM again, then SFC a second time, rather than assuming the repair failed outright.
For a closer look, Windows logs everything SFC checked at %WinDir%\Logs\CBS\CBS.log. Opening it in Notepad and searching for "corrupt" (Ctrl+F) shows exactly which files were flagged — useful if the problem persists after a clean run and you want to see whether it's still flagging the same file repeatedly.
Cause 7: A corrupted user profile
The clearest sign here is that the problem follows one Windows sign-in and not others. Create a new local user account (Settings > Accounts > Other users > Add account on either version); if File Explorer renders text normally there, the issue lives in your original profile, not Windows itself.
Full profile repair means moving your personal files to the new profile and setting it up as your daily account, not something you finish in five minutes. Try one narrower step first: sign out completely, sign back in, and check whether the problem returns. A profile mid-corruption from a bad shutdown sometimes clears with one clean sign-in cycle; deeper, persistent corruption shows the exact same blank labels again immediately.
✅ Why this is the right order to test in
Testing with a new account tells you, in under a minute, whether you're about to spend an evening migrating a profile or whether the real fix was one of the two-minute options above all along.
When corruption keeps returning: checking drive health
If the icon cache or system files keep needing rebuilding every few weeks despite a clean SFC run, rule out the drive itself before assuming Windows is the problem. A drive starting to fail can silently corrupt whatever gets written to it, cache files included, well before it throws an obvious error. Run chkdsk /f from an administrator Command Prompt (it will offer to schedule a restart if checking the drive Windows runs from) and check SMART status through Settings > System > Storage > Disks & volumes on Windows 11, or a free SMART-reading utility on Windows 10. A drive reporting warnings there is a stronger lead than anything above, and it's the one scenario here where backing up first is the sensible move, since a failing drive can genuinely take files with it.
Laptops, multiple monitors, Remote Desktop, and virtual machines
Laptops with hybrid graphics. Most modern laptops pair an integrated GPU with a discrete one and switch between them automatically. If one driver in that pair is behind the other, Explorer can render fine on battery and break on the charger, or the reverse — update both.
Multiple monitors, especially mismatched refresh rates or resolutions. Moving a window between two displays DWM is scaling differently can leave render artifacts on one screen. Dragging the window fully onto one monitor and back isolates whether this is a scaling issue rather than corruption.
Remote Desktop sessions. Blank or blocky text over Remote Desktop is more often a bandwidth or color-depth setting than anything on the machine itself. Click Show Options > Experience and try a lower color depth or a wired connection before troubleshooting the remote PC directly.
Virtual machines. A VM's display runs through a virtual graphics adapter, so the fix is usually updating the VM's guest tools or virtual display driver from inside the VM software, rather than anything covered above for physical PCs.
Automate it for next time
If you're the person who ends up fixing this more than once, whether for your own PC or, like Jake, for a steady stream of walk-in customers, the three commands in Cause 1 are worth saving as a script instead of retyping. Open Notepad, paste the following, and save it as fix-explorer.bat, choosing "All Files" as the type so it doesn't get saved with a hidden .txt extension by mistake:
taskkill /f /im explorer.exe
ie4uinit.exe -show
start explorer.exe
Right-click the saved file and choose Run as administrator whenever the symptom shows up. It's a convenience, not a diagnostic tool — it won't tell you whether the real cause is a driver, security software, or a profile issue, so don't reach for it automatically the third or fourth time in a month. At that point, treat the repeat itself as the symptom worth investigating.
Safe Mode is also worth knowing about, even though it isn't a fix by itself. Restarting into Safe Mode (Settings > System > Recovery > Advanced startup > Restart now, then Troubleshoot > Advanced options > Startup Settings, nearly identical on both versions) loads Windows with third-party drivers and most non-essential software disabled. If File Explorer renders normally there, that's a strong signal the cause is a driver or installed software rather than Windows itself.
A note on third-party cache and repair tools, since search results for this problem are full of them: a dedicated icon-cache tool saves you the manual sequence in Cause 1, and a general system-utility suite bundles that alongside registry cleaning and other extras. Neither does anything the commands on this page can't already do for free, and both add a program with deep system access for a problem you'll likely hit a handful of times a year. Reasonable if you already own one for other maintenance; not worth buying specifically for this.
One privacy-adjacent note: if a shop or colleague is checking your PC over Remote Desktop or a remote-support tool because of this, confirm the session before handing over control, and close it the moment the fix is confirmed. A blank-Explorer complaint is common enough that it gets used as a pretext in unsolicited "tech support" calls; a legitimate fix here never requires reading out a one-time passcode or installing software you didn't ask for.
Windows 10 users: one honest note
Windows 10 stopped receiving free security updates on October 14, 2025. Every fix above still works on Windows 10 exactly as described, and none require ESU or an upgrade. But if you're troubleshooting a machine this old, it's worth knowing your options: Consumer Extended Security Updates can be enrolled through Settings > Windows Update, are free if you sync settings through Windows Backup, and now run through October 2027 after Microsoft's June 2026 extension. If the PC in front of you also happens to be a good candidate for Windows 11, that's a separate, calmer conversation than the blank-text problem, not something to decide mid-fix.
Frequently asked questions
Is missing text in File Explorer a virus?
Almost never. It's far more commonly a corrupted icon cache, a stuck Explorer.exe process, or High Contrast mode having been switched on by accident. A security scan is worth ruling out, but don't assume infection from this symptom alone.
Do I need to reinstall Windows to fix this?
No. Reinstalling is the last resort here, not the first step. Most blank-text cases resolve with an icon cache rebuild, an Explorer restart, or an SFC/DISM repair, none of which touch your personal files.
Why did this start right after a Windows update?
Feature updates rebuild large parts of the shell and icon database in one pass. If that rebuild is interrupted, or security software intercepts it mid-update, the interface can come up with a partially built cache or theme, which shows as blank labels or solid color blocks.
Why do only some icons show text and others don't?
That points specifically to icon cache corruption rather than a system-wide theme or driver problem. The cache builds per-item as you browse, so a partially corrupted database leaves some entries readable and others blank.
My whole screen looks like blocks of color, not just Explorer. Is that the same issue?
That's usually a High Contrast theme, not icon corruption. Windows swaps the entire interface for a stripped-down high-visibility palette, and on unfamiliar color combinations it can genuinely look like text is missing.
Will restarting Explorer.exe close my open files?
No. Restarting Explorer.exe only relaunches the desktop shell and File Explorer windows. Separate programs like a browser or Word keep running because they are separate processes entirely.
Does this happen on Windows 10 too, or only Windows 11?
Both. The underlying causes aren't tied to one version of Windows. The exact settings paths differ between the two, which is why this guide covers each separately.
I don't have Comodo. Can antivirus software still cause this?
Yes. Any security product that hooks into how Explorer renders files, not just Comodo, can cause this if it's out of date or conflicts with a recent Windows update. Updating the security software first is the standard fix.
Can a graphics driver really affect text in a file manager?
Yes. File Explorer's window is composited by the same GPU-accelerated Desktop Window Manager that draws everything else on the desktop, so a driver mismatched with a recent Windows update can affect it exactly the way it would any other window.
What is the icon cache and where does it live?
It's a database Windows keeps of pre-rendered thumbnails and icons so it doesn't have to regenerate them every time you open a folder. On modern Windows it's stored per-user under the AppData folder as a set of iconcache database files.
I fixed it once and it came back a few weeks later. Why?
A recurring problem usually means something is corrupting the cache repeatedly rather than it having happened once, commonly a security product still fighting with Explorer, a driver reverting on updates, or a failing drive. Check the profile-corruption step if the basic fixes keep needing to be repeated.
Does this fix work the same on a laptop as a desktop?
Yes, the fixes themselves are identical. Laptops add two extra suspects worth checking: a hybrid graphics driver pairing an integrated and discrete GPU, and battery-saver modes that throttle GPU composition.
Can this happen inside a Remote Desktop or VM session?
Yes, and there it's more often a display or graphics-passthrough setting than icon corruption. Try adjusting the color depth in Remote Desktop's Experience settings, or updating the virtual display driver in a VM, before touching the icon cache.
Should I back up anything before trying these fixes?
None of the fixes here touch your personal files, so a backup isn't required for them specifically. It's still good practice to keep a current backup on any PC, especially one showing unexplained interface problems, in case a separate issue is developing underneath.
Can I put these fixes into a script I run every time?
Yes, the icon cache rebuild in particular is safe to save as a batch file for repeat use, but treat it as a convenience, not a diagnosis. If you need it more than a couple of times a month, look at the other causes on this page instead of just re-running it.
Does Safe Mode help diagnose this?
Yes. If File Explorer renders normally in Safe Mode, that points to a driver or installed software rather than Windows itself, since Safe Mode loads with third-party drivers and most non-essential software turned off.
Revision note. Originally published April 28, 2017, covering a specific Comodo antivirus conflict during the Windows 10 Creators Update rollout. Rewritten August 21, 2026 for Windows 11 and Windows 10, since that particular Creators Update bug is nearly a decade behind us but the blank-text symptom it caused keeps showing up for newer, more varied reasons. If you found your way here at midnight with a customer waiting or a deadline looming, the two-minute icon cache rebuild above is almost certainly your answer — hang in there, you're closer to done than it feels right now.