Installshied WOWEXEC Error

[Lokester]

Installshield WOWEXEC error

I ran This XP Pro OS for nearly a year. Installing several programs
without a problem. Then I suddenly could not install some new
software - the first that I noted was Photoshop 7.0. Installshield
would not start - I'd get an hour glass for a few seconds - then
nothing. Each time I noticed WOWEXEC at the top of the Task Manager
and occasionally and error saying WOWEXEC was not responding when I
shut the computer down. Occasionally I would get an error message
stating that a 16 bit task had timed out and the 16 bit subsystem may
be unstable.

I googled the problem and on adivise:

1. Checked for Viruses
2. turned off the Virus program
3. Deleted WOWEXEC and NTVDM - loaded them from another computer
and also had them reinstall from this OS.

Nothing worked.

In frustration I reloaded the XP operating system on a different
drive, and went through the whole thing of reinstalling programs - and
VOLA - problem solved. All programs loaded - including Photoshop 7.0.
Installshield started right up.

A few days passed - during that time XP was busy loading updates -
including SP2. I tried to load a small little program and same thing
- no Installshield - again - WOWEXEC at the top of the Task Manager??

So - it worked fine in the beginning - and now it's doing the same
thing. I've checked for viruses again - none found.

Considering loading up another OS and not installing SP2. Has there
been compatibility problems with SP2 & WOW - or any other specific XP
update? After one complete reload I'm reluctant to do it again
without some hope. I guess I can load every program I need before I
do any updates at all - hoping that the Updates cause the problem and
I can do everything before this weird problem returns. Again - I want
to be clear - the problem does not occur in the beginning - after a
fresh OS is loaded.

Any advice would be very greatly appreciated.

LL

 

[Wesley Vogel]

WOWEXEC.exe and ntvdm.exe only run for 16 bit applications, old MS-DOS
programs.

ntvdm.exe is NT Virtual DOS Machine and WOWEXEC.exe is Windows On Windows
Execution Process.

I bet you have a trojan.

What happens if you type: cmd in Start | Run and click OK?

Any error messages?

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Lokester]

What happens if you type: cmd in Start | Run and click OK?

Any error messages?

No error message. Just get an MS-DOS window with a normal command
line.

I've run complete virus scans and I'm pretty sure that I'm up to date
with definitions - I'll try again.

I'm running Microsoft Bookshelf which is a pretty old program and as I
recall the problems with this latest installed OS occurred when I
installed that. Also I did get an error on that installation -
however it did load. I checked the version of installashied for
Bookshelf 2000 & it is Version 1 - seems I remember something about
Installashield recommending Version 2 or better. Could that have
somehow contaminated futher Installshield programs?

I'd like to get a bit better idea of what I'm dealing with before I go
through the process of loading yet another OS and reloading all of my
programs. It appears that I'll have to do that anyway - I tried to
load Studio 9 and was happy when it appeared to load correctly until
the very end - then my computer locked and the program is in there but
will not uninstall.

Any suggestions on checking this Trojan possibility other than virus
scans?

Thanks for any suggestions.

LL

 

[Wesley Vogel]

Trojans usually add cmd.com so typing cmd opens cmd.com instead of cmd.exe
and you'd get an error message like...
--------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------
or
---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------

I suspected something like...
WORM_ALCAN.A - Technical details
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_ALCAN.A&VSect=T

or..
Symantec Security Response - W32.Alcra.A
http://securityresponse.symantec.com/avcenter/venc/data/w32.alcra.a.html

InstallShield Search for wowexec brings up nothing
http://www.installshield.com/search/gsearch.asp?filter=p&as_epq=&q=wowexec&area=kb&area=helpnet

InstallShield Search for ntvdm brings up one article
http://www.installshield.com/search/gsearch.asp?filter=p&as_epq=&q=ntvdm&area=kb&area=helpnet

This article applies to the following:
Product(s):
InstallShield Express 2.1x, 3.5x
InstallShield Professional 3.x, 5.x
http://support.installshield.com/kb/view.asp?articleid=Q103299

InstallShield Consumer Central Frequently Asked Questions
http://consumer.installshield.com/faq.asp?

InstallShield Consumer Central - Common Errors
http://consumer.installshield.com/common.asp

Other than virus scans, yes, spyware scans.

If you are trying to load old programs I can see why wowexec and ntvdm may
be involved, but not for programs written for XP.

