You Are Unable to Start a Program with an .exe File Extension (250931)
The information in this article applies to:
- Microsoft Windows 98
- Microsoft Windows 98 Second Edition
- Microsoft Windows 95
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows Millennium Edition
This article was previously published under Q250931 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
When you attempt to start a program that has a .exe file extension, the program may not start, and you may receive one of the following error messages:
Windows cannot find FILES32.VXD. This program is needed for opening files of type "Application".
Path to program is not a valid Windows NT application
Your desktop may appear to be blank. Also, the problem appears many times on reboot. Even after an anti-virus program has indicated it has cleaned the virus, the registry entry listed later in this article is still in the registry.
CAUSE
This issue may be caused by the Pretty Park virus. The Pretty Park virus creates the Files32.vxd file, and then copies the Files32.vxd file to the Windows\System folder of your computer. Also, the Pretty Park virus modifies a registry key that causes the Files32.vxd file to run when you attempt to run any program that has a .exe file extension. NOTE:Microsoft does not offer software for computer virus detection or removal. Microsoft recommends that you obtain current anti-virus software from a vendor commercially involved in virus detection and removal. For a list of suppliers (vendors) of anti-virus software, please see the following article in the Microsoft Knowledge Base:
49500 List of Anti-Virus Software Vendors
RESOLUTIONWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk.
To resolve this issue, perform the following steps: NOTE: When you run the Regedit.exe file, you may experience the symptoms described earlier in this article. To work around this issue, rename the Regedit.exe file to Regedit.com, and then follow the instructions listed later in this article. After you are finished, rename the Regedit.com file back to Regedit.exe.
- Use Registry Editor to view and then modify the following registry key:
HKEY_LOCAL_MACHINE\Software\Classes\Exefile\Shell\Open\Command
- Double-click the following registry string value:
In Windows NT:
<NO NAME>: REG_SZ: "files32.vxd" "%1" %*
In Windows 95/98:
(Default)"files32.vxd" "%1" %*
- In the String box, remove Files32.vxd from the string. The correct string for this value is:
NOTE: HKEY_CLASSES_ROOT\Exefile\Shell\Open\Command may also contact the same string value and must also be modified to remove Files32.vxd from the string. When removing the Files32.vxd from the string, if a space is included, you may receive the message windows cannot find .exe when trying to run an .exe file. Verify that there are no extra spaces in the string after removing Files32.vxd.
- Click OK, and then quit Registry Editor.
- Click Start, point to Find, and then click Files or Folders.
- In the Named box, type files32.vxd, and then click Find Now
- In the Name box, right-click the Files32.vxd file, and then click Delete.
NOTE: The Files32.vxd file is not a Windows file and does not reside on the Windows media.
Modification Type: | Minor | Last Reviewed: | 3/17/2005 |
---|
Keywords: | kbenv kberrmsg kbprb kbui KB250931 |
---|
|