Fails to initialize

[Guest]

Just wanted to let everyone know that I still get the error 0x80010005 with
the new version of WD.

 

[plun]

Hi

Have you disabled any services ?

For example DCOM ? but check all.

http://www.theeldergeek.com/services_guide.htm

regards
plun

 

[Guest]

Hello JKB,

Go to Windows Update, do an Express scan, 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 have these files.
--

Go to the System Event log:

Start, Run, eventvwr.msc <enter>

Click on the System event log

Go to View, choose Filter, and choose "windefend" in the source control.

Look for yellow triangle entries that give the precise path and location of
what was detected, and use the button provided to paste the content of the
detection back to a message here.
--

Could you supply some information on what your OS is, firewall, anti-virus,
other RTP programs, WD engine, etc?

Eиçel

 

[Guest]

Engel
Even though I get the failed to initialize error, the program seems to
function. For example, the event log for today just shows the scan beginning
and the scan end. Nothing was found. I am running XP Pro, SP2. Firewall is
ZoneAlarm Pro and antivirus is McAfee. Everything is current.

 

[Guest]

Hi JKB,

I'm really confuse.

Do you follow plun sugeastion?

So you went to Windows Update, do an Express scan, and apply all offered
updªtes?

Now, to be sure, if you select the Process tab you should see MSASCui.exe
(the user interface), and MsMpEng.exe (the service executable) running.
In Windows Defender--real-time protection is done by a system service,
starting at boot time--that's the Windows Defender service, whose executable
is MsMpEng.exe.
MpCmdRun.exe monitors for the existence of new signatures and is responsible
initiating the updating process when new signatures are available.

So I understend you problem is going away. Please don't force WD to check
for updates or do any scan (only if is a emergency for you) out of the daily
quick scan scheduled. Wait about 3 o 4 days until the next update. Let hope
still the same.

Good luck, and thank you for reportimg back about your good news.

Еиçеl

 

[Guest]

Of the 3 files you mention to check under the Processes tab, MsMpEng.exe is
the only one shown running. When I do a search for the other 2, they are
present in the WinDefend file but are not running. Yes, I did follow Plun's
suggestion.

 

[Guest]

Check your Zone Alarm firewall log.

Is been reported to interfier with WD in different ways.
Ejemplo: see this posts
Subject: Finally updated to 1.14.1396.12 - Mpas-f.exe was blocked by ZA
4/17/2006 9:27 PM PST
By: (e-mail address removed)
In: microsoft.private.security.spyware.general

Good luck,

 

[Guest]

This is the only interesting thread I found on this issue so I decided to
post here

I've been through the different tips provided here but none of them sort out
this problem.

I'm running Windows Defender under W2000 SP4 and I always get the
application error at Defender startup "Application failed to initialize:
0x80010005. It is illegal to call out while inside message filter."

I've found an article in Microsoft Knowledge base: KB179692. It deals with
MFC Client application issue when calling methods on a COM server from within
OnDraw() or a WM_PAINT message handler. This KB Article provides three
workarounds; all based on code adaptation...

I then thought that it could come from the version of .net framework. I've
got both 1.1 and 2.0 versions installed. I unistalled them, launch
windowsupdate which reinstall both. Still the same error after reboot when
Windows Defender starts..

I checked the system requirements and the release notes
http://support.microsoft.com/?kbid=915052 . It does mentionned an issue with
GDI+, I copied the Gdiplus.dll in system32. No change

I'm stuck...

Anyone's got any idea?

Renaud

 

[Guest]

Well, I've had the problem since Feb 18 and could not find any satisfactory
answer.
Let's try to find out the common mode causes, since I guess there must be
more that just four or five guys running Win2K SP4 *and* Windows Defender.

I've got VS 2003 and VS3005 (thus the JIT debugger) installed. Are the other
one experiencing the 0x80010005 (that MS does not seem in a hurry to
solve...) using the same tools?

 

[Guest]

I'm facing the same issue. W2K SP4, completely uptodate. Is it a problem
with international versions? I'm running on pt_BR, and I've seen mention to
the same problem in french. Do any one of you run an US version of W2K?

Regards,

Gatto