Not everything in the following article will apply. The article was written
for Windows 2000. However most of it does.
[[If it was not one of those, you can try the DLLs under the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\W

Value: Known DLLs]]

The above should read...
[[If it was not one of those, you can try the DLLs under the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WOW

Value: Known DLLs]]
Troubleshooting NTVDM and WOW Startup Errors
http://support.microsoft.com/default.aspx?scid=kb;en-us;196453


Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314106

How to Troubleshoot 16-Bit Windows Programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314495

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Lokester]

Did a full virus scan with current definitions, ran spybot & adware.

I'm frustrated. I'm going to run a complete OS XP Pro Installation
and load all the important programs before I do any updates - then I'm
not doing SP2. This stuff is becoming way too expensive time wise.

The strange thing is - although I still get WOWEXEC warnings and 16
bit messages - the majority of the time it's after trying to load
recent XP type programs - photoshop 7.0. Again this is after they
have loaded properly before?

My buddy says I should get a Mac - I'm starting to wonder.

LL

Trojans usually add cmd.com so typing cmd opens cmd.com instead of cmd.exe
and you'd get an error message like...
--------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------
or
---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------

I suspected something like...
WORM_ALCAN.A - Technical details
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_ALCAN.A&VSect=T

or..
Symantec Security Response - W32.Alcra.A
http://securityresponse.symantec.com/avcenter/venc/data/w32.alcra.a.html

InstallShield Search for wowexec brings up nothing
http://www.installshield.com/search/gsearch.asp?filter=p&as_epq=&q=wowexec&area=kb&area=helpnet

InstallShield Search for ntvdm brings up one article
http://www.installshield.com/search/gsearch.asp?filter=p&as_epq=&q=ntvdm&area=kb&area=helpnet

This article applies to the following:
Product(s):
InstallShield Express 2.1x, 3.5x
InstallShield Professional 3.x, 5.x
http://support.installshield.com/kb/view.asp?articleid=Q103299

InstallShield Consumer Central Frequently Asked Questions
http://consumer.installshield.com/faq.asp?

InstallShield Consumer Central - Common Errors
http://consumer.installshield.com/common.asp

Other than virus scans, yes, spyware scans.

If you are trying to load old programs I can see why wowexec and ntvdm may
be involved, but not for programs written for XP.

Not everything in the following article will apply. The article was written
for Windows 2000. However most of it does.
[[If it was not one of those, you can try the DLLs under the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\W

Value: Known DLLs]]

The above should read...
[[If it was not one of those, you can try the DLLs under the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WOW

Value: Known DLLs]]
Troubleshooting NTVDM and WOW Startup Errors
http://support.microsoft.com/default.aspx?scid=kb;en-us;196453


Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314106

How to Troubleshoot 16-Bit Windows Programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314495

 

[Lokester]

Gawd !! I'm going to Mac. This is BS !! I've done a full OS
reinstall for the third time and every time I get near a 16 bit
program I get blocked out of installing any further programs that have
anything to do with 16 bit - and you'd be surprised what those are -
Studio 9, Photoshop 7.0 etc, etc.

I've tried to get answers and I get a lot of maybe it's this, maybe
it's that. I tried to follow your advise but it got vaguer and vaguer
- and I see a lot of other inquires about this same subject - all
concluding with the same advise involving a lot of effort on our part
with no tangible results.

Microsoft just isn't worth the effort - it was fun for a while, when I
thought I the effort was going to pay off - but I'm in business.

LL

Did a full virus scan with current definitions, ran spybot & adware.

I'm frustrated. I'm going to run a complete OS XP Pro Installation
and load all the important programs before I do any updates - then I'm
not doing SP2. This stuff is becoming way too expensive time wise.

The strange thing is - although I still get WOWEXEC warnings and 16
bit messages - the majority of the time it's after trying to load
recent XP type programs - photoshop 7.0. Again this is after they
have loaded properly before?

My buddy says I should get a Mac - I'm starting to wonder.

LL

Trojans usually add cmd.com so typing cmd opens cmd.com instead of cmd.exe
and you'd get an error message like...
--------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------
or
---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------

I suspected something like...
WORM_ALCAN.A - Technical details
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_ALCAN.A&VSect=T

or..
Symantec Security Response - W32.Alcra.A
http://securityresponse.symantec.com/avcenter/venc/data/w32.alcra.a.html

