Probleme mit WSUS 4.0 (2023)

Hallo zusammen,

ich habe wieder mal schwierigkeiten mit WSUS, vielleicht kann mir hier jemand helfen. Grundsätzlich gibt es immer mal wieder Fälle, wo von dem client keine Berichte erstellt werden, bzw. diese sich nach WDS Verteilung gar nicht erst melden. Momentan geht es um solch einen Rechner mit W10Pro Build 1607 14393.1066 letztes cum update wurde it DISM integriert. Nach Hochfahren des Rechner steht er sogar im WSUS, erstellt aber keinen Bericht.

(Video) Windows server 2019 - How to Resolve Wsus Server Connection Error | Fix: WSUS Connection Error Reset

hier mal ein Ausschnitt aus dem log dazu, vielen Dank im voraus!

2017.04.27 10:46:23.2032981 484 7588 Agent Search Scope = {Machine}
2017.04.27 10:46:23.2033005 484 7588 Agent Caller SID for Applicability: S-1-5-21-1370898019-654996262-1539857752-5094
2017.04.27 10:46:23.2033009 484 7588 Agent ProcessDriverDeferrals is set
2017.04.27 10:46:23.2033009 484 7588 Agent RegisterService is set
2017.04.27 10:46:23.2075322 484 7588 Misc Got WSUS Client/Server URL: http://192.168.250.195:8530/ClientWebService/client.asmx;;
2017.04.27 10:46:23.4245446 484 7588 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.250.195:8530/ClientWebService/client.asmx
2017.04.27 10:46:23.4246749 484 7588 ProtocolTalker OK to reuse existing configuration
2017.04.27 10:46:23.4246785 484 7588 ProtocolTalker Existing cookie is valid, just use it
2017.04.27 10:46:23.4246793 484 7588 ProtocolTalker PTInfo: Server requested registration
2017.04.27 10:46:24.5343800 484 7588 WebServices Auto proxy settings for this web service call.
2017.04.27 10:47:24.5243291 484 7588 WebServices WS error: Fehler bei der Kommunikation mit dem Endpunkt bei http://192.168.250.195:8530/ClientWebService/client.asmx;.;
2017.04.27 10:47:24.5243319 484 7588 WebServices WS error: Fehler beim Empfangen der HTTP-Antwort.
2017.04.27 10:47:24.5243386 484 7588 WebServices WS error: Der Vorgang wurde nicht innerhalb der vorgesehenen Zeit abgeschlossen.
2017.04.27 10:47:24.5243733 484 7588 WebServices WS error: Das Zeitlimit f??r den Vorgang wurde erreicht.
2017.04.27 10:47:24.5243781 484 7588 WebServices Web service call failed with hr = 8024401c.
2017.04.27 10:47:24.5243792 484 7588 WebServices Current service auth scheme=0.
2017.04.27 10:47:24.5243800 484 7588 WebServices Current Proxy auth scheme=0.
2017.04.27 10:47:26.5394060 484 7588 WebServices Auto proxy settings for this web service call.
2017.04.27 10:48:28.5250034 484 7588 WebServices WS error: Fehler bei der Kommunikation mit dem Endpunkt bei http://192.168.250.195:8530/ClientWebService/client.asmx;.;
2017.04.27 10:48:28.5250089 484 7588 WebServices WS error: Fehler beim Empfangen der HTTP-Antwort.
2017.04.27 10:48:28.5250105 484 7588 WebServices WS error: Der Vorgang wurde nicht innerhalb der vorgesehenen Zeit abgeschlossen.
2017.04.27 10:48:28.5250132 484 7588 WebServices WS error: Fehler bei der Kommunikation mit dem Endpunkt bei http://192.168.250.195:8530/ClientWebService/client.asmx;.;
2017.04.27 10:48:28.5250148 484 7588 WebServices WS error: Fehler beim Empfangen der HTTP-Antwort.
2017.04.27 10:48:28.5250168 484 7588 WebServices WS error: Der Vorgang wurde nicht innerhalb der vorgesehenen Zeit abgeschlossen.
2017.04.27 10:48:28.5250187 484 7588 WebServices WS error: Das Zeitlimit f??r den Vorgang wurde erreicht.
2017.04.27 10:48:28.5250239 484 7588 WebServices Web service call failed with hr = 8024401c.
2017.04.27 10:48:28.5250255 484 7588 WebServices Current service auth scheme=0.
2017.04.27 10:48:28.5250266 484 7588 WebServices Current Proxy auth scheme=0.
2017.04.27 10:48:30.5401912 484 7588 WebServices Auto proxy settings for this web service call.
2017.04.27 10:49:32.5290449 484 7588 WebServices WS error: Fehler bei der Kommunikation mit dem Endpunkt bei http://192.168.250.195:8530/ClientWebService/client.asmx;.;
2017.04.27 10:49:32.5290476 484 7588 WebServices WS error: Fehler beim Empfangen der HTTP-Antwort.
2017.04.27 10:49:32.5290496 484 7588 WebServices WS error: Der Vorgang wurde nicht innerhalb der vorgesehenen Zeit abgeschlossen.
2017.04.27 10:49:32.5290520 484 7588 WebServices WS error: Fehler bei der Kommunikation mit dem Endpunkt bei http://192.168.250.195:8530/ClientWebService/client.asmx;.;
2017.04.27 10:49:32.5290539 484 7588 WebServices WS error: Fehler beim Empfangen der HTTP-Antwort.
2017.04.27 10:49:32.5290555 484 7588 WebServices WS error: Der Vorgang wurde nicht innerhalb der vorgesehenen Zeit abgeschlossen.
2017.04.27 10:49:32.5290583 484 7588 WebServices WS error: Fehler bei der Kommunikation mit dem Endpunkt bei http://192.168.250.195:8530/ClientWebService/client.asmx;.;
2017.04.27 10:49:32.5290599 484 7588 WebServices WS error: Fehler beim Empfangen der HTTP-Antwort.
2017.04.27 10:49:32.5290626 484 7588 WebServices WS error: Der Vorgang wurde nicht innerhalb der vorgesehenen Zeit abgeschlossen.
2017.04.27 10:49:32.5290646 484 7588 WebServices WS error: Das Zeitlimit f??r den Vorgang wurde erreicht.
2017.04.27 10:49:32.5290674 484 7588 WebServices Web service call failed with hr = 8024401c.
2017.04.27 10:49:32.5290686 484 7588 WebServices Current service auth scheme=0.
2017.04.27 10:49:32.5290697 484 7588 WebServices Current Proxy auth scheme=0.
2017.04.27 10:49:32.5290839 484 7588 ProtocolTalker PTError: 0x8024401c
2017.04.27 10:49:32.5290907 484 7588 ProtocolTalker SyncUpdates_WithRecovery failed. 0x8024401c
2017.04.27 10:49:32.5291368 484 7588 ProtocolTalker SyncUpdates round trips: 1
2017.04.27 10:49:32.5291388 484 7588 ProtocolTalker Sync of Updates 0x8024401c
2017.04.27 10:49:32.5291633 484 7588 ProtocolTalker SyncServerUpdatesInternal failed 0x8024401c
2017.04.27 10:49:32.5418646 484 7588 Agent Failed to synchronize, error = 0x8024401C
2017.04.27 10:49:32.5790640 484 7588 Agent Exit code = 0x8024401C
2017.04.27 10:49:32.5790652 484 7588 Agent * END * Finding updates CallerId = UpdateOrchestrator Id = 2
2017.04.27 10:49:32.5909896 484 3680 ComApi *RESUMED* Search ClientId = UpdateOrchestrator
2017.04.27 10:49:32.5914072 484 3680 ComApi Updates found = 0
2017.04.27 10:49:32.5914080 484 3680 ComApi Exit code = 0x00000000, Result code = 0x8024401C
2017.04.27 10:49:32.5914084 484 3680 ComApi * END * Search ClientId = UpdateOrchestrator
2017.04.27 10:49:32.5917720 484 160 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2017.04.27 10:50:16.5553688 484 7316 ComApi * START * Init Search ClientId = Device Driver Retrieval Client
2017.04.27 10:50:16.5553779 484 7316 ComApi * START * Search ClientId = Device Driver Retrieval Client
2017.04.27 10:50:16.5674992 484 7316 Agent * START * Queueing Finding updates [CallerId = Device Driver Retrieval Client Id = 3]
2017.04.27 10:50:16.5675146 484 7316 Agent Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is not in sequential scan list
2017.04.27 10:50:16.5675178 484 7316 Agent Added service 9482F4B4-E343-43B6-B170-9A65BC822C77 to sequential scan list
2017.04.27 10:50:16.5675367 484 7316 ComApi Search ClientId = Device Driver Retrieval Client
2017.04.27 10:50:16.5675861 484 6136 Agent Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is in sequential scan list
2017.04.27 10:50:16.5724897 484 3516 Agent * END * Queueing Finding updates [CallerId = Device Driver Retrieval Client Id = 3]
2017.04.27 10:50:16.5783408 484 3516 Agent * START * Finding updates CallerId = Device Driver Retrieval Client Id = 3
2017.04.27 10:50:16.5783416 484 3516 Agent Online = Yes; AllowCachedResults = No; Ignore download priority = No
2017.04.27 10:50:16.5783420 484 3516 Agent Criteria = IsInstalled=0 and Type='Driver'""
2017.04.27 10:50:16.5783448 484 3516 Agent ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2017.04.27 10:50:16.5783452 484 3516 Agent Search Scope = {Machine}
2017.04.27 10:50:16.5783479 484 3516 Agent Caller SID for Applicability: S-1-5-18
2017.04.27 10:50:16.5783483 484 3516 Agent RegisterService is set
2017.04.27 10:50:16.5814843 484 3516 Misc EP: error: 0x8024500C : - failed to get SLS data
2017.04.27 10:50:16.5814878 484 3516 Misc Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL, error = 0x8024500C
2017.04.27 10:50:16.5814894 484 3516 ProtocolTalker PTError: 0x8024500c
2017.04.27 10:50:16.5814918 484 3516 ProtocolTalker Initialization failed for Protocol Talker Context 0x8024500c
2017.04.27 10:50:16.6060045 484 3516 Agent Exit code = 0x8024500C
2017.04.27 10:50:16.6060057 484 3516 Agent * END * Finding updates CallerId = Device Driver Retrieval Client Id = 3
2017.04.27 10:50:16.6100445 484 3680 ComApi *RESUMED* Search ClientId = Device Driver Retrieval Client
2017.04.27 10:50:16.6104823 484 3680 ComApi Updates found = 0
2017.04.27 10:50:16.6104830 484 3680 ComApi Exit code = 0x00000000, Result code = 0x8024500C
2017.04.27 10:50:16.6104834 484 3680 ComApi * END * Search ClientId = Device Driver Retrieval Client
2017.04.27 10:50:16.6111277 484 7316 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2017.04.27 10:54:21.1073372 7312 4776 ComApi * START * Init Search ClientId = TrustedInstaller FOD
2017.04.27 10:54:21.1073396 7312 4776 ComApi * START * Search ClientId = TrustedInstaller FOD
2017.04.27 10:54:21.1178235 484 4920 Agent * START * Queueing Finding updates [CallerId = TrustedInstaller FOD Id = 4]
2017.04.27 10:54:21.1178271 484 4920 Agent Removing service 00000000-0000-0000-0000-000000000000 from sequential scan list
2017.04.27 10:54:21.1178291 484 4920 Agent Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
2017.04.27 10:54:21.1179554 7312 4776 ComApi Search ClientId = TrustedInstaller FOD
2017.04.27 10:54:21.1211478 484 6728 Agent * END * Queueing Finding updates [CallerId = TrustedInstaller FOD Id = 4]
2017.04.27 10:54:21.1242150 484 6728 Agent * START * Finding updates CallerId = TrustedInstaller FOD Id = 4
2017.04.27 10:54:21.1242158 484 6728 Agent Online = Yes; AllowCachedResults = No; Ignore download priority = No
2017.04.27 10:54:21.1242166 484 6728 Agent Criteria = CategoryIDs contains 'e104dd76-2895-41c4-9eb5-c483a61e9427'""
2017.04.27 10:54:21.1242186 484 6728 Agent ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017.04.27 10:54:21.1242190 484 6728 Agent Search Scope = {Machine}
2017.04.27 10:54:21.1242209 484 6728 Agent Caller SID for Applicability: S-1-5-21-1370898019-654996262-1539857752-5094
2017.04.27 10:54:21.1242213 484 6728 Agent RegisterService is set
2017.04.27 10:54:21.1284255 484 6728 Misc Got WSUS Client/Server URL: http://192.168.250.195:8530/ClientWebService/client.asmx;;
2017.04.27 10:54:21.2373821 484 6728 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.250.195:8530/ClientWebService/client.asmx
2017.04.27 10:54:21.2373829 484 6728 ProtocolTalker OK to reuse existing configuration
2017.04.27 10:54:21.2373853 484 6728 ProtocolTalker Existing cookie is valid, just use it
2017.04.27 10:54:21.2373861 484 6728 ProtocolTalker PTInfo: Server requested registration
2017.04.27 10:54:21.3166799 484 6728 WebServices Auto proxy settings for this web service call.
2017.04.27 10:54:21.3307688 484 6728 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.250.195:8530/ClientWebService/client.asmx
2017.04.27 10:54:21.3308959 484 6728 ProtocolTalker OK to reuse existing configuration
2017.04.27 10:54:21.3308990 484 6728 ProtocolTalker Cached cookie has expired or new PID is available
2017.04.27 10:54:21.3309101 484 6728 Misc Got WSUS SimpleTargeting URL: http://192.168.250.195:8530;;
2017.04.27 10:54:21.3310652 484 6728 ProtocolTalker Initializing simple targeting cookie, clientId = 9984dcbf-6171-41d9-a559-aac634f2e60c, target group = <NULL>, DNS name = tester.hal.prologa.intern
2017.04.27 10:54:21.3310660 484 6728 ProtocolTalker Server URL = http://192.168.250.195:8530/SimpleAuthWebService/SimpleAuth.asmx
2017.04.27 10:54:21.3310775 484 6728 WebServices Auto proxy settings for this web service call.
2017.04.27 10:54:21.3448750 484 6728 ProtocolTalker PTInfo: Server requested registration
2017.04.27 10:54:21.3638351 484 6728 ProtocolTalker SyncUpdates round trips: 1
2017.04.27 10:54:21.3712668 484 6728 Agent Found 0 updates and 3 categories in search; evaluated appl. rules of 3 out of 3 deployed entities
2017.04.27 10:54:21.3851879 484 6728 Agent * END * Finding updates CallerId = TrustedInstaller FOD Id = 4
2017.04.27 10:54:21.3992289 7312 7724 ComApi *RESUMED* Search ClientId = TrustedInstaller FOD
2017.04.27 10:54:21.4109619 7312 7724 ComApi Updates found = 0
2017.04.27 10:54:21.4109627 7312 7724 ComApi * END * Search ClientId = TrustedInstaller FOD
2017.04.27 10:54:21.4119219 7312 4776 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2017.04.27 10:58:11.5949908 484 2980 Misc Got WSUS Client/Server URL: http://192.168.250.195:8530/ClientWebService/client.asmx;;
2017.04.27 10:58:11.5950686 484 2980 ProtocolTalker OK to reuse existing configuration
2017.04.27 10:58:11.5950789 484 2980 ProtocolTalker Existing cookie is valid, just use it
2017.04.27 10:58:11.5950816 484 2980 ProtocolTalker PTInfo: Server requested registration
2017.04.27 10:58:11.7247898 484 2980 Misc Got WSUS Reporting URL: http://192.168.250.195:8530/ReportingWebService/ReportingWebService.asm ...;
2017.04.27 10:58:11.7248360 484 2980 WebServices Auto proxy settings for this web service call.
2017.04.27 11:06:28.4296121 4176 4944 ComApi * START * Init Search ClientId = TrustedInstaller FOD
2017.04.27 11:06:28.4296157 4176 4944 ComApi * START * Search ClientId = TrustedInstaller FOD
2017.04.27 11:06:28.4395288 484 3680 Agent * START * Queueing Finding updates [CallerId = TrustedInstaller FOD Id = 5]
2017.04.27 11:06:28.4395324 484 3680 Agent Removing service 00000000-0000-0000-0000-000000000000 from sequential scan list
2017.04.27 11:06:28.4395343 484 3680 Agent Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
2017.04.27 11:06:28.4396378 4176 4944 ComApi Search ClientId = TrustedInstaller FOD
2017.04.27 11:06:28.4428396 484 2444 Agent * END * Queueing Finding updates [CallerId = TrustedInstaller FOD Id = 5]
2017.04.27 11:06:28.4459053 484 2444 Agent * START * Finding updates CallerId = TrustedInstaller FOD Id = 5
2017.04.27 11:06:28.4459057 484 2444 Agent Online = Yes; AllowCachedResults = No; Ignore download priority = No
2017.04.27 11:06:28.4459065 484 2444 Agent Criteria = CategoryIDs contains 'e104dd76-2895-41c4-9eb5-c483a61e9427'""
2017.04.27 11:06:28.4459081 484 2444 Agent ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017.04.27 11:06:28.4459085 484 2444 Agent Search Scope = {Machine}
2017.04.27 11:06:28.4459104 484 2444 Agent Caller SID for Applicability: S-1-5-21-1370898019-654996262-1539857752-5094
2017.04.27 11:06:28.4459108 484 2444 Agent RegisterService is set
2017.04.27 11:06:28.4501000 484 2444 Misc Got WSUS Client/Server URL: http://192.168.250.195:8530/ClientWebService/client.asmx;;
2017.04.27 11:06:28.5555054 484 2444 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.250.195:8530/ClientWebService/client.asmx
2017.04.27 11:06:28.5555062 484 2444 ProtocolTalker OK to reuse existing configuration
2017.04.27 11:06:28.5555085 484 2444 ProtocolTalker Existing cookie is valid, just use it
2017.04.27 11:06:28.5555093 484 2444 ProtocolTalker PTInfo: Server requested registration
2017.04.27 11:06:28.6470872 484 2444 WebServices Auto proxy settings for this web service call.
2017.04.27 11:06:28.6598090 484 2444 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.250.195:8530/ClientWebService/client.asmx
2017.04.27 11:06:28.6599610 484 2444 ProtocolTalker OK to reuse existing configuration
2017.04.27 11:06:28.6599645 484 2444 ProtocolTalker Existing cookie is valid, just use it
2017.04.27 11:06:28.6599649 484 2444 ProtocolTalker PTInfo: Server requested registration
2017.04.27 11:06:28.6788520 484 2444 ProtocolTalker SyncUpdates round trips: 1
2017.04.27 11:06:28.6854425 484 2444 Agent Found 0 updates and 3 categories in search; evaluated appl. rules of 3 out of 3 deployed entities
2017.04.27 11:06:28.6995199 484 2444 Agent * END * Finding updates CallerId = TrustedInstaller FOD Id = 5
2017.04.27 11:06:28.7078496 4176 7620 ComApi *RESUMED* Search ClientId = TrustedInstaller FOD
2017.04.27 11:06:28.7090177 4176 7620 ComApi Updates found = 0
2017.04.27 11:06:28.7090181 4176 7620 ComApi * END * Search ClientId = TrustedInstaller FOD
2017.04.27 11:06:28.7099754 4176 4944 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2017.04.27 11:12:59.2424449 5908 5716 ComApi * START * Init Search ClientId = TrustedInstaller FOD
2017.04.27 11:12:59.2424472 5908 5716 ComApi * START * Search ClientId = TrustedInstaller FOD
2017.04.27 11:12:59.3421381 484 3116 Agent * START * Queueing Finding updates [CallerId = TrustedInstaller FOD Id = 6]
2017.04.27 11:12:59.3421417 484 3116 Agent Removing service 00000000-0000-0000-0000-000000000000 from sequential scan list
2017.04.27 11:12:59.3421441 484 3116 Agent Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
2017.04.27 11:12:59.3422546 5908 5716 ComApi Search ClientId = TrustedInstaller FOD
2017.04.27 11:12:59.3468740 484 7812 Agent * END * Queueing Finding updates [CallerId = TrustedInstaller FOD Id = 6]
2017.04.27 11:12:59.3500494 484 7812 Agent * START * Finding updates CallerId = TrustedInstaller FOD Id = 6
2017.04.27 11:12:59.3500506 484 7812 Agent Online = Yes; AllowCachedResults = No; Ignore download priority = No
2017.04.27 11:12:59.3500510 484 7812 Agent Criteria = CategoryIDs contains 'e104dd76-2895-41c4-9eb5-c483a61e9427'""
2017.04.27 11:12:59.3500534 484 7812 Agent ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017.04.27 11:12:59.3500538 484 7812 Agent Search Scope = {Machine}
2017.04.27 11:12:59.3500577 484 7812 Agent Caller SID for Applicability: S-1-5-21-1370898019-654996262-1539857752-5094
2017.04.27 11:12:59.3500581 484 7812 Agent RegisterService is set
2017.04.27 11:12:59.3543985 484 7812 Misc Got WSUS Client/Server URL: http://192.168.250.195:8530/ClientWebService/client.asmx;;
2017.04.27 11:12:59.5277035 484 7812 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.250.195:8530/ClientWebService/client.asmx
2017.04.27 11:12:59.5277043 484 7812 ProtocolTalker OK to reuse existing configuration
2017.04.27 11:12:59.5277070 484 7812 ProtocolTalker Existing cookie is valid, just use it
2017.04.27 11:12:59.5277078 484 7812 ProtocolTalker PTInfo: Server requested registration
2017.04.27 11:12:59.6462156 484 7812 WebServices Auto proxy settings for this web service call.
2017.04.27 11:12:59.6727053 484 7812 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.250.195:8530/ClientWebService/client.asmx
2017.04.27 11:12:59.6728257 484 7812 ProtocolTalker OK to reuse existing configuration
2017.04.27 11:12:59.6728292 484 7812 ProtocolTalker Existing cookie is valid, just use it
2017.04.27 11:12:59.6728296 484 7812 ProtocolTalker PTInfo: Server requested registration
2017.04.27 11:12:59.6940774 484 7812 ProtocolTalker SyncUpdates round trips: 1
2017.04.27 11:12:59.7075161 484 7812 Agent Found 0 updates and 3 categories in search; evaluated appl. rules of 3 out of 3 deployed entities
2017.04.27 11:12:59.7247578 484 7812 Agent * END * Finding updates CallerId = TrustedInstaller FOD Id = 6
2017.04.27 11:12:59.7327670 5908 1648 ComApi *RESUMED* Search ClientId = TrustedInstaller FOD
2017.04.27 11:12:59.7579726 5908 1648 ComApi Updates found = 0
2017.04.27 11:12:59.7579734 5908 1648 ComApi * END * Search ClientId = TrustedInstaller FOD
2017.04.27 11:12:59.7589468 5908 5716 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2017.04.27 11:15:07.7082578 484 2980 Misc Got WSUS Client/Server URL: http://192.168.250.195:8530/ClientWebService/client.asmx;;
2017.04.27 11:15:07.7083229 484 2980 ProtocolTalker OK to reuse existing configuration
2017.04.27 11:15:07.7083336 484 2980 ProtocolTalker Existing cookie is valid, just use it
2017.04.27 11:15:07.7083352 484 2980 ProtocolTalker PTInfo: Server requested registration
2017.04.27 11:15:07.8505859 484 2980 Misc Got WSUS Reporting URL: http://192.168.250.195:8530/ReportingWebService/ReportingWebService.asm ...;
2017.04.27 11:15:07.8506305 484 2980 WebServices Auto proxy settings for this web service call.
2017.04.27 11:20:59.4402220 484 504 Agent Earliest future timer found:
2017.04.27 11:20:59.4402421 484 504 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2017-04-27 10:21:12, not idle-only, not network-only
2017.04.27 11:20:59.4530895 484 504 Misc WUTaskManager couldn't register scheduled start task, hr=800706b5
2017.04.27 11:20:59.4532004 484 504 Handler CUHCbsHandler::CancelDownloadRequest called
2017.04.27 11:20:59.5222653 484 504 Shared * END * Service exit Exit code = 0x240001
2017.04.27 11:21:23.0008228 524 3192 Agent WU client version 10.0.14393.1066
2017.04.27 11:21:23.0010920 524 3192 Agent SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2017.04.27 11:21:23.0011536 524 3192 Agent Base directory: C:\Windows\SoftwareDistribution
2017.04.27 11:21:23.0016167 524 3192 Agent Datastore directory: C:\Windows\SoftwareDistribution\DataStore\DataStore.edb
2017.04.27 11:21:23.0257951 524 3192 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2017.04.27 11:21:23.0258196 524 3192 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2017.04.27 11:21:23.0264828 524 3192 Shared Network state: Connected
2017.04.27 11:21:23.0321049 524 3192 Misc LoadHistoryEventFromRegistry completed, hr = 8024000C
2017.04.27 11:21:23.0327156 524 3192 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2017.04.27 11:21:23.0327219 524 3192 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2017.04.27 11:21:23.0327262 524 3192 Shared Power status changed
2017.04.27 11:21:23.0359482 524 3192 Agent Initializing global settings cache
2017.04.27 11:21:23.0359486 524 3192 Agent WSUS server: http://192.168.250.195:8530
2017.04.27 11:21:23.0359490 524 3192 Agent WSUS status server: http://192.168.250.195:8530
2017.04.27 11:21:23.0359490 524 3192 Agent Alternate Download Server: NULL
2017.04.27 11:21:23.0359494 524 3192 Agent Fill Empty Content Urls: No
2017.04.27 11:21:23.0359498 524 3192 Agent Target group: (Unassigned Computers)
2017.04.27 11:21:23.0359498 524 3192 Agent Windows Update access disabled: No
2017.04.27 11:21:23.0371866 524 3192 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2017-04-27 10:21:12, not idle-only, not network-only
2017.04.27 11:21:23.0437774 524 3192 Agent Initializing Windows Update Agent
2017.04.27 11:21:23.0440798 524 3192 DownloadManager Download manager restoring 0 downloads
2017.04.27 11:21:23.0444394 524 3192 Agent CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
2017.04.27 11:21:24.3113087 524 3236 DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
2017.04.27 11:21:24.3480763 524 3236 DownloadManager PurgeExpiredUpdates::Found 0 non expired updates.
2017.04.27 11:21:24.3560220 524 3236 DownloadManager PurgeExpiredUpdates::Found 0 expired updates.
2017.04.27 11:21:24.3568273 524 3236 Shared Effective power state: AC
2017.04.27 11:21:24.3568277 524 3236 DownloadManager Power state change detected. Source now: AC
2017.04.27 11:21:25.0949513 524 1792 ComApi * START * Init Search ClientId = Device Driver Retrieval Client
2017.04.27 11:21:25.0951661 524 1792 ComApi * START * Search ClientId = Device Driver Retrieval Client
2017.04.27 11:21:25.1821459 524 1792 Agent * START * Queueing Finding updates [CallerId = Device Driver Retrieval Client Id = 1]
2017.04.27 11:21:25.1823986 524 1792 Agent Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is not in sequential scan list
2017.04.27 11:21:25.1826883 524 1792 Agent Added service 9482F4B4-E343-43B6-B170-9A65BC822C77 to sequential scan list
2017.04.27 11:21:25.1827262 524 1792 ComApi Search ClientId = Device Driver Retrieval Client
2017.04.27 11:21:25.1829417 524 3516 Agent Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is in sequential scan list
2017.04.27 11:21:25.1862616 524 3520 Agent * END * Queueing Finding updates [CallerId = Device Driver Retrieval Client Id = 1]
2017.04.27 11:21:25.1892223 524 3520 Agent * START * Finding updates CallerId = Device Driver Retrieval Client Id = 1
2017.04.27 11:21:25.1892227 524 3520 Agent Online = Yes; AllowCachedResults = No; Ignore download priority = No
2017.04.27 11:21:25.1892231 524 3520 Agent Criteria = IsInstalled=0 and Type='Driver'""
2017.04.27 11:21:25.1892255 524 3520 Agent ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2017.04.27 11:21:25.1892259 524 3520 Agent Search Scope = {Machine}
2017.04.27 11:21:25.1892275 524 3520 Agent Caller SID for Applicability: S-1-5-18
2017.04.27 11:21:25.1892278 524 3520 Agent RegisterService is set
2017.04.27 11:21:25.1922430 524 3520 Misc EP: error: 0x8024500C : - failed to get SLS data
2017.04.27 11:21:25.1922505 524 3520 Misc Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL, error = 0x8024500C
2017.04.27 11:21:25.1922584 524 3520 ProtocolTalker PTError: 0x8024500c
2017.04.27 11:21:25.1922683 524 3520 ProtocolTalker Initialization failed for Protocol Talker Context 0x8024500c
2017.04.27 11:21:25.2086890 524 3520 Agent Exit code = 0x8024500C
2017.04.27 11:21:25.2086897 524 3520 Agent * END * Finding updates CallerId = Device Driver Retrieval Client Id = 1
2017.04.27 11:21:25.2108048 524 2712 ComApi *RESUMED* Search ClientId = Device Driver Retrieval Client
2017.04.27 11:21:25.2112091 524 2712 ComApi Updates found = 0
2017.04.27 11:21:25.2112095 524 2712 ComApi Exit code = 0x00000000, Result code = 0x8024500C
2017.04.27 11:21:25.2112099 524 2712 ComApi * END * Search ClientId = Device Driver Retrieval Client
2017.04.27 11:21:25.2114617 524 1792 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2017.04.27 11:21:48.1332427 524 1776 ComApi * START * Init Search ClientId = Device Driver Retrieval Client
2017.04.27 11:21:48.1332451 524 1776 ComApi * START * Search ClientId = Device Driver Retrieval Client
2017.04.27 11:21:48.1429205 524 1776 Agent * START * Queueing Finding updates [CallerId = Device Driver Retrieval Client Id = 2]
2017.04.27 11:21:48.1429249 524 1776 Agent Removing service 9482F4B4-E343-43B6-B170-9A65BC822C77 from sequential scan list
2017.04.27 11:21:48.1429273 524 1776 Agent Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is not in sequential scan list
2017.04.27 11:21:48.1429304 524 1776 Agent Added service 9482F4B4-E343-43B6-B170-9A65BC822C77 to sequential scan list
2017.04.27 11:21:48.1429462 524 1776 ComApi Search ClientId = Device Driver Retrieval Client
2017.04.27 11:21:48.1430090 524 3516 Agent Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is in sequential scan list
2017.04.27 11:21:48.1463151 524 4408 Agent * END * Queueing Finding updates [CallerId = Device Driver Retrieval Client Id = 2]
2017.04.27 11:21:48.1498185 524 4408 Agent * START * Finding updates CallerId = Device Driver Retrieval Client Id = 2
2017.04.27 11:21:48.1498193 524 4408 Agent Online = Yes; AllowCachedResults = No; Ignore download priority = No
2017.04.27 11:21:48.1498197 524 4408 Agent Criteria = IsInstalled=0 and Type='Driver'""
2017.04.27 11:21:48.1498229 524 4408 Agent ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2017.04.27 11:21:48.1498233 524 4408 Agent Search Scope = {Machine}
2017.04.27 11:21:48.1498260 524 4408 Agent Caller SID for Applicability: S-1-5-18
2017.04.27 11:21:48.1498264 524 4408 Agent RegisterService is set
2017.04.27 11:21:48.1522621 524 4408 Misc EP: error: 0x8024500C : - failed to get SLS data
2017.04.27 11:21:48.1522656 524 4408 Misc Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL, error = 0x8024500C
2017.04.27 11:21:48.1522664 524 4408 ProtocolTalker PTError: 0x8024500c
2017.04.27 11:21:48.1522688 524 4408 ProtocolTalker Initialization failed for Protocol Talker Context 0x8024500c
2017.04.27 11:21:48.1688217 524 4408 Agent Exit code = 0x8024500C
2017.04.27 11:21:48.1688229 524 4408 Agent * END * Finding updates CallerId = Device Driver Retrieval Client Id = 2
2017.04.27 11:21:48.1734036 524 2680 ComApi *RESUMED* Search ClientId = Device Driver Retrieval Client
2017.04.27 11:21:48.1739417 524 2680 ComApi Updates found = 0
2017.04.27 11:21:48.1739421 524 2680 ComApi Exit code = 0x00000000, Result code = 0x8024500C
2017.04.27 11:21:48.1739429 524 2680 ComApi * END * Search ClientId = Device Driver Retrieval Client
2017.04.27 11:21:48.1743321 524 1776 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C

