Printable View
I thought I had solved the having to log in every day thing by adding the .exe file to my exceptions in Webroot Secure Anywhere app. But since the update, even after adding the .exe file again I have had to log in every day.
I have not had this problem with Pro X so why am I still having this issue with Pro+?
Logging in and allowing a Firewall pass-through are two different matters.Quote:
Originally Posted by gwpriester
You should have no need for the latter and the log-in issue is possibly you have been over exuberant with blocking the log-in service Xara is using to authenticate a valid Pro+ licence.
Try going into Xara Cloud+ directly before you jump though the hoops. Two reasons:
- If you have to go in there every time, it is more evidence where the problem might lie.
- If, when you are in Xara Cloud+, see if opening Pro+ is working without an additional log-in.
Rob-Xar said such authentications were infrequent, around monthly otherwise how can you work off-grid on a mobile away from the Internet?
Acorn
short answer - they are different activation systems, witness magix distribution programs require a key, pro+ does notQuote:
Originally Posted by gwpriester
when the pro+ progam closes it should stay 'logged-on' and for that it will need access to log-on credentials I would think, so it is being denied these in some way, either by webroot secure, or something else
these would be encrypted in the registry and maybe webroot will not allow pro+ access at startup
maybe the update has in some way changed what needs access to this information
all pretty much guesswork really :(
must be something specific to your set-up...
I have to do this one way or the other.Quote:
Try going into Xara Cloud+ directly before you jump though the hoops
It was fine before the latest update and now it is not.
I ran as administrator yesterday. Today good. We'll have to see.
Still good?Quote:
Originally Posted by gwpriester
Acorn
FWIW - i had a request to log on to verify account with pro+ recently, but I noticed there were two instances open, and closing the one requesting a log on [without logging on] I found the other instance did not require log on and had opened as normal
it's not opening, multiple instances per-se as I can do that without the need to log on , it's more of a go figure..
Mixed bag. Mostly opening OK.