Build 613 Released

  • Thread starter Thread starter Steve Dodson [MSFT]
  • Start date Start date
When you say "selectively suppressing these" exactly what do you mean,
temporarily turning them off one at a time in the order you suggested?

I have learned something. I think NOD32 may not be installed correctly or
may have become corrupt. X-Cleaner keeps noting a problem with the Winsock
LSPs every time I reboot the computer. If I let X-Cleaner fix that, then
IMON is disabled (grayed out). Microsoft Antispyware shows question marks
next to the NOD32 LSPs, and Spybot shows no information and no green check
mark for those particular LSPs. Let me try uninstalling and reinstalling
NOD32. Perhaps that is the problem. And there is a new build of X-Cleaner
also. In what order should I uninstall-reinstall. Spybot, Ad-Aware, and
Ewido seem to be okay. It's Microsoft Antispyware and NOD32 that are not.
And X-Cleaner is fine, it just has a new build to install.


Bill Sanderson said:
It'd be nice to pin this down, if we can--you might try selectively
supressing these and re-trying the update.

I'd do that in this order:

1) Spybot's TeaTimer
2) Ad-Aware Pro's Ad-Watch
3) Ewido Antitrojan
4) NOD32 Antivirus


--

SeaMaid said:
Yes, but they never caused a problem with the previous build of Microsoft
Antispyware.

Spybot's TeaTimer
Ad-Aware Pro's Ad-Watch
NOD32 Antivirus
Ewido Antitrojan


Bill Sanderson said:
Are you running any third-party products that attempt to protect other
apps against modification by spyware or viruses?

--

Let me take that back. Before the first reboot, it updated fine to 25.
After the first and subsequent reboots, it doesn't freeze, but it keeps
trying to install the same update file 25 to 27. At the end it says 27
has been successfully installed, but if you go to update again, it
tries to install 27 again. It's like the update isn't taking.
Subsequent reboots, and it still installs 27 over and over again. What
should I do?



Thanks! Glad it worked. I expect that the upgrade will work on most
machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works just
fine. No more freezes on updates as with doing an update install over
the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or
the program down. It would not even shut down with Task Manager, so
I had to push the reset button on my PC. Microsoft Antispyware had
to be completely uninstalled using Add/Remove Programs. Then I
manually deleted the Microsoft Antispyware folder in Program Files.
I manually downloaded the new version 6-23-05 and will install it
and set it up from scratch. If it still does freezes when trying to
update, I will report back.


message
I wanted to let the group know that we are pushing out build 613 to
the beta testers over the next few hours. You will start to see a
notification stating a new build is available starting today. I
wrote a quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified
at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to
this
message are best directed to the newsgroup/thread from which they
originated.
 
Temporarily turning them off one at a time was what I meant. I'm not sure I
know anyone else using NOD32 and Microsoft Antispyware to ask how this looks
on their system. I've seen false alarms about LSP's from Microsoft
Antispyware, so I don't know how easy this is for any product to get
right--I've very little experience looking at other than the stock Microsoft
LSP's.

--

SeaMaid said:
When you say "selectively suppressing these" exactly what do you mean,
temporarily turning them off one at a time in the order you suggested?

I have learned something. I think NOD32 may not be installed correctly or
may have become corrupt. X-Cleaner keeps noting a problem with the Winsock
LSPs every time I reboot the computer. If I let X-Cleaner fix that, then
IMON is disabled (grayed out). Microsoft Antispyware shows question marks
next to the NOD32 LSPs, and Spybot shows no information and no green check
mark for those particular LSPs. Let me try uninstalling and reinstalling
NOD32. Perhaps that is the problem. And there is a new build of X-Cleaner
also. In what order should I uninstall-reinstall. Spybot, Ad-Aware, and
Ewido seem to be okay. It's Microsoft Antispyware and NOD32 that are not.
And X-Cleaner is fine, it just has a new build to install.


Bill Sanderson said:
It'd be nice to pin this down, if we can--you might try selectively
supressing these and re-trying the update.

I'd do that in this order:

1) Spybot's TeaTimer
2) Ad-Aware Pro's Ad-Watch
3) Ewido Antitrojan
4) NOD32 Antivirus


--

SeaMaid said:
Yes, but they never caused a problem with the previous build of
Microsoft Antispyware.

Spybot's TeaTimer
Ad-Aware Pro's Ad-Watch
NOD32 Antivirus
Ewido Antitrojan


Are you running any third-party products that attempt to protect other
apps against modification by spyware or viruses?

--

Let me take that back. Before the first reboot, it updated fine to 25.
After the first and subsequent reboots, it doesn't freeze, but it
keeps trying to install the same update file 25 to 27. At the end it
says 27 has been successfully installed, but if you go to update
again, it tries to install 27 again. It's like the update isn't
taking. Subsequent reboots, and it still installs 27 over and over
again. What should I do?



