I have been keen to get hold of this update early to check it out before some of our other users get hold of it so have been checking Windows Update directly rather than going via our WSUS server. The update is now available via Windows Update but is not being picked up by my WSUS servers.
Currently this behaviour is by design, due to KB2919355 breaking connectivity with SSL (HTTPS) secured WSUS servers. The 2919355 update has been held back from WSUS whilst a new update to fix this problem can be prepared and released, otherwise you’d potentially get 2919355 and then nothing else from WSUS, ever.
I’m not using SSL for my WSUS servers so this wouldn’t affect me, but at least I now know why the update isn’t showing.
- KB2919355 (8.1. update 1) breaks WSUS clients
- Windows 8.1 Update (KB 2919355) prevents interaction with WSUS 3.2 over SSL
Quoting from the latter:
There is a known issue which causes some PCs updated with the Windows 8.1 Update (KB 2919355) to stop scanning against Windows Server Update Services 3.0 Service Pack 2 (WSUS 3.0 SP2 or WSUS 3.2) servers which are configured to use SSL and have not enabled TLS 1.2.
Microsoft plans to issue an update as soon as possible that will correct the issue and restore the proper behavior for Windows 8.1 Update KB 2919355 scanning against all supported WSUS configurations. Until that time, we are temporarily suspending the distribution of the Windows 8.1 Update KB 2919355 to WSUS servers.
There is now a KB article KB2959977 about this issue, though no fix yet (and I also fixed the link to the blog post above that I’m quoting from).