G
Guest
Sorry for the delay in replying to you. I had replied to
similar questions from another advisor - Robin Walker -
who is also puzzled by my failure to carry out this
procedure. I think it must be something I an doing
wrongly - but what!! To answer your questions -
Yes I am on build .616 and I did delete gcUnCompress.dll
file before performing the repair. And I double-checked
that it had been deleted before carrying out the repair.
I have also tried the procedure after closing my
antivirus software and firewall.
Just an additional thought - I do have Spybot which I use
weekly to scan my computer. Do you think this could be
interfering with the procedure? Perhaps I should
uninstall this and try again.
What if I don't manage to carry out this repair? Will MS
eventually correct it themselves?
Regards
Alvis
similar questions from another advisor - Robin Walker -
who is also puzzled by my failure to carry out this
procedure. I think it must be something I an doing
wrongly - but what!! To answer your questions -
Yes I am on build .616 and I did delete gcUnCompress.dll
file before performing the repair. And I double-checked
that it had been deleted before carrying out the repair.
I have also tried the procedure after closing my
antivirus software and firewall.
Just an additional thought - I do have Spybot which I use
weekly to scan my computer. Do you think this could be
interfering with the procedure? Perhaps I should
uninstall this and try again.
What if I don't manage to carry out this repair? Will MS
eventually correct it themselves?
Regards
Alvis
-----Original Message-----
Are you on build .614?
See Help, about--should read 1.0.614.
Did you delete the gcUnCompress.dll file, before performing the repair
installation?
I'd suggest re-trying the procedure, checking carefully to be sure that the
file is gone before going on to the update repair.
Is there third-party software that might be "protecting" system files?
--
Alvis said:I am afraid this hasn't worked for me. I am in the Uk
and have Windows XP (Home). When I
rechecked "gcUnCompress.dll" is still 130.272 in length.
Should I have restarted the system"
Alvis
-----Original Message-----
Subject: Definition update recycling - Permanent Fix
From: "Robin Walker [MVP]" <[email protected]> Sent:
7/9/2005 3:33:19 PM
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)
.
.