When you start a 16-bit program on a computer running Windows NT, the Ntvdm.exe and Wowexec.exe processes start. After you quit the 16-bit program, the Ntvdm.exe and Wowexec.exe ...

support.microsoft.com/kb/181333

Just above it in the list, you'll see indented entries for Wowexec.exe (the Windows on Windows subsystem) and the executable name of each 16-bit program running in that virtual ...

www.microsoft.com/windowsxp/using/security/learnmore/spot16bit.mspx

There must be a valid WOWEXEC.EXE in the SYSTEM32 subdirectory for the WOW subsystem to start. If the file is corrupt or missing, the above error message may appear during logon ...

support.microsoft.com/kb/101924

Reapply your current service pack (in case any of these DLLs were replaced in subsequent service packs) NOTE: You should also verify that the Wowexec.exe and Gdi.exe files exist in ...

support.microsoft.com/kb/222975

You also see wowexec.exe (the Windows on Windows subsystem), and the executable name of each 16-bit program that is running in that WOW virtual machine.

support.microsoft.com/kb/320127

Note that if any changes are made to variables related to the Windows 3.0 or Windows 3.1 subsystem (Wowexec.exe), you may have to restart the computer for these changes to be ...

support.microsoft.com/kb/314495

support.microsoft.com/search/default.aspx?query=wowexec.exe&x=11&y=16&catalog=LCID%3D10...

Note that if any changes are made to variables related to the Windows 3.0 or 3.1 subsystem (WOWEXEC.EXE), the user may have to restart the computer in order for these ...

support.microsoft.com/kb/103656

The VDMEnumProcessWOW() function provides a simple way to enumerate all VDMs running 16-bit Windows tasks. These VDMs contain the WowExec.exe task.

support.microsoft.com/kb/182559

Wowexec.exe; Vdmredir.dll; Krnl386.exe; Krnl286.exe (Windows NT 3.1 only) Gdi.exe; User.exe; Wow32.dll (not in Windows 3.1) Commdlg.dll; Version.dll; Shell32.dll

support.microsoft.com/kb/196453