1709 Update failure - Windows updates database corruption

Highlighted
New Contributor

At my company we've started piloting 1709 using deployment of the feature update via config mgr. So far success rate is pretty good. With the 20% or so that have failed we have found that running the Windows update troubleshooter finds corrupted windows update database. After doing the repair and retrying the update via config mgr it is succeeding most of the time. We have not tracked down the cause of the corruption yet but wondering how common this is and also is there any way to automate a health check of the windows update db/datastore and repair if automatically if issues are found? by script or any other method?

 

Thanks!

0 Replies