Entries in Config.nt or Autoexec.nt May Cause NTVDM Errors

• Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
• Microsoft Windows NT Server versions 3.5, 3.51, 4.0
• Microsoft Windows 2000 Professional
• Microsoft Windows 2000 Server
• Microsoft Windows 2000 Advanced Server

SYMPTOMS

When you start a 16-bit application, you receive an error message similar to the following:

16 Bit Windows Subsystem - Hidden Console of WOWVDM.
The NTVDM CPU has encountered an illegal instruction. Source

CAUSE

When you receive WOWVDM error messages when starting 16 bit applications, they may be caused by problems with the Config.nt or Autoexec.nt file. These files are parsed each time a VDM is started. If there are problems with these files, you may see error messages such as the above.

RESOLUTION

Either restore the Config.nt or Autoexec.nt file, or remark (REM) any nonstandard lines in the existing files to determine which file is the source of the errors. Remove the offending line(s).

MORE INFORMATION

Also, check the version(s) of the Command.com file(s). The modified date should be the same as the dates of the original installation of Windows NT. For example, the original Windows NT has 8/2/96 dates and Windows NT with SP1 has 10/13/96 dates.

Rename any versions of Command.com that are not of these dates, with the exception of a version of Command.com in the root folder of the boot partition (usually drive C) and the Windows folder if you are dual-booting with Windows 95/98.

You should also make sure that there is only one copy of the Windows NT Command.com file, in the System32 folder.

Additional query words: prodnt

Keywords : kbusage nt16ap NTSrvWkst
Version : WINDOWS:2000; winnt:3.5,3.51,4.0
Platform : WINDOWS winnt
Issue type : kbprb