Since Windows 7 and Windows 2008 R2 everytime you open a console program, the system opens another process called conhost.exe, to apply windows themes and enable the drag&drop functionality to that console window.
Provided that on a server system windows themes are disabled, that I won't ever use the drag&drop functionality, that each of this process takes at least 2 MB of RAM and, most important, according to sysinternals process explorer each conhost.exe process has more than 2500-3000 context switches per second (thus reducing the performance of the whole system), I would like to restore the old behaviour of windows 2008/vista and disable conhost.exe entirely.
Any ideas?
Windows – How to disable console host on Windows Server 2008 R2
windowswindows 7windows-server-2008-r2
Related Solutions
I've had success with Sysinternals Process Explorer. With this, you can search to find what process(es) have a file open, and you can use it to close the handle(s) if you want. Of course, it is safer to close the whole process. Exercise caution and judgement.
To find a specific file, use the menu option Find->Find Handle or DLL... Type in part of the path to the file. The list of processes will appear below.
If you prefer command line, Sysinternals suite includes command line tool Handle, that lists open handles.
Examples
c:\Program Files\SysinternalsSuite>handle.exe |findstr /i "e:\"(finds all files opened from drivee:\"c:\Program Files\SysinternalsSuite>handle.exe |findstr /i "file-or-path-in-question"
Related Topic
- Windows – Weird “missing” CD/DVD driver during Windows Server 2008 installation
- Windows – Permission denied to create files on root of C: Windows Server 2008 R2
- Windows – Cant kill process on Windows Server 2008!! – Thread in Wait:Executive State
- Windows Server – How to Kill a Process Running Under SYSTEM Account
Best Answer
it isn't possible: from http://blogs.technet.com/b/askperf/archive/2009/10/05/windows-7-windows-server-2008-r2-console-host.aspx
ConHost represents a permanent change in the way that console application I/O is handled. There is no registry key or group policy setting that can force Windows to revert back to “legacy mode” console behavior.