I have just bought CS3 but couldn't activate it online or by telephone.
Then, 3 days into the Activation period I got a message that my CS3 had been uninstalled.
So, I took an afternoon off work. When I managed to get home during UK support office hours 9am to 5pm I was told to remove CS3 and then run Abvove CS3Cleanup script.
I removed CS3 and then downloaded the kb401056 script only THEN to learn that I must first deactivate CS3. Grrrrrrr!
I then ran the Cleanup Script and it stopped because I didn't have the Microsoft Windows Installer CleanUP Utility. I went to Microsoft's site and downloaded their msicuu2.exe script. That produced an error message "ActiveX component can't create object: 'Scripting.FileSystemObject' Code: 800A01AD.
By then the UK support office was closed.
Is there anyone out there who can deal with this nonsense? I would guess that I'm not the only victim of Adobe's security Gestapo.
#1
When I run into trouble like this I sometimes do a system restore just prior to the program install. I set a restore point prior to installing any software.
Hope this helps since it is a rather drastic move but it gets me out of the problem quickly. Art
#2
Thanks Art
I managed to resolve this eventually by deleting the numbers CS3 automatically inserted in the activation screen and substituting the numbers on the box. However, I am cross that there are still bits and bobs of the CS3 Beta floating around in my Windwos Registry.
Significantly, nobody from Adobe has condescended to comment
#3
I neglected to deactivate the Beta before installing and then everything expired. I solved it be setting my computer back to a date before May 3, re-installing the Beta, de-activating it, uninstall the Beta, and then installed the PS10 release version. It worked fine - finally.
Russell
#4
For regular Adobe software, there is an important purpose to be served by deactivating before uninstalling -- namely, you get the ability to activate it again on a different computer (or the same computer, rebuilt or under a different OS) without using up your second available activation. For an expired beta, I fail to see why deactivating is of any importance. The beta will never run again, given that the beta period is over. You won't be activating it on another computer.
#5
I fail to see why deactivating is of any importance.
for me, i was wondering if (as a cs3 beta) not deactivating the beta would affect my production release count of activations. guess i'll find out one of these days. :)
#6
Given that the expired beta uses a different serial number than the installed final version, I can't imagine it affects your final version's activation count. Surely the activation count is keyed to the serial number.
In any event, I didn't deactivate the beta before uninstalling it (and uninstalling the Bridge beta update). I had a flawless install of the final version of PsCS3 (standard).
#7
Surely the activation count is keyed to the serial number.
very few things in life are "sure"... :)
In any event, I didn't deactivate the beta before uninstalling it (and uninstalling the Bridge beta update). I had a flawless install of the final version of PsCS3 (standard).
me too (thank bob!). cs3 ee.
#8
Thanks for the insight. I'm still trying to figure out what the heck happened with my 1st PS10 install that would have caused it to time out on May 3? I purchased the download version. Perhaps I simply used the Beta serial # by accident when I did the install? As we all know, most computer errors are between the keyboard and the chair. But the only way I could fix it was to reinstall the Beta and deactivate it so I thought I had discovered a potential problem that might affect others. If it was just a unique issue with my system then it's pointless to suggest that it's a fix for anyone else. I don't want to mislead folks.
It's very good to hear that folks who did not deactivate the Beta are NOT having any PS10 install problems. Sorry if I led anyone astray.
Russell
#9