Make sure inside x86 and x64 you have a Win7SP1 folder.
All advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee.
Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk.
This again is related to processing time, but, simply lowering the frequency is not enough due to the differences in how the Windows Update Client now works.
First thing we need to do is make sure your server is patched to support Windows 10. KB3159706 includes manual steps to complete, which are: You may find these changes are already present, if not enter those highlighted, and save the file. We need to make some adjustments to IIS which we can do with Power Shell.
The following will update, the Wsus App Pool (Wsus Pool) memory usage and CPU settings, the Client Web Service http Runtime settings and adds a new MIME Type.
You can either paste it into an elevated Power Shell window, or save it as a ps1 file.
The fix for that was easy, and required creating and populating that folder.
The folder in question can be found here, C:\Program Files\Update Services\Self Update\WSUS3 inside here are 3 folders one for each architecture.
In addition they now have about 30 Windows 10 devices.
I also have a WSUS Server i point client servers to which i decided to point some Windows 10 lab machines at.
The issue is described here in a blog post which focuses on Windows 10 1511, additionally another KB article which is for 1607 describes an issue where you had synced updates prior to KB3159706 being installed.