(Video) Windows Update funktioniert nicht? Problem gelöst mit WSUS Offline Update!

Thema steht ebenfalls im Technet Forum

Content-Key: 336278

Url: https://administrator.de/contentid/336278

(Video) How to Rebuild or Relocate a WSUS Server that is a ConfigMgr Software Update Point (SUP)

Ausgedruckt am: 11.06.2023 um 05:06 Uhr

(Video) How To Clean Up WSUS

FAQs

What is 0x80244007 error when Windows tries to scan for updates on a WSUS server? ›

This issue occurs when the number of updates to be synchronized exceeds the maximum number of installed prerequisites that a WSUS client can pass to SyncUpdates .

Read More ›
How to install kb44744 security update? ›

To install KB4474419 manually:
  1. Go to Microsoft Update Catalog.
  2. Select your computer's version of the OS and click Download button.
  3. Download the update to your computer by clicking the link in the opened window.
  4. Install the update.

View Details ›
Why is WSUS server not communicating with clients? ›

If the WSUS server is unreachable from the client, the most likely causes include: There's a name resolution issue on the client. There's a network-related issue, such as a proxy configuration issue.

Discover More ›
Do not allow update deferral policies to cause scans against Windows updates? ›

The policy Do not allow update deferral policies to cause scans against Windows Update, also known as Dual Scan, is no longer supported on Windows 11 and on Windows 10 it is replaced by the new Windows scan source policy and is not recommended for use.

