Windows 10 not obeying updates check frequency GPO?

%3CLINGO-SUB%20id%3D%22lingo-sub-269555%22%20slang%3D%22en-US%22%3EWindows%2010%20not%20obeying%20updates%20check%20frequency%20GPO%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-269555%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20recently%20added%20Automatic%20Updates%20detection%20frequency%20GPO%20to%20our%20AD%20with%20a%20value%20of%206.%20Because%20i%20wanted%20our%20systems%20to%20get%20updates%20faster%20and%20get%20updated%20faster.%20So%20every%20PC%20should%20be%20checking%20in%20to%20WSUS%20every%204-6%20hours.%20Windows%207%20do%20that.%20But%20Windows%2010%201803%20seems%20to%20still%20use%20some%20internal%20timer%20for%20this%20and%20only%20checking%20in%20after%208%20or%20so%20hours.%20It%20still%20takes%20the%20value%20of%20WSUS%20URL%2C%20so%20GPO%20works%2C%20but%20this%20setting%20not.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278149%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20not%20obeying%20updates%20check%20frequency%20GPO%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278149%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20setting%20is%20set%20to%206%2C%20so%20check%20interval%20should%20be%204%2C8-6%20hours%20(it%20is%20only%20minus%200-20%25%2C%20not%20plus).%20Windows%2010%20is%20checking%20every%20~8%20hours.%20Windows%207%20PCs%20are%20checking%20every%205-6%20hours.%20So%20it%20works%20on%20Windows%207%20and%20not%20on%20Windows%2010.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278123%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20not%20obeying%20updates%20check%20frequency%20GPO%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278123%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22x-hidden-focus%22%3E%3CEM%3EThe%20exact%20wait%20time%20is%20determined%20by%20using%20the%20hours%20specified%20here%20minus%20zero%20to%20twenty%20percent%20of%20the%20hours%20specified.%20For%20example%2C%20if%20this%20policy%20is%20used%20to%20specify%20a%2020-hour%20detection%20frequency%2C%20then%20all%20clients%20to%20which%20this%20policy%20is%20applied%20will%20check%20for%20updates%20anywhere%20between%2016%20to%2020%20hours.%20Windows%20will%20check%20for%20available%20updates%20at%20the%20default%20interval%20of%2022%20hours.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3EThis%20is%20by%20design%20and%20prevents%20all%20of%20your%20devices%20from%20trying%20to%20pull%20updates%20simultaneously%20and%20saturating%20your%20network.%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwaas-wu-settings%23automatic-updates-detection-frequency%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwaas-wu-settings%23automatic-updates-detection-frequency%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-788571%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20not%20obeying%20updates%20check%20frequency%20GPO%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-788571%22%20slang%3D%22en-US%22%3EDoes%20the%20problem%20still%20exist%3F%20in%20Windows%2010%201903%3F%3C%2FLINGO-BODY%3E
Highlighted
Super Contributor

I have recently added Automatic Updates detection frequency GPO to our AD with a value of 6. Because i wanted our systems to get updates faster and get updated faster. So every PC should be checking in to WSUS every 4-6 hours. Windows 7 do that. But Windows 10 1803 seems to still use some internal timer for this and only checking in after 8 or so hours. It still takes the value of WSUS URL, so GPO works, but this setting not.

3 Replies
Highlighted

The exact wait time is determined by using the hours specified here minus zero to twenty percent of the hours specified. For example, if this policy is used to specify a 20-hour detection frequency, then all clients to which this policy is applied will check for updates anywhere between 16 to 20 hours. Windows will check for available updates at the default interval of 22 hours.

 

This is by design and prevents all of your devices from trying to pull updates simultaneously and saturating your network.

 

https://docs.microsoft.com/en-us/windows/deployment/update/waas-wu-settings#automatic-updates-detect...

 

Highlighted

The setting is set to 6, so check interval should be 4,8-6 hours (it is only minus 0-20%, not plus). Windows 10 is checking every ~8 hours. Windows 7 PCs are checking every 5-6 hours. So it works on Windows 7 and not on Windows 10.

Highlighted
Does the problem still exist? in Windows 10 1903?