As you know, any version of Windows is notare insured against the emergence of critical failures, which can be caused even by systemic processes. One such is COM Surrogate. What it is, for example, in the same "Task Manager", very few people imagine. And it is this service that can cause serious mistakes that can lead to complete crash. Despite all this, it is possible to combat such manifestations quite simply. But to understand the methods used to solve problems, you first need to figure out what kind of system component it is and what it is responsible for. Many of the solutions offered below will help to get rid of the many problems associated with the operation of this service, and with the constant hang of the operating system due to failures that it can provoke.
The process itself and the EXE file responsible for executing it are a cross between the system applet and the multimedia application control.
How can I explain this?Let's look at the COM Surrogate system process (Windows 7 x64). What it is? This is an application startup service that uses COM + rules for the IIS environment in which commands are executed. On the one hand, as already mentioned, this is a system service, on the other - the process responsible for starting multimedia programs and playing such content. The system library and the executable dllhost (COM Surrogate) responds for it. What it is in terms of the process, it is not difficult to guess, if you analyze the functioning of the component itself.
Many users are watching an increase in the loadto system resources. Usually, if this is not a virus, but a standard process, the use of RAM and the processor does not exceed fifty percent. But the completion of the process can lead to serious failures.
After completing this process, you can even getthe appearance of the so-called blue screen of death, which is fraught with serious consequences. In this case, you will need to have some means of eliminating errors of this kind that are available in the operating system itself (there are currently third-party tools).
The main method of error correction is to go into the standard "Control Panel" and use the setting of additional parameters in the system section.
Here you need to go to the tabprevent the execution of data and refuse to use DEP for all programs by activating the line below and making changes to the list by adding the file dllhost.exe (it is located in the System32 directory). When all actions are completed, a complete reboot of the system is required. Perhaps the load on system resources will decrease after that.
But the above actions sometimes do not give an effect. In Windows 8, COM Surrogate can cause an error also because the software does not meet the system requirements.
For example, often failures canoccur due to the KMPlayer player. Reviews of some users on the Internet even say that to remove problems you have to remove a set of codecs and decoders K-Lite or their analogs.
Removal is best done not usingtools of the operating system, and apply uninstaller programs that have a module for in-depth scanning of residual objects in the form of directories, files, and entries in the system registry. Only in this case the complete uninstallation is guaranteed (own Windows tools do not completely remove everything).
Actually, this is the service COM Surrogate. What is this applet, I think, at least a little clear. Now it is necessary to consider those actions that can not be performed under any circumstances.
The first condition:categorically it is forbidden to terminate the process in the "Task Manager" (the system, in the presence of unresolved errors, simply "crashes"). Secondly: in no case can you delete the dllhost.exe file from the System32 folder.
At such actions even after check of systemThe components of the sfc / scannow command will not be positive for their integrity. You can, of course, try to restore the system or download the latest successful configuration, but it's by no means the fact that the workability will be restored.
That's all for COM Surrogate.What is it is already clear. Finally, it is especially worthwhile to focus all users' attention on the fact that it is not recommended at all to perform any manipulations with the process itself and the file responsible for executing it (unless, of course, you want the operating system to stop working).
If these actions are impossibledue to the lack of rights to change the system parameters, you can advise to reduce the level of control of UAC. The section itself is quite easy to find through the search system, and in the window that appears, the slider that sets the security priorities should be moved to the lowest position.
In the rest, I think, problems should not be.This also concerns the understanding of the service itself, its principles of operation, and the methods that are used in the event of its forced stop. But sometimes even in case of short-term failure, the most common restart of a stationary computer terminal or laptop helps. But on mobile devices with Windows on board such problems were not noticed, so these issues were not considered at all (the system file in mobile OS is not available as such).