Continue Reading ›
How do I fix Windows Update error 0x80244007? ›

On This Page :
  1. About Error 0x80244007.
  2. Fix 1: Run Windows Update Troubleshooter.
  3. Fix 2: Delete Junk Files with Disk Cleanup.
  4. Fix 3: Reset Windows Update Components.
  5. Fix 4: Run DISM and SFC Scan.
  6. Fix 5: Uninstall Third-party Antivirus.
  7. Fix 6: Preform a Clean Install.
  8. Bottom Line.
May 31, 2023

Learn More ›
How do I fix Windows Update error 0x80244019? ›

In order to solve the Windows update error 0x80244019, you can temporarily disable the third-party antivirus software. And reboot your computer to check whether the Windows update error 80244019 is solved.

Know More ›
How to Download KB4474419 KB4490628 update for Windows 7? ›

How to download Windows 7 KB4474419, KB4490628, and KB4484071?
  1. Open Control Panel.
  2. Select Windows Update.
  3. Now click the Check for updates button.
  4. Windows will look for available updates and download them automatically.
Nov 5, 2022

Discover More Details ›
What is KB4490628? ›

9.1 MB. 2019-03 Servicing Stack Update for Windows Embedded Standard 7 for x64-based Systems (KB4490628) Windows Embedded Standard 7.