Thanks! Glad it worked. I expect that the upgrade will work on most
machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works
just fine. No more freezes on updates as with doing an update install
over the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or
the program down. It would not even shut down with Task Manager, so
I had to push the reset button on my PC. Microsoft Antispyware had
to be completely uninstalled using Add/Remove Programs. Then I
manually deleted the Microsoft Antispyware folder in Program Files.
I manually downloaded the new version 6-23-05 and will install it
and set it up from scratch. If it still does freezes when trying to
update, I will report back.


message
I wanted to let the group know that we are pushing out build 613 to
the beta testers over the next few hours. You will start to see a
notification stating a new build is available starting today. I
wrote a quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers
no rights.
Use of included script samples are subject to the terms specified
at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to
this
message are best directed to the newsgroup/thread from which they
originated.
 
I am experiencing the same thing too. Keeps trying to reinstall 27 over and
over and over again.
Ed

SeaMaid said:
Let me take that back. Before the first reboot, it updated fine to 25.
After the first and subsequent reboots, it doesn't freeze, but it keeps
trying to install the same update file 25 to 27. At the end it says 27 has
been successfully installed, but if you go to update again, it tries to
install 27 again. It's like the update isn't taking. Subsequent reboots,
and it still installs 27 over and over again. What should I do?



Bill Sanderson said:
Thanks! Glad it worked. I expect that the upgrade will work on most
machines as well--I'm testing that today and over the weekend.

--

SeaMaid said:
I am pleased to report that a clean install of the new beta works just
fine. No more freezes on updates as with doing an update install over the
existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or the
program down. It would not even shut down with Task Manager, so I had
to push the reset button on my PC. Microsoft Antispyware had to be
completely uninstalled using Add/Remove Programs. Then I manually
deleted the Microsoft Antispyware folder in Program Files. I manually
downloaded the new version 6-23-05 and will install it and set it up
from scratch. If it still does freezes when trying to update, I will
report back.


I wanted to let the group know that we are pushing out build 613 to the
beta testers over the next few hours. You will start to see a
notification stating a new build is available starting today. I wrote a
quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to
this
message are best directed to the newsgroup/thread from which they
originated.
 
Ed, what other security software do you have installed?

Ed Barba said:
I am experiencing the same thing too. Keeps trying to reinstall 27 over and
over and over again.
Ed

SeaMaid said:
Let me take that back. Before the first reboot, it updated fine to 25.
After the first and subsequent reboots, it doesn't freeze, but it keeps
trying to install the same update file 25 to 27. At the end it says 27
has been successfully installed, but if you go to update again, it tries
to install 27 again. It's like the update isn't taking. Subsequent
reboots, and it still installs 27 over and over again. What should I do?



Bill Sanderson said:
Thanks! Glad it worked. I expect that the upgrade will work on most
machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works just
fine. No more freezes on updates as with doing an update install over
the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or the
program down. It would not even shut down with Task Manager, so I had
to push the reset button on my PC. Microsoft Antispyware had to be
completely uninstalled using Add/Remove Programs. Then I manually
deleted the Microsoft Antispyware folder in Program Files. I manually
downloaded the new version 6-23-05 and will install it and set it up
from scratch. If it still does freezes when trying to update, I will
report back.


I wanted to let the group know that we are pushing out build 613 to
the beta testers over the next few hours. You will start to see a
notification stating a new build is available starting today. I wrote
a quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to
this
message are best directed to the newsgroup/thread from which they
originated.
 
Since the next part of the troubleshooting process requires uninstalling and
reinstalling Microsoft Antispyware, is there an ini file or some way to back
up settings between installations? Then I don't have to customize all my
settings again.


Bill Sanderson said:
Temporarily turning them off one at a time was what I meant. I'm not sure
I know anyone else using NOD32 and Microsoft Antispyware to ask how this
looks on their system. I've seen false alarms about LSP's from Microsoft
Antispyware, so I don't know how easy this is for any product to get
right--I've very little experience looking at other than the stock
Microsoft LSP's.

--

SeaMaid said:
When you say "selectively suppressing these" exactly what do you mean,
temporarily turning them off one at a time in the order you suggested?

I have learned something. I think NOD32 may not be installed correctly or
may have become corrupt. X-Cleaner keeps noting a problem with the
Winsock LSPs every time I reboot the computer. If I let X-Cleaner fix
that, then IMON is disabled (grayed out). Microsoft Antispyware shows
question marks next to the NOD32 LSPs, and Spybot shows no information
and no green check mark for those particular LSPs. Let me try
uninstalling and reinstalling NOD32. Perhaps that is the problem. And
there is a new build of X-Cleaner also. In what order should I
uninstall-reinstall. Spybot, Ad-Aware, and Ewido seem to be okay. It's
Microsoft Antispyware and NOD32 that are not. And X-Cleaner is fine, it
just has a new build to install.


Bill Sanderson said:
It'd be nice to pin this down, if we can--you might try selectively
supressing these and re-trying the update.

I'd do that in this order:

1) Spybot's TeaTimer
2) Ad-Aware Pro's Ad-Watch
3) Ewido Antitrojan
4) NOD32 Antivirus


--

Yes, but they never caused a problem with the previous build of
Microsoft Antispyware.

