Problem with software upgrade key 
Autore: John W.
Visite 1063,
Followers 1,
Condiviso 0
I did not see an answer to this.
I upgraded to 2020.3.6 and received a key.
Every time I start the program, it asks me for the key again.
How do I get passed this problem.
I uninstalled the previous version and reinstalled 2020.3.6 but, it is still doing the same thing.
HELP!!!
Thanks!
Postato il
Hello.Perhaps you have installed the program as an administrator and run it as a user.Or you installed the program from one administrator, and run it like another.
Autore
My admin account is secure and I do not use it full time. I use, a user account on my computer and enter the admin credentials when needed. However, The websitex5 program is the only program known to man that, has had this issure, carry over, to every upgrade; I have ever done on this computer. No other program I own has this flaw! The program is looking to the admin account when opening a photo file and other things, instead of the user account that installed the program.
So, can you tell me how to fix it?
"My admin account is secure and I do not use it full time. I use, a user account on my computer and enter the admin credentials when needed." - I do the same.
"The websitex5 program is the only program known to man that, has had this issure, carry over, to every upgrade; I have ever done on this computer." - I had such a problem, it seems in 2019 or 17 version. But I don't remember about such a problem in 2020. Perhaps due to the fact that the program is installed not on the system drive C, but on drive D.
When this problem was, I had to elevate my account to the administrator level, activate the program, and then again demote my account to the user level.
Hello John,
In addition to Aleksej's valuable advice, please see the instructions from Elisa in the following thread:
https://helpcenter.websitex5.com/it/post/208562
Kind regards,
Paul
Search the WebSite X5 Help Center
Autore
I copied the license file from the administrator account to the user account and this resolved the issue.
Maybe this will be fixed in the next version upgrade.