Explore More ›
What is update KB4474419 SHA 2 code signing support? ›

Microsoft rolled out a security patch (KB4474419 - SHA-2 code signing support update ) for Windows 7 to support signed binaries with SHA 2 certificates. Because software publishing certificates was deprecated on 15th April 2021, Norton will switch code signing to SHA 2 certificates.

Learn More ›
What is the default port for WSUS? ›

The client computer must have outbound access to two ports on the WSUS server. By default, these are ports 8530 and 8531.

Read On ›

How can I check if WSUS is working? ›

To verify the server version, follow these steps:
  1. Open the WSUS console.
  2. Click the server name.
  3. Locate the version number under Overview > Connection > Server Version.
  4. Check whether the version is 3.2. 7600.283 or a later version.
Oct 28, 2022

Continue Reading ›
How do I troubleshoot Windows Update client? ›

If you get an error code while downloading and installing Windows updates, the Update Troubleshooter can help resolve the problem. Select Start > Settings > Update & Security > Troubleshoot > Additional troubleshooters.

View Details ›
What is the difference between WUfB and WSUS? ›

The first difference between WSUS and WUfB is the client scanning process. In Windows Update for Business (aka WUfB) deployment service scenario, the clients scan against Windows Update in the cloud. However, in the WSUS scenario, all the clients scan against the updates available in WSUS (CAB file).

