Why are Icon Overlays (from 3rdParty-Apps) not showing up in the Win8 Explorer?

Question

These wonderful icon overlays that give you useful information in the Windows Explorer are not showing up.

It's the most annoying with Dropbox (I already read https://www.dropbox.com/help/154/en). I just tried reinstalling Dropbox - no help. I have this problem also with the Link Shell Extension so I don't think that it is a dropbox problem specifically; and something is wrong in my OS. The OS is actually a pretty fresh clean-install...

OS: Win8 Pro 64-bit.

Answer 1

Looks like you've installed too many tools which register Overlay icons. Windows has an ugly limit of only 15 overlay icons because of old 16 Bit code that can't be changed:

The value 15 came from the corresponding limit for image lists. The Image­List_Set­Overlay­Image function supports up to 15 image list overlays per image list. (Hey, it used to be worse. The limit used to be only 3!)

Okay, but why only 15? Why not more?

The overlay image is one of the pieces of information used when drawing an image from an image list. The options are encoded in the fStyle parameter, and when the bits were divided up for various purposes, four bits were available to be used to specify the overlay image. (You get 15 overlay images instead of 16 because you lose one of the values in order to specify “no overlay.”)

Okay, but the values in the fStyle parameter use only the bottom 16 bits. What about the upper 16 bits? There’s plenty of room there.

The 16-bit limit was carried over from the 16-bit version of the common controls (which still needed to be supported in Windows 95). Of course, nowadays, nobody cares about the 16-bit version of the common controls, so why not start using the upper bits?

There’s an unsatisfying explanation: The code internally that manages the fStyle still uses a WORD in some places, so all the code that manages the fStyle would have to be revised. This occurs in multiple modules across Windows, so a synchronized change would have to be made across multiple components. This is a breaking change at the binary level because the interfaces are no longer compatible. Breaking changes are procedurally difficult to coordinate: The affected code may not be visible to the shell team because they are sitting in a far-away leaf branch that has not yet RI’d to the trunk. It might be that expanding fStyle from a WORD to a DWORD has far-reaching consequences for some component.

So Microsoft can't really fix it without breaking Explorer.

Open regedit, go to

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers and
• HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers

and count the number of items. Are you hitting the limit of 15?

If yes, then either uninstall or reconfigure applications that are shown here or remove the registry entries manually (backing them up of course).

Answer 2

you don't necessarily need to delete any keys, all you have to do is to rename these keys with a number in front of them in sequential order then restart the machine. The sequential numbers will make sure that your OS only counts the top 15.

Here is an example: