Act! 2010 reinstallation licensing problem
I'm in the process of rebuilding a Windows 10 computer from scratch (new drive, new Windows installation, etc.) but am running into a snag with Act! 2010. Once it is installed, it needs to activate with a licensing server. The problem (well documented) is that the vendor's licensing servers are permanently shut down.
Does anyone have any process for working around this? I still have a working copy on the old drive. I'm wondering if there's a file or registry key that can be copied over to get around the issue.
I'm not trying to violate licensing rules here. The software is licensed for this computer. I'm simply trying to move that license over to a new drive in the same computer.
One solution is to buy the new version of Act!, but I'm not excited to spend $300 when the version I have is more than adequate for my needs.
Thanks to all in advance for useful advice.
Does anyone have any process for working around this? I still have a working copy on the old drive. I'm wondering if there's a file or registry key that can be copied over to get around the issue.
I'm not trying to violate licensing rules here. The software is licensed for this computer. I'm simply trying to move that license over to a new drive in the same computer.
One solution is to buy the new version of Act!, but I'm not excited to spend $300 when the version I have is more than adequate for my needs.
Thanks to all in advance for useful advice.
ASKER
The computer is using Windows 10, so there's not a Documents and Settings folder. I did find the following:
c:\ProgramData\Act\Act For Windows 12\RegistrationData.xml
I opened it and it looked like it would do the trick. I've copied it over to the new drive, but Act! still wants me to register.
Any other thoughts?
c:\ProgramData\Act\Act For Windows 12\RegistrationData.xml
I opened it and it looked like it would do the trick. I've copied it over to the new drive, but Act! still wants me to register.
Any other thoughts?
ASKER
I also noted that if I rename the registration file that I found (on the old drive), Act! will run properly without the message about activating it.
I'm wondering if it uses that file once and then sets some flag to say that it has been activated.
I'm wondering if it uses that file once and then sets some flag to say that it has been activated.
Look in HKLM\Software\Wow6432Node for the registry settings if running on 64-bit Windows previously.
Apologies I don't have a direct answer, but I do not use Act!
Apologies I don't have a direct answer, but I do not use Act!
ASKER
Thanks for the suggestion. No need for an apology, I appreciate any reasonable suggestion.
I did find HKLM\Sfotware\Wow6432Node\
As a test, I exported the key from the working drive and imported it on the one that needs to be activated. It mentioned that I had been using Act! for a long time (wanted me to do a survey), which tells me that it is recognizing the registry change. It still wanted activation.
I tried changing the CurrentMachineName to the name of the new computer (I used a different name when reinstalling Windows), but that didn't help either.
I did find HKLM\Sfotware\Wow6432Node\
As a test, I exported the key from the working drive and imported it on the one that needs to be activated. It mentioned that I had been using Act! for a long time (wanted me to do a survey), which tells me that it is recognizing the registry change. It still wanted activation.
I tried changing the CurrentMachineName to the name of the new computer (I used a different name when reinstalling Windows), but that didn't help either.
What is the OS on the old drive?
Legally speaking, if you rebuild the OS from scratch, it is a new computer and you need a new license.
Legally speaking, if you rebuild the OS from scratch, it is a new computer and you need a new license.
ASKER
It is Windows 10 Pro.
I'm curious, from which license agreement do you base the claim that rebuilding an OS from scratch requires a new license? I've seen many recommendations on EE to start over when problems get too tough to fix (or in cases of a virus), but don't ever recall anyone including the comment that a new license will have to be purchased.
I'm curious, from which license agreement do you base the claim that rebuilding an OS from scratch requires a new license? I've seen many recommendations on EE to start over when problems get too tough to fix (or in cases of a virus), but don't ever recall anyone including the comment that a new license will have to be purchased.
Case law in both the United States and the European Union (specifically cases against Microsoft) disagree with @Jackie lee's comment above.
Unfortunately, the owners of the copyright for Act! 2010 have not released it into the public domain and hold the copyright for this software at least until 2129.
Your best course of action is to either find someone with Act! 2010 installed who can export your data into a useable format or purchase a current copy of Act!.
Good luck!
Unfortunately, the owners of the copyright for Act! 2010 have not released it into the public domain and hold the copyright for this software at least until 2129.
Your best course of action is to either find someone with Act! 2010 installed who can export your data into a useable format or purchase a current copy of Act!.
Good luck!
ASKER
@Darrell
As posted, I have a working system with Act installed and functioning properly. I'm just trying to repeat that on a replacement system. It's not a matter of exporting; it's a matter of getting my licensed copy of Act! to get past the 30-day limit on a new installation.
I'm trying to avoid spending $300 (new version of Act!) for the sole purpose of continuing to run something that I already own and believe I have a legal right to run.
As posted, I have a working system with Act installed and functioning properly. I'm just trying to repeat that on a replacement system. It's not a matter of exporting; it's a matter of getting my licensed copy of Act! to get past the 30-day limit on a new installation.
I'm trying to avoid spending $300 (new version of Act!) for the sole purpose of continuing to run something that I already own and believe I have a legal right to run.
Can you search the registry of the working machine for Protexis and let us know if you find anything?
ASKER
I found 12 keys or branches that mention Protexis. I've exported all of them and edited out the non-Protexis entries.
I'll fire up the new drive later and see what it has to compare in the registry and the specified folders.
Thanks!
I'll fire up the new drive later and see what it has to compare in the registry and the specified folders.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry for the long delay in responding. I've not gotten back to the issue until recently.
I'm afraid that Jackie Man is very likely correct. Darrell provided some excellent suggestions, which lead me to inspect a number of keys. I tried copying them over with some thought to what might fix it, but was not successful.
The biggest clue to me was when I looked into the Protexis keys as Darrell suggested. I checked those keys on two different computers that were successfully registered with Act! and their values were very different. The one I thought would be most likely to work was HKLM\software\wow6432node\
At this point, the only way I can see getting this version of Act! running on a new installation is to clone the existing system, whittle away everything else, and do an in-place reinstallation. That may or may not achieve the cleanup that I want.
Thanks for your suggestions!
I'm afraid that Jackie Man is very likely correct. Darrell provided some excellent suggestions, which lead me to inspect a number of keys. I tried copying them over with some thought to what might fix it, but was not successful.
The biggest clue to me was when I looked into the Protexis keys as Darrell suggested. I checked those keys on two different computers that were successfully registered with Act! and their values were very different. The one I thought would be most likely to work was HKLM\software\wow6432node\
At this point, the only way I can see getting this version of Act! running on a new installation is to clone the existing system, whittle away everything else, and do an in-place reinstallation. That may or may not achieve the cleanup that I want.
Thanks for your suggestions!
ASKER
As I posted, the responses were helpful, even though I didn't accomplish what I had hoped to. Thanks to both of you for your efforts!
C:\Documents and Settings\All Users\Application Data\Act\Act for Windows 12
and copy the RegistrationData.XML file to the new computer.