Tell Me More ›
What is the WSUS source for Windows Update? ›

The update source is the location from which your WSUS server gets its updates and update metadata. You can specify that the update source should be either Microsoft Update or another WSUS server (the WSUS server that acts as the update source is the upstream server, and your server is the downstream server).

See Details ›
What is the deferral policy for Windows Update? ›

You can defer feature updates for up to 365 days and defer quality updates for up to 30 days. Deferring simply means that you won't receive the update until it has been released for at least the number of deferral days you specified (offer date = release date + deferral date).

See More ›
How do I fix error code 0x80244017? ›

The RSAT error code 0x80244017 can be fixed by temporarily disabling the WSUS on the client machine and manually restarting Windows Update service. What is this? If you are encountering error code 0x80244022, error code 0x8024402C while installing RSAT, the same fix described in this post should work.

Show Me More ›
What is error 0x80070003 Windows updates? ›

The Windows Update service and other relevant services required by the system to install the pending updates are disabled or have become corrupt. In this case, you can simply restart the services to resolve the issue.

Read On ›
What is download error 0x80248007? ›

The download error 0x80248007 is a Windows Update error that occurs during the download phase of the update. It generally happens because of the following causes: Missing Files. Bug with the Update.

Show Me More ›
What is Windows 10 feature update error 0x800704c7? ›

