Ivo wrote:
This can happen if <No Skin> is selected as the skin option. Try selecting another skin.
I've just tried several skins... and have shut down and restarted CSM after each one. No joy, though. I did have "no skin" selected. I haven't rebooted yet, but then again, I'm not inclined towards "flailing around" when I don't understand what's happening.
Am I correct that CSM stores its own cache of icons, separate from the Windows icon cache database? (Which, FYI, I've already deleted and allowed to rebuild itself as I've tried to figure this out.)
Again, Explorer shows the right icons, and the "real" Windows start Menu (Win7 Ultimate, 64-bit) works as expected. It's ONLY in CSM that the icons aren't present.
Am I wrong about there being some file stored somewhere in my system which keeps all these icons used by CSM recorded? I know that CSM, in the past, would "rebuild" its database periodically, or was doing something that seemed to be that, anyway. I also know that a total uninstallation, reboot, reinstallation, reboot, didn't help... but since Windows allows programs to put their files all over the place, rather than in tightly-controlled locations... even putting some in the OS folder itself (which is HORRIFIC practice!)... I suspect that CSM could possibly be storing its own "custom icon cache" somewhere else, and that this file (or database, or whatever) didn't get removed when Classic Shell was removed.
I could be totally wrong about this, but I have to say, "do this odd thing with no explanation of what it's doing" seems... wrong... to me.
As an example, for years, people have struggled with Windows periodically losing large numbers of icons from the taskbar tray (and, of course, losing those applications in the process). People proposed all variety of "fixes" which were never "fixes" at all (like disabling universal plug-and-play). Microsoft would never explain what they were doing... but we finally discovered that the whole issue was due to MS hard-coding in a four-second window during which all startup-events need to initialize in order to get loaded into the tray.
What a HORRIBLE design decision on MS's part... and what an EASY fix, once fully understood (even if they have since made it so that you have to increase the timeout using a hex editor, not a mere registry edit as was the case before). Change the time-out cycle from "four seconds" to something more reasonable (say, fifteen seconds), and you get all of your icons and related apps showing up in the tray 100% of the time. (Some fixers increase this to as much as a minute, but I've found that fifteen seconds works out fine for me).
In order to fix things, you need to know WHY they're not working, not merely be given a nonsensical "do this and it'll be OK" solution... like "turn off universal plug-and-play" (which helped in some cases only because this allowed the machine to run faster through the remaining startup services and items).
So... I THINK that the issue here seems likely to be a application-specific-icon-cache issue, but maybe it's not. "Turning skins on and off" is (a) not solving the issue, and (b) not really an explanation of WHAT IS ACTUALLY HAPPENING.
I realize that you may not know what's happening... in which case, I'll be happy to share more information in figuring this out.
But if you do know what's happening, please, share the "What" as well as the proposed "how to fix" info.
Thanks!