Spybot's TeaTimer
Ad-Aware Pro's Ad-Watch
NOD32 Antivirus
Ewido Antitrojan


Are you running any third-party products that attempt to protect other
apps against modification by spyware or viruses?

--

Let me take that back. Before the first reboot, it updated fine to
25. After the first and subsequent reboots, it doesn't freeze, but it
keeps trying to install the same update file 25 to 27. At the end it
says 27 has been successfully installed, but if you go to update
again, it tries to install 27 again. It's like the update isn't
taking. Subsequent reboots, and it still installs 27 over and over
again. What should I do?



Thanks! Glad it worked. I expect that the upgrade will work on
most machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works
just fine. No more freezes on updates as with doing an update
install over the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or
the program down. It would not even shut down with Task Manager,
so I had to push the reset button on my PC. Microsoft Antispyware
had to be completely uninstalled using Add/Remove Programs. Then I
manually deleted the Microsoft Antispyware folder in Program
Files. I manually downloaded the new version 6-23-05 and will
install it and set it up from scratch. If it still does freezes
when trying to update, I will report back.


message
I wanted to let the group know that we are pushing out build 613
to the beta testers over the next few hours. You will start to see
a notification stating a new build is available starting today. I
wrote a quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers
no rights.
Use of included script samples are subject to the terms specified
at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses
to this
message are best directed to the newsgroup/thread from which they
originated.
 
Is the repeated update from 5725 to 5727 a bug with the new build of
Microsoft Antispyware or a conflict with other software? I think it may be a
bug with the new version. I am sure my system is clean.

Troubleshooting Steps
-----------------------
1. Disable (one at a time) Spybot, Ad-Watch, NOD32, and Ewido by turning off
their protection from within Windows. No effect. MSAS update problem
persists.
2. Prevent the other security programs from starting up with Windows by
unchecking their options in MSCONFIG and Services. No effect. MSAS update
problem persists.
3. Uninstall NOD32. No effect.
4. Uninstall X-Cleaner. No effect.
5. Uninstall & reinstall MSAS with everything disabled in the taskbar. No
effect.
5. Reinstall NOD32. No effect.
6. All programs & protections enabled. No effect.

There is other security software installed that does not have real-time
protection (A2 Free Antitrojan, for example), but I do not think any of them
are the problem.

SUMMARY: MSAS still repeatedly tries to install 5727 during each update. No
app freezes or system freezes any more. When the 5728 patterns come
out we will see better how the new build reacts to updates.

One note about the new build of X-Cleaner Free (not the stand-alone exe that
has no installer but the one with the installer). Ad-Watch gave me a warning
during installation that the setup file contained malware called Virtual
Bouncer. That seems strange for an antispyware program, doesn't it. Ad-Watch
blocked
the malware for me, but I am losing faith in X-Cleaner and have temporarily
stopped using that program until I get more information. I do not know if
this is a false positive or not. Previous versions did not have that
warning. The update feature in the new build of X-Cleaner still does not
work. Before installing X-Cleaner, I used the context menu scanners for
Ad-Aware, Ewido, A2, and NOD32. None of them found anything. Sometimes
malware has to load into memory before it can be detected. If it was not a
false positive and indeed is malware, thank goodness Ad-Watch was able to
detect it and block it.


Bill Sanderson said:
Temporarily turning them off one at a time was what I meant. I'm not sure
I know anyone else using NOD32 and Microsoft Antispyware to ask how this
looks on their system. I've seen false alarms about LSP's from Microsoft
Antispyware, so I don't know how easy this is for any product to get
right--I've very little experience looking at other than the stock
Microsoft LSP's.

--

SeaMaid said:
When you say "selectively suppressing these" exactly what do you mean,
temporarily turning them off one at a time in the order you suggested?

I have learned something. I think NOD32 may not be installed correctly or
may have become corrupt. X-Cleaner keeps noting a problem with the
Winsock LSPs every time I reboot the computer. If I let X-Cleaner fix
that, then IMON is disabled (grayed out). Microsoft Antispyware shows
question marks next to the NOD32 LSPs, and Spybot shows no information
and no green check mark for those particular LSPs. Let me try
uninstalling and reinstalling NOD32. Perhaps that is the problem. And
there is a new build of X-Cleaner also. In what order should I
uninstall-reinstall. Spybot, Ad-Aware, and Ewido seem to be okay. It's
Microsoft Antispyware and NOD32 that are not. And X-Cleaner is fine, it
just has a new build to install.


Bill Sanderson said:
It'd be nice to pin this down, if we can--you might try selectively
supressing these and re-trying the update.

I'd do that in this order:

1) Spybot's TeaTimer
2) Ad-Aware Pro's Ad-Watch
3) Ewido Antitrojan
4) NOD32 Antivirus


--

Yes, but they never caused a problem with the previous build of
Microsoft Antispyware.

Spybot's TeaTimer
Ad-Aware Pro's Ad-Watch
NOD32 Antivirus
Ewido Antitrojan


Are you running any third-party products that attempt to protect other
apps against modification by spyware or viruses?

--

