Problems with "some" IconPackages not displaying properly ?

Make sure you do this first

from WinCustomize Forums

I've had a few messages sent my way indicating that a few people have a problem with a couple of my iconpackages not displaying as they should (i.e. some icons not showing in the iconpackager UI  etc.  ) 

Therefore I have created this graphical so that everyone who has had this problem can try this fix, then I don't have to keep addressing this problem individually. It may be the way that I packaged the download to begin with , but apparently some folks are getting it wrong. Hope this will help.     --- Ace ---

Iconpackage download and install graphic

69,458 views 14 replies
Reply #1 from WinCustomize Forums Top

I usually just look for the IP icon and click on it. Works for me.

Reply #2 from WinCustomize Forums Top

It's a mystery to me as to why anyone should be having an issue. This is the only reason I could come up with as to why this could happen. Anything other than this and I have not a clue.

Sins of a Solar Empire: Rebellion
Reply #3 from WinCustomize Forums Top

I can't help with an answer as I never had a problem. 

Maybe it's people that use an insider build of win10. Just saying as again have no idea. Hope its worked out for you Ace

Reply #4 from WinCustomize Forums Top

Well , I know for a fact that it has nothing to do with my iconpackages. I suspect that it's issues with customers computers. Whether that be software they may be using, settings, caches, who knows. I offer this solution for them, but if it doesn't solve the issue, then they probably should investigate other avenues.

Reply #5 from WinCustomize Forums Top

I don't understand why the Icon Packager trash bin doesn't refresh unless I click the desktop after dumping the bin. The DesktopX bin does, and the Windows bin does. IP bin doesn't.

Reply #6 from WinCustomize Forums Top

Quoting AceMatrix, reply 4

other avenues
End of AceMatrix's quote

I'll offer this up in case it helps.  On Win10, using a Standard (Non-Admin) user (with UAC enabled as well),  I have to apply icon packages twice to get them applied:

1st time - Open up Icon Packager using the right-click "Run as Admin" option.  Apply the icon package and close Icon Packager. (This of course also changes the icons on the Admin user.)

2nd time - Open up Icon Packager normally.  Apply the icon package and close Icon Packager.

Don't know if that's what some people are running into, haven't seen anything about it, but that's how it works for me.

Reply #7 from WinCustomize Forums Top

That's a mystery as well there, Jim. I've never had that happen on my computer.

Reply #8 from WinCustomize Forums Top

Windows 10?

Reply #9 from WinCustomize Forums Top

No Jim. I'm still using Windows7 . So , I'm assuming your problem occurs on Win10 ?  Hmmm...interesting.

Reply #10 from WinCustomize Forums Top

I'm not a big fan of saying "It works fine for me", but it does.

Reply #11 from WinCustomize Forums Top

Yup Ace, Win 10.

Reply #12 from WinCustomize Forums Top

I'm also seeing some packages not working well on Win 8.1. Mostly older ones.

Reply #13 from WinCustomize Forums Top

An IconPackage itself is not a complicated or complex program, it's just a folder with a bunch of numbered images in it, nothing more , nothing less. I suspect that the "Package Builder" portion of the Stardock Iconpackager software is the culprit. It's still the same old portion of the program that was around from the WinXP configuration days and was not updated when the IconPackager software was updated.  I don't see how that portion of the software can possibly be completely compatible with the newer Windows Operating systems. I hope that Stardock will investigate this or at the very least, update the outdated "Package Builder" portion of the software.

Reply #14 from Stardock Forums Top

Quoting AceMatrix, reply 13

An IconPackage itself is not a complicated or complex program, it's just a folder with a bunch of numbered images in it, nothing more , nothing less. I suspect that the "Package Builder" portion of the Stardock Iconpackager software is the culprit. It's still the same old portion of the program that was around from the WinXP configuration days and was not updated when the IconPackager software was updated.  I don't see how that portion of the software can possibly be completely compatible with the newer Windows Operating systems. I hope that Stardock will investigate this or at the very least, update the outdated "Package Builder" portion of the software.
End of AceMatrix's quote

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.
Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.