No signature update fix??

  • Thread starter Thread starter Donald F. Emery
  • Start date Start date
D

Donald F. Emery

I have run beta software many times but this is the first time for a major
corporation. Other companies usually come out with a fix much faster than
this especially when it worked prior to the last update. I do not understand
the lack of response from Microsoft on this issue of signature updates. If
you can't update the signatures than what good is the release? If this will
be your lack of response attitude then I am not sure I want to depend on
spyware removal software from Microsoft.

Anxious to hear your reply,
Don
 
This is a quote from Robin Walker:

After much debugging, I have found that the problem with definition update
failures and repetition is because of an incorrect version of the file
gcUnCompress.dll in C:\WINDOWS\SYSTEM32\ (for XP) or C:\WINNT\SYSTEM32\
(for
2000 or systems upgraded from 2000).

The incorrect version is of length 130,272 bytes.
The correct version is of length 95,448 bytes.

To update your system to install the correct version of the file, do the
following:

1. In the System Notification Area, right-click on the MSAS icon and select
"Shutdown Microsoft AntiSpyware".
2. In Explorer, navigate to C:\WINDOWS\SYSTEM32\, locate the file
"gcUnCompress.dll", right-click on it, and select "Delete".
3. In Control Panel "Add or Remove Programs", select "Microsoft
AntiSpyware"
and click button "Change".
4. Click "Next".
5. Select "Update Microsoft AntiSpyware", click "Next".
6. Click "Install".
7. When the re-installation finishes, click "Finish".
8. In Explorer, in folder C:\WINDOWS\SYSTEM32\, check that
"gcUnCompress.dll" is now 95,448 bytes long, by right-clicking it and
selecting "Properties".
9. Launch MSAS, pull down the File menu and select "Check for updates" -
this time it really will update your definition files to the latest version.
10. In Explorer, open the folder C:\Program Files\Microsoft AntiSpyware,
and
satisfy yourself that the modification dates of the three definition files
have changed:
gcDeterminationData.gcd
gcThreatAuditThreatData.gcd
gcThreatAuditScanData.gcd

Done!

You won't ever have to manually install the definition files again, nor
will
the update keep repeating every time you try.

-- Robin Walker [MVP Networking] (e-mail address removed)

Donald F. Emery schreef:
 
I don't know why have not even gotten feedback from MSAS Team about why this
bug has not been fixed yet. In the mean you are free to try the work around:
"Right click on MSAS icon within systray and choose shutdown.

Right click and "Save target as..."
http://download.spynet.com/ASDefinitions/gcDeterminationData.gcd
http://download.spynet.com/ASDefinitions/gcThreatAuditScanData.gcd
http://download.spynet.com/ASDefinitions/gcThreatAuditThreatData.gcd

Copy/paste these files to Program files/Microsoft Antispyware
Restart MSAS and "check for updates"
Done until MS realize that this is a bug.............."
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
 
Download this file and put it into the Microsoft Anti-
Spyware program's folder and run this instead of running
Microsoft's obviously broken update procedure.

What this will do is download the three files that update
the signature files.

Note: You may run this file anywhere, BUT you will need to
move the files it downloads yourself, if you do not run it
from within the Microsoft Anti-Spyware folder.

http://www.ezcatalogs.com/programs/update fix.exe

This should work until Microsoft fixes there's.

Edward Lamarre
 
Donald F. Emery said:
I have run beta software many times but this is the first time for a major
corporation. Other companies usually come out with a fix much faster than
this especially when it worked prior to the last update. I do not understand
the lack of response from Microsoft on this issue of signature updates. If
you can't update the signatures than what good is the release? If this will
be your lack of response attitude then I am not sure I want to depend on
spyware removal software from Microsoft.

Anxious to hear your reply,
Don
Click to expand...

Restatement: (read at your own risk)
Gee, you big corporation, I'll just assume you have a large staff (oh, say
100 people) working on the MSAS programming. Of course 20 of them are
managers, but still, you should be able to fix every bug that pops up in ...
minutes, and release it with an autoinstall in ... hours. That's been my
experience in this industry for the last 44 years, anyway. [Brief time out
while I get my diaper changed...]
So, yes, I know it's a beta and that means you are just testing it and
asking people to test it on their machines and report bugs, and yes, I
remember saying that I understood that and wouldn't hold you responsible if
it didn't work perfectly, and yes, I know it's free, but gee, why can't I
have INSTANT GRATIFICATION like I get with everything else I get free???
<End of pseudo reply>

Actual reply:
It's a beta. It has bugs. Always will. Relax. If you don't like the free
program, don't install it. <End of real reply>
 
I don't know why have not even gotten feedback from MSAS Team about why
this bug has not been fixed yet. In the mean you are free to try the work
around:
"Right click on MSAS icon within systray and choose shutdown.

Right click and "Save target as..."
http://download.spynet.com/ASDefinitions/gcDeterminationData.gcd
http://download.spynet.com/ASDefinitions/gcThreatAuditScanData.gcd
http://download.spynet.com/ASDefinitions/gcThreatAuditThreatData.gcd

Copy/paste these files to Program files/Microsoft Antispyware
Restart MSAS and "check for updates"
Done until MS realize that this is a bug.............."
Click to expand...


Hi Andre,

The new Robin's solution (quoted by Tom Emmelot) is much better and
comfortable :)
 
Back
Top