Run the Recommended SQL database Maintenance script on the actual SQL database. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.ĩ.

Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).Ĩ. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).ħ. Remove declined updates from the WSUS Database.Ĥ. Shrink your WSUSContent folder's size by declining superseded updates.ģ. Remove all Drivers from the WSUS Database.Ģ. It is the last WSUS Script you will ever need.ġ. Have a peek at my Adamj Clean-WSUS script. Has anyone else had the same issue since the 1703 upgrade and have you fixed it on your WSUS server? I need to get this fixed to move on to bigger and better thing. I have installed the ADMX files but I don't want to make to many changes that it breaks things for anyone.

Set the GPO to disable downloading drivers & prevent it from checking the internet for updates.

Approved the updates for the correct groups.

Set all the computers in the correct groups.

esd to the application pool as 'application/octet-stream' I am trying to get those to go to 1703 as well.Īs for the initial client though it will not download or install the needed updates. The other 1607 clients check in with the WSUS Server fine and install updates fine.

If I restart the computer it does the same thing. It stays like this for hours!Īccording to WSUS server it hasn't check in successfully for almost 24 hours now and it shows that the updates for 2017-06 failed. When I click Install Now it shows that it is downloading and then when they disappear the windows shows 'Download Updates 0%'. It shows they need to be downloaded and installed. It was able to find the Defender Definitions and updates from (2017-06) from the WSUS Server. Once the client updated it then checked for the updates again now as a 1703 computer. I was recently able to push the 1703 update to a 1607 client through WSUS without a problem. I am running WSUS on an Offline network running Windows Server 2016.

Update win 10 offline