dexplore.exe shown as a virus by windows defender

[Guest]

After installation of Defender this will keep coming up. It indicates that
the particular process ID for the error Adware:32/ClickSpring.PuritySCAN is
my dexplore.exe which is for my VS2003 installation. I have been choosing
remove up to this point and determined that I am not infected with sed
virus/malware but that it is finding my VS installation incorrectly. Why
would a MS program find a virus which isn't? Any help is appreciated as I
won't choose ignore until I feel comfortable. A high risk error isn't
something I like to pass on.

 

[Bill Sanderson MVP]

Thanks for reporting this. Given the software involved, I would expect this
to have been seen in Redmond, and be fixed rather swiftly. Keep an eye out
for a new set of definitions.

Can you post what definition set is in place when this detection happens?

 

[Bill Sanderson MVP]

Thinking further about this:

Please consider going here:

http://www.microsoft.com/security/portal

and clicking on the link for 32-bit Windows Defender definitions in the
upper right.

These definitions are updated daily, and if what you are seeing is a false
positive, this will be a quick way of getting definitions which change the
detection.

(assuming that you are not running Windows XP 64 bit edition, or Vista 64
bit edition., in which case you will know that you need the 64-bit
definitions.)

 

[Joe Faulhaber[MSFT]]

Hi Maggi,

Clickspring will use common Windows filenames like rundll.exe, iexplore.exe,
and notepad.exe as its file names - can you please check the path of the
file detected and make sure it's from your VS installation? Also, the file
could have been replaced, see if the file date makes sense.

If you believe this is a false positive, please follow the "Submit a false
positive file to Microsoft" instructions at
http://www.microsoft.com/athome/security/spyware/software/isv/fpform.aspx.

And since this is a Microsoft file, I'd be quite suprised if we don't have
it in the collection we use to detect false positives, which makes a false
detection far less likely.

Regards,
Joe

 

[Guest]

Maggi there is more on this subject over in Home users

http://www.microsoft.com/communitie...7db-5e84-471d-acdc-5de6595ecd0c&lang=en&cr=US