E
Eliran A
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
Continue reading...
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
Continue reading...