Answered by:
Another Classic WSUS Windows 10 Problem, anyone know what to do?

Question
-
Yippeeee! Yet another problem with WSUS without any sense or meaning.
I have set up a dedicated new WSUS 2012 server for distributing updates to Windows 10 machines because Microsoft decided to make it difficult for Windows 2008R2 WSUS to do this very task.
Anyway everything was working fine until suddenly all clients will not install updates even though they are reporting to the WSUS server (Today) and the WSUS server has approved the updates needed. The clients just say "Your Device is up to date" which I know for a fact it isn't.
Make sense to anybody? Appreciate any advice as WSUS is starting to drive me completely crazy.
Here is an image to show what I mean:
Tuesday, March 1, 2016 3:51 PM
Answers
-
Hi Yes the client could detect when checking online and would recieve updates.
Anyway as the Server only does WSUS I decided to reboot it.
for now it appears to have fixed the problem, so I guess a service stopped for one reason or another.
- Marked as answer by dubsdj - MCITP - CCA-V Wednesday, March 2, 2016 9:43 AM
Wednesday, March 2, 2016 9:43 AM
All replies
-
Below is the log, I cannot see anything unusual can anyone else?
2016/03/01 16:42:19.7928583 1060 4128 Shared * START * Service startup
2016/03/01 16:42:19.7981659 1060 4128 Agent WU client version 10.0.10586.103
2016/03/01 16:42:19.7982942 1060 4128 Agent SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2016/03/01 16:42:19.7983346 1060 4128 Agent Base directory: C:\WINDOWS\SoftwareDistribution
2016/03/01 16:42:19.7983901 1060 4128 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2016/03/01 16:42:19.7984048 1060 4128 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2016/03/01 16:42:19.7986573 1060 4128 Shared Network state: Connected
2016/03/01 16:42:19.8008017 1060 4128 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2016/03/01 16:42:19.8008065 1060 4128 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2016/03/01 16:42:19.8008098 1060 4128 Shared Power status changed
2016/03/01 16:42:19.8091872 1060 8380 Agent Initializing global settings cache
2016/03/01 16:42:19.8091875 1060 8380 Agent WSUS server: http://mywsus:8530
2016/03/01 16:42:19.8091878 1060 8380 Agent WSUS status server: http://mywsus:8530
2016/03/01 16:42:19.8091881 1060 8380 Agent Target group: (Unassigned Computers)
2016/03/01 16:42:19.8091884 1060 8380 Agent Windows Update access disabled: No
2016/03/01 16:42:19.8092192 1060 4128 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-03-02 08:14:23, not idle-only, not network-only
2016/03/01 16:42:19.8151433 1060 4128 Agent Initializing Windows Update Agent
2016/03/01 16:42:19.8151956 1060 4128 DownloadManager Download manager restoring 0 downloads
2016/03/01 16:42:19.8152398 1060 4128 Agent CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
2016/03/01 16:42:19.8735792 1060 12096 DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
2016/03/01 16:42:19.8788784 1060 12096 DownloadManager PurgeExpiredUpdates::Found 394 non expired updates.
2016/03/01 16:42:19.9050867 1060 8380 Agent * START * Queueing Finding updates [CallerId = UpdateOrchestrator Id = 1]
2016/03/01 16:42:19.9050909 1060 8380 Agent Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
2016/03/01 16:42:19.9051098 1060 8380 ComApi Search ClientId = UpdateOrchestrator
2016/03/01 16:42:19.9055358 1060 11128 Agent * END * Queueing Finding updates [CallerId = UpdateOrchestrator Id = 1]
2016/03/01 16:42:19.9057247 1060 11128 Agent * START * Finding updates CallerId = UpdateOrchestrator Id = 1
2016/03/01 16:42:19.9057253 1060 11128 Agent Online = Yes; Ignore download priority = No
2016/03/01 16:42:19.9057256 1060 11128 Agent Criteria = IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1""
2016/03/01 16:42:19.9057276 1060 11128 Agent ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2016/03/01 16:42:19.9057279 1060 11128 Agent Search Scope = {Machine}
2016/03/01 16:42:19.9057301 1060 11128 Agent Caller SID for Applicability: S-1-5-21-3954137694-296334654-1926628749-5126
2016/03/01 16:42:19.9057304 1060 11128 Agent RegisterService is set
2016/03/01 16:42:19.9061064 1060 11128 Misc Got WSUS Client/Server URL: http://mywsus:8530/ClientWebService/client.asmx""
2016/03/01 16:42:19.9338404 1060 12096 DownloadManager PurgeExpiredUpdates::Found 0 expired updates.
2016/03/01 16:42:19.9424048 1060 12096 Shared Effective power state: AC
2016/03/01 16:42:19.9424054 1060 12096 DownloadManager Power state change detected. Source now: AC
2016/03/01 16:42:20.1748708 1060 11128 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mywsus:8530/ClientWebService/client.asmx
2016/03/01 16:42:20.1748750 1060 11128 ProtocolTalker OK to reuse existing configuration
2016/03/01 16:42:20.1748798 1060 11128 ProtocolTalker Cached cookie has expired or new PID is available
2016/03/01 16:42:20.1758379 1060 11128 Misc Got WSUS SimpleTargeting URL: http://mywsus:8530""
2016/03/01 16:42:20.1760101 1060 11128 ProtocolTalker Initializing simple targeting cookie, clientId = f5f7907c-6aa9-4c95-89d2-3f88717c4bf6, target group = <NULL>, DNS name = it-manage01.abbey.local
2016/03/01 16:42:20.1760104 1060 11128 ProtocolTalker Server URL = http://mywsus:8530/SimpleAuthWebService/SimpleAuth.asmx
2016/03/01 16:42:20.1760216 1060 11128 WebServices Auto proxy settings for this web service call.
2016/03/01 16:42:20.2885025 1060 11128 WebServices Auto proxy settings for this web service call.
2016/03/01 16:42:20.3600088 1060 11128 ProtocolTalker PTInfo: Server requested registration
2016/03/01 16:42:21.1214500 1060 11128 ProtocolTalker PTInfo: syncing with server using normal query
2016/03/01 16:42:21.1316550 1060 11128 ProtocolTalker SyncUpdates round trips: 2
- Edited by dubsdj - MCITP - CCA-V Tuesday, March 1, 2016 8:38 PM
Tuesday, March 1, 2016 5:00 PM -
tried again and I still see no updates available. I enabled client side targeting and set default group to Workstations just to see if that made any difference, Log:
2016/03/01 17:13:35.3706076 2928 9192 AppAU * START * Finding app updates
2016/03/01 17:13:35.3706586 2928 9192 AppAU * END * Finding app updates, exit code = 0x00000000
2016/03/01 17:16:22.1975190 8980 4384 AppAU * START * Finding app updates
2016/03/01 17:16:22.1975751 8980 4384 AppAU * END * Finding app updates, exit code = 0x00000000
2016/03/01 17:16:50.7961042 660 3644 Misc Got WSUS Client/Server URL: http://mywsus:8530/ClientWebService/client.asmx""
2016/03/01 17:16:50.7961639 660 3644 ProtocolTalker OK to reuse existing configuration
2016/03/01 17:16:50.7961664 660 3644 ProtocolTalker Existing cookie is valid, just use it
2016/03/01 17:16:50.7961671 660 3644 ProtocolTalker PTInfo: Server requested registration
2016/03/01 17:16:50.8508924 660 3644 Misc Got WSUS Reporting URL: http://mywsus:8530/ReportingWebService/ReportingWebService.asmx""
2016/03/01 17:16:50.8993719 660 3644 WebServices Auto proxy settings for this web service call.
2016/03/01 17:19:31.4867033 660 3616 Agent Refreshing global settings cache
2016/03/01 17:19:31.4867043 660 3616 Agent WSUS server: http://mywsus:8530 (Unchanged)
2016/03/01 17:19:31.4867046 660 3616 Agent WSUS status server: http://mywsus:8530 (Unchanged)
2016/03/01 17:19:31.4867049 660 3616 Agent Target group: Workstations (Changed)- Edited by dubsdj - MCITP - CCA-V Tuesday, March 1, 2016 8:40 PM
Tuesday, March 1, 2016 5:25 PM -
Hi dubsdj,
What about the result if you check for update on win10 from Internet? Could the client detect these updates from Microsoft Update?
We may also test unstall an update on win10 (remember the KB number, in case we can re-install it), and approve that KB on WSUS server, check if the WIN10 can detect the uninstalled KB from WSUS server.
If we found that client is only unable to detect updates from WSUS server, they can detect from MU successfully, then we may check if re-index WSUS database and run server cleanup wizard could help:
re-index WSUS database:
https://technet.microsoft.com/en-us/library/dd939795(v=ws.10).aspx
Best Regards,
Anne
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Wednesday, March 2, 2016 7:51 AM -
Hi Yes the client could detect when checking online and would recieve updates.
Anyway as the Server only does WSUS I decided to reboot it.
for now it appears to have fixed the problem, so I guess a service stopped for one reason or another.
- Marked as answer by dubsdj - MCITP - CCA-V Wednesday, March 2, 2016 9:43 AM
Wednesday, March 2, 2016 9:43 AM -
Hi dubsdj-MCITP,
>Anyway as the Server only does WSUS I decided to reboot it. for now it appears to have fixed the problem, so I guess a service stopped for one reason or another.
Glad to hear you have solved the issue.
Best Regards,
Anne
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Thursday, March 3, 2016 1:21 AM