Can't get my old icons back

I installed all of the modules from Object Desktop and applied a theme for my desktop.  Everything seemed corrupted (couldn't open Control Panel, couldn't open Windows Explorer, etc.) so I uninstalled everything.  The only problem is that now my icons are still corrupted.  I've tried deleting IconCache.db but my computer is still holding on to the icons from the theme.  I've also tried going to Properties for a shortcut and changing the icon.  Even if I select the correct icon they don't change.  Some are OK, like Word and Excel.  I need help!

47,161 views 15 replies
Reply #1 Top

Are you on Windows10?

There's a reason IP is not supported on Win10 and is no longer part of ODNT, as you see. I am afraid you may need to load a backup or reinstall you OS to get things straightened out.

Reply #2 Top

Although I think Wiz has diagnosed the problem correctly, Perhaps give us some details on your OS and what you did before the corrupted icons occurred?

Reply #3 Top

I was using Windows 7.  After I installed everything from Object Desktop, I used one of the themes (I think Green Mint).  Once I saw all of the problems I had I uninstalled everything.  Standard icons like folders were changed and program and shortcut icons changed to just a some generic icon.  .Since then I've updated to Windows 10 thinking that would fix it.  That did take care of the folder icons but I can't reset many of the shortcut icons.  I go to Properties and change the icon to the correct one but after clicking OK it doesn't change.

 

So far I haven't gotten any help from Stardock support either.

Reply #4 Top

Open regedit (Start menu search) and drill down to HKEY_CLASSES_ROOT\exefile\shellex and delete the Iconhandler folder, then reboot.

Reply #5 Top

Quoting Wizard1956, reply 4

Open regedit (Start menu search) and drill down to HKEY_CLASSES_ROOT\exefile\shellex and delete the Iconhandler folder, then reboot.

 

I don't get it. This issue (the blank page icon) has been know (and causing problems) FOR YEARS and YEARS now. Why doesn't IconPackager simply remove that key when uninstalled?!

I'm peeved about this too because I've had countless reports of people installing Nexus, seeing the blank icons and, of course, assuming this is a bug in Nexus. I even added an entry regarding this issue (and how to fix it!) to the Winstep FAQs (but who reads them anyway?!) !

Reply #6 Top

Quoting JcRabbit, reply 5

Why doesn't IconPackager simply remove that key when uninstalled?!

That, Sir, is the 64 Thousand Dollar Question. The fix is widely known (apparently only in the forums, however and not by support or the Devs) and the problem has been around for, as you said,  years and years.

Reply #7 Top

It's being looked at.  :D

Reply #8 Top

 

Quoting ZubaZ, reply 7

It's being looked at.  :D
:congrat:

Reply #9 Top

If it changed your icons, you must have used ThemeManager and/or Icon Packager. Those 2 programs are fubar and shouldn't even be available anymore, IMHO. They should be removed from downloads.

Reply #10 Top

IP is perfectly fine for any OS other than Win10.  No reason to remove it. 

+1 Loading…
Reply #12 Top

You're welcome. :thumbsup:

Reply #13 Top

Quoting Daiwa, reply 10

IP is perfectly fine for any OS other than Win10.  No reason to remove it. 

IP is fubar on Windows 7 forward IF you try to uninstall it. Also, it has problems with Live Folders on 7. I had to reinstall 7 once because of IP.  If memory serves, so did Wizard1956.

Reply #14 Top

Dunno.  Fubar seems a bit dramatic a description, not to minimize any issues you had with it personally.  Used it for as long as I've been on Win7, on multiple rigs, without any problems.  But then, I never felt the need to uninstall it, so there's that.

Reply #15 Top

For myself, and Wiz, IP would change some icons, but the live folders would remain the same ones from the prior iconset. You'd get different results between different sizes set in view, meaning if you changed from small icons, to large, etc.

Upon trying to reset IP to use the OS icons, it would revert some, but not others. Eventually, only a reinstall of the OS fixed it all.