Windows Defender Install opens in Notepad

[Guest]

Windows Defender Opens in Notepad automatically on install. Will do nothing
else. I have a couple other programs that have done the same thing. The
others are driver analysis programs. I reset some of my services a couple
weeks ago and this issue developed then. But have only had 3 including
Defender that won't install. No other issues otherwise. What services are
required to run for Defender to install? OS is XP Pro SP2 OEM. Have racked my
brain for a week trying to find it suspect 2 or more services disabled or not
started and outside of turning them on all at once which I would not go
through there isn't an easy option I know of. Can't find info anywhere on
which are required.

 

[Bill Sanderson]

You need the Windows Installer service not disabled.

You may want to reinstall Windows Installer 3.1:

http://www.microsoft.com/downloads/...fc-5f56-4a38-b838-de776fd4138c&DisplayLang=en

 

[Guest]

Windows Installer is enabled and I have never disabled it. I Clean Installed
my OS about 2 weeks ago. Some services I know are not necessary those i know
I disable. Went into Tweak XP and looked at several different lists on the
subject and didn't even disable as many as in these lists. Stayed real close
to safe settings. I have installed probably 15 apps. since I set my services
the way they are and no issues. Except Defender, MSI Live Update, and Driver
Headquarters Driver Detective. Just these three. I will reinstall Win
installer and see but have doubts. To many other installs with no issue.
Something about these apps. seem to be using a service that the other apps I
have installed are not. Or is there something maybe in Win Installer they are
tying to use nothing else has? Will see. Learning.Have also tried with all my
security turned off. Thanks for help.

 

[Bill Sanderson]

I've now seen at least three people with this symptom, although a different
app (i.e. notepad) is involved in each case. So there must be some common
cause.

I haven't succeeded in solving this in the other cases--it'd be nice to get
your services back to the default settings and see whether that resolves
this.

--

 

[Guest]

Let me show you what is showing up in Notepad. Will go back to default on my
services later today and see what happens. Any way this is what shows to me
to be where the fault on the install this is straight out of Notepad. Ran SFC
and tried to install again didn't change anyhing. Have the complete i386
copied off the install disk to the C:Windows/DriverCache/i386 anyway and
those registry settings are still default. Install DirectX Enduser Runtime
Feb 06 & .Net Framework 2.0 Redistributable a few days ago also. All other
updates are current.
ÂTLOSS error
ÂÂSING error
ÂÂÂDOMAIN error
ÂR6029
This application cannot run using the active version of the Microsoft .NET
Runtime
Please contact the application's support team for more information.
ÂÂR6028
unable to initialize heap
ÂÂÂR6027
- not enough space for lowio initialization
ÂÂÂR6026
- not enough space for stdio initialization
ÂÂÂR6025
- pure virtual function call
ÂÂR6024
- not enough space for _onexit/atexit table
ÂÂÂR6019
- unable to open console device
ÂÂÂR6018
- unexpected heap error
ÂÂÂR6017
- unexpected multithread lock error
ÂÂÂR6016
- not enough space for thread data

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
ÂÂR6009
- not enough space for environment
R6008
- not enough space for arguments
ÂÂR6002
- floating point not loaded
ÂÂÂMicrosoft Visual C++ Runtime Library ÂÂÂ

ÂRuntime Error!


Program: ÂÂ... <program name unknown>









TLOSS error
SING error
DOMAIN error
R6032
Attempt to use MSIL code from this assembly during native code initialization
This indicates a bug in your application. It is most likely the result of
calling an MSIL-compiled (/clr) function from a native constructor or from
DllMain.
R6032
not enough space for locale information
R6031
- Attempt to initialize the CRT more than once.
This indicates a bug in your application.
R6030
- CRT not initialized
R6028
- unable to initialize heap
R6027
- not enough space for lowio initialization
R6026
- not enough space for stdio initialization
R6025
- pure virtual function call
R6024
- not enough space for _onexit/atexit table
R6019
- unable to open console device
R6018
- unexpected heap error
R6017
- unexpected multithread lock error
R6016
- not enough space for thread data

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
R6009
- not enough space for environment
R6008
- not enough space for arguments
R6002
- floating point not loaded
Microsoft Visual C++ Runtime Library

... <program name unknown> Runtime Error!

Program: InitializeCriticalSectionAndSpinCount

 

[Bill Sanderson]

I know that RPC is a prerequisite for the Windows Defender service, so make
sure that one is not disabled.


--

 

[Guest]

Installed XP Pro x64 on the system that originally started this issue but I
am going to install the same XP Pro OS and setup on another PC that was on
this one and see if the same issue arises. Will set it up the same way. By
the way why won't Defender run on x64? Is it going to be resolved in the
Final Release or will it not ever run x64? Didn't expect it to have 16bit
code or Legacy DOS on it now.Haven't studied it but tried to install on x64
and would not even open, at all. RPC was enabled by the way thats a service
that is a must. Will set up the other system same as this one and work back
to see if it does it the same way interested to know what causes it myself.
Thanks for the help. If it does do it again do I just need to pick up this
thread or start another?

 

[Guest]

Installed XP Pro x64 on the system that originally started this issue but I
am going to install the same XP Pro OS and setup on another PC that was on
this one and see if the same issue arises. Will set it up the same way. By
the way why won't Defender run on x64? Is it going to be resolved in the
Final Release or will it not ever run x64? Didn't expect it to have 16bit
code or Legacy DOS on it now.Haven't studied it but tried to install on x64
and would not even open, at all. RPC was enabled by the way thats a service
that is a must. Will set up the other system same as this one and work back
to see if it does it the same way interested to know what causes it myself.
Thanks for the help. If it does do it again do I just need to pick up this
thread or start another?

 

[Bill Sanderson]

There is a separate Defender download for x64--check the download site--the
link is quite inconspicuous, but it is on the same page as the 32-bit
download.

You can stick with this thread, I think.
--