Related Posts

1 Comment Already

commenter
Insomnic Said,
May 6th, 2009 @11:36 am  

I recently had to deal with this fun issue and found a few other items could cause the problem. One specific one is if %systemroot% is used in the PATH variable instead of “C:\Windows” or “C:\WINNT”. There is a registry key that can be messed up by other installs to point %systemroot% to the wrong location. In my case, it was pointing to C:\Windows but our environment uses C:\WINNT. In order to keep from breaking the program that changed it I just added C:\WINNT as well as the %systemroot% options to the PATH variable.

Please Leave Your Comments Below

Please Note: All comments will be moderated