Windows Defender Release Notes Updated

[Steve Dodson [MSFT]]

Thanks for testing Windows Defender Beta 2. We have updated the release
notes at:
http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx
Here we have links to KB's and other FAQs of issues commonly reported in the
newsgroups, and is a good place to start before posting issues with the
beta. Once again thanks for running Windows Defender!

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
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.

 

[Guest]

The release notes DO NOT address the problem of Beta2 not starting on boot up.

 

[Bill Sanderson]

What is not starting?

There's no need for the system tray icon or the User Interface (UI) to start
on startup--there is a service running.

To check, go to a command prompt and do sc query windefend <enter>



--

The release notes DO NOT address the problem of Beta2 not starting on boot
up.
--
LR

Thanks for testing Windows Defender Beta 2. We have updated the release
notes at:
http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx
Here we have links to KB's and other FAQs of issues commonly reported in
the
newsgroups, and is a good place to start before posting issues with the
beta. Once again thanks for running Windows Defender!

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
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.

 

[Guest]

I suspect that racerdude is referring to an error that I am also seeing on
one of my systems. It is an application popup from Windows Defender itself:

Windows Defender
Application failed to initialize: 0x80070057.

And Windows Defender is, indeed, not running on that computer. The software
was installed from an admin account, but the system is usually used from a
limited account. Windows Defender doesn't load when booting up and logging
into that limited user account.

BTW, the setting for allowing non-admin users to make use of Windows
Defender is checked under the settings dialog for the software.

It's annoying enough that the updates only work from an admin account, but
not even being able to run the software at all from a limited account is a
real problem, at least for me.

What is not starting?

There's no need for the system tray icon or the User Interface (UI) to start
on startup--there is a service running.

To check, go to a command prompt and do sc query windefend <enter>



--

The release notes DO NOT address the problem of Beta2 not starting on boot
up.
--
LR

Thanks for testing Windows Defender Beta 2. We have updated the release
notes at:
http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx
Here we have links to KB's and other FAQs of issues commonly reported in
the
newsgroups, and is a good place to start before posting issues with the
beta. Once again thanks for running Windows Defender!

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
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.

 

[Bill Sanderson]

OK - that's much clearer. I think a post with that error as part of the
subject header is much more likely to get read by the Microsoft staff
looking in here at the moment than it is in this thread.

I'm not sure whether this error relates to the service, or to the UI app.

It'd be interesting to see the results of sc query windefend <enter> at a
cmd prompt

Maybe put that in a message starting a new thread? I know General is
awash--but that might be the right place to put it. It is where I see the
most responses from [MSFT] folks.

--

I suspect that racerdude is referring to an error that I am also seeing on
one of my systems. It is an application popup from Windows Defender
itself:

Windows Defender
Application failed to initialize: 0x80070057.

And Windows Defender is, indeed, not running on that computer. The
software
was installed from an admin account, but the system is usually used from a
limited account. Windows Defender doesn't load when booting up and logging
into that limited user account.

BTW, the setting for allowing non-admin users to make use of Windows
Defender is checked under the settings dialog for the software.

It's annoying enough that the updates only work from an admin account, but
not even being able to run the software at all from a limited account is a
real problem, at least for me.

What is not starting?

There's no need for the system tray icon or the User Interface (UI) to
start
on startup--there is a service running.

To check, go to a command prompt and do sc query windefend <enter>



--

The release notes DO NOT address the problem of Beta2 not starting on
boot
up.
--
LR


:

Thanks for testing Windows Defender Beta 2. We have updated the
release
notes at:
http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx
Here we have links to KB's and other FAQs of issues commonly reported
in
the
newsgroups, and is a good place to start before posting issues with
the
beta. Once again thanks for running Windows Defender!

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
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.

 

[Guest]

You're quite right. I'll try to get around to checking the issue more
thoroughly this evening and post a thread -- if I don't see the subject
matter already covered by that time. Haven't had time so far this week, and
the computer in question doesn't see much use until the weekend.