Let me take that back. Before the first reboot, it updated fine to
25. After the first and subsequent reboots, it doesn't freeze, but it
keeps trying to install the same update file 25 to 27. At the end it
says 27 has been successfully installed, but if you go to update
again, it tries to install 27 again. It's like the update isn't
taking. Subsequent reboots, and it still installs 27 over and over
again. What should I do?



Thanks! Glad it worked. I expect that the upgrade will work on
most machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works
just fine. No more freezes on updates as with doing an update
install over the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or
the program down. It would not even shut down with Task Manager,
so I had to push the reset button on my PC. Microsoft Antispyware
had to be completely uninstalled using Add/Remove Programs. Then I
manually deleted the Microsoft Antispyware folder in Program
Files. I manually downloaded the new version 6-23-05 and will
install it and set it up from scratch. If it still does freezes
when trying to update, I will report back.


message
I wanted to let the group know that we are pushing out build 613
to the beta testers over the next few hours. You will start to see
a notification stating a new build is available starting today. I
wrote a quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers
no rights.
Use of included script samples are subject to the terms specified
at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses
to this
message are best directed to the newsgroup/thread from which they
originated.
 
I haven't tested this carefully, but I believe if you simply uninstall via
control panel, the settings file will be left intact, and setting preserved
over the uninstall/reinstall. Quite a bit is left in the installation
folder, and I "think" that is one of them.

--

SeaMaid said:
Since the next part of the troubleshooting process requires uninstalling
and reinstalling Microsoft Antispyware, is there an ini file or some way
to back up settings between installations? Then I don't have to customize
all my settings again.


Bill Sanderson said:
Temporarily turning them off one at a time was what I meant. I'm not
sure I know anyone else using NOD32 and Microsoft Antispyware to ask how
this looks on their system. I've seen false alarms about LSP's from
Microsoft Antispyware, so I don't know how easy this is for any product
to get right--I've very little experience looking at other than the stock
Microsoft LSP's.

--

SeaMaid said:
When you say "selectively suppressing these" exactly what do you mean,
temporarily turning them off one at a time in the order you suggested?

I have learned something. I think NOD32 may not be installed correctly
or may have become corrupt. X-Cleaner keeps noting a problem with the
Winsock LSPs every time I reboot the computer. If I let X-Cleaner fix
that, then IMON is disabled (grayed out). Microsoft Antispyware shows
question marks next to the NOD32 LSPs, and Spybot shows no information
and no green check mark for those particular LSPs. Let me try
uninstalling and reinstalling NOD32. Perhaps that is the problem. And
there is a new build of X-Cleaner also. In what order should I
uninstall-reinstall. Spybot, Ad-Aware, and Ewido seem to be okay. It's
Microsoft Antispyware and NOD32 that are not. And X-Cleaner is fine, it
just has a new build to install.


It'd be nice to pin this down, if we can--you might try selectively
supressing these and re-trying the update.

I'd do that in this order:

1) Spybot's TeaTimer
2) Ad-Aware Pro's Ad-Watch
3) Ewido Antitrojan
4) NOD32 Antivirus


--

Yes, but they never caused a problem with the previous build of
Microsoft Antispyware.

Spybot's TeaTimer
Ad-Aware Pro's Ad-Watch
NOD32 Antivirus
Ewido Antitrojan


Are you running any third-party products that attempt to protect
other apps against modification by spyware or viruses?

--

Let me take that back. Before the first reboot, it updated fine to
25. After the first and subsequent reboots, it doesn't freeze, but
it keeps trying to install the same update file 25 to 27. At the end
it says 27 has been successfully installed, but if you go to update
again, it tries to install 27 again. It's like the update isn't
taking. Subsequent reboots, and it still installs 27 over and over
again. What should I do?



Thanks! Glad it worked. I expect that the upgrade will work on
most machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works
just fine. No more freezes on updates as with doing an update
install over the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the
update dialog box just froze and froze and froze. I could not
shut it or the program down. It would not even shut down with
Task Manager, so I had to push the reset button on my PC.
Microsoft Antispyware had to be completely uninstalled using
Add/Remove Programs. Then I manually deleted the Microsoft
Antispyware folder in Program Files. I manually downloaded the
new version 6-23-05 and will install it and set it up from
scratch. If it still does freezes when trying to update, I will
report back.


message
I wanted to let the group know that we are pushing out build 613
to the beta testers over the next few hours. You will start to
see a notification stating a new build is available starting
today. I wrote a quick blurb in my blog if you want more
information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers
no rights.
Use of included script samples are subject to the terms
specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses
to this
message are best directed to the newsgroup/thread from which
they
originated.
 
They've put up (June 24) a new build 614 at the download site. No notice,
and no information I'm aware of about what's different. Wouldn't hurt to
test it.

--

SeaMaid said:
Ed, what other security software do you have installed?

Ed Barba said:
I am experiencing the same thing too. Keeps trying to reinstall 27 over
and over and over again.
Ed

