It is well known that Windows Modules Installer Worker (windows update) does not really care about resource efficiency, and just takes whatever cpu %, ram and disk usage it wants. I suppose I already got used to that.
Using Intel Core I7-10510U cpu (and 16GB ram), it takes 25%-26% on average:
But I was surprised to discover that it only uses one cpu core and exhausts it to the max, causing a heat spike that affect other cores, and overall prevents an efficient cpu usage:
Why is it doing so? Is there a way to force it use other cores or just take less cpu?
My main concern is all the heat it generates, and the long time it takes while maxing out a whole cpu core!