NMAgent Takes Over CPU Processing When IPCONFIG /RELEASE Is Performed

After you upgrade from Microsoft Windows NT 4.0 to Windows 2000, using the "IPCONFIG /RELEASE" command may halt processing on the computer. When this occurs, CPU usage may reach 90 to 100 percent.

This behavior can occur if an earlier version of Network Manager (version 1.2) is installed and running on the computer. The NMAgent service is the cause of the high CPU usage. This service does not respond to Task Manager commands, but can be stopped with the "NET STOP NMAGENT" command.

NOTE: This issue occurs only if the full version of Network Monitor 1.2 is installed before you upgrade to Windows 2000. If the version of Network Monitor included with Windows NT 4.0 is installed, it is upgraded to Network Monitor 2.0 during the upgrade process.

To resolve this problem, uninstall the NMAgent service and install Network Monitor 2.0.

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

Network Monitor 1.2 is not supported in Windows 2000 and should be upgraded to version 2.0 for accurate and complete captures. Network Monitor 2.0 is intended for use with Windows 2000.