SeaMaid said:
Let me take that back. Before the first reboot, it updated fine to 25.
After the first and subsequent reboots, it doesn't freeze, but it keeps
trying to install the same update file 25 to 27. At the end it says 27
has been successfully installed, but if you go to update again, it tries
to install 27 again. It's like the update isn't taking. Subsequent
reboots, and it still installs 27 over and over again. What should I
do?



Thanks! Glad it worked. I expect that the upgrade will work on most
machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works just
fine. No more freezes on updates as with doing an update install over
the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or the
program down. It would not even shut down with Task Manager, so I had
to push the reset button on my PC. Microsoft Antispyware had to be
completely uninstalled using Add/Remove Programs. Then I manually
deleted the Microsoft Antispyware folder in Program Files. I manually
downloaded the new version 6-23-05 and will install it and set it up
from scratch. If it still does freezes when trying to update, I will
report back.


message
I wanted to let the group know that we are pushing out build 613 to
the beta testers over the next few hours. You will start to see a
notification stating a new build is available starting today. I wrote
a quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to
this
message are best directed to the newsgroup/thread from which they
originated.
 
An excellent idea. Thank you. Maybe that fixed it. Do you think I should
uninstall 613 before installing 614 or just try doing an update install
overtop 613?

Sea


Bill Sanderson said:
They've put up (June 24) a new build 614 at the download site. No notice,
and no information I'm aware of about what's different. Wouldn't hurt to
test it.

--

SeaMaid said:
Ed, what other security software do you have installed?

Ed Barba said:
I am experiencing the same thing too. Keeps trying to reinstall 27 over
and over and over again.
Ed

Let me take that back. Before the first reboot, it updated fine to 25.
After the first and subsequent reboots, it doesn't freeze, but it keeps
trying to install the same update file 25 to 27. At the end it says 27
has been successfully installed, but if you go to update again, it
tries to install 27 again. It's like the update isn't taking.
Subsequent reboots, and it still installs 27 over and over again. What
should I do?



Thanks! Glad it worked. I expect that the upgrade will work on most
machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works just
fine. No more freezes on updates as with doing an update install over
the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or
the program down. It would not even shut down with Task Manager, so
I had to push the reset button on my PC. Microsoft Antispyware had
to be completely uninstalled using Add/Remove Programs. Then I
manually deleted the Microsoft Antispyware folder in Program Files.
I manually downloaded the new version 6-23-05 and will install it
and set it up from scratch. If it still does freezes when trying to
update, I will report back.


message
I wanted to let the group know that we are pushing out build 613 to
the beta testers over the next few hours. You will start to see a
notification stating a new build is available starting today. I
wrote a quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified
at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to
this
message are best directed to the newsgroup/thread from which they
originated.
 
I would do the uninstall first, particularly where you are having some
difficulty. Also Defs are up to 5729 now.

Ron Chamberlin
MS-MVP

SeaMaid said:
An excellent idea. Thank you. Maybe that fixed it. Do you think I should
uninstall 613 before installing 614 or just try doing an update install
overtop 613?

Sea


Bill Sanderson said:
They've put up (June 24) a new build 614 at the download site. No
notice, and no information I'm aware of about what's different. Wouldn't
hurt to test it.

--

SeaMaid said:
Ed, what other security software do you have installed?

I am experiencing the same thing too. Keeps trying to reinstall 27 over
and over and over again.
Ed

Let me take that back. Before the first reboot, it updated fine to 25.
After the first and subsequent reboots, it doesn't freeze, but it
keeps trying to install the same update file 25 to 27. At the end it
says 27 has been successfully installed, but if you go to update
again, it tries to install 27 again. It's like the update isn't
taking. Subsequent reboots, and it still installs 27 over and over
again. What should I do?



Thanks! Glad it worked. I expect that the upgrade will work on most
machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works
just fine. No more freezes on updates as with doing an update install
over the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or
the program down. It would not even shut down with Task Manager, so
I had to push the reset button on my PC. Microsoft Antispyware had
to be completely uninstalled using Add/Remove Programs. Then I
manually deleted the Microsoft Antispyware folder in Program Files.
I manually downloaded the new version 6-23-05 and will install it
and set it up from scratch. If it still does freezes when trying to
update, I will report back.


message
I wanted to let the group know that we are pushing out build 613 to
the beta testers over the next few hours. You will start to see a
notification stating a new build is available starting today. I
wrote a quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers
no rights.
Use of included script samples are subject to the terms specified
at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to
this
message are best directed to the newsgroup/thread from which they
originated.
 
You use Lotus Notes Mikolaj, which version is that, 6.5?

No, I do not :-) I used to use it, but for almost a year it's unused
database of old emails :-)
And yes, it was 6.5 version.
 
I haven't even got 614 on a machine yet, and the defs are a version ahead of
me too! Back from the seaside, but off to the pool sometime this afternoon.

Severely limits my testing time, I'm afraid--between actual work and hanging
out......and we didn't get WIFI at the pool this year--maybe next.
--

Ron Chamberlin said:
I would do the uninstall first, particularly where you are having some
difficulty. Also Defs are up to 5729 now.

