Discussion in 'Prevx Releases' started by jmc777, Sep 4, 2010.
What does that mean? Couldn't be verified? I have a metric ton of them in my scan log.
Could you post a couple of lines from the log that have the X?
Sure. The initial learning scan took 5mins 50secs — which is unusual!
Edit: Uninstalled/reinstalled and everything's back to normal. Weird.
Interesting we will see what Joe has to say!
Yes - this means that the file couldn't be verified. This would likely be caused from a firewall blocking Prevx. If the reinstall has cleared it up, everything should be working properly now
I don't know if there is a list of these codes anywhere - I can't find one and it would be useful to have a reference to them handy.
It must have been some kind of network issue, as Windows Firewall wouldn't have blocked anything at my end. Was there any issues at Prevx last night at 23:35? I ask because the log is nothing but X's and U's, which would suggest that some kind of communication took place (but genuinely good Windows files were marked 'U' in the log). I'll attach the entire log:
View attachment scan.log
Edit: Event Viewer suggests that the problem was at my end. There was an entry relating to my network adapter at 23:31:27, which would have happened during the scan.
This post explains some of them.
The codes are for Prevx internal use to help users if they have problems they don't mean much to the end user. Here is a post with most mentioned: https://www.wilderssecurity.com/showpost.php?p=1510147&postcount=2
EDIT: jmc777 beat me to the link!
Thanks for the link both of you! Thanks for the link both of you! (Stereo response)
Separate names with a comma.