The error 0x800704c7 occurs when downloading the Windows updates, is caused due to missing or corrupted files with the update. The reason could be you got this error might be third-party applications, particularly antivirus programs that often block programs they deem as threats from connecting to the Internet.

Read On ›
How do I manually install KB3033929? ›

We suggest that you follow the steps below.
  1. Running the following FIX-it (for resolving WUS issues) LINK: http://support.microsoft.com/en-us/kb/971058.
  2. Then change windows update to "manual" update mode (as a posed to install updates automatically)
  3. Scan for updates.
  4. Uncheck and then "hide" KB KB3033929.
Oct 19, 2016

See Details ›

How do I manually update Windows 7 64 bit? ›

Windows 7
  1. Select Start > Control Panel > System and Security > Windows Update.
  2. In the Windows Update window, select either important updates are available or optional updates are available.

Get More Info ›
How to change Windows 7 64 bit to 32 bit without reinstall? ›

If the program is not compatible, then try to install and run the program in compatibility mode. 1) Right click on the Program 2) Click on Properties3) Click on Compatibility tab4) Select Run this program in compatibility mode and select Windows Vista or another operating system the program was running successfully.

View Details ›
How do I run Windows Update KB5008215? ›

KB5008215 is a mandatory cumulative update containing security updates, performance improvements, and bug fixes for Windows 11 21H2. You can install this update by going to Start > Settings > Windows Update and clicking on 'Check for Updates. '

