Microsoft AntiSpyware Beta Version .615

[Guest]

I have had no problems with the MS AntiSpyware, lately, until yesterday. It
did an update, yesterday (Oct. 26th.) and gave me last week's update, not a
'new' update. What would cause this problem? I wondered if Spy Sweeper could
be causing a conflict with this software. MS AntiSpyware re-updated to the
Microsoft Anti-Spyware Definitions "5769." If anyone could help or has had
the same problem and knows what could be causing an old update, I would
appreciate it.

My Spy Sweeper version and build is: 4.5.5 (build 604). Spy Sweeper has not
caused any conflicts with Microsoft AntiSpyware in any of the previous
versions I have had, but has several new features so maybe someone has some
answers.

My diagnostics for MS AntiSpyware is below if this will help:

Microsoft AntiSpyware version 1.0.615
Windows OS: XP
Windows OS Version Info: 148
Windows OS Major Version: 5
Windows OS Minor Version: 1
Windows OS Build: 2600
Current Path: C:\Program Files\Microsoft AntiSpyware
Install Path: C:\Program Files\Microsoft AntiSpyware\
Session.RunMode: 5
Session.TimeBombDaysRemaining: 65
Session.TimeBombExpirationDate: 12/31/2005
Real-time protection running: True
Real-time protection enabled: True
Security Agents Application Enabled: True
Security Agents Internet Enabled: True
Security Agents System Enabled: True
Security Agents Checkpoints: 59
Definitions Update Date: 10/26/2005 9:57:50 PM
AutoUpdater Enabled: 1
AutoUpdater AutoApply Enabled: 1
Definitions Increment Version: 122/122
Definitions ThreatAuditThreatData: 1290536
Definitions ThreatAuditScanData: 2800884
Definitions DeterminationData: 616803

Thanks you much, in advance.

 

[Dave M]

Hi Mary;
Also running SS 4.5.5, and your MSAS diagnostics match mine. I just tried the
update and none is available yet. Although they usually come on Thursday, it
hasn't happened yet. So I can only surmise that you've been running with
definitions that weren't fully current until yesterday, the 26th. You're
defiantly current for right this second though, until perhaps later today. Are
you running on dialup? I've seen update problems a lot using dialup, but never
considered SpySweeper, either 4.0 or 4.5 as a potential conflict, maybe I
should. About the only way to tell all the definition line counts and
increments are correct is to ask what's current on this forum. It took me 12
update attempts to get fully current two weeks ago. Then last week it only took
one.... weirdness, but we're not alone, many are having this "experience".

Here's what to watch for and compare in the diagnostics, (these are from my
system):
Spyware Definition Version: 5769
Definitions Increment Version: 122/122
Definitions ThreatAuditThreatData: 1290536
Definitions ThreatAuditScanData: 2800884
Definitions DeterminationData: 616803

 

[Dave M]

Hi Mary;
Also running SS 4.5.5, and your MSAS diagnostics match mine. I just tried the
update and none is available yet. Although they usually come on Thursday, it
hasn't happened yet. So I can only surmise that you've been running with
definitions that weren't fully current until yesterday, the 26th. You're
defiantly current for right this second though, until perhaps later today. Are
you running on dialup? I've seen update problems a lot using dialup, but never
considered SpySweeper, either Version 4.0 or 4.5 as a potential conflict, maybe
I
should. About the only way to tell all the definition line counts and
increments are correct is to ask what's current on this forum. It took me 12
update attempts to get fully current two weeks ago. Then last week it only took
one.... weirdness, but we're not alone, many are having this "experience".

Here's what to watch for and compare in the diagnostics, (these are from my
system):
Spyware Definition Version: 5769
Definitions Increment Version: 122/122
Definitions ThreatAuditThreatData: 1290536
Definitions ThreatAuditScanData: 2800884
Definitions DeterminationData: 616803

 

[Bill Sanderson]

Mary - if you did updates both last week and yesterday, and got the same
definitions, this indicates that the update last week was not complete.