InstallShield Search for wowexec brings up nothing
http://www.installshield.com/search/gsearch.asp?filter=p&as_epq=&q=wowexec&area=kb&area=helpnet

InstallShield Search for ntvdm brings up one article
http://www.installshield.com/search/gsearch.asp?filter=p&as_epq=&q=ntvdm&area=kb&area=helpnet

This article applies to the following:
Product(s):
InstallShield Express 2.1x, 3.5x
InstallShield Professional 3.x, 5.x
http://support.installshield.com/kb/view.asp?articleid=Q103299

InstallShield Consumer Central Frequently Asked Questions
http://consumer.installshield.com/faq.asp?

InstallShield Consumer Central - Common Errors
http://consumer.installshield.com/common.asp

Other than virus scans, yes, spyware scans.

If you are trying to load old programs I can see why wowexec and ntvdm may
be involved, but not for programs written for XP.

Not everything in the following article will apply. The article was written
for Windows 2000. However most of it does.
[[If it was not one of those, you can try the DLLs under the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\W

Value: Known DLLs]]

The above should read...
[[If it was not one of those, you can try the DLLs under the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WOW

Value: Known DLLs]]
Troubleshooting NTVDM and WOW Startup Errors
http://support.microsoft.com/default.aspx?scid=kb;en-us;196453


Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314106

How to Troubleshoot 16-Bit Windows Programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314495

 

[Lokester]

Add to the Software - ATI Software package - so I can't run any or
the bebefits or the installed video card.

What answers do you have? I don't mean the try this -- try that -
what real answers do you have?

LL

Gawd !! I'm going to Mac. This is BS !! I've done a full OS
reinstall for the third time and every time I get near a 16 bit
program I get blocked out of installing any further programs that have
anything to do with 16 bit - and you'd be surprised what those are -
Studio 9, Photoshop 7.0 etc, etc.

I've tried to get answers and I get a lot of maybe it's this, maybe
it's that. I tried to follow your advise but it got vaguer and vaguer
- and I see a lot of other inquires about this same subject - all
concluding with the same advise involving a lot of effort on our part
with no tangible results.

Microsoft just isn't worth the effort - it was fun for a while, when I
thought I the effort was going to pay off - but I'm in business.

LL

Did a full virus scan with current definitions, ran spybot & adware.

I'm frustrated. I'm going to run a complete OS XP Pro Installation
and load all the important programs before I do any updates - then I'm
not doing SP2. This stuff is becoming way too expensive time wise.

The strange thing is - although I still get WOWEXEC warnings and 16
bit messages - the majority of the time it's after trying to load
recent XP type programs - photoshop 7.0. Again this is after they
have loaded properly before?

My buddy says I should get a Mac - I'm starting to wonder.

LL

Trojans usually add cmd.com so typing cmd opens cmd.com instead of cmd.exe
and you'd get an error message like...
--------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------
or
---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------

I suspected something like...
WORM_ALCAN.A - Technical details
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_ALCAN.A&VSect=T

or..
Symantec Security Response - W32.Alcra.A
http://securityresponse.symantec.com/avcenter/venc/data/w32.alcra.a.html

InstallShield Search for wowexec brings up nothing
http://www.installshield.com/search/gsearch.asp?filter=p&as_epq=&q=wowexec&area=kb&area=helpnet

InstallShield Search for ntvdm brings up one article
http://www.installshield.com/search/gsearch.asp?filter=p&as_epq=&q=ntvdm&area=kb&area=helpnet

This article applies to the following:
Product(s):
InstallShield Express 2.1x, 3.5x
InstallShield Professional 3.x, 5.x
http://support.installshield.com/kb/view.asp?articleid=Q103299

InstallShield Consumer Central Frequently Asked Questions
http://consumer.installshield.com/faq.asp?

InstallShield Consumer Central - Common Errors
http://consumer.installshield.com/common.asp

Other than virus scans, yes, spyware scans.

If you are trying to load old programs I can see why wowexec and ntvdm may
be involved, but not for programs written for XP.

Not everything in the following article will apply. The article was written
for Windows 2000. However most of it does.
[[If it was not one of those, you can try the DLLs under the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\W

Value: Known DLLs]]

The above should read...
[[If it was not one of those, you can try the DLLs under the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WOW

Value: Known DLLs]]
Troubleshooting NTVDM and WOW Startup Errors
http://support.microsoft.com/default.aspx?scid=kb;en-us;196453


Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314106

