Share via

Windows icons has frame around

Batuhan Altan 0 Reputation points
2026-04-07T16:21:41.75+00:00

Windows always remembers folder paths and and saves a copy of them. If you using custom or original shortcut icons sometimes after clearing cache desktop icons has corruption somehow. My solution is :

From cmd execute this commands for clearing icon cache of windows

taskkill /f /im explorer.exe

cd /d %userprofile%\AppData\Local

del IconCache.db /a

start explorer.exe

and afterwards is has to fixed or if you are using custom icons make sure to choose from copy of icons new destination i solved my problem like this.

Windows for home | Windows 11 | Display and graphics

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Hendrix-V 12,660 Reputation points Microsoft External Staff Moderator
    2026-04-08T04:41:59.7633333+00:00

    Hi Batuhan Altan,

    Windows stores folder paths and icon data in an internal icon cache to help display desktop items more efficiently. In some cases (such as after clearing cached items, changing display settings, or using custom shortcut icons) the icon cache can become outdated or inconsistent. When this happens, desktop icons may appear corrupted or display incorrectly.

    Refreshing the Windows icon cache can help restore correct icon behavior. This process forces Windows to rebuild the cache using current file paths and icon sources. After rebuilding the cache, desktop icons typically display as expected again.

    If custom shortcut icons are in use, it’s also important to ensure the icon files are stored in a permanent, accessible location and to reassign the icons if needed.

    I'm glad you were able to resolve the issue using this approach. Your acknowledgment helps others facing similar situations find useful references and contributes to building a stronger community. If you notice similar display behavior in the future or need help with other Windows settings, feel free to reach out. I'm happy to help ensure everything continues to work smoothly.

    0 comments No comments
  2. Q&A Assist
    2026-04-07T16:21:55.2333333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The behavior described matches a known issue where the Windows icon cache becomes corrupted, causing icons to appear with incorrect frames or visuals. Clearing and rebuilding the icon cache is an appropriate fix.

    The documented remediation for icon corruption in Windows (XP/Vista/7, and conceptually similar in later versions) is:

    1. Log off the affected user and sign in with another account that has administrator rights.
    2. In that admin session, create or update the Max Cached Icons registry value to increase the icon cache size:
      1. Run regedit.
      2. Navigate to: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer
      3. On the Edit menu, select New → String Value.
      4. Name it MaxCachedIcons.
      5. Set its Value data to 2048.
    3. Delete the icon cache database (IconCache.db) for the affected user:
      • Windows XP: C:\Documents and Settings\<User Name>\Local Settings\Application Data\IconCache.db
      • Windows Vista or Windows 7: C:\Users\<User Name>\AppData\Local\IconCache.db
    4. Log back in as the original user so Windows recreates the icon cache.

    The command-line method shown in the question (taskkill explorer, delete IconCache.db, restart explorer) is a manual variant of step 3 that forces Explorer to stop using the cache file so it can be deleted and rebuilt. For persistent or recurring icon corruption, also setting MaxCachedIcons as above is recommended.

    When using custom icons, ensure they are referenced from a stable, permanent location (not temporary folders) so that when the cache is rebuilt, Windows can reload the correct icon resources.

    Modifying the registry incorrectly can cause system issues, so a registry backup is recommended before changes.


    References:

    0 comments No comments