New defs for MS AntiSpyware

  • Thread starter Thread starter OldBoy
  • Start date Start date
Apparently not for long--mine says it is now updating to 5743. Will look
again at the numbers when it completes.
 
Hmm.

Was on 5739

Ran Microsoft Antispyware Updater, and it claimed it was going to 5743.

Opened Microsoft Antispyware, said it was on 5743.

Did File, Check for update.

Said it was on 5741, and was putting in 5743.

When done, Help About read 5743, with a current timestamp.

Did File, check for update, and again cycled 5741 to 5743.

I recommend waiting a bit on this one--looks like there was a quick change
that hasn't propagated.
 
Still have the same problem of repetitive download of the
same defintions. Anyone have any idea when MS is going to
fix this problem?
 
Can you say what numbers you are seeing?

My impression at this point is that we are seeing issues beyond the
individual client machines, especially early in the definition release
cycle, such as right now.
 
5743 here too


--
The people think the Constitution protects their rights;
But government sees it as an obstacle to be overcome.
some support
http://www.usdoj.gov/olc/secondamendment2.htm



message
| Apparently not for long--mine says it is now updating to
5743. Will look
| again at the numbers when it completes.
|
| --
|
|
| > 5741 is out
| >
| > OldBoy
| >
| >
|
|
 
I wouldn't worry too much about this, but you might try a manual update on a
machine and see whether that cycle repeats.

--
 
Hello Bill,

this one you would not beleaf! ;)
I was today by a friend, where i put in May MSAS on his PC, did his scan
everyday, was automatic updated till 615 and was on 5741 as def and had
never trouble with anything!!!! ;)
My PC is on 5743 with no problem, automatic update!!!
So keep on smiling!

Regards >*< TOM >*<
 
As robin walker stated in earlier posts if your using build 615 the waiting
game is the only fix.waiting for all the caches to be updated. i just
checked only one *.cat is dated today the other 2 are dated for yesterday
only one file was updated untill the stale .cats are updated it will only be
time till the full update is complete.
 
I believe that most users are not experiencing the issues that fill these
groups--otherwise they'd be overflowing!

I know from looking at the 3 dozen or so machines I see regularly in small
offices that the issues are out there, but they are generally taking care of
themselves--i.e. folks on 614 weren't updating, but they got offered .615,
and that fixed it.

--
 
MSAS - v615 -w2kPro & XPH
Updated Adaware w2kPro - worked fine
Tried to update MSAS on w2kPro and get a "Cannot connect to internet" message.

Updated MSAS on my wife's XPH machine - worked fine.

Any ideas?
 
OK - now it's getting strange!
As soon as I sent my post I got a message that "new update is ready to install".
I said OK, came back and said I was updated.
Checked and "About" has old version (5739) but with current date (the problem that's
existed from day 1).
So, just for fun, I did the manual update and got the "cannot connect to the internet"
message that triggered my 1st post.

Now, it's a hot day and I admit to having consumed about four beers-so maybe my thinking
isn't as straight as it could be-but I'm getting confused!
 
Help, about cannot be trusted to be accurate.

It is accurate if you have just completed a manual update (file, check for
update) which has, in fact, been able to reach the servers via the
Internet--i.e. probably not in the case you just mentioned.

Others have observed that it should be accurate upon restarting the program.

--
 
Back
Top