New build 614 still try to download old definitions

[Mikolaj]

Chaotic performance=MS product.

No more often than hardware incompatibility, beta "performance-boosting"
drivers and PEBCAK - so stop trolling, please..

Besides - it's a BETA only and don't expect shining, polished product in it.

 

[Mikolaj]

Hmmm, I have tested it on XP HE, XP Pro will be tested on monday..
OK, tests have been done on Windows XP Pro (polish). First "dirty" ;-)
upgrade from 1.0.613 to 1.0.614 - aftre that says that signatures are 5727.
So click on Spyware Definitions on the Summary screen - and the result is
that (what is obviously not true) latest signatures are installed.
Second - clean instal of 614. 613 uninstalled, deleted what was lef over in
MSAS folder, fresh install - signatures are now 5725. Click on Spyware
Definitions - MSAS downloads and installs new 5729.

So it looks like the best way is to uninstall 1.0.613, delete C:\Program
Files\Microsoft AntiSpyware folder, make fresh install of 1.0.614 and start
the update process.

 

[plun]

Mikolaj formulated on måndag :

OK, tests have been done on Windows XP Pro (polish). First "dirty" ;-)
upgrade from 1.0.613 to 1.0.614 - aftre that says that signatures are 5727.
So click on Spyware Definitions on the Summary screen - and the result is
that (what is obviously not true) latest signatures are installed.
Second - clean instal of 614. 613 uninstalled, deleted what was lef over in
MSAS folder, fresh install - signatures are now 5725. Click on Spyware
Definitions - MSAS downloads and installs new 5729.

So it looks like the best way is to uninstall 1.0.613, delete C:\Program
Files\Microsoft AntiSpyware folder, make fresh install of 1.0.614 and start
the update process.

Hi Mikolaj

On a XP Pro PC I can see definition files dated June 16, maybe 5727
beacuse
MSAS tries to update to 5729 every time I "check for updates".

With a XP Home PC it is impossible to get other definitions then June 9
= 5725

Help-about says 5729 on both........

http://support.microsoft.com/default.aspx?scid=kb;en-us;892519
Not updated but we can see 5725, June 9

 

[Mikolaj]

Hi Mikolaj

On a XP Pro PC I can see definition files dated June 16, maybe 5727
beacuse
MSAS tries to update to 5729 every time I "check for updates".

With a XP Home PC it is impossible to get other definitions then June 9 =
5725

Help-about says 5729 on both........

http://support.microsoft.com/default.aspx?scid=kb;en-us;892519
Not updated but we can see 5725, June 9

Hi,

It really looks strange.. Now I'm chcecking it on my XP Pro workstation and
MSAS says, that it has 5729 signatures, but according to the article
http://support.microsoft.com/default.aspx?scid=kb;en-us;892519 you have
suggested, it looks like at your computer - that these are 5725 signatures
(at least dates and FCIV say so). Checking results are here:

C:\>FCIV -md5 -sha1 "c:\program files\Microsoft
Antispyware\gcThreatAuditScanData.gcd"
//
// File Checksum Integrity Verifier version 2.05.
//
MD5 SHA-1
-------------------------------------------------------------------------
7601929d47cdbb22e01730ac2b8951cd 1d41f1fffed47a42d23fe2bcf6217d0e267f9480
c:\program files\microsoft antispyware\gcthreatauditscandata.gcd

C:\>FCIV -md5 -sha1 "c:\program files\Microsoft
Antispyware\gcThreatAuditThreatData.gcd"
//
// File Checksum Integrity Verifier version 2.05.
//
MD5 SHA-1
-------------------------------------------------------------------------
665fa20e059fa33925b907d76bc748d6 9c8160045ec3d12ceb0d0f49d52771c41d3f0de7
c:\program files\microsoft antispyware\gcthreatauditthreatdata.gcd

