Start 10 1.56 key not activating 1.61

My organization owns a ton of Start 10 licenses. I was tasked with updating the software in SCCM. The activation code I have only works in 1.56, not 1.61. Do I need a new serial?

5,347 views 11 replies
Reply #1 Top

Hello,

I have forwarded your problem to Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

 

Basj

Stardock Community Assistant.

Reply #2 Top

Hello,

Sorry to hear you are having trouble.


My organization owns a ton of Start 10 licenses. I was tasked with updating the software in SCCM. The activation code I have only works in 1.56, not 1.61. Do I need a new serial?
End of quote

I don't see any failures on the logs for your help****@***********.com email.  What error are you getting (screenshot perhaps) when you try a manual activation?

----------------
Sean Drohan
Stardock Customer Service Manager

Reply #3 Top

Activation works fine if I run it locally on machine. I use the below code:

 

"C:\Program Files (x86)\Stardock\Start10\SASUpgrade.exe" -prodId=**** -prodName="Start10" -company="Stardock" -ver="1.56" -email="help****@************.com" -serial="SN"

 

But if I run this step in SCCM while using Start10 1.61, it fails the step. 1.56 works fine. 

Reply #4 Top

Quoting helpdesk84, reply 3

Activation works fine if I run it locally on machine. I use the below code: 

"C:\Program Files (x86)\Stardock\Start10\SASUpgrade.exe" -prodId=**** -prodName="Start10" -company="Stardock" -ver="1.56" -email="help****@************.com" -serial="SN" 

But if I run this step in SCCM while using Start10 1.61, it fails the step. 1.56 works fine. 
End of helpdesk84's quote

I just tested it with this syntax (edited with my credentials) at a command prompt:

"C:\Program Files (x86)\Stardock\Start10"\SASUpgrade.exe -prodId=2623 -prodName="Start10" -company="Stardock" -ver="1.61" -email="USER@USER.COM" serial="PRODUCTKEYGOESHERE"

with version 1.61 and it does work - it activated for me.  I then tried with your credentials and it worked as well.

Make sure you have the version in the line as well as the prodId

----------------
Sean Drohan
Stardock Customer Service Manager

Reply #6 Top

Quoting helpdesk84, reply 5

I tried that very line and it did not work. It is still not activating in SCCM. 
End of helpdesk84's quote

Are you able to activate from a command prompt?

Reply #8 Top

Quoting helpdesk84, reply 7

Yes
End of helpdesk84's quote

Then there is something wrong in the package - perhaps that you are trying the activation before its (fully) installed.  Remember, the activation has to happen on the client PC - not anywhere else.  You might consider a RunOnce reg entry to have it run a batch file to activate.

----------------
Sean Drohan
Stardock Customer Service Manager

Reply #9 Top

Start10 will no longer activate at all. It says it can't reach the activation server. This is completely new.  

Reply #10 Top

Quoting helpdesk84, reply 9

Start10 will no longer activate at all. It says it can't reach the activation server. This is completely new.
End of helpdesk84's quote

That is almost always a firewall issues.  This is the destination that it needs to get to:

https://activate.api.stardock.net over port 443

Reply #11 Top

Nevermind. It's all figured out. For future reference, if you are going to switch your executable naming conventions - WARN A PERSON.... Start10-1.56_setup_sd.exe became Start10_1.61_setup_sd.exe