Ron Chamberlin
MS-MVP

SeaMaid said:
An excellent idea. Thank you. Maybe that fixed it. Do you think I should
uninstall 613 before installing 614 or just try doing an update install
overtop 613?

Sea


Bill Sanderson said:
They've put up (June 24) a new build 614 at the download site. No
notice, and no information I'm aware of about what's different.
Wouldn't hurt to test it.

--

Ed, what other security software do you have installed?

I am experiencing the same thing too. Keeps trying to reinstall 27 over
and over and over again.
Ed

Let me take that back. Before the first reboot, it updated fine to
25. After the first and subsequent reboots, it doesn't freeze, but it
keeps trying to install the same update file 25 to 27. At the end it
says 27 has been successfully installed, but if you go to update
again, it tries to install 27 again. It's like the update isn't
taking. Subsequent reboots, and it still installs 27 over and over
again. What should I do?



Thanks! Glad it worked. I expect that the upgrade will work on
most machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works
just fine. No more freezes on updates as with doing an update
install over the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or
the program down. It would not even shut down with Task Manager,
so I had to push the reset button on my PC. Microsoft Antispyware
had to be completely uninstalled using Add/Remove Programs. Then I
manually deleted the Microsoft Antispyware folder in Program
Files. I manually downloaded the new version 6-23-05 and will
install it and set it up from scratch. If it still does freezes
when trying to update, I will report back.


message
I wanted to let the group know that we are pushing out build 613
to the beta testers over the next few hours. You will start to see
a notification stating a new build is available starting today. I
wrote a quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers
no rights.
Use of included script samples are subject to the terms specified
at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses
to this
message are best directed to the newsgroup/thread from which they
originated.
 
The inability to update has been seen throughout the beta, I think. Some
folks have associated it with a particular set of defs, but there's nothing
clear I can point to.
--

SeaMaid said:
Is the repeated update from 5725 to 5727 a bug with the new build of
Microsoft Antispyware or a conflict with other software? I think it may be
a bug with the new version. I am sure my system is clean.

Troubleshooting Steps
-----------------------
1. Disable (one at a time) Spybot, Ad-Watch, NOD32, and Ewido by turning
off their protection from within Windows. No effect. MSAS update problem
persists.
2. Prevent the other security programs from starting up with Windows by
unchecking their options in MSCONFIG and Services. No effect. MSAS update
problem persists.
3. Uninstall NOD32. No effect.
4. Uninstall X-Cleaner. No effect.
5. Uninstall & reinstall MSAS with everything disabled in the taskbar. No
effect.
5. Reinstall NOD32. No effect.
6. All programs & protections enabled. No effect.

There is other security software installed that does not have real-time
protection (A2 Free Antitrojan, for example), but I do not think any of
them are the problem.

SUMMARY: MSAS still repeatedly tries to install 5727 during each update.
No app freezes or system freezes any more. When the 5728 patterns come
out we will see better how the new build reacts to updates.

One note about the new build of X-Cleaner Free (not the stand-alone exe
that has no installer but the one with the installer). Ad-Watch gave me a
warning
during installation that the setup file contained malware called Virtual
Bouncer. That seems strange for an antispyware program, doesn't it.
Ad-Watch blocked
the malware for me, but I am losing faith in X-Cleaner and have
temporarily stopped using that program until I get more information. I do
not know if this is a false positive or not. Previous versions did not
have that warning. The update feature in the new build of X-Cleaner still
does not work. Before installing X-Cleaner, I used the context menu
scanners for Ad-Aware, Ewido, A2, and NOD32. None of them found anything.
Sometimes malware has to load into memory before it can be detected. If it
was not a false positive and indeed is malware, thank goodness Ad-Watch
was able to detect it and block it.


Bill Sanderson said:
Temporarily turning them off one at a time was what I meant. I'm not
sure I know anyone else using NOD32 and Microsoft Antispyware to ask how
this looks on their system. I've seen false alarms about LSP's from
Microsoft Antispyware, so I don't know how easy this is for any product
to get right--I've very little experience looking at other than the stock
Microsoft LSP's.

--

SeaMaid said:
When you say "selectively suppressing these" exactly what do you mean,
temporarily turning them off one at a time in the order you suggested?

I have learned something. I think NOD32 may not be installed correctly
or may have become corrupt. X-Cleaner keeps noting a problem with the
Winsock LSPs every time I reboot the computer. If I let X-Cleaner fix
that, then IMON is disabled (grayed out). Microsoft Antispyware shows
question marks next to the NOD32 LSPs, and Spybot shows no information
and no green check mark for those particular LSPs. Let me try
uninstalling and reinstalling NOD32. Perhaps that is the problem. And
there is a new build of X-Cleaner also. In what order should I
uninstall-reinstall. Spybot, Ad-Aware, and Ewido seem to be okay. It's
Microsoft Antispyware and NOD32 that are not. And X-Cleaner is fine, it
just has a new build to install.


It'd be nice to pin this down, if we can--you might try selectively
supressing these and re-trying the update.

I'd do that in this order:

