I have the exact same problem, systems that succesfully upgraded to 1607 using the new upgrade mechanism in WSUS now fail to get past 0% for any CU. We will have to wait and see until the next CU.

Update: this issue seems to only happen if there is an update for Windows 10 version 1607 but it does not happen if there are only Office suite updates (they are installing fine). I also tried to dump Windows Update logs using 'Get-WindowsUpdateLog' but I could not find anything 'strange' (and there are a lot of GUIDs inside it). Update, Windows Management Instrumentation and Windows Push Notifications System Service) and Windows Update application stucks on 'Downloading updates'.Īlso, after that the first time I try to open an application I get an error message window that shows 'The stub received bad data'. I just approved KB3176929 and KB3176495 for Windows 10 Version 1607 on the WSUS side and once the client tries do download them, a list of services start crashing (Windows Update, Application Information, Background Intelligent Transfer Service, Computerīrowser, Delivery Optimization, IKE and AuthIP IPsec Keying Modules, IP Helper, Server, Geolocation Service, User Profile Service, System Event Notification Service, Shell Hardware Detection, Themes, User Manager, Update Orchestrator Service for Windows Windows Server 2012 R2 with WSUS role (KB3095113 + KB3159706 with manual steps after the installation) Hi! I am the facing the same behaviour, tried that last registry key (it was already set like this) and it did not work.

Windows 10, versao 1607.