Err: "Hidden Console of WOW VDM" Running 16-bit or MS-DOS App (142026)

SYMPTOMS

When running a 16-bit Windows application or an MS-DOS application, you may receive one of the following error messages:

Hidden console of WOWVDM NT VDM has encountered a system error. The handle is invalid. Choose Close to terminate the application.

Hidden console of WOW VDM c:\<winnt>\System32\Config.nt. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.

Hidden Console of WOW VDM c:\<winnt>\System32\Autoexec.nt. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.

Hidden Console of WOW VDM error while setting up environment for the application. Choose Close to terminate the application.

Config.nt The system file is not suitable for running MS-DOS and Microsoft Windows Applications.

CAUSE

The symptoms above may occur for one or more of the following reasons:

One or all of the following files are corrupt or missing from the %Systemroot\System32 folder:

Autoexec.nt
Config.nt
Command.com
Windows NT is installed on a removable drive such as Bernoulli, IOMEGA, or SyQuest drive.
You attempt to install another version of Windows NT on a removable drive.
Pagefile.sys resides on a removable drive.

RESOLUTION

To correct this problem, perform one or more of the following:

Run the emergency repair disk (ERD) to replace the missing or corrupt file(s). The ERD also verifies the integrity of Windows NT system files in general.
Manually expand the Autoexec.nt, Config.nt, and Command.com files off the Windows NT CD-ROM.
Move the paging file to a permanent physical drive.

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

MORE INFORMATION

For more information on troubleshooting MS-DOS applications, please see the following Microsoft Knowledge Base article:

ARTICLE-ID: 165214
TITLE : Troubleshooting MS-DOS-Based Programs in Windows NT 4.0