We have Windows XP SP2 clients in environment currently running Defender
v.1.1.1347.0. I am attempting to deploy windows defender 1.1.1593.0 across
the network via MSI and GPO Software deployment. It installs ok during the
windows startup but we i try and run defender as a user or an administrator
on the pc the error comes up

Application Failed to Intialize: 0x80070005. Access is denied.

The error seems to go away after a first reboot. Any ideas on how to fix it?

Thank you!

Same issue here... I have SMS 2003 SP2 and use it to deploy Defender. A few
weeks ago I updated clients to build 1592 with no error. 1593 just came out
and I pushed out a uninstall script to remove 1592 and installed 1593. No
errors at all however open up the software and you get an error "Application
failed to initialize: 0x80070005. Access is denied. The only thing I can
think of is that since we are required to remove the older build the folder
permisssions are not set correctly again until after the restart. Once you
reboot, you can open up the software with no issues.

"Veronika" wrote:

> We have Windows XP SP2 clients in environment currently running Defender
> v.1.1.1347.0. I am attempting to deploy windows defender 1.1.1593.0 across
> the network via MSI and GPO Software deployment. It installs ok during the
> windows startup but we i try and run defender as a user or an administrator
> on the pc the error comes up
>
> Application Failed to Intialize: 0x80070005. Access is denied.
>
> The error seems to go away after a first reboot. Any ideas on how to fix it?
>
> Thank you!
>
>

I am also having this issue...I use defender to protect my 1500+ W2K3
Enterprise. I've instructed my people to ignore this error, as most machines
seem to work fine to spite it. Anyone from Microsoft want to take a crack at
this? I installed the new Defender on my home machine without a GPO and
didn't get the error.

Excellent! Not because this issue exists.. But the fact that I am not the
only one experiencing it!! Agreed, let's get an idea on what might be
happening here Microsoft....

"Antipode" wrote:

> I am also having this issue...I use defender to protect my 1500+ W2K3
> Enterprise. I've instructed my people to ignore this error, as most machines
> seem to work fine to spite it. Anyone from Microsoft want to take a crack at
> this? I installed the new Defender on my home machine without a GPO and
> didn't get the error.

Have you tried going to Windows Update and checking for available updates?

Whatever you do, (installing and updateting or unistalling) always as a
administratºr.
This is the key!
The installation as an admin is not enough.
You needed to login as an Adm!n!stratºr.

Can you gº to Windows Update, select Express (Get high-priority updates),
and apply all offered updªtes
http://update.microsoft.com


Once that is finished, can you verify the update installs? There are many
pre-requisite files which are needed from windows update and signature update
with windows defender will fail until you hªve these f!les.


After , see here:
http://support.microsoft.com/kb/904423/en-us

Good luck
--

"FlaglerCollege" wrote:

> Excellent! Not because this issue exists.. But the fact that I am not the
> only one experiencing it!! Agreed, let's get an idea on what might be
> happening here Microsoft....
>
> "Antipode" wrote:
>
> > I am also having this issue...I use defender to protect my 1500+ W2K3
> > Enterprise. I've instructed my people to ignore this error, as most machines
> > seem to work fine to spite it. Anyone from Microsoft want to take a crack at
> > this? I installed the new Defender on my home machine without a GPO and
> > didn't get the error.

Interesting.... I thought that when you deploy with SMS 2003 and specify that
it uses an administrator user account it does get installed as an
administrator. What do you recommend for larger installations such as ours if
you have to manually log in as administrator?

"Engel" wrote:

> Have you tried going to Windows Update and checking for available updates?
>
> Whatever you do, (installing and updateting or unistalling) always as a
> administratºr.
> This is the key!
> The installation as an admin is not enough.
> You needed to login as an Adm!n!stratºr.
>
> Can you gº to Windows Update, select Express (Get high-priority updates),
> and apply all offered updªtes
> http://update.microsoft.com
>
>
> Once that is finished, can you verify the update installs? There are many
> pre-requisite files which are needed from windows update and signature update
> with windows defender will fail until you hªve these f!les.
>
>
> After , see here:
> http://support.microsoft.com/kb/904423/en-us
>
> Good luck
> --
>
> "FlaglerCollege" wrote:
>
> > Excellent! Not because this issue exists.. But the fact that I am not the
> > only one experiencing it!! Agreed, let's get an idea on what might be
> > happening here Microsoft....
> >
> > "Antipode" wrote:
> >
> > > I am also having this issue...I use defender to protect my 1500+ W2K3
> > > Enterprise. I've instructed my people to ignore this error, as most machines
> > > seem to work fine to spite it. Anyone from Microsoft want to take a crack at
> > > this? I installed the new Defender on my home machine without a GPO and
> > > didn't get the error.

