Every hour Windows appears to check for updates

We have a strange one here.

A bunch of servers across a domain appear to be checking for Windows updates every hour. I believe this is causing the systems to spike a little in CPU as it's the only event I can see happening on the hour. (we experience an hourly spike in CPU activity).

The weird thing is, windows update service and windows module installer service have both been disabled, yet this still happens. We've removed all group policies that specify windows update settings and set the servers manually to never check for updates.

Yet, within the Event Viewer, under the WindowsUpdateClient logs, we see events generated every hour that say

Log Name: Microsoft-Windows-WindowsUpdateClient/Operational
Source: Microsoft-Windows-WindowsUpdateClient
Date: 19/02/2015 15:01:04
Event ID: 40
Task Category: Windows Update Agent
Level: Information
Keywords: Check for Updates
User: SYSTEM
Computer: server.domain.local
Description:An update was detected.
Event Xml:


40
0
4
1
17
0x4000000000000002

61197


Microsoft-Windows-WindowsUpdateClient/Operational
SBS.mdcl.local



{0E32A997-25B7-46B6-9AB8-BF93CD0436B7}
200



I believe when there is critical updates windows update runs in the background using as little as possible the resources on the system/s. Everytime the computer is used windows updates pauses till there is no activity then continues until it is fully downloaded then you should see a message update waiting to be installed.
Just my thoughts as I see this occasionally and since I have auto download turned off it only happens with critical updates.



I believe when there is critical updates windows update runs in the background using as little as possible the resources on the system/s. Everytime the computer is used windows updates pauses till there is no activity then continues until it is fully downloaded then you should see a message update waiting to be installed.
Just my thoughts as I see this occasionally and since I have auto download turned off it only happens with critical updates.



what about the actual local settings for Windows Updates under Control Panel? is the option greyed or set to a particular choice?



This turned out to be a third party monitoring application (N-ABLE) that was causing this. Disabling the services sorted it out.



Self resolved



good to know the problem has been solved.

it was a pity that the 3rd-party application N-ABLE was not mentioned in the question.

Share this

Related Posts

There was an error in this gadget