Microsoft KB Archive/221911

Knowledge Base

You receive a "Could not execute: Path not found" error message and the memory usage increases when you start and stop the Visual C++ integrated debugger by using the F5 key

Article ID: 221911

Article Last Modified on 8/24/2005

---

APPLIES TO

• Microsoft Visual C++ 6.0 Enterprise Edition, when used with:
  • Microsoft Windows NT 4.0
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server

---

This article was previously published under Q221911

SYMPTOMS

The Windows NT Task Manager shows an increase in memory usage every time the Visual C++ integrated debugger is started using F5 and then stopped. When the system exhausts the virtual memory limit, the application and debugger crashes displaying the following 3 message boxes:

• Microsoft Visual C++ "Could not execute: Path not found (win 32 error3)"Microsoft Visual C++ "DM0025: Error attaching to Process"Sample.exe- Application Error "The application failed to initialize properly (0xc000012d)
  Click on OK to terminate the application"

RESOLUTION

The memory can be freed before the system runs out of virtual memory by closing the Visual C++ IDE.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

This problem was corrected in Microsoft Visual C++ .NET.

MORE INFORMATION

Steps to reproduce the behavior

1. Create a default MFC application using the AppWizard and build it.
2. Start Windows NT Task Manager, click the Performance tab and watch MEM Usage.
3. Start the integrated debugger by pressing F5.
4. Note MEM Usage.
5. Stop the debugger.
6. Repeat steps 3-5.

Note Mem Usage has increased by quite some amount. If the virtual memory limit is reached then the errors messages described above are seen.

Keywords: kberrmsg kbtshoot kbnoupdate kbide kbdebug KB221911

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.