1.0.614 updates

  • Thread starter Thread starter Russ
  • Start date Start date
R

Russ

The "better beta" is driving me crazy. I have manually
updated definitions 5731 and 5733. In each case Auto
Update reverts the update to 5729.

Either the program is totally losing track of the updates
or something else is going on.

I just finished manually updating to 5733. I checked to
see that MSAS showed the correct definitions.
I just reopened MSAS. It now shows definitions 5729 need
to be updated to 5733.

This is an endless loop. Never occurred until
the "Better Beta".
 
Please see the .announcements group.
Look for a July 9th posting from Robin Walker.
The simple steps in that post will fix this problem
permanently.
 
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.
--
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
 
We are investigating this, and hope to have something shortly.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
How about

1) Delete the three .gcd definition files (which are 5729)
2) Update from the program (this loads the new definitions)

I hope this helps.
 
This doesn't work for some users.

--

Rich said:
How about

1) Delete the three .gcd definition files (which are 5729)
2) Update from the program (this loads the new definitions)

I hope this helps.
Click to expand...
 
Russ,
I used the suggestion of Edward Lamarre and used the
connection he suggested and it fixed the problem on my
computer. There was some heated correspondence over
Edward's posting however i loaded it 3 days ago and
nothing untoward has happened except when i ran the
suggested link, it upgraded to 5733 no problems.

There was also a remedy suggeted by Robin Walker, however
i found that a bit complicated even to read it let alone
to try and follow it as i am not a computer freak, just an
average user trying to keep my programs updated with the
latest on offer.
 
The heat over Edward Lamarre's post is less to do with the content--it was
and is entirely innocent and meant to be helpfuo--than with the broader
issue of the danger of running an anonymously provided binary.

Microsoft is aware of the definition update issue, and I would expect that
we'll hear something from them soon. I've found Robin Walker's instructions
quite easy to use, in practice, but if you have any qualms about it at all,
I'd wait.

--
 
Back
Top