Learn More ›
What is KB5004476 Windows Update? ›

TitleProductsClassification
2021-06 Cumulative Update for Windows Server, version 20H2 for ARM64-based Systems (KB5004476)Windows Server, version 1903 and laterUpdates
2021-06 Cumulative Update for Windows Server, version 2004 for ARM64-based Systems (KB5004476)Windows Server, version 1903 and laterUpdates
11 more rows

Get More Info ›
How to fix Windows Update error 0x80070663 in Windows 10? ›

Step 1: Press the Win + I keys at the same time to open the Settings. Choose Update & Security. Step 2: Go to the Troubleshoot tab, click Windows Update, and then click Run the troubleshooter. Step 3: Then you just need to wait for the process to complete and follow the instructions to fix the error.

Continue Reading ›
How do I fix error KB3033929? ›

Turn on automatic Windows updates:
  1. Select the Start button . ...
  2. In the left pane, select Change settings, and then under Important updates, select Install updates automatically (recommended).
  3. Under Recommended updates, turn on Give me recommended updates the same way I receive important updates, and then select OK.

See More ›
What is KB3033929 error? ›

Windows 7 drivers installation failed - make sure hotfix KB3033929 is installed. This happens because the Audient drivers require the latest Windows 7 updates, including the convenience rollup update for Windows 7 SP1, which does not get installed through the automatic Windows Update but requires a manual installation.

Continue Reading ›
How to install security update KB3033929? ›

To start the download, click the Download button and then do one of the following, or select another language from Change Language and then click Change.
  1. Click Run to start the installation immediately.
  2. Click Save to copy the download to your computer for installation at a later time.
Mar 9, 2015

Explore More ›
Does WSUS use port 445? ›

By default, WSUS is configured to use HTTP (non-SSL) over port 8530, and HTTPS (SSL) over port 8531.

View Details ›
Does WSUS use port 80? ›

By default, WSUS will use port 8530 for HTTP and 8531 for HTTPS are used.

Discover More Details ›

How do I know if port 8530 is open? ›

To check port connectivity from the client, run the following command:telnet SUPSERVER.CONTOSO.COM <PortNumber>For example:telnet SUPSERVER.CONTOSO.COM 8530If the port is not accessible, telnet will return an error that resembles the following, suggesting that firewall rules mustbe configured to allow communication for ...

Keep Reading ›
How do I force a client to update from WSUS? ›

Run gpupdate /force command on the Windows client/server that have a registration issue in WSUS. Run wuauclt /detectnow command on the Windows client/server that have a registration issue in WSUS. You can use the Event Viewer to review the re-registration.

Tell Me More ›
How do I manually check for WSUS updates? ›

In the WSUS administration console, expand Updates, and then select All Updates. In the center pane next to Approval, select the desired approval status, and next to Status select the desired installation status. Select Refresh.

Discover More ›
What is the current version of WSUS? ›

Microsoft has released an update for Windows Server Update Services (WSUS) 3.0 Service Pack 2 (SP2).

Explore More ›
How do I manually reset Windows Update Agent? ›

Reset Windows Update components manually
  1. Open a Windows command prompt. ...
  2. Stop the BITS service, the Windows Update service and the Cryptographic service. ...
  3. Delete the qmgr*.dat files.
Apr 28, 2023

Keep Reading ›
Why Windows Update is not working? ›

The system may be unable to install the updates under the software distribution folder due to corrupted files. These temporary update files are restored in the folder that is causing the error. Corrupt system files - Another prominent reason is corrupted system files, as each file is crucial to updating Windows.

View More ›
How do I know if Windows Update is working properly? ›

To double check that your device is up to date, open Settings > Update & Security > Windows Update and see your update status and available updates.

Learn More ›
What has replaced WSUS? ›

Heimdal Security Patch & Asset Management (FREE TRIAL)

This package is delivered from the cloud and accesses each endpoint through an agent program. Key Features: Replaces WSUS and SCCM.

Get More Info Here ›
Does WSUS use SQL or WID? ›

Most Windows Server Update Services (WSUS) installations run on the Windows Internal Database (WID). If you prefer switching to SQL Server, you can do this relatively easily with the sqlcmd and wsusutil command-line tools. It is also possible to revert to WID.

Discover More Details ›
What is the disadvantage of WSUS server? ›

Disadvantages of WSUS include:
  • It is only supported on Windows Server (Expensive licensing required).
  • It requires at least 4GB of memory to run (the more updates, the more RAM needed).
  • It requires hundreds of GB to store downloaded updates.

Get More Info Here ›

Does WSUS need a database? ›

WSUS requires one of the following databases: Windows Internal Database (WID) Any supported Microsoft SQL Server version.

Get More Info ›
Where is the WSUS database located? ›

The WSUS database can use the WID (Windows Internal Database) or a separate SQL Server instance. The database files are called SUSDB. mdf and SUSDB_log. ldf, and when using the built-in WID as a WSUS database, they are located in %WinDir%\WID\Data.

Read The Full Story ›
Does WSUS automatically install updates? ›

Specify intranet Microsoft update service location

Specifies an intranet server to host updates from Microsoft Update. You can then use WSUS to automatically update computers on your network. This setting enables you to specify a WSUS server on your network that will function as an internal update service.

Know More ›
What is the longest users can pause Windows Updates for? ›

