Windows 10: How to fix high CPU usage of "Service host DCOM server process launcher"

Actually, after updating to windows 11, I've had a lot of problems and now after plugging in my adapter my fan speeds up to max so I've closed everything and opened task manager to see what happening and there I came to know that this service host DCOM server process launcher is taking high CPU usage and I even plugged out and seen but still the service host DCOM server process takes a lot of CPU usage so please help me solve this issue

:)

 

Service Host: DCOM Server Process Launcher High CPU Usage (100%)

So, it starts when I start development server from npm. And continues till next restart even when I shut down the server. And my CPU runs at 100% usage.
Why is this? And how do I fix this?

 

DCOM server process launcher high cpu usage

Hi, Demon

To fix DCOM server process launcher high usage issue on Windows 10, you can try to disconnect all the external devices from
your computer. ... So to fix this issue, disconnect all the external devices from your computer and restart your computer and check whether the DCOM server still having a high
usage issue.

If this won't work then see this article

https://answers.microsoft.com/en-us...high-cpu/3be0f3c1-616f-4601-bc82-3f566aed8b96

 

service host DCOM server process laucher high CPU usage

Same in my Windows 10 for a long time.

Recently, I used the process monitor (remember to click file-show details for all processes) from Windows Sysinternals suit to check the DCOM server process launcher process (svchost.exe). I found a System Events Broker server thread with start address
“DAB.dll!DabSessionStateChanged+0xe4c” use a lot of CPU and make a lot of cycles delta(ten times than others)record. After suspended this thread, the DCOM server process launcher seems works fine, no more high CPU usage. I don’t know is there some side effects
to suspend the thread or is it the same dll cause this problem in another computer.

Although I had to do this every boot, it`s really a workable temporary solution for me.
Hope MS fix it as soon as possible and this is helpful.