D
D@annyBoy
MSAS keeps upating 5701
hmmmm......................
anyone else?
hmmmm......................
anyone else?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
E
Ed Barba
No problem here. It updated to 5701 the first time and subsequent manual
checks for updates shows I have the latest definitions.
Ed
checks for updates shows I have the latest definitions.
Ed
D
D@annyBoy
mine keeps wanting to update to 5701
Ed Barba said:No problem here. It updated to 5701 the first time and subsequent manual
checks for updates shows I have the latest definitions.
Ed
D
D@annyBoy
had to do a uninstall and reinstall before everything is alright
hmmmm............................................................................
hmmmm............................................................................
O
Ofelas
I'd go to Add/Remove Programs, select the "Change" option
for MSAS, select "Update" & go from there...
Keep us posted!
for MSAS, select "Update" & go from there...
Keep us posted!
E
Ed Barba
I know I had to uninstall and reinstall because I had this happen with a
prior definition but I do not know why. But the uninstall and reinstall
fixed the problem the last time. I forget the number of the definition
though.
Ed
prior definition but I do not know why. But the uninstall and reinstall
fixed the problem the last time. I forget the number of the definition
though.
Ed
D
D@annyBoy
it's happening again
5701 keeps updating even though after uninstall and reinstall
5701 keeps updating even though after uninstall and reinstall
D
D@annyBoy
no go
I did a repair and update
checked for updates and 5701 is still being downloaded
oh well..........................
I did a repair and update
checked for updates and 5701 is still being downloaded
oh well..........................
B
Bill Sanderson
Have you tried deleting the definition files?
D
D@annyBoy
B
Bill Sanderson
http://support.microsoft.com/default.aspx?scid=kb;en-us;892519
The above article gives the names (and I think, the location--the folder
Microsoft Antispyware is installed in.)
Shut down Microsoft Antispyware via right-clicking on the system tray icon,
and delete the files--they should have the same date and time, and the names
as shown in the KB article.
See what happens.
The above article gives the names (and I think, the location--the folder
Microsoft Antispyware is installed in.)
Shut down Microsoft Antispyware via right-clicking on the system tray icon,
and delete the files--they should have the same date and time, and the names
as shown in the KB article.
See what happens.
D
D@annyBoy
it works
thanks
do you know the cause?
can you add MS article to your FAQ?
thanks
do you know the cause?
can you add MS article to your FAQ?
B
Bill Sanderson
No - I don't know the cause--my thinking was that something was preventing
the in-place files from being replaced, and just deleting them might kick
something. My general observation about the GCD files--I should check this
with a clean install sometime--is that they are re-created on first
execution if you delete them. This can be useful with the files that
contain user settings--you can reset them to the initial defaults.
So--I'm not sure what happens--in my test, I deleted the current defs which
were one batch out of date, and expected that it would then revert to 5687
which was what was included in the download. Instead, it went to 5699,
which was then current--or something like that. There are also temporary
files involved, and I'm not sure how.
I'm gonna hold off adding this to the FAQ for a bit, if I may.
the in-place files from being replaced, and just deleting them might kick
something. My general observation about the GCD files--I should check this
with a clean install sometime--is that they are re-created on first
execution if you delete them. This can be useful with the files that
contain user settings--you can reset them to the initial defaults.
So--I'm not sure what happens--in my test, I deleted the current defs which
were one batch out of date, and expected that it would then revert to 5687
which was what was included in the download. Instead, it went to 5699,
which was then current--or something like that. There are also temporary
files involved, and I'm not sure how.
I'm gonna hold off adding this to the FAQ for a bit, if I may.
D
D@annyBoy
after deleting the files and restarting MSAS, the files were recreated and
problem was solved
I think a current copy is saved somewhere
will do a search on the harddisk
problem was solved
I think a current copy is saved somewhere
will do a search on the harddisk
B
Bill Sanderson
That was my experience, too--I expected to end up with the original version
from the download, and ended up with the latest. I've never spent the time
to figure out how this works---if I did, it might give me a clue to what's
going wrong, but I expect Microsoft has that under control, and probably
doesn't need my time used that way.
from the download, and ended up with the latest. I've never spent the time
to figure out how this works---if I did, it might give me a clue to what's
going wrong, but I expect Microsoft has that under control, and probably
doesn't need my time used that way.
C
citizenDAK
I have two machines, XP and 2k, neither of which
auto-updates it's signatures. Bill Sanderson's suggestion
fixed it for me:
(It was difficult for me to find in these forums, so I'm
posting a summary it here.)
1. Shut down MSAS.
2. Delete the two signature files:
gcThreatAuditScanData.gcd
gcThreatAuditThreatData.gcd
3. [Disk Cleanup]: removed "Downloaded Program Files"
4. Restart MSAS and then flail about... Probably just
takes patience to wait for it to update itself? (The ugly
details are below if you're interested.)
On computer #1: First I checked for updates, but it didn't
work. "About" listed an old sig version. Next I started a
quick-scan. Finally I re-checked "About" and it listed the
latest version, 5701. (Running the scan seemed to
"magically" get the new sigs?)
Double checked on computer #2: About listed old ver.
Start then abort quick scan, still About listed old ver.
Check for updates, didn't look like it did anything.
Start/abort quick scan again. Sig files started appearing
in the program folder but were too small. About still old
ver. Waited, then About again, finally it listed 5701 and
the files looked about the right sizes.
good luck
auto-updates it's signatures. Bill Sanderson's suggestion
fixed it for me:
(It was difficult for me to find in these forums, so I'm
posting a summary it here.)
1. Shut down MSAS.
2. Delete the two signature files:
gcThreatAuditScanData.gcd
gcThreatAuditThreatData.gcd
3. [Disk Cleanup]: removed "Downloaded Program Files"
4. Restart MSAS and then flail about... Probably just
takes patience to wait for it to update itself? (The ugly
details are below if you're interested.)
On computer #1: First I checked for updates, but it didn't
work. "About" listed an old sig version. Next I started a
quick-scan. Finally I re-checked "About" and it listed the
latest version, 5701. (Running the scan seemed to
"magically" get the new sigs?)
Double checked on computer #2: About listed old ver.
Start then abort quick scan, still About listed old ver.
Check for updates, didn't look like it did anything.
Start/abort quick scan again. Sig files started appearing
in the program folder but were too small. About still old
ver. Waited, then About again, finally it listed 5701 and
the files looked about the right sizes.
good luck
B
Bill Sanderson
There are several issues involved in what you report here.
First--the actual non-update. Don't know the cause, but the fix seems to be
solid.
Second--the appearances afterward. In my case(s)--I've just restarted
Microsoft Antispyware and the version number has been 5703.
However, there's an appearance bug where often you will need to file, check
for updates--and then look at help about, and the info should be correct.
--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
I have two machines, XP and 2k, neither of which
auto-updates it's signatures. Bill Sanderson's suggestion
fixed it for me:
(It was difficult for me to find in these forums, so I'm
posting a summary it here.)
1. Shut down MSAS.
2. Delete the two signature files:
gcThreatAuditScanData.gcd
gcThreatAuditThreatData.gcd
3. [Disk Cleanup]: removed "Downloaded Program Files"
4. Restart MSAS and then flail about... Probably just
takes patience to wait for it to update itself? (The ugly
details are below if you're interested.)
On computer #1: First I checked for updates, but it didn't
work. "About" listed an old sig version. Next I started a
quick-scan. Finally I re-checked "About" and it listed the
latest version, 5701. (Running the scan seemed to
"magically" get the new sigs?)
Double checked on computer #2: About listed old ver.
Start then abort quick scan, still About listed old ver.
Check for updates, didn't look like it did anything.
Start/abort quick scan again. Sig files started appearing
in the program folder but were too small. About still old
ver. Waited, then About again, finally it listed 5701 and
the files looked about the right sizes.
good luck
First--the actual non-update. Don't know the cause, but the fix seems to be
solid.
Second--the appearances afterward. In my case(s)--I've just restarted
Microsoft Antispyware and the version number has been 5703.
However, there's an appearance bug where often you will need to file, check
for updates--and then look at help about, and the info should be correct.
--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
I have two machines, XP and 2k, neither of which
auto-updates it's signatures. Bill Sanderson's suggestion
fixed it for me:
(It was difficult for me to find in these forums, so I'm
posting a summary it here.)
1. Shut down MSAS.
2. Delete the two signature files:
gcThreatAuditScanData.gcd
gcThreatAuditThreatData.gcd
3. [Disk Cleanup]: removed "Downloaded Program Files"
4. Restart MSAS and then flail about... Probably just
takes patience to wait for it to update itself? (The ugly
details are below if you're interested.)
On computer #1: First I checked for updates, but it didn't
work. "About" listed an old sig version. Next I started a
quick-scan. Finally I re-checked "About" and it listed the
latest version, 5701. (Running the scan seemed to
"magically" get the new sigs?)
Double checked on computer #2: About listed old ver.
Start then abort quick scan, still About listed old ver.
Check for updates, didn't look like it did anything.
Start/abort quick scan again. Sig files started appearing
in the program folder but were too small. About still old
ver. Waited, then About again, finally it listed 5701 and
the files looked about the right sizes.
good luck
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.