1) Spybot's TeaTimer
2) Ad-Aware Pro's Ad-Watch
3) Ewido Antitrojan
4) NOD32 Antivirus


--

Yes, but they never caused a problem with the previous build of
Microsoft Antispyware.

Spybot's TeaTimer
Ad-Aware Pro's Ad-Watch
NOD32 Antivirus
Ewido Antitrojan


Are you running any third-party products that attempt to protect
other apps against modification by spyware or viruses?

--

Let me take that back. Before the first reboot, it updated fine to
25. After the first and subsequent reboots, it doesn't freeze, but
it keeps trying to install the same update file 25 to 27. At the end
it says 27 has been successfully installed, but if you go to update
again, it tries to install 27 again. It's like the update isn't
taking. Subsequent reboots, and it still installs 27 over and over
again. What should I do?



Thanks! Glad it worked. I expect that the upgrade will work on
most machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works
just fine. No more freezes on updates as with doing an update
install over the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the
update dialog box just froze and froze and froze. I could not
shut it or the program down. It would not even shut down with
Task Manager, so I had to push the reset button on my PC.
Microsoft Antispyware had to be completely uninstalled using
Add/Remove Programs. Then I manually deleted the Microsoft
Antispyware folder in Program Files. I manually downloaded the
new version 6-23-05 and will install it and set it up from
scratch. If it still does freezes when trying to update, I will
report back.


message
I wanted to let the group know that we are pushing out build 613
to the beta testers over the next few hours. You will start to
see a notification stating a new build is available starting
today. I wrote a quick blurb in my blog if you want more
information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers
no rights.
Use of included script samples are subject to the terms
specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses
to this
message are best directed to the newsgroup/thread from which
they
originated.
 
Good catch--I don't think I've seen that dialog yet. This is probably a
message already present in the code as received from Giant. Microsoft is
putting as little energy as possible into the old code, I believe, in favor
of work on beta2. So cosmetics are generally being left alone.

--

Patrick Kinlin said:
-----Original Message-----
I wanted to let the group know that we are pushing out build 613 to the beta
testers over the next few hours. You will start to see a notification
stating a new build is available starting today. I wrote a quick blurb in my
blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.


.
It may seem picayune, but the "Donwloading ..." text in
the updater window did give me momentary cause for
concern. Couldn't MS put these messages past a
spellchecker? I know this is just beta, but it is a
security application (i.e. misspellings are expected in
malware, but from Microsoft???).
 
Build 614 (clean install) still has the same update problem. First update is
from 5725 to 5727. Help-About then shows 5727. Clicking File-Update again
shows the program is updating from 5725 to 5727. Same after reboots. So far,
I have not been offered update pattern 5729. Maybe the server that serves my
area has not yet been updated to 5729 and it will be offered to me soon. Is
there a manual way to download and install the updates, or is there
something else I can try that I have not already tried? No problem updating
any of my other software: antivirus, antitrojan, etc.

Ron Chamberlin said:
Now at build 614.

Ron Chamberlin
MS-MVP


Steve Dodson said:
I wanted to let the group know that we are pushing out build 613 to the
beta testers over the next few hours. You will start to see a notification
stating a new build is available starting today. I wrote a quick blurb in
my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
For now Spybot S&D 1.4 with nothing running resident. Ad-Aware SE1.06 free.
MSAS ver 613, SpywareBlaster, Webroot Spy Sweeper MSN Branded ver 3.2 with
nothing running resident. Avast! anti-virus and AVG free Anti-virus. Thats
all.
Ed

SeaMaid said:
Ed, what other security software do you have installed?

Ed Barba said:
I am experiencing the same thing too. Keeps trying to reinstall 27 over
and over and over again.
Ed

SeaMaid said:
Let me take that back. Before the first reboot, it updated fine to 25.
After the first and subsequent reboots, it doesn't freeze, but it keeps
trying to install the same update file 25 to 27. At the end it says 27
has been successfully installed, but if you go to update again, it tries
to install 27 again. It's like the update isn't taking. Subsequent
reboots, and it still installs 27 over and over again. What should I
do?



Thanks! Glad it worked. I expect that the upgrade will work on most
machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works just
fine. No more freezes on updates as with doing an update install over
the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the update
dialog box just froze and froze and froze. I could not shut it or the
program down. It would not even shut down with Task Manager, so I had
to push the reset button on my PC. Microsoft Antispyware had to be
completely uninstalled using Add/Remove Programs. Then I manually
deleted the Microsoft Antispyware folder in Program Files. I manually
downloaded the new version 6-23-05 and will install it and set it up
from scratch. If it still does freezes when trying to update, I will
report back.


message
I wanted to let the group know that we are pushing out build 613 to
the beta testers over the next few hours. You will start to see a
notification stating a new build is available starting today. I wrote
a quick blurb in my blog if you want more information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to
this
message are best directed to the newsgroup/thread from which they
originated.
 
Not a good idea having a laptop by the pool I would think. ;-)
Ed

Bill Sanderson said:
I haven't even got 614 on a machine yet, and the defs are a version ahead
of me too! Back from the seaside, but off to the pool sometime this
afternoon.

