Activation when I try to change an icon??

Activate.exe is missing

Whenever I try to change the icon of a file, I get an error telling me that "windows cannotg find C:\Documents and Settings\All Users\Application Data\Stardock\IconPackager\Activate.exe"

I have tried uninstalling it then re-installing it using Impulse, I have tried the "In Impulse try right clicking on the serial number next to Icon Packager and removing it. Then replace it with your Object Desktop serial number. After that restart Impulse and let us know if the problem persists. " This did not make a diffeence. All I was told was that I entered an invalid activation key.

If I take the Activate.exe that's in C:\Program Files\Stardock\Object Desktop\Iconpackager, and put it where the error says cannot find it, I get asked for an Activation key. But since I got all this through my Object Desktop Ultimate, I don't have an activation key for Iconpackager.

As far as I know, this error started when I installed the .165 update.

The only way I can change the icon for a file, is through IconPackager itself. Which can be pretty useless at times.

Can anybody give me a real solution?

16,321 views 21 replies
Reply #2 Top
As far as I know, this error started when I installed the .165 update.


There is a new update for IconPackager in Impulse that should clear up this issue.

If that does not work then contact support@stardock.com.
Reply #3 Top
As far as I know, my IconPackager is updated to the latest using Impulse. still happens. Guess I'll have to wait until they release a new version that hopefully corrects the issue..
Reply #4 Top
Thanks hun:)I hope they come out with a fix soon. By the way, cute avatar :D
Reply #5 Top
As far as I know, this error started when I installed the .165 update.There is a new update for IconPackager in Impulse that should clear up this issue.If that does not work then contact support@stardock.com.

Newest update still didn't fix it.
Reply #6 Top
@Bebi, it wasn't intended to.. Seabass mentioned this when it was released.

Hopefully a fix for this issue is released soon.
Reply #7 Top
And it really started with .164
Reply #8 Top
I'm having the same issue. I hope this gets fixed, because I have a few icons I want to have replaced on some programs to spice it up.
Reply #10 Top
This issue is addressed in several other posts as well as the support news letter found here: https://forums.wincustomize.com/315744

Skinning the DvD Icon and changing the individual icons are still outstanding bugs we are working as quickly as we can on. We hope to have a solution out asap but not with out proper testing. My apologies for the wait.
Reply #11 Top
I don't know where to post this but was able to resolve the activate.exe not found problem.

I read the error message then searched for activate.exe and found it located in the Program Files (C:\Program Files\Stardock\Object Desktop\IconPackager). I copied it from there and pasted it in Program Data (C:\ProgramData\Stardock\IconPackage). It worked!

You will be asked for your serial number, which you can retrieve from Impluse. Click on the upper right little white box.
Reply #12 Top
@Dazzyl, now try to run IconPackager and IconExplorer..

At least one of them will demand activation, and when you do, the shell extension won't be.
Reply #13 Top
This from the IconPackager v4 Support Thread forum...

When I got the 'can't find..activate.exe' error on attempting to change an individual file type icon copying the 'activate.exe' file from C:\Program Files\Stardock\Object Desktop\Icon Packager to C:\Documents and Settings\All Users\Application Data\Stardock\IconPackager allowed me to change the individual file type icon.

Subsequently (meaning 'just now) I experienced a "new" variant on the problem where (under the above circumstance - having copied the 'activate.exe' file to the appropriate directory) IP4 was asking for activation info (email/sn) when the "apply' of the 'change icon' tab is selected. After entering the requested info for IP4 the change on the individual icon for the file type was processed and the icon was changed.

It's a bit sloppy, but it does work if you want/need to change the display icon for certain file types not covered in an icon set.


I first did an uninstall of IP4. Cleaned with CCcleaner. Did a reboot. Then reinstalled via Impulse. Like I say, it's a bit sloppy, but it does work... :)
Reply #14 Top
Well, I have a variant to this issue. I installed IconPackager through Impulse and the application itself runs fine. And when the 'apply' of the 'change icon' tab is selected I get the activation popup. But as IconPackager is part of my Object Desktop subscription, I don't have a separate serial number for IconPackager. And it doesn't accept my Object Desktop serial number as a valid one. So, basically I'm stuck. The joys of product activation  :( 
Reply #15 Top
All right, just as a follow up for those searching these forums in the months to come, Stardock support really does exist ;) , and they solved my problem. It appeared I had one of the original Object Desktop serials which format could no longer be handled by the activation checks. I got a new serial and now it works.
Reply #16 Top
@Schekker, good for you :)

Now you probably only have the battle of activations left, which hopefully will be solved on the next update..
I haven't heard it from anyone official, but I can hope they'll make it happen.
Reply #17 Top
It is still a known issue that we are battling hard.

If you should need us Schekker please contact us at support@stardock.com. We are present in the forums but this is the official channel and you are sure to get our attention.
Reply #18 Top
I must say I did a very quick test right after I received my new serial and didn't experience the battle of activations. I only needed IconPackager to change an individual icon for a program I used on an ObjectDock anyway, so I'm not too worried.

And Seabass, so I can expect a resolution to my LogonStudio Vista ticket soon?  :LOL: 
Reply #19 Top
I certainly hope so. If you don't get something please let me know. I would be happy to help.
Reply #20 Top
Hi

I surely hope that schekker's experience doesn't close the case of "the battle of activations". Hopefully we get a fix real soon!
Reply #21 Top

The activation issue was resolved in the current beta of Icon Packager. If you are using Impulse you will find the option under the Stardock Orb > Preferances. Check the box that says show prerelease versions then update as you would normally.