Prevx3 v3.0.5.171 running on XP Pro. Recently, each time I boot up, Prevx pops up saying that it is about to expire (there's about 300 days on the multi-user licence) also the Windows security centre warns that Prevx2 sic is turned off. The licence warning then disappears, but the Security centre warn remains. Prevx appears to then run fine & the Prevx task is in the task manager. My other Prevx licences running on Windows 7 do not have an issue with the licence.
Same happens to me on Win 7 64 bit. Prevx still works fine and removes any threats, but still pops up telling me that my licence has expired (I have about 6 months left).
I did notice this when I tried Online Armor as it would not let any Internet connection until the computer fully boot it up and it went away by uninstalling Prevx and rebooting and installing Prevx http://info.prevx.com/downloadcsi.asp again and letting it through all the firewall prompts I'm sure it's a firewall issue because as soon as I went back to Look'n'Stop it stopped! IMO TH
No, I will reinstall if it's a definite fix, but you know what happens reinstalling Prevx... we have the hell that is Myprevx to contend with.
You shouldn't have to if it is on the same machine as I do it all the time without problems and no need to go to MyPrevx! Just uninstall Reboot and install a fresh copy and have your license code ready to install after the learning scan! You should only have to go to MyPrevx if you reinstalled the OS or put it on a different machine! TH
OK thanks for the info! You should keep in contact with Prevx Support inbox to see if they have other ideas to fix your problem and Joe (PrevxHelp) should be around to add futher comments! It's my guess it has something to do on boot up with no internet connection right away as you said it works fine! Like I said I did see that when I tried Online Armor and going back to Look'n'Stop solve my problem on Win 7 32bit! Thanks, TH
The Prevx2 warning is likely from an old installation (nothing in Prevx2 has survived to 3). However, we've had a few users report similar problems but we were under the impression that it was fixed with build 171. If you are seeing this on a persistent basis, could you send me a PM so that we can try a remote support session to see if that will help get to the bottom of it? Thanks for the help!