However, looking at your diagnostic below, it appears to me that you are
fine at the moment--i.e. yesterdays update worked properly--so I'd not worry
about this.

Updates are often available sometime late Thursday afternoon (or later.)
The update process is more likely to be unsuccessful if you try it very
early in the release cycle--i.e. just after they are first released. One
way to gauge the success is to look for the equivalent of the 122/122 in
your diagnostic list--if both numbers have incremented to the same number,
that's a good indicator of a successful update, I believe.

 

[Guest]

Thanks for the reply, Dave M. Usually I notice if the update doesn't update
to the latest version but missed this -- odd fluke. Yes, MS AntiSpware
usually updates on Thursday's and probably will later, today. If I still have
the problem, will report to the 'professionals' that read these posts. Is the
first time in quite awhile that my updater didn't update, correctly. Had
these update problems shortly after Build .615 came out and it worked itself
out of the update problem after following another poster's suggestions. Will
be curious to see if it updates correctly, this next time. Am updated now,
one week later. I enjoy this software and has been very useful.

Thank you. Have a nice day.


Mary

P.S. Am using cable. No dialup connection.

*************************

:

Hi Mary;
Also running SS 4.5.5, and your MSAS diagnostics match mine. I just tried the
update and none is available yet. Although they usually come on Thursday, it
hasn't happened yet. So I can only surmise that you've been running with
definitions that weren't fully current until yesterday, the 26th. You're
defiantly current for right this second though, until perhaps later today.
Are
you running on dialup? I've seen update problems a lot using dialup, but
never
considered SpySweeper, either Version 4.0 or 4.5 as a potential conflict,
maybe
I should. About the only way to tell all the definition line counts and
increments are correct is to ask what's current on this forum. It took me 12
update attempts to get fully current two weeks ago. Then last week it only
took
one.... weirdness, but we're not alone, many are having this "experience".

Here's what to watch for and compare in the diagnostics, (these are from my
system):
Spyware Definition Version: 5769
Definitions Increment Version: 122/122
Definitions ThreatAuditThreatData: 1290536
Definitions ThreatAuditScanData: 2800884
Definitions DeterminationData: 616803
--
Regards, Dave


Mary wrote:
I have had no problems with the MS AntiSpyware, lately, until yesterday. It
did an update, yesterday (Oct. 26th.) and gave me last week's update, not a
'new' update. What would cause this problem? I wondered if Spy Sweeper could
be causing a conflict with this software. MS AntiSpyware re-updated to the
Microsoft Anti-Spyware Definitions "5769." If anyone could help or has had
the same problem and knows what could be causing an old update, I would
appreciate it.

My Spy Sweeper version and build is: 4.5.5 (build 604). Spy Sweeper has not
caused any conflicts with Microsoft AntiSpyware in any of the previous
versions I have had, but has several new features so maybe someone has some
answers.

My diagnostics for MS AntiSpyware is below if this will help:

Microsoft AntiSpyware version 1.0.615
Windows OS: XP
Windows OS Version Info: 148
Windows OS Major Version: 5
Windows OS Minor Version: 1
Windows OS Build: 2600
Current Path: C:\Program Files\Microsoft AntiSpyware
Install Path: C:\Program Files\Microsoft AntiSpyware\
Session.RunMode: 5
Session.TimeBombDaysRemaining: 65
Session.TimeBombExpirationDate: 12/31/2005
Real-time protection running: True
Real-time protection enabled: True
Security Agents Application Enabled: True
Security Agents Internet Enabled: True
Security Agents System Enabled: True
Security Agents Checkpoints: 59
AutoUpdater Enabled: 1
AutoUpdater AutoApply Enabled: 1
Definitions Increment Version: 122/122
Definitions ThreatAuditThreatData: 1290536
Definitions ThreatAuditScanData: 2800884
Definitions DeterminationData: 616803

Thanks you much, in advance.

 

[Guest]

Mr. Sanderson:

