Activate.exe issue

from Stardock Forums

After updating to v4.0, I was prompted to enter the activation name and serial number. I did it once and all seemed OK.

Then, while on my wifes account (XP Pro SP2) I tried to open Icon Packager, and was prompted to enter this info again.

Also, if I try to change an individual icon, I get an error message about activate.exe not being found in the all users.WINDOWS folder.

Any ideas?

iconpackager
3,922 views 4 replies
Reply #1 from WinCustomize Forums Top
Also, if I try to change an individual icon, I get an error message about activate.exe not being found in the all users.WINDOWS folder.
End of quote

That's a known bug, they are working on a fix.

Are you using the latest version?
Reply #2 from Stardock Forums Top
I'm using 4.00.165, the one being offered through Object Desktop right now. I'm relieved it isn't necessarily a problem in my system anyway. Thanks
Offworld Trading Company
Reply #3 from Stardock Forums Top
I have a OD Ultimate sub until june of next year. I try to update Iconpackager and it tells me my subscription is invalid and when I go to the update registration page, my old Wincustomize subscription is highlighted. I wasn't aware that a WC sub was required to update OD components, so maybe this is where the bug is. I uninstalled IP, rebooted, and reinstalled it but it seems the "install" version is not the same as the updated version yet as the update available message is still there.
Reply #4 from Stardock Forums Top
Same here. After the latest update, which said up top of the history that the activation issue was resolved I had the indentical problem. I'm not being sarcastic, but doesn't Stardock test these fixes many, many times before they issue them?
Can anyone sign up to help test fixes?

Version 4 was a very long time coming-- it seems unusual this was not caught before the release or resolved during the last update. Like any user that spent the money to upgrade I am very anxious to put it through its paces and most icon changes I make are one at a time rather than using the package feature very much. This activation issue ties my hands quite a bit. Let's hope they resolve it soon and permanently.