Is Icon Packer included in Object Desktop?

from Stardock Forums

I 'thought' it came with Object Desktop but, like other's have found that the 5.10 version didn't work in 10.

So, somehow - and for what reason I can't recall, I downloaded a 'public' version which works without any problem.

Is it possible to register the packager that works as part of Object Desktop or do I have to buy it 'again' if I want Icon

Packager that works?

iconpackager
47,199 views 19 replies
Reply #1 from WinCustomize Forums Top

Where did you download this 'public' version? Iconpackager is not compatible with Win10 and it is strongly recommended you do not install it as serious problems can and do occur trying to uninstall it. 

Reply #2 from WinCustomize Forums Top


I 'thought' it came with Object Desktop but, like other's have found that the 5.10 version didn't work in 10.

So, somehow - and for what reason I can't recall, I downloaded a 'public' version which works without any problem.

From Stardock-

Please DO NOT INSTALL IP on Windows 10.

I strongly recommend against the use as you WILL end up with problems.

There is a very good reason we block the installer, please trust us!

Curtains - Customize Windows with additional styles
Reply #3 from Stardock Forums Top

IconPackager is not part of Object Desktop, and as the others have said, do not install it on Windows 10.

 

Reply #4 from Stardock Forums Top

Well then is Icon Packager going to be made compatible with Windows 10, or will it no longer be made available and compatible with Windows 10.  Definitely miss having it.

Reply #5 from WinCustomize Forums Top

Quoting bucks, reply 4

Well then is Icon Packager going to be made compatible with Windows 10, or will it no longer be made available and compatible with Windows 10.  Definitely miss having it.

 

 

https://forums.wincustomize.com/474436/page/3/#3613804 

 

Reply #6 from Stardock Forums Top

I had IconPackager installed on Win10 and the only issue I had was when it was uninstalled, the icons in the system tray and explorer were a bit odd. All I did to fix it was to go into regedit HKEY_CLASSES_ROOT\exefile\shellex and delete the Iconhandler folder rebooted and all icons were back to normal.  Had no other issues, might have been extremely lucky.

 

Reply #7 from WinCustomize Forums Top

Quoting bucks, reply 6

Had no other issues, might have been extremely lucky.

Yes you were.

Again, Do NOT install it on Windows 10.

Reply #8 from WinCustomize Forums Top

Iconpackeger WAS a part of Object tDesktop,

Sadly, the goalposts were moved and it is no longer.

Thing is, it should be.... STILL!!!!

Desktop customisation is incomplete without it.  End of story.

+1 Loading…
Reply #9 from WinCustomize Forums Top

It may be that IP was pulled from Object Desktop to prevent downloads and installation on an OS it could really mess up. The powers that be are looking into making IP compatible with W10 and it was suggested that they are discussing it. I'm pretty sure that if the devs find a way to do that IP will be reinstated. Hopefully.

*this post should be in no way considered a hint......hint*

Reply #10 from WinCustomize Forums Top

Quoting RedneckDude, reply 5


Quoting bucks,
reply 4

Well then is Icon Packager going to be made compatible with Windows 10, or will it no longer be made available and compatible with Windows 10.  Definitely miss having it.



 

 

https://forums.wincustomize.com/474436/page/3/#3613804 

 

 

Reading that thread... interesting the response from, Neil. Sounds hopeful! However... Last post on page 1, is Icon Packager perfectly safe on 64bit Windows 7? As the post from Wizard1956 is a bit discouraging?

 

If it is fine it be a real shame to so many if I was to release an icon set and only those on Windows 7 can use it...

Reply #11 from WinCustomize Forums Top

Quoting voo, reply 10

If it is fine it be a real shame to so many if I was to release an icon set and only those on Windows 7 can use it...

WHY?

If you truly enjoy making the icons and you can make many people still on windows 7 happy why not make it. Windows 7 if far form dead and people still use icon packager. 

What has me confused is you have been here since 2001 and I can't find one thing you ever made. So if you plan to make your very first icon set knock yourself out so we can all see it.

Reply #12 from WinCustomize Forums Top

Quoting DaveBax, reply 11

I can't find one thing you ever made. So if you plan to make your very first icon set knock yourself out so we can all see it.
4 real ! ;)

Reply #13 from WinCustomize Forums Top

Quoting DaveBax, reply 11

WHY?


If you truly enjoy making the icons and you can make many people still on windows 7 happy why not make it. Windows 7 if far form dead and people still use icon packager. 

What has me confused is you have been here since 2001 and I can't find one thing you ever made. So if you plan to make your very first icon set knock yourself out so we can all see it.

 

I just assumed most were on Windows 10 by now. If there are still a lot on Windows 7 I'll release them.

 

As for not finding anything of mine, I removed them a long time ago as there was a lot of awful stuff in there.

Reply #14 from WinCustomize Forums Top

I still use IP on Win 8.1. I'm always looking for new sets. \o/

Reply #16 from WinCustomize Forums Top

Quoting cardinalsyn_25, reply 15

I used compatibility for windows 7, to install Iconpackager for windows 10, and it worked great.

And since everyone from Stardock has said "Do NOT install Icon Packager on Windows 10"...

Please do not complain WHEN you have issues, particularly if you try to uninstall....;)

Reply #18 from WinCustomize Forums Top

Working fine for me on Windows 10 too!  I do not intend to uninstall so I am not worried about the uninstall issues.

Reply #19 from WinCustomize Forums Top

I suppose if you're happy.... for now.... no harm done.... yet! 

I'd dearly love to have Iconpackager on Win 10, it'd beat the method I'm using hands down, but when Neil Banfield says it's not a good idea because it is not compatible and will cause damage if uninstalled, then I'm going to heed his warning.  Cos if anybody knows, it's him.