![]() Why Is Conhost.exe Using So Much CPU and Disk? For the most part, each process should take up very little memory (usually under 10 MB) and almost zero CPU unless the process is active. Many background apps work this way, so it’s not uncommon to see multiple instances of the Console Window Host process running at any given time. A good example of this is the Plex Media Server app, which runs as a background app and uses the command line to make itself available to other devices on your network. In addition, other apps that make use of the command line will spawn their own Console Windows Host process-even if you don’t see an active window for them. Each instance of Command Prompt running will spawn its own Console Window Host process. You’ll often see several instances of the Console Window Host process running in Task Manager. Why Are There Several Instances of the Console Window Host Process Running? In the end, the Console Window Host is something like a shell that maintains the power of running a system-level service like CSRSS, while still securely and reliably granting the ability to integrate modern interface elements. If you check the conhost.exe process out in Process Explorer, you can see that it actually runs under the csrss.ese process. And that’s the method still used in Windows 8 and 10, allowing all the new interface elements and styling that have come along since Windows 7.Įven though the Task Manager presents the Console Window Host as a separate entity, it’s still closely associated with CSRSS. The process sort of sits in the middle between CSRSS and the Command Prompt (cmd.exe), allowing Windows to fix both of the previous issues-interface elements like scrollbars draw correctly, and you can again drag and drop into the Command Prompt. As the name implies, its a host process for the console window. This is because the Desktop Window Manager handles drawing the title bars and frame, but an old-fashioned CSRSS window still sits inside.Įnter Windows 7 and the Console Window Host process. Still, that theming only went so far. If you take a look at the console in Windows Vista, it looks like it uses the same theme as everything else, but you’ll notice that the scrollbars are still using the old style. The Command Prompt gained some superficial theming from this (like the glassy frame present in other windows), but it came at the expense of being able to drag and drop files, text, and so on into the Command Prompt window. Windows Vista introduced the Desktop Window Manager-a service that “draws” composite views of windows onto your desktop rather than letting each individual app handle that on its own. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |