unins000.exe found by defs 5711

  • Thread starter Thread starter Ron
  • Start date Start date
R

Ron

Now this is strange. When I had definitions 5709 no
spyware was found in 2
scans. Now with definitions 5711 after scan I have
unins000.exe found in
SpywareBlaster directory as spyware. This is freaking me
out.
Ed Barba<<<

I found it, too. I'm quarantining it. What harm can
that cause?

Ron
 
Ron said:
spyware was found in 2
scans. Now with definitions 5711 after scan I have
unins000.exe found in
SpywareBlaster directory as spyware. This is freaking me
out.
Ed Barba<<<

I found it, too. I'm quarantining it. What harm can
that cause?
If you permanently delete it, you can't uninstall SpywareBlaster any more!

Gr. Jan
 
This is a false positive if the file has properties indicating that it is
version 51.34.0.0 of Innovisions installer package.

You may have trouble uninstalling the associated software if the file is
unavailable.
 
Also now when I check for updates it keeps trying to reinstall 5711 even
though I already have it installed. Whats up with that?
Ed
 
Ron - can you please double check the files actually in place on your
machine?

Here's what 5711 looks like on my machine--and it fixes this issue for
me--i.e. the false positive goes away.
------------------------------

04/21/2005 12:13 AM 2,309,022 gcThreatAuditScanData.gcd
04/22/2005 06:46 PM 1,320,692 gcThreatAuditThreatData.gcd

Detailed File Analysis
Display name: gcThreatAuditThreatData.gcd
Name: gcThreatAuditThreatData.gcd
Publisher: Unspecified
Path: D:\Program Files\Microsoft AntiSpyware\gcThreatAuditThreatData.gcd
Size: 1320692 bytes
Create date: Friday April 15, 2005
Access date: Saturday April 23, 2005
Modified date: Friday April 22, 2005

MD5: b14f9714dec123e0194f7febd9d09c57

Detailed File Analysis
Display name: gcThreatAuditScanData.gcd
Name: gcThreatAuditScanData.gcd
Publisher: Unspecified
Path: D:\Program Files\Microsoft AntiSpyware\gcThreatAuditScanData.gcd
Size: 2309022 bytes
Create date: Friday April 15, 2005
Access date: Saturday April 23, 2005
Modified date: Thursday April 21, 2005

MD5: 71790386817e73328e9cb157119e01cd
 
Correct threatauditthreatdata now by re-downloading 5711,
restored the quarantined file, and Quick Scan is not
picking it up (saw it go right through the x-ray machine
or oscilloscope. Thanks for the help.
 
Great--I've now seen 4 separate reports of difficulty with this
update--don't know why, but it seems to be "sticky."
 
MICROSOFT IS TERRIBLY WRONG BY MAKING THIS!!!!

"unins000.exe" is no spyware it's just an uninstall file
made by inno setup:

http://www.innosetup.com

many applications use this file.

MS Spyaware does not check the insides of "unins000.exe",
it just seems to alert you because of the same file name
with that keylogger!!!

microsoft is hurting the market of alernative software
producers by these false alerts.... :(

(escpecially those who are using free innosetup)

well... well... well...
 
OH_MY_GOD said:
MICROSOFT IS TERRIBLY WRONG BY MAKING THIS!!!!

"unins000.exe" is no spyware it's just an uninstall file
made by inno setup:

http://www.innosetup.com

many applications use this file.

MS Spyaware does not check the insides of "unins000.exe",
it just seems to alert you because of the same file name
with that keylogger!!!

microsoft is hurting the market of alernative software
producers by these false alerts.... :(

(escpecially those who are using free innosetup)

well... well... well...


MS knows this already and they indeed hurry up with new defs !

Credit to MS for that.
 
This is indeed a false positive.

However, this false positive is FIXED in the 5711 definitions.

So--there is another problem--in your case, although you believe you have
5711 definitions in place, you do not, in actuality.

Can you try:

1) do an update reinstall of the program:

Control Panel, add or remove programs, Microsoft Antispyware, change,
update.

2) After that completes, go to File, Check for updates.

Attempt to verify the actual definition files on your drive according to the
information in this KB article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;892519

This article is not yet updated for 5711, but it shows which files to check.
 
Dear God,

FWIW, the error was for a particular version .exe, not all of them.

Let's not load up the Ark so quickly with panic attacks.

Ron Chamberlin
MS-MVP
 
Back
Top