Select either Pause updates for 7 days or Advanced options. Then, in the Pause updates section, select the drop-down menu and specify a date for updates to resume.

Explore More ›
Is it OK to interrupt Windows Update? ›

You should never shut down your device to stop the update in progress. This can cause serious damage to Windows and make your computer unusable. When the process finishes, you can either uninstall the update or use Windows 10's rollback option to set your computer back to the previous version.

Find Out More ›
How many times can you postpone a Windows Update? ›

You can pause updates for up to 35 days in both versions of the OS. In Windows 10, click Pause updates for 7 days up to five times for a total of 35 days.

Read On ›
What does Windows Update client failed to detect with error 0x8024402? ›

What does the Windows Update client fail to detect with error 0x8024402c? An incorrect network setting, LAN setting, or update setting that does not comply with the update requirements could cause this issue. By approving the Automatically detected connection settings, it can be stopped.

Show Me More ›
How do I get rid of Windows Update error? ›

If you've recently installed a Windows update and you are having a problem, here's how to uninstall the update to try to resolve the issue: Select the Start button, then select Settings > Update & Security > Windows Update > View update history > Uninstall updates.

Read The Full Story ›
What is Windows server update error 0x8024002e? ›

Resolving Windows Update Error 0x8024002e

Most of the time, this issue is related to corrupted or missing system files in your Windows Update service. In case you still experience problems afterward, then a system restore should do the trick.

View More ›
What is SCCM software update error 0x8024401c? ›

To recap, 0x8024401c is a Windows 10 error code that stops Windows Update and blocks system updates on your computer. However, you can try to fix it by using the Windows Update troubleshooter and Windows Update Diagnostic, as well as by checking Services, Group Policy and system registry settings.

View Details ›

What is Windows Update error 0x80190194? ›

Error codes 0x80072f06 and 0x80190194 are Outlook Send/Receive errors that may occur when a problem is with the Outlook data file (OST) or Exchange Server security certificate.

See Details ›
What is Windows Update failure 0x80242016? ›

Sometimes third-party security software can interfere with the Windows Update process, which may result in error 0x80242016. To rule this out, you can temporarily disable the security software and then try to install the update again. Usually, your antivirus will come with an option to temporarily disable its shields.

Learn More Now ›
What does Windows Update client failed to detect with error 0x80244011? ›

Windows update Error 0x80244011 means "WU_E_PT_SUS_SERVER_NOT_SET WUServer policy value is missing in the registry." So, please you if you have configured WSUS server's setting in registry keys.

Show Me More ›
How do I fix error 0x80248007? ›

Here are some useful methods that can help you to fix the error:
  1. Method 1: Start the Windows Installer Service.
  2. Method 2: Reboot the Windows Update Service.
  3. Method 3: Run the Windows Update Troubleshooter.
  4. Method 4: Remove the Software Distribution Folder.
  5. sfc /scannow.
  6. DISM /Online /Cleanup-Image /ScanHealth.
Mar 20, 2023

Tell Me More ›
Why is there an error when I try to update Windows? ›

The most common cause of Windows Update Error 0x800f080a is an issue with the system file. If certain key system files become outdated or corrupted, it can prevent Windows from properly downloading and installing updates. Another possible cause could be an issue with the Windows Update components themselves.

See Details ›
How do I manually clean up Windows Update? ›

Delete Old Windows Update Files by Disk Cleanup

Open the Start menu, type Control Panel, and press Enter. Go to Administrative Tools. Double-click on Disk Cleanup. Select Clean up system files.

Get More Info Here ›
What is WSUS error 80073712? ›

Windows error code 0x80073712 usually occurs when trying to upgrade Windows or install an update or service pack. This can cause your Windows system to run sluggishly and not perform the required update.

Get More Info ›
What is WSUS error 80243004? ›

The easiest way to solve error code 80243004 is to run Windows Update troubleshooter. It is a Windows built-in feature which can help to solve various problems related to update issues. This might not work in some cases, but it is worth trying as it is quite simple.

Learn More Now ›
What is WSUS error 80244022? ›

When you see error 0x80244022 in Windows update or in the Windows Update log, it relates to a networking error. If you are using WSUS, it could be an indication that the IIS AppPool running your WSUS has stopped and needs to be started: Start IIS Manager. Expand APPLICATION POOLS.

Learn More ›
How do I fix Windows 10 update error 0x80244018? ›

Resolving the Windows Update Error 0x80244018

There are a few things that you can try to fix this error, such as disabling the proxy settings. You can also try removing all security software and the firewall, and running Windows Update Troubleshooter. In case none of these work, try restoring the system.

Learn More Now ›

What is install error 0x80070103 Windows Updates? ›

If you receive Windows Update error 80070103 while installing updates, you might be trying to install a driver that's already installed or a driver that might be less compatible than one you already have installed on your PC.

Know More ›
What is 0X87D00324 Windows Update error? ›

What Causes Error 0X87D00324 During SCCM Deployment? This error code means that the application was installed, but it couldn't be detected by SCCM. Usually, a faulty or incorrect detection method is set in the application you are deploying.

Read On ›

Videos

1. Let's Fix It - Sync Failed WSUS Update Source Not Found on Site SCCM 2012 R2
(BTNHD)
2. HOW TO INSTALL WSUS ON SERVER 2022 - VIDEO 21 INFOSEC PAT
(InfoSec Pat)
3. Upgrade to Windows 10 version 20H2 from WSUS Server
(microsoft lab)
4. Setting up Windows Server Update Services (WSUS) on 2012 R2
(Patrick Hornung)
5. Understanding How the ConfigMgr SUP Interacts with WSUS - Learn with Patch My PC
(Patch My PC)
6. Formation WSUS - Module 2 - Intégration des ordinateurs dans WSUS
(IT-Connect)

References

Top Articles
Latest Posts
Article information

Author: Msgr. Benton Quitzon

Last Updated: 07/08/2023

Views: 6003

Rating: 4.2 / 5 (43 voted)

Reviews: 82% of readers found this page helpful

Author information

Name: Msgr. Benton Quitzon

Birthday: 2001-08-13

Address: 96487 Kris Cliff, Teresiafurt, WI 95201

Phone: +9418513585781

Job: Senior Designer

Hobby: Calligraphy, Rowing, Vacation, Geocaching, Web surfing, Electronics, Electronics

Introduction: My name is Msgr. Benton Quitzon, I am a comfortable, charming, thankful, happy, adventurous, handsome, precious person who loves writing and wants to share my knowledge and understanding with you.