Windows 10: Windows server 2016- Tiworker.exe taking 40% cpu.

Hi


I am using windows server 2016 in our production environment, a week ago we find out that there is a process called TIworker.exe that taking 40% CPU usage from our production machines and i found out that this proccess belongs to windows update.

the affected machines can't go to restart or do windows updates automatically and because this reason once I set up those machines I set up from the SCONFIG to do "Manual" updates only, but for some reason last week we saw the Tiworker.exe running and taking 40% CPU, this cause some slowness to our customers.

I would like to know why this process keep running if we already change the windows update to manual mode from the sconfig and how I can make sure it won't happen again, i also disabled the "wuauserv" (windows update service) from the services.msc and change the startup type to "Disable".

I will appreciate your help in this case.


thanks

Eliran

:)

 

WIn 10 Tiworker.exe CPU hogging

6 Tips to Fix High CPU Usage by Tiworker.exe Process on Windows 10 hope this helps.
Here is another that suggests what Microsoft suggested.

BEST FIX: High CPU Usage By TiWorker.exe - Appuals.com

Part of windows updates.

 

Input Personalization Server keeps taking 40% CPU time..

Hello Niranjan,

I m using win10 on a surface 3.

For method 2 & 3, I m already using the latest driver on surface 3.

For method 1, even I m not in safe mode, the process sometimes uses high cpu, sometimes not.

I think it's not a driver issue.

There is also an input personalization server process on my other pc.

But it always eat 0% of cpu.

I was wondering why input personalization server eats 40% cpu on surface 3.

 

svc host exe takes 50% cpu in windows server std 2016

we are using windows server std 2016 and hosted some services which uses high network usage sometimes. but there is one svchost.exe which is not associated with any service ( i.e go to services from task manager does not show any associated services running)
keeps on running and takes 50% cpu straight away. if we kill it, again it popups in few minutes. how to identify the problem. what will be permanent solution? thanks in advance.