Severely limits my testing time, I'm afraid--between actual work and
hanging out......and we didn't get WIFI at the pool this year--maybe next.
--

Ron Chamberlin said:
I would do the uninstall first, particularly where you are having some
difficulty. Also Defs are up to 5729 now.

Ron Chamberlin
MS-MVP

SeaMaid said:
An excellent idea. Thank you. Maybe that fixed it. Do you think I should
uninstall 613 before installing 614 or just try doing an update install
overtop 613?

Sea


They've put up (June 24) a new build 614 at the download site. No
notice, and no information I'm aware of about what's different.
Wouldn't hurt to test it.

--

Ed, what other security software do you have installed?

I am experiencing the same thing too. Keeps trying to reinstall 27
over and over and over again.
Ed

Let me take that back. Before the first reboot, it updated fine to
25. After the first and subsequent reboots, it doesn't freeze, but
it keeps trying to install the same update file 25 to 27. At the end
it says 27 has been successfully installed, but if you go to update
again, it tries to install 27 again. It's like the update isn't
taking. Subsequent reboots, and it still installs 27 over and over
again. What should I do?



Thanks! Glad it worked. I expect that the upgrade will work on
most machines as well--I'm testing that today and over the weekend.

--

I am pleased to report that a clean install of the new beta works
just fine. No more freezes on updates as with doing an update
install over the existing version.



There is a problem with the autoupdate installing it over the old
version. Afterward, when I tried to update the program, the
update dialog box just froze and froze and froze. I could not
shut it or the program down. It would not even shut down with
Task Manager, so I had to push the reset button on my PC.
Microsoft Antispyware had to be completely uninstalled using
Add/Remove Programs. Then I manually deleted the Microsoft
Antispyware folder in Program Files. I manually downloaded the
new version 6-23-05 and will install it and set it up from
scratch. If it still does freezes when trying to update, I will
report back.


message
I wanted to let the group know that we are pushing out build 613
to the beta testers over the next few hours. You will start to
see a notification stating a new build is available starting
today. I wrote a quick blurb in my blog if you want more
information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers
no rights.
Use of included script samples are subject to the terms
specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses
to this
message are best directed to the newsgroup/thread from which
they
originated.
 
It's true that my favorite spots tend to get splashes from one activity or
another. Also that the pool water this year is salt-water--new
filtration/purification scheme. Seems to work pretty well. Not nearly as
salty as the ocean, but enough.

I had it there one day to survey for antenna locations, but the board didn't
go for it. I can still steal a connection from "Yvonne", though!

--

Ed Barba said:
Not a good idea having a laptop by the pool I would think. ;-)
Ed

Bill Sanderson said:
I haven't even got 614 on a machine yet, and the defs are a version ahead
of me too! Back from the seaside, but off to the pool sometime this
afternoon.

Severely limits my testing time, I'm afraid--between actual work and
hanging out......and we didn't get WIFI at the pool this year--maybe
next.
--

Ron Chamberlin said:
I would do the uninstall first, particularly where you are having some
difficulty. Also Defs are up to 5729 now.

Ron Chamberlin
MS-MVP

An excellent idea. Thank you. Maybe that fixed it. Do you think I
should uninstall 613 before installing 614 or just try doing an update
install overtop 613?

Sea


They've put up (June 24) a new build 614 at the download site. No
notice, and no information I'm aware of about what's different.
Wouldn't hurt to test it.

--

Ed, what other security software do you have installed?

I am experiencing the same thing too. Keeps trying to reinstall 27
over and over and over again.
Ed

Let me take that back. Before the first reboot, it updated fine to
25. After the first and subsequent reboots, it doesn't freeze, but
it keeps trying to install the same update file 25 to 27. At the
end it says 27 has been successfully installed, but if you go to
update again, it tries to install 27 again. It's like the update
isn't taking. Subsequent reboots, and it still installs 27 over and
over again. What should I do?



message
Thanks! Glad it worked. I expect that the upgrade will work on
most machines as well--I'm testing that today and over the
weekend.

--

I am pleased to report that a clean install of the new beta works
just fine. No more freezes on updates as with doing an update
install over the existing version.



There is a problem with the autoupdate installing it over the
old version. Afterward, when I tried to update the program, the
update dialog box just froze and froze and froze. I could not
shut it or the program down. It would not even shut down with
Task Manager, so I had to push the reset button on my PC.
Microsoft Antispyware had to be completely uninstalled using
Add/Remove Programs. Then I manually deleted the Microsoft
Antispyware folder in Program Files. I manually downloaded the
new version 6-23-05 and will install it and set it up from
scratch. If it still does freezes when trying to update, I will
report back.


message
I wanted to let the group know that we are pushing out build 613
to the beta testers over the next few hours. You will start to
see a notification stating a new build is available starting
today. I wrote a quick blurb in my blog if you want more
information.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and
confers no rights.
Use of included script samples are subject to the terms
specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses
to this
message are best directed to the newsgroup/thread from which
they
originated.
 
Back
Top