I am also having the same problem. i deployed Defender via a GPO software
assignment. I receive the error after the initial install but it does not
reappear after a reboot.

"FlaglerCollege" wrote:

> Interesting.... I thought that when you deploy with SMS 2003 and specify that
> it uses an administrator user account it does get installed as an
> administrator. What do you recommend for larger installations such as ours if
> you have to manually log in as administrator?
>
> "Engel" wrote:
>
> > Have you tried going to Windows Update and checking for available updates?
> >
> > Whatever you do, (installing and updateting or unistalling) always as a
> > administratºr.
> > This is the key!
> > The installation as an admin is not enough.
> > You needed to login as an Adm!n!stratºr.
> >
> > Can you gº to Windows Update, select Express (Get high-priority updates),
> > and apply all offered updªtes
> > http://update.microsoft.com
> >
> >
> > Once that is finished, can you verify the update installs? There are many
> > pre-requisite files which are needed from windows update and signature update
> > with windows defender will fail until you hªve these f!les.
> >
> >
> > After , see here:
> > http://support.microsoft.com/kb/904423/en-us
> >
> > Good luck
> > --
> >
> > "FlaglerCollege" wrote:
> >
> > > Excellent! Not because this issue exists.. But the fact that I am not the
> > > only one experiencing it!! Agreed, let's get an idea on what might be
> > > happening here Microsoft....
> > >
> > > "Antipode" wrote:
> > >
> > > > I am also having this issue...I use defender to protect my 1500+ W2K3
> > > > Enterprise. I've instructed my people to ignore this error, as most machines
> > > > seem to work fine to spite it. Anyone from Microsoft want to take a crack at
> > > > this? I installed the new Defender on my home machine without a GPO and
> > > > didn't get the error.

I'm having this problem and the message appears even after I reboot. It
appears when I go the Start -> Programs and then try to start Defender. It
only goes away when I manually navigate to the deployment share and reinstall
Defender. The other thing that I noticed is that the Definition version is
1.0.0.0 created on 1/25/2006 at 2:29 PM. When I try to update the
definitions, Defender tells me that there are no updates available. The way
it stands right now, I can't deploy Defender. This needs to be resolved first.

"Mike Zirbes" wrote:

> I am also having the same problem. i deployed Defender via a GPO software
> assignment. I receive the error after the initial install but it does not
> reappear after a reboot.
>
> "FlaglerCollege" wrote:
>
> > Interesting.... I thought that when you deploy with SMS 2003 and specify that
> > it uses an administrator user account it does get installed as an
> > administrator. What do you recommend for larger installations such as ours if
> > you have to manually log in as administrator?
> >
> > "Engel" wrote:
> >
> > > Have you tried going to Windows Update and checking for available updates?
> > >
> > > Whatever you do, (installing and updateting or unistalling) always as a
> > > administratºr.
> > > This is the key!
> > > The installation as an admin is not enough.
> > > You needed to login as an Adm!n!stratºr.
> > >
> > > Can you gº to Windows Update, select Express (Get high-priority updates),
> > > and apply all offered updªtes
> > > http://update.microsoft.com
> > >
> > >
> > > Once that is finished, can you verify the update installs? There are many
> > > pre-requisite files which are needed from windows update and signature update
> > > with windows defender will fail until you hªve these f!les.
> > >
> > >
> > > After , see here:
> > > http://support.microsoft.com/kb/904423/en-us
> > >
> > > Good luck
> > > --
> > >
> > > "FlaglerCollege" wrote:
> > >
> > > > Excellent! Not because this issue exists.. But the fact that I am not the
> > > > only one experiencing it!! Agreed, let's get an idea on what might be
> > > > happening here Microsoft....
> > > >
> > > > "Antipode" wrote:
> > > >
> > > > > I am also having this issue...I use defender to protect my 1500+ W2K3
> > > > > Enterprise. I've instructed my people to ignore this error, as most machines
> > > > > seem to work fine to spite it. Anyone from Microsoft want to take a crack at
> > > > > this? I installed the new Defender on my home machine without a GPO and
> > > > > didn't get the error.