Installed the June 2026 Windows update and your custom folder icons or localized folder names suddenly vanished? Folders from network shares and downloaded locations are the ones that lose their look. Nothing is broken, and your files are untouched. Microsoft changed how Windows reads desktop.ini files on purpose.

What Changed

The June 9, 2026 cumulative, KB5094126, on Windows 11 builds 26100.8655 and 26200.8655, adds a security hardening change to how Windows processes desktop.ini files. Microsoft put it plainly in the release notes: some users might notice missing custom folder icons or localized folder names for content from downloaded or remote locations.

A desktop.ini file is the hidden config that tells File Explorer to show a custom icon or a friendly localized name for a folder. After this update, Windows ignores those instructions when the folder content carries the mark of the web, the tag Windows adds to anything that came from the internet or another machine.

You can read the change on Microsoft's KB5094126 release notes.

Your Files Are Safe

This is cosmetic. Access to the folders and everything inside them is unchanged. You are looking at a generic folder icon and the real directory name instead of the custom ones. No data is lost or locked.

Local Folders Fix Themselves

For folders stored locally that you created yourself, the custom icons come back on their own. If a local folder still looks generic, refresh the icon cache and restart Explorer:

ie4uinit.exe -show
taskkill /f /im explorer.exe
start explorer.exe

Give Explorer a moment to rebuild thumbnails and icons after it restarts.

Restore Icons on Network or Downloaded Folders

The hardening keys off the mark of the web. If you trust the source, removing that tag from the desktop.ini file restores the custom icon and name. Check whether the tag is present first:

Get-Item "\\server\share\Folder\desktop.ini" -Stream Zone.Identifier

If that returns a Zone.Identifier stream, the file is marked as remote. Clear it with:

Unblock-File -Path "\\server\share\Folder\desktop.ini"

Only do this on shares and downloads you actually trust. The whole point of the change is to stop a planted desktop.ini from dressing up a malicious folder to look legitimate.

If the icon still does not show after unblocking, confirm the file still has its system and hidden attributes, which Explorer needs to treat it as a folder customizer:

attrib +s +h "\\server\share\Folder\desktop.ini"

Why Microsoft Did This

Attackers have used desktop.ini to spoof folder names and swap in misleading icons, making a downloaded folder look like something safe and familiar. Tying customization to the mark of the web means a folder you pulled from the internet cannot quietly rewrite how it presents itself in Explorer. It is the same defensive idea behind SmartScreen and Office blocking macros in downloaded files.

Should You Change It Across a Fleet

There is no fleet-wide toggle worth flipping here, and there should not be. If a department relies on custom icons or localized names on an internal file server, unblock those specific desktop.ini files on the share once and they stay fixed. Leave the protection in place everywhere else. The cosmetic loss is not worth weakening a sensible security default.

Fix Explorer Crashes After April 2026 Windows Update

Fix Secure Boot Certificate Expiration Before June 2026

AMD GPU Crashes After May 2026 Windows Update

Custom folder customizations breaking across your network after a Windows update? Contact Rain City Techworks.