The reporting back can take up to 20 minutes, beats me why, clear evidence of a system that is overly convoluted and error prone. To do is compare applicable updates, downloads them, installs them and report back. Every dam patch tuesday there are problems, mostly client problems. Oh and to add, I am sick and tired off this whole Windows Update charade, it's time they re-engineer the whole process as it quite clearly not works correctly. Any other updates seem to be working fine by the wayĪdding the MSU mine type as suggested doesn't work for me by the way. ![]() Indeed running something like windows update mini tool will download from the Microsoft servers but not from Wsus, which in my view points to a wsus problem. Even though the actual files ARE downloaded into the softwaredistribution folder. 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.
0 Comments
Leave a Reply. |