How to Troubleshoot 16-Bit Windows Programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314495

 

[Wesley Vogel]

The strange thing is - although I still get WOWEXEC warnings and 16

bit messages - the majority of the time it's after trying to load

What WOWEXEC warnings and 16 bit messages?

Error message when you install or start an MS-DOS or 16-bit Windows-based
program
http://support.microsoft.com/default.aspx?scid=kb;en-us;324767

"16 Bit MS-DOS Subsystem" Error Message When You Install a Program
http://support.microsoft.com/default.aspx?scid=kb;en-us;314452

16-bit MS-DOS Subsystem error while installing or running a DOS application
http://windowsxp.mvps.org/16bit.htm

Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314106

How to Troubleshoot 16-Bit Windows Programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314495

Troubleshooting NTVDM and WOW Startup Errors
http://support.microsoft.com/default.aspx?scid=kb;en-us;196453


--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Add to the Software - ATI Software package - so I can't run any or
the bebefits or the installed video card.

What answers do you have? I don't mean the try this -- try that -
what real answers do you have?

LL

Gawd !! I'm going to Mac. This is BS !! I've done a full OS
reinstall for the third time and every time I get near a 16 bit
program I get blocked out of installing any further programs that have
anything to do with 16 bit - and you'd be surprised what those are -
Studio 9, Photoshop 7.0 etc, etc.

I've tried to get answers and I get a lot of maybe it's this, maybe
it's that. I tried to follow your advise but it got vaguer and vaguer
- and I see a lot of other inquires about this same subject - all
concluding with the same advise involving a lot of effort on our part
with no tangible results.

Microsoft just isn't worth the effort - it was fun for a while, when I
thought I the effort was going to pay off - but I'm in business.

LL

Did a full virus scan with current definitions, ran spybot & adware.

I'm frustrated. I'm going to run a complete OS XP Pro Installation
and load all the important programs before I do any updates - then I'm
not doing SP2. This stuff is becoming way too expensive time wise.

The strange thing is - although I still get WOWEXEC warnings and 16
bit messages - the majority of the time it's after trying to load
recent XP type programs - photoshop 7.0. Again this is after they
have loaded properly before?

My buddy says I should get a Mac - I'm starting to wonder.

LL


On Sat, 10 Dec 2005 14:56:08 -0700, "Wesley Vogel"

Trojans usually add cmd.com so typing cmd opens cmd.com instead of
cmd.exe and you'd get an error message like...
--------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for
running MS-DOS and Microsoft Windows applications. Choose 'Close' to
terminate the application.
---------------------------
Close Ignore
---------------------------
or
---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for
running MS-DOS and Microsoft Windows applications. Choose 'Close' to
terminate the application.
---------------------------
Close Ignore
---------------------------

I suspected something like...
WORM_ALCAN.A - Technical details
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_ALCAN.A&VSect=T

or..
Symantec Security Response - W32.Alcra.A
http://securityresponse.symantec.com/avcenter/venc/data/w32.alcra.a.html

InstallShield Search for wowexec brings up nothing
http://www.installshield.com/search/gsearch.asp?filter=p&as_epq=&q=wowexec&area=kb&area=helpnet

InstallShield Search for ntvdm brings up one article
http://www.installshield.com/search/gsearch.asp?filter=p&as_epq=&q=ntvdm&area=kb&area=helpnet

This article applies to the following:
Product(s):
InstallShield Express 2.1x, 3.5x
InstallShield Professional 3.x, 5.x
http://support.installshield.com/kb/view.asp?articleid=Q103299

InstallShield Consumer Central Frequently Asked Questions
http://consumer.installshield.com/faq.asp?

InstallShield Consumer Central - Common Errors
http://consumer.installshield.com/common.asp

Other than virus scans, yes, spyware scans.

If you are trying to load old programs I can see why wowexec and ntvdm
may be involved, but not for programs written for XP.

Not everything in the following article will apply. The article was
written for Windows 2000. However most of it does.
[[If it was not one of those, you can try the DLLs under the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\W

Value: Known DLLs]]

The above should read...
[[If it was not one of those, you can try the DLLs under the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WOW

Value: Known DLLs]]
Troubleshooting NTVDM and WOW Startup Errors
http://support.microsoft.com/default.aspx?scid=kb;en-us;196453


Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314106

How to Troubleshoot 16-Bit Windows Programs in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314495