Application failed to initialize: 0x8007005. Access is denied.

[Guest]

After installation of Windows Defender (version as of today) on XP Pro SP2
x86, Windows Defender updates itself and runs a quick scan. On the next
reboot of the machine, I get the following error:

====
Windows Defender
====
Application failed to initalize: 0x80070005. Access is denied.
====
OK

Removing the Windows Defender key in the Run key solves this, but obviously
the client front-end doesn't function (for standard Users or Administrators).
Launching the application manually also produces this error.

Any ideas?

 

[Anonymous Bob]

After installation of Windows Defender (version as of today) on XP Pro SP2
x86, Windows Defender updates itself and runs a quick scan. On the next
reboot of the machine, I get the following error:

====
Windows Defender
====
Application failed to initalize: 0x80070005. Access is denied.
====
OK

Removing the Windows Defender key in the Run key solves this, but obviously
the client front-end doesn't function (for standard Users or Administrators).
Launching the application manually also produces this error.

Any ideas?

Could this help?
http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=940284&SiteID=2

Bob Vanderveen

 

[dean-dean]

Was this the first time Defender has been installed on your computer, or
have you had previous versions? If you had the version just prior to the
current one (Version 1.1.1592.0), did you manually remove it, using
Add/Remove Programs? OR, did you have a Beta version prior to the current
one?

 

[Guest]

First time on the machine (1593.0). I will try Authenticated Users = FC, but
from what I can tell the issue is, after the reboot, MSASCui.exe is running
as SYSTEM...I had seen, somehwere, that the front end (which is what that app
is) cannot be run under two different user accounts at the same time. I just
don't know WHY it is running as SYSTEM on reboot.

 

[Dave M]

Any chance that this KB could apply?:

You may receive an "0x80070005: Access is denied" error message when you
create a scheduled task on a Windows XP-based computer after you install
security update 841873

http://support.microsoft.com/kb/904423/en-us

 

[Guest]

I can't confirm it, but I don't believe it does.

I installed WD via Altiris which installs the application as SYSTEM. For
what ever reason, the UI for the application starts as SYSTEM after the
reboot of the computer. Since the Run key exists for WD to launch as the
user (as well), I believe I'm running into essentially this issue:

http://support.microsoft.com/kb/925544/en-us

Of course, no resolution on that and no information on if it applies to the
RTM version.