So how to EXACTLY check the signature files?
Maybe this unability to verify the signatures also produces the error within
the update process (that one can't get the latest definitions)?

 

[plun]

Mikolaj formulated on måndag :

Hi,

It really looks strange.. Now I'm chcecking it on my XP Pro workstation and
MSAS says, that it has 5729 signatures, but according to the article
http://support.microsoft.com/default.aspx?scid=kb;en-us;892519 you have
suggested, it looks like at your computer - that these are 5725 signatures
(at least dates and FCIV say so). Checking results are here:

C:\>FCIV -md5 -sha1 "c:\program files\Microsoft
Antispyware\gcThreatAuditScanData.gcd"
//
// File Checksum Integrity Verifier version 2.05.
//
MD5 SHA-1
-------------------------------------------------------------------------
7601929d47cdbb22e01730ac2b8951cd 1d41f1fffed47a42d23fe2bcf6217d0e267f9480
c:\program files\microsoft antispyware\gcthreatauditscandata.gcd

C:\>FCIV -md5 -sha1 "c:\program files\Microsoft
Antispyware\gcThreatAuditThreatData.gcd"
//
// File Checksum Integrity Verifier version 2.05.
//
MD5 SHA-1
-------------------------------------------------------------------------
665fa20e059fa33925b907d76bc748d6 9c8160045ec3d12ceb0d0f49d52771c41d3f0de7
c:\program files\microsoft antispyware\gcthreatauditthreatdata.gcd

So how to EXACTLY check the signature files?
Maybe this unability to verify the signatures also produces the error within
the update process (that one can't get the latest definitions)?

Hi

Well, who knows.... MS Redmond wakes up now and they have the answer

 

[plun]

Hi Mikolaj, something for you to test:

A user named Taxman solved this workaround for 614 and def files

Just download them and extract with newer Winzip or 7-Zip
http://download.spynet.com/ASDefinitions/gcDeterminationData.gcz
http://download.spynet.com/ASDefinitions/gcThreatAuditScanData.gcz
http://download.spynet.com/ASDefinitions/gcThreatAuditThreatData.gcz


They are then dated June 24 and I beleive that versions with June 16 is
ver 5727
and June 24 is ver 5729.

So something is probably really corrupted within 614 and update
function and
maybe we will se version 615 soon................

C:\>FCIV -md5 -sha1 "c:\program files\Microsoft
Antispyware\gcThreatAuditScanData.gcd"
//
// File Checksum Integrity Verifier version 2.05.
//
MD5 SHA-1

Manual download, dated June 24:

C:\Program\Microsoft AntiSpyware>fciv -md5 -sha1 "c:\program\Microsoft
Antispywa
re\gcThreatAuditScanData.gcd"

File Checksum Integrity Verifier version 2.05.

MD5 SHA-1
-------------------------------------------------------------------------
a9159bf00863d3b822d4e79cab64f5d4
f768bf399f1c82220754af625c6b62bca7343019 c:\pro
gram\microsoft antispyware\gcthreatauditscandata.gcd

C:\>FCIV -md5 -sha1 "c:\program files\Microsoft
Antispyware\gcThreatAuditThreatData.gcd"
//
// File Checksum Integrity Verifier version 2.05.
//
MD5 SHA-1

Manual download, dated June 24


File Checksum Integrity Verifier version 2.05.

MD5 SHA-1

 

[Donald Anadell]

Hi Plun,

Thanks for posting this.

It cured the problem on my machine, however it's worth noting that the file extensions on these
three files had to be changed to .zip after downloading them in order for WinZip to be able to
extract them, at least with WinZip 8.1 this was necessary.

Thanks again,

Don

 

[Mikolaj]

Hi Mikolaj, something for you to test:

A user named Taxman solved this workaround for 614 and def files

Just download them and extract with newer Winzip or 7-Zip
http://download.spynet.com/ASDefinitions/gcDeterminationData.gcz
http://download.spynet.com/ASDefinitions/gcThreatAuditScanData.gcz
http://download.spynet.com/ASDefinitions/gcThreatAuditThreatData.gcz


They are then dated June 24 and I beleive that versions with June 16 is
ver 5727
and June 24 is ver 5729.

So something is probably really corrupted within 614 and update function
and
maybe we will se version 615 soon................

Thanks, downloaded and reloaded ;-) (into MSAS of course).
OK, so we have to wait for some movement from MSAS Team and until then
check the signatures manually..