This is getting silly

This is beyond a joke, my Prevx SO has just updated to version 3.0.5.143.
A few seconds later it ran a scan, with the following results
I have saved the scan that produced this "farce" if it is wanted

 

.143 is a beta and as such, this probably would have been best mentioned in that forum.

 

Try another scan now as I just did and it shows clean!

HTH,

TH

 

Isn't it also recommended to reboot after an update? I usually reboot and then run a deep scan to make new build of Prevx feel more "at home".

 

Prevx must of pushed the new RC version out before whitelisting there own files that's all!

TH

 

Not so. It is the release on the Prevx site here

http://info.prevx.com/downloadsafeonline.asp

Thats why I posted it here and not in the beta forum

 

Prevx 3.0.5.140 updated of its own accord without any input from me. I hadn't even run a scan. The first I new of it was when the Prevx icon disappeared from the task bar and then returned followed a few seconds later by the scan that threw up those results.
As TH says, they probably hadn't even whitelisted their own files when I got it. Fast, but daft.
I have now run another scan and it has come up clean but they should have been whitelisted and cleared before they were put on the servers.

 

Certainly Joe will clear this up when he sees this thread!

TH

 

True as I just downloaded the Final Version Prevx 3.0.5.143 with SafeOnline from there site!

Thanks,

TH

 

Autoupdates for official release versions are usually delayed but prevx must have pushed this one out quicker to support people across the globe before prevx uninstalls itself on their machines

 

Search Prevx forum for "mismatch"

You will find answers like (and i quote Prevxhelp):

 

HeHe!

I use the freebie and it normally takes ages for it to auto-update itself - even if i update it through the gui (nothing available but i know there is )

Today, it updated - i wonder why

 

This detection is caused because the data isn't fully flushed to disk. Dark Star 72 - we've seen this a couple other times on your PC: could you let me know if you have your harddisk set to cache data before flushing it to disk or if you use any virtualization products? This is not the default detection across the Prevx community and will have only happened on your PC as it is a mismatch between the data stored raw on the harddisk and the data readable by Prevx.

 

Joe,
I have Returnil 2010 installed on this machine and it was actually virtualised when this happened. This was the first time I have known PSO to update without either a scan or myself triggering it. Normally it will either update on the boot scan when it is not virtualised or if I know there is an update available I will reboot out of the virtualised state for the update to take place.
I was actually doing some work that I do specifically in a virtualised state and then save to a separate hard drive when this happened and it caused more than a few problems which was why I was rather annoyed at the time. My apologies if I seemed rather pi**ed off when I posted
What I will do to make sure it doesn't happen again is to untick the "Automatically download and apply updates" and then manually update when I know there is an update available.

 

I'm doing this too. Also if you password protect your options you will need to give a password to uninstall and update (Hoping PrevxHelp Joe can confirm. It only works if you are a standard user not administrator though).

 

That's quite interesting - I do suspect this would be the cause as I believe Prevx reads/writes below the protection of Returnil when scanning/cleaning although it would probably correct itself after a reboot or rescan if the data has time to flush itself to disk.

If you do encounter this again, please let me know and I'll see if I can get in contact with the Returnil team to see if we can find a mutual solution to the problem.

For now, I do think that disabling automatic updates will be the best way to go as it appears that Returnil and Prevx don't get along very well with temporary data not fully written to the harddrive during a raw-level scan.

 

Updates will still be allowed through irrespective of the password, but you will get a warning when uninstalling if you're under a standard user.

 

This should be easy enough to replicate. I will ensure I am in System Safe/virtualised state and then run a scan to trigger the next update. Will let you know either way what happens and send the initial scan log attn:Joe at prevxresearch...... if you want to look at it.

 

Thank you! (also note that the email is report@prevxresearch.com, but if you throw "Joe" in the title, it will definitely get to me )