I will check to see whether it's the service or the UI applet, but I suspect
that it's the service. If I try to crank up WD from within that account I get
a repeat of the same application popup. But maybe I'm not following the
design logic.

Thanks for your suggestions.

OK - that's much clearer. I think a post with that error as part of the
subject header is much more likely to get read by the Microsoft staff
looking in here at the moment than it is in this thread.

I'm not sure whether this error relates to the service, or to the UI app.

It'd be interesting to see the results of sc query windefend <enter> at a
cmd prompt

Maybe put that in a message starting a new thread? I know General is
awash--but that might be the right place to put it. It is where I see the
most responses from [MSFT] folks.

--

I suspect that racerdude is referring to an error that I am also seeing on
one of my systems. It is an application popup from Windows Defender
itself:

Windows Defender
Application failed to initialize: 0x80070057.

And Windows Defender is, indeed, not running on that computer. The
software
was installed from an admin account, but the system is usually used from a
limited account. Windows Defender doesn't load when booting up and logging
into that limited user account.

BTW, the setting for allowing non-admin users to make use of Windows
Defender is checked under the settings dialog for the software.

It's annoying enough that the updates only work from an admin account, but
not even being able to run the software at all from a limited account is a
real problem, at least for me.

What is not starting?

There's no need for the system tray icon or the User Interface (UI) to
start
on startup--there is a service running.

To check, go to a command prompt and do sc query windefend <enter>



--

The release notes DO NOT address the problem of Beta2 not starting on
boot
up.
--
LR


:

Thanks for testing Windows Defender Beta 2. We have updated the
release
notes at:
http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx
Here we have links to KB's and other FAQs of issues commonly reported
in
the
newsgroups, and is a good place to start before posting issues with
the
beta. Once again thanks for running Windows Defender!

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
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.

 

[Bill Sanderson]

Steve Dodson has said that the dependency is on RPC--but I think there are
some others--WMI and WMI extensions, maybe.

--

You're quite right. I'll try to get around to checking the issue more
thoroughly this evening and post a thread -- if I don't see the subject
matter already covered by that time. Haven't had time so far this week,
and
the computer in question doesn't see much use until the weekend.

I will check to see whether it's the service or the UI applet, but I
suspect
that it's the service. If I try to crank up WD from within that account I
get
a repeat of the same application popup. But maybe I'm not following the
design logic.

Thanks for your suggestions.

OK - that's much clearer. I think a post with that error as part of the
subject header is much more likely to get read by the Microsoft staff
looking in here at the moment than it is in this thread.

I'm not sure whether this error relates to the service, or to the UI app.

It'd be interesting to see the results of sc query windefend <enter> at a
cmd prompt

Maybe put that in a message starting a new thread? I know General is
awash--but that might be the right place to put it. It is where I see
the
most responses from [MSFT] folks.

--

I suspect that racerdude is referring to an error that I am also seeing
on
one of my systems. It is an application popup from Windows Defender
itself:

Windows Defender
Application failed to initialize: 0x80070057.

And Windows Defender is, indeed, not running on that computer. The
software
was installed from an admin account, but the system is usually used
from a
limited account. Windows Defender doesn't load when booting up and
logging
into that limited user account.

BTW, the setting for allowing non-admin users to make use of Windows
Defender is checked under the settings dialog for the software.

It's annoying enough that the updates only work from an admin account,
but
not even being able to run the software at all from a limited account
is a
real problem, at least for me.

:

What is not starting?

There's no need for the system tray icon or the User Interface (UI) to
start
on startup--there is a service running.

To check, go to a command prompt and do sc query windefend <enter>



--

The release notes DO NOT address the problem of Beta2 not starting
on
boot
up.
--
LR


:

Thanks for testing Windows Defender Beta 2. We have updated the
release
notes at:
http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx
Here we have links to KB's and other FAQs of issues commonly
reported
in
the
newsgroups, and is a good place to start before posting issues with
the
beta. Once again thanks for running Windows Defender!

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
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.

 

[Guest]

Thanks Steve

 

[Guest]

Steve could you tell us how to update the definitions of windows defender
through SUS?.