The WSO log on the client logs that these fixes aren't found.
- Code: Select all
Mon 07/23/2018 20:08:26.89 - Warning: Update kb4340006 (id: 1d638098-af3d-4ca5-84e1-db9cb0e82ae4) not found
Mon 07/23/2018 20:08:26.89 - Warning: Update kb4340558 (id: 16fbeb32-5ed2-4a46-bcd6-d7ac17887ee3) not found
When I then run MBSA, it identifies these fixes as missing.
- Code: Select all
| 4340558 | Missing | 2018-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Server 2012 R2 for x64 (KB4340558) | Important |
| 4099639 | Missing | 2018-05 Security Only Update for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 on Windows 8.1 and Server 2012 R2 for x64 (KB4099639) | Important |
| 4340006 | Missing | 2018-07 Security Only Update for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Server 2012 R2 for x64 (KB4340006) | Important |
I looked these up on Microsoft's Update Catalog web page, and when I click on [Download] I discover that these fixes are really just references to other fixes (e.g. kb4340006 references kb4338600, kb4338605, and kb4338613 and then kb4340558 references kb4338415, kb4338419 and kb4338424). When I look at the patches in the glb directory, WSO did actually retrieve each of these 6 referenced patches.
I can force these to be installed by adding a custom "StaticUpdateIds-w63-x64.txt" that lists these 6 fixes. The question here is whether I should be doing that or whether WSO should be determining this on its own.