Doesn't it defeat the whole purpose of protecting your system if the update
didn't "take" until 1 whole week later? I am waiting for this week's update
and haven't seen any postings of any new updates, as of yet. Hopefully, it
won't take another whole week for the latest update to install correctly.
replying . I uninstalled MS AntiSpyware and deleted the folder and started
over, hoping this may help the problem. The 'updating' seems to be a little
fickle from time to time. I do find this software very handy and helpful when
it works right.

Thank you for your reply.


Mary

****************************

:

Mary - if you did updates both last week and yesterday, and got the same
definitions, this indicates that the update last week was not complete.

However, looking at your diagnostic below, it appears to me that you are
fine at the moment--i.e. yesterdays update worked properly--so I'd not worry
about this.

Updates are often available sometime late Thursday afternoon (or later.)
The update process is more likely to be unsuccessful if you try it very
early in the release cycle--i.e. just after they are first released. One
way to gauge the success is to look for the equivalent of the 122/122 in
your diagnostic list--if both numbers have incremented to the same number,
that's a good indicator of a successful update, I believe.

--

I have had no problems with the MS AntiSpyware, lately, until yesterday. It
did an update, yesterday (Oct. 26th.) and gave me last week's update, not
a 'new' update. What would cause this problem? I wondered if Spy Sweeper
could
be causing a conflict with this software. MS AntiSpyware re-updated to the
Microsoft Anti-Spyware Definitions "5769." If anyone could help or has had
the same problem and knows what could be causing an old update, I would
appreciate it.

My Spy Sweeper version and build is: 4.5.5 (build 604). Spy Sweeper has
not caused any conflicts with Microsoft AntiSpyware in any of the previous
versions I have had, but has several new features so maybe someone has
some answers.

My diagnostics for MS AntiSpyware is below if this will help:

Microsoft AntiSpyware version 1.0.615
Windows OS: XP
Windows OS Version Info: 148
Windows OS Major Version: 5
Windows OS Minor Version: 1
Windows OS Build: 2600
Current Path: C:\Program Files\Microsoft AntiSpyware
Install Path: C:\Program Files\Microsoft AntiSpyware\
Session.RunMode: 5
Session.TimeBombDaysRemaining: 65
Session.TimeBombExpirationDate: 12/31/2005
Real-time protection running: True
Real-time protection enabled: True
Security Agents Application Enabled: True
Security Agents Internet Enabled: True
Security Agents System Enabled: True
Security Agents Checkpoints: 59
Definitions Update Date: 10/26/2005 9:57:50 PM
AutoUpdater Enabled: 1
AutoUpdater AutoApply Enabled: 1
Definitions Increment Version: 122/122
Definitions ThreatAuditThreatData: 1290536
Definitions ThreatAuditScanData: 2800884
Definitions DeterminationData: 616803

Thank you much, in advance.

 

[Bill Sanderson]

Yes indeed--the fact that the update didn't happen last week is a serious
bug.

There hasn't been an update issued yet this week, so we can't tell whether
you are out of the woods yet.

The update process is a bit crotchety, especially if you try to do it
manually the instant the update is released.

Beta1 is nearing the end of its lifespan, I think. I'm sure that the
process involved will be improved with beta2.
--

 

[Guest]

Mr. Sanderson:

Hurray, hurray! I am guessing that the updater 'took' this time. Diagnostics
showed info below:

Microsoft AntiSpyware version 1.0.615
Windows OS: XP
Windows OS Version Info: 148
Windows OS Major Version: 5
Windows OS Minor Version: 1
Windows OS Build: 2600
Current Path: C:\Program Files\Microsoft AntiSpyware
Install Path: C:\Program Files\Microsoft AntiSpyware\
Session.RunMode: 5
Session.TimeBombDaysRemaining: 63
Session.TimeBombExpirationDate: 12/31/2005
Real-time protection running: True
Real-time protection enabled: True
Security Agents Application Enabled: True
Security Agents Internet Enabled: True
Security Agents System Enabled: True
Security Agents Checkpoints: 59
Definitions Update Date: 10/29/2005 9:54:02 AM
AutoUpdater Enabled: 1
AutoUpdater AutoApply Enabled: 1
Definitions Increment Version: 124/124
Definitions ThreatAuditThreatData: 1291846
Definitions ThreatAuditScanData: 2817373
Definitions DeterminationData: 631595

The definitions increment version numbers are the same so all is well, this
time? The latest update I received this morning is "5771", so this is
current??


Mary

:

Yes indeed--the fact that the update didn't happen last week is a serious
bug.

There hasn't been an update issued yet this week, so we can't tell whether
you are out of the woods yet.

The update process is a bit crotchety, especially if you try to do it
manually the instant the update is released.

Beta1 is nearing the end of its lifespan, I think. I'm sure that the
process involved will be improved with beta2.
--

Mr. Sanderson:

Doesn't it defeat the whole purpose of protecting your system if the
update
didn't "take" until 1 whole week later? I am waiting for this week's
update
and haven't seen any postings of any new updates, as of yet. Hopefully, it
won't take another whole week for the latest update to install correctly.
replying . I uninstalled MS AntiSpyware and deleted the folder and started
over, hoping this may help the problem. The 'updating' seems to be a
little
fickle from time to time. I do find this software very handy and helpful
when
it works right.

Thank you for your reply.


Mary

****************************

:

Mary - if you did updates both last week and yesterday, and got the same
definitions, this indicates that the update last week was not complete.

However, looking at your diagnostic below, it appears to me that you are
fine at the moment--i.e. yesterdays update worked properly--so I'd not
worry
about this.

Updates are often available sometime late Thursday afternoon (or later.)
The update process is more likely to be unsuccessful if you try it very
early in the release cycle--i.e. just after they are first released. One
way to gauge the success is to look for the equivalent of the 122/122 in
your diagnostic list--if both numbers have incremented to the same number,
that's a good indicator of a successful update, I believe.

--

I have had no problems with the MS AntiSpyware, lately, until yesterday.
It did an update, yesterday (Oct. 26th.) and gave me last week's update, not
a 'new' update. What would cause this problem? I wondered if Spy Sweeper
could
be causing a conflict with this software. MS AntiSpyware re-updated to the
Microsoft Anti-Spyware Definitions "5769." If anyone could help or has had
the same problem and knows what could be causing an old update, I would
appreciate it.

My Spy Sweeper version and build is: 4.5.5 (build 604). Spy Sweeper has
not caused any conflicts with Microsoft AntiSpyware in any of the previous
versions I have had, but has several new features so maybe someone has
some answers.

My diagnostics for MS AntiSpyware is below if this will help:

Microsoft AntiSpyware version 1.0.615
Windows OS: XP
Windows OS Version Info: 148
Windows OS Major Version: 5
Windows OS Minor Version: 1
Windows OS Build: 2600
Current Path: C:\Program Files\Microsoft AntiSpyware
Install Path: C:\Program Files\Microsoft AntiSpyware\
Session.RunMode: 5
Session.TimeBombDaysRemaining: 65
Session.TimeBombExpirationDate: 12/31/2005
Real-time protection running: True
Real-time protection enabled: True
Security Agents Application Enabled: True
Security Agents Internet Enabled: True
Security Agents System Enabled: True
Security Agents Checkpoints: 59
Definitions Update Date: 10/26/2005 9:57:50 PM
AutoUpdater Enabled: 1

 

[Bill Sanderson]

Hurray, hurray! I am guessing that the updater 'took' this time.
Diagnostics
showed info below:

Definitions Increment Version: 124/124
Definitions ThreatAuditThreatData: 1291846
Definitions ThreatAuditScanData: 2817373
Definitions DeterminationData: 631595

The definitions increment version numbers are the same so all is well,
this
time? The latest update I received this morning is "5771", so this is
current??

I agree--this is the current definition level, and the version numbers are
the same, so this looks good to me!