Hi,
I’ve been all over every post I could find about this, and tried anything that applied to my situation. The most common solution (specifying default port) is not applicable because it was specified as 8530 (and still is, in GPO and registry on the client) and was working for several months with no issues.
We have started to deploy images to workstations, however I am using sbs 2008 and WDS which requires sysprep to be run before the image can even be taken.
Here is a sample of the WindowsUpdate.log from a client:
2009-04-29 15:36:42:811 888 180 Agent *************
2009-04-29 15:36:42:811 888 180 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-04-29 15:36:42:811 888 180 Agent *********
2009-04-29 15:36:42:811 888 180 Agent * Online = Yes; Ignore download priority = No
2009-04-29 15:36:42:811 888 180 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»
2009-04-29 15:36:42:811 888 180 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-04-29 15:36:42:812 888 180 Agent * Search Scope = {Machine}
2009-04-29 15:36:42:812 888 180 Setup Checking for agent SelfUpdate
2009-04-29 15:36:42:812 888 180 Setup Client version: Core: 7.2.6001.788 Aux: 7.2.6001.788
2009-04-29 15:36:42:812 888 180 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-04-29 15:36:42:815 888 180 Misc Microsoft signed: Yes
2009-04-29 15:36:42:822 888 180 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-04-29 15:36:42:825 888 180 Misc Microsoft signed: Yes
2009-04-29 15:36:42:827 888 180 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-04-29 15:36:42:830 888 180 Misc Microsoft signed: Yes
2009-04-29 15:36:42:834 888 180 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-04-29 15:36:42:836 888 180 Misc Microsoft signed: Yes
2009-04-29 15:36:42:877 888 180 Setup Determining whether a new setup handler needs to be downloaded
2009-04-29 15:36:42:877 888 180 Setup SelfUpdate handler update required: Current version: 7.2.6001.788, required version: 7.1.6001.65
2009-04-29 15:36:42:877 888 180 Setup Evaluating applicability of setup package «WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.1.6001.65»
2009-04-29 15:36:42:880 888 180 Setup Setup package «WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.1.6001.65» is already installed.
2009-04-29 15:36:42:881 888 180 Setup Evaluating applicability of setup package «WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65»
2009-04-29 15:36:42:905 888 180 Setup Setup package «WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65» is already installed.
2009-04-29 15:36:42:905 888 180 Setup Evaluating applicability of setup package «WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65»
2009-04-29 15:36:42:941 888 180 Setup Setup package «WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65» is already installed.
2009-04-29 15:36:42:941 888 180 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2009-04-29 15:36:45:323 888 180 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2009-04-29 15:36:45:323 888 180 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://sbs.syntapa.local:8530/ClientWebService/client.asmx
2009-04-29 15:36:45:413 888 180 PT WARNING: Cached cookie has expired or new PID is available
2009-04-29 15:36:45:413 888 180 PT Initializing simple targeting cookie, clientId = c76e43ac-29d2-465e-ab61-cfd1d090130d, target group = , DNS name = devwork4.syntapa.local
2009-04-29 15:36:45:413 888 180 PT Server URL = http://sbs.syntapa.local:8530/SimpleAuthWebService/SimpleAuth.asmx
2009-04-29 15:36:45:424 888 180 PT WARNING: GetAuthorizationCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
2009-04-29 15:36:45:424 888 180 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244008
2009-04-29 15:36:45:424 888 180 PT WARNING: PopulateAuthCookies failed: 0x80244008
2009-04-29 15:36:45:424 888 180 PT WARNING: RefreshCookie failed: 0x80244008
2009-04-29 15:36:45:424 888 180 PT WARNING: RefreshPTState failed: 0x80244008
2009-04-29 15:36:45:424 888 180 PT WARNING: Sync of Updates: 0x80244008
2009-04-29 15:36:45:425 888 180 PT WARNING: SyncServerUpdatesInternal failed: 0x80244008
2009-04-29 15:36:45:425 888 180 Agent * WARNING: Failed to synchronize, error = 0x80244008
2009-04-29 15:36:45:475 888 180 Agent * WARNING: Exit code = 0x80244008
2009-04-29 15:36:45:475 888 180 Agent *********
2009-04-29 15:36:45:475 888 180 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-04-29 15:36:45:475 888 180 Agent *************
2009-04-29 15:36:45:475 888 180 Agent WARNING: WU client failed Searching for update with error 0x80244008
2009-04-29 15:36:45:479 888 e74 AU >>## RESUMED ## AU: Search for updates [CallId = {A4F87745-DEB6-45CB-BB05-3887A2F96A10}]
2009-04-29 15:36:45:479 888 e74 AU # WARNING: Search callback failed, result = 0x80244008
2009-04-29 15:36:45:479 888 e74 AU # WARNING: Failed to find updates with error code 80244008
2009-04-29 15:36:45:479 888 e74 AU #########
2009-04-29 15:36:45:479 888 e74 AU ## END ## AU: Search for updates [CallId = {A4F87745-DEB6-45CB-BB05-3887A2F96A10}]
2009-04-29 15:36:45:479 888 e74 AU #############
2009-04-29 15:36:45:479 888 e74 AU AU setting next detection timeout to 2009-04-30 00:36:45
2009-04-29 15:36:50:477 888 180 Report REPORT EVENT: {061A5CAB-395F-46F1-95C6-C7EFB6074BBA} 2009-04-29 15:36:45:475-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244008 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244008.
This phrase «SelfUpdate handler update required: Current version: 7.2.6001.788, required version: 7.1.6001.65» confuses me, however the error seems to come later, but maybe it is related to that?
I have no issue getting updates from microsoft servers (ie not through local WSUS).
The last successful update check was April 14, 2009 @ 3:55PM, updates were last installed April 14, 2009 @ 1:09PM.
I am about to install the most recent updates manually but I don’t see anything in there that might resolve it (other than -maybe- SBS update rollup 2).
In this article I will try to help you solve the Windows Update Error 80244008 which occurs when you try to download Windows Updates. The error code (80244008) itself means SUS_E_PT_SOAPCLIENT_PARSEFAULT which tells you nothing at all if your not a tech geek or a Google Wizard. However the error itself is caused by Internet Settings which are not correct.
In this tutorial I will show you how to correct your internet settings to fix the error 80244008 from occurring when updating. However If this is the first time you are experiencing this problem you could try to wait a few minutes, or try to reboot your device and try it again.
Step 1: Check your connectivity
Make sure your connected to the Internet on the device you wish to update with, this is the main cause of this issue, if your viewing this article on the device with the problems then skip this step and continue to the next step.
Step 2: Enable “Automatically detect settings” option in Internet Properties
To make sure the problems (80244008) are not caused by wrong Internet Settings, we are going to set the Internet Options to Automatically Detect Settings.
1. On your keyboard press the Windows + R key at the same time and type in inetcpl.cpl and click on OK. Or open Start and type inetcpl.cpl, then tap or click on inetcpl.cpl
2. Now click on the Connections tab, and then click on LAN-Settings
3. Then check the box Automatically detect Settings and click on OK.
4. Reboot your device
5. Try to run Windows Update once again
If the problems are no longer occuring then this was the problem, if they still occur then continue with the next step, on the next page
If you’ve been searching for the best way to get your online business up and…
Are you eager to make your reaction GIFs and memes? Reaction GIFs have become a…
If there’s one streaming platform that has taken over the world in a flash, that’s…
In today’s rapidly evolving business environment, it is essential that all businesses understand the importance…
Hello all,
My department just created a new WSUS server (we upgraded from Server 2008 to 2016). I have clients populating into WSUS through GP correctly, but all the machines are showing the warning «This computer has not reported status yet» even after
24 hours. If I attempt to run WU on a client, I receive error 80244008. Looking at the logs (see below) I see a SOAP client error, but I don’t suspect duplicate SUSClientIds as all these machines worked on the previous server.
To be honest, I’ve tried so many different things, I can’t remember off the top of my head what I’ve attempted and what I haven’t, so any help at this point would be appreciated. Thanks!
Edit: Apologies for the weird HTML formatting. I thought it still easier to read than a copy/paste from the log.
————————-
SolarWinds:
WSUS Server Connectivity
clientwebservice/client.asmx: Error:Client found response content type of », but expected ‘text/xml’.
The request failed with an empty response.
simpleauthwebservice/simpleauth.asmx: OK
content:
Error: Forbidden (Incorrect proxy client configuration — use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implementation or access rights on WSUS server)
selfupdate/iuident.cab: OK
iuident.cab: Error: NotFound
(Omitting required port suffix on URL to access WSUS installed to port 8530 or resource is unreachable)
————————-
Windows Update Log (from this morning):
| 2017-05-26 | 09:08:29:712 | 1060 | 7b8 | Agent | *********** Agent: Initializing Windows Update Agent *********** | |||||
| 2017-05-26 | 09:08:29:713 | 1060 | 7b8 | Agent | * Prerequisite roots succeeded. | |||||
| 2017-05-26 | 09:08:29:713 | 1060 | 7b8 | Agent | *********** Agent: Initializing global settings cache *********** | |||||
| 2017-05-26 | 09:08:29:713 | 1060 | 7b8 | Agent | * WSUS server: http://xxxxx.ad.ufl.edu:8530 | |||||
| 2017-05-26 | 09:08:29:713 | 1060 | 7b8 | Agent | * WSUS status server: http://xxxxx.ad.ufl.edu:8530 | |||||
| 2017-05-26 | 09:08:29:713 | 1060 | 7b8 | Agent | * Target group: Student Computers | |||||
| 2017-05-26 | 09:08:29:713 | 1060 | 7b8 | Agent | * Windows Update access disabled: No | |||||
| 2017-05-26 | 09:08:29:713 | 1060 | 7b8 | DnldMgr | Download manager restoring 0 downloads | |||||
| 2017-05-26 | 09:08:29:716 | 1060 | 7b8 | AU | ########### AU: Initializing Automatic Updates ########### | |||||
| 2017-05-26 | 09:08:29:717 | 1060 | 7b8 | AU | # WSUS server: http://xxxxx.ad.ufl.edu:8530 | |||||
| 2017-05-26 | 09:08:29:717 | 1060 | 7b8 | AU | # Detection frequency: 22 | |||||
| 2017-05-26 | 09:08:29:717 | 1060 | 7b8 | AU | # Target group: Student Computers | |||||
| 2017-05-26 | 09:08:29:717 | 1060 | 7b8 | AU | # Approval type: Scheduled (User preference) | |||||
| 2017-05-26 | 09:08:29:717 | 1060 | 7b8 | AU | # Scheduled install day/time: Every day at 3:00 | |||||
| 2017-05-26 | 09:08:29:717 | 1060 | 7b8 | AU | # Auto-install minor updates: Yes (User preference) | |||||
| 2017-05-26 | 09:08:29:717 | 1060 | 7b8 | AU | # Will interact with non-admins (Non-admins are elevated (User preference)) | |||||
| 2017-05-26 | 09:08:29:717 | 1060 | 7b8 | AU | Setting AU scheduled install time to 2017-05-27 07:00:00 | |||||
| 2017-05-26 | 09:08:29:842 | 1060 | 7b8 | Report | *********** Report: Initializing static reporting data *********** | |||||
| 2017-05-26 | 09:08:29:842 | 1060 | 7b8 | Report | * OS Version = 6.1.7601.1.0.65792 | |||||
| 2017-05-26 | 09:08:29:842 | 1060 | 7b8 | Report | * OS Product Type = 0x00000004 | |||||
| 2017-05-26 | 09:08:29:849 | 1060 | 7b8 | Report | * Computer Brand = Dell Inc. | |||||
| 2017-05-26 | 09:08:29:849 | 1060 | 7b8 | Report | * Computer Model = OptiPlex 990 | |||||
| 2017-05-26 | 09:08:29:851 | 1060 | 7b8 | Report | * Bios Revision = A17 | |||||
| 2017-05-26 | 09:08:29:851 | 1060 | 7b8 | Report | * Bios Name = Default System BIOS | |||||
| 2017-05-26 | 09:08:29:851 | 1060 | 7b8 | Report | * Bios Release Date = 2013-03-14T00:00:00 | |||||
| 2017-05-26 | 09:08:29:851 | 1060 | 7b8 | Report | * Locale ID = 1033 | |||||
| 2017-05-26 | 09:08:30:319 | 1060 | 7b8 | AU | Successfully wrote event for AU health state:0 | |||||
| 2017-05-26 | 09:08:30:319 | 1060 | 7b8 | AU | Initializing featured updates | |||||
| 2017-05-26 | 09:08:30:319 | 1060 | 7b8 | AU | Found 0 cached featured updates | |||||
| 2017-05-26 | 09:08:30:319 | 1060 | 7b8 | AU | Successfully wrote event for AU health state:0 | |||||
| 2017-05-26 | 09:08:30:320 | 1060 | 7b8 | AU | Successfully wrote event for AU health state:0 | |||||
| 2017-05-26 | 09:08:30:320 | 1060 | 7b8 | AU | AU finished delayed initialization | |||||
| 2017-05-26 | 09:08:30:336 | 1060 | 10c4 | PT | WARNING: GetConfig failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200 | |||||
| 2017-05-26 | 09:08:30:336 | 1060 | 10c4 | PT | WARNING: PTError: 0x80244008 | |||||
| 2017-05-26 | 09:08:30:336 | 1060 | 10c4 | PT | WARNING: GetConfig_WithRecovery failed: 0x80244008 | |||||
| 2017-05-26 | 09:08:30:336 | 1060 | 10c4 | PT | WARNING: RefreshConfig failed: 0x80244008 | |||||
| 2017-05-26 | 09:08:30:336 | 1060 | 10c4 | PT | WARNING: RefreshPTState failed: 0x80244008 | |||||
| 2017-05-26 | 09:08:30:336 | 1060 | 10c4 | PT | WARNING: PTError: 0x80244008 | |||||
| 2017-05-26 | 09:08:30:336 | 1060 | 10c4 | Report | WARNING: Reporter failed to upload events with hr = 80244008. | |||||
| 2017-05-26 | 09:08:30:346 | 1060 | 10c4 | PT | WARNING: GetConfig failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200 | |||||
| 2017-05-26 | 09:08:30:346 | 1060 | 10c4 | PT | WARNING: PTError: 0x80244008 | |||||
| 2017-05-26 | 09:08:30:346 | 1060 | 10c4 | PT | WARNING: GetConfig_WithRecovery failed: 0x80244008 | |||||
| 2017-05-26 | 09:08:30:346 | 1060 | 10c4 | PT | WARNING: RefreshConfig failed: 0x80244008 | |||||
| 2017-05-26 | 09:08:30:346 | 1060 | 10c4 | PT | WARNING: RefreshPTState failed: 0x80244008 | |||||
| 2017-05-26 | 09:08:30:346 | 1060 | 10c4 | PT | WARNING: PTError: 0x80244008 | |||||
| 2017-05-26 | 09:08:30:346 | 1060 | 10c4 | Report | WARNING: Reporter failed to upload events with hr = 80244008. | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 11a8 | AU | Triggering AU detection through DetectNow API | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 11a8 | AU | Triggering Online detection (interactive) | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 7b8 | AU | ############# | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 7b8 | AU | ## START ## AU: Search for updates | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 7b8 | AU | ######### | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 7b8 | AU | <<## SUBMITTED ## AU: Search for updates [CallId = {FFA58614-C3A7-4065-941E-C060EC351058}] | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 10c4 | Agent | ************* | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 10c4 | Agent | ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 10c4 | Agent | ********* | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 10c4 | Agent | * Online = Yes; Ignore download priority = No | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 10c4 | 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» |
|||||
| 2017-05-26 | 09:09:06:847 | 1060 | 10c4 | Agent | * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 10c4 | Agent | * Search Scope = {Machine} | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 10c4 | Setup | Checking for agent SelfUpdate | |||||
| 2017-05-26 | 09:09:06:847 | 1060 | 10c4 | Setup | Client version: Core: 7.6.7601.23775 Aux: 7.6.7601.23775 | |||||
| 2017-05-26 | 09:09:06:848 | 1060 | 10c4 | Misc | Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080: | |||||
| 2017-05-26 | 09:09:06:880 | 1060 | 10c4 | Misc | Microsoft signed: NA | |||||
| 2017-05-26 | 09:09:06:880 | 1060 | 10c4 | Misc | Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP8BB1.tmp with dwProvFlags 0x00000080: | |||||
| 2017-05-26 | 09:09:06:896 | 1060 | 10c4 | Misc | Microsoft signed: NA | |||||
| 2017-05-26 | 09:09:06:912 | 1060 | 10c4 | Misc | Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080: | |||||
| 2017-05-26 | 09:09:06:912 | 1060 | 10c4 | Misc | Microsoft signed: NA | |||||
| 2017-05-26 | 09:09:06:927 | 1060 | 10c4 | Misc | Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080: | |||||
| 2017-05-26 | 09:09:06:943 | 1060 | 10c4 | Misc | Microsoft signed: NA | |||||
| 2017-05-26 | 09:09:06:974 | 1060 | 10c4 | Setup | Determining whether a new setup handler needs to be downloaded | |||||
| 2017-05-26 | 09:09:06:974 | 1060 | 10c4 | Setup | SelfUpdate handler is not found. It will be downloaded | |||||
| 2017-05-26 | 09:09:06:974 | 1060 | 10c4 | Setup | Evaluating applicability of setup package «WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320» | |||||
| 2017-05-26 | 09:09:06:974 | 1060 | 10c4 | Setup | Setup package «WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320» is already installed. | |||||
| 2017-05-26 | 09:09:06:974 | 1060 | 10c4 | Setup | Evaluating applicability of setup package «WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320» | |||||
| 2017-05-26 | 09:09:07:005 | 1060 | 10c4 | Setup | Setup package «WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320» is already installed. | |||||
| 2017-05-26 | 09:09:07:005 | 1060 | 10c4 | Setup | Evaluating applicability of setup package «WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320» | |||||
| 2017-05-26 | 09:09:07:036 | 1060 | 10c4 | Setup | Setup package «WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320» is already installed. | |||||
| 2017-05-26 | 09:09:07:036 | 1060 | 10c4 | Setup | SelfUpdate check completed. SelfUpdate is NOT required. | |||||
| 2017-05-26 | 09:09:07:068 | 1060 | 10c4 | PT | +++++++++++ PT: Synchronizing server updates +++++++++++ | |||||
| 2017-05-26 | 09:09:07:068 | 1060 | 10c4 | PT | + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://xxxxx.ad.ufl.edu:8530/ClientWebService/client.asmx | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | PT | WARNING: GetConfig failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | PT | WARNING: PTError: 0x80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | PT | WARNING: GetConfig_WithRecovery failed: 0x80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | PT | WARNING: RefreshConfig failed: 0x80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | PT | WARNING: RefreshPTState failed: 0x80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | PT | WARNING: Sync of Updates: 0x80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | PT | WARNING: SyncServerUpdatesInternal failed: 0x80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | Agent | * WARNING: Failed to synchronize, error = 0x80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | Agent | * WARNING: Exit code = 0x80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | Agent | ********* | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | Agent | ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | Agent | ************* | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 10c4 | Agent | WARNING: WU client failed Searching for update with error 0x80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | >>## RESUMED ## AU: Search for updates [CallId = {FFA58614-C3A7-4065-941E-C060EC351058}] | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | # WARNING: Search callback failed, result = 0x80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | # WARNING: Failed to find updates with error code 80244008 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | ######### | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | ## END ## AU: Search for updates [CallId = {FFA58614-C3A7-4065-941E-C060EC351058}] | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | ############# | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | Successfully wrote event for AU health state:0 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | AU setting next detection timeout to 2017-05-26 18:09:07 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | Setting AU scheduled install time to 2017-05-27 07:00:00 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | Successfully wrote event for AU health state:0 | |||||
| 2017-05-26 | 09:09:07:083 | 1060 | 12ac | AU | Successfully wrote event for AU health state:0 | |||||
| 2017-05-26 | 09:09:12:084 | 1060 | 10c4 | Report | REPORT EVENT: {B908E531-F459-447F-B0E8-5E0EB41854C0} | |||||
| 2017-05-26 09:09:07:083-0400 | 1 | 148 | 101 | {00000000-0000-0000-0000-000000000000} | 0 | 80244008 | AutomaticUpdates | Failure | Software Synchronization | Windows Update Client failed to detect with error 0x80244008. |
| 2017-05-26 | 09:09:12:084 | 1060 | 10c4 | Report | CWERReporter::HandleEvents — WER report upload completed with status 0x8 | |||||
| 2017-05-26 | 09:09:12:084 | 1060 | 10c4 | Report | WER Report sent: 7.6.7601.23775 0x80244008(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0 |
Hi everyone. We just went through our monthly pilot patching cycle last night and out of 17 servers on the list, we encountered errors with five of them. Two (the 80244019 errors) showed patches available to download and install and also checked in with WSUS earlier in the day, prior to scheduled patching. Three showed no patches available, but threw an error message (either 8024401f or 80244008) when I attempted to check for updates. Two months ago (the last time I was on the hook to update servers), I did not see these errors. I do not believe the individual who ran the patches last month saw these either. Nothing I’m seeing in the Windows Update log leads to anything that would seem (to me, at least) to apply.
We have a script that does a number of different things to troubleshoot the issue. Rather than listing them out, I’ve copied the script below. I’ll also upload the WindowsUpdate log files.
Beyond this, I found the WSUS Client Diagnostics Tool and there is a single error message that appears on every failed machine, but my Google Fu must be weak as I’m not seeing anything that makes sense. There is no proxy server are there were not a lot of patches approved (and we’ve approved far more in the past, successfully).
Here is the script we run:
GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002
The system cannot find the file specified
I’ve also checked that bandwidtch if perfectly fine; I can manually copy hundreds of Gb from the WSUS server to the failing servers in a very quick time frame. In addition, other servers in the same subnet with more patches approved are working just fine.
@echo on
gpupdate /force
net stop wuauserv /y
net stop bits /y
rmdir c:\windows\SoftwareDistribution /S /Q
del C:\Windows\WindowsUpdate.log /S /Q
REG DELETE «HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate» /v AccountDomainSid /f
REG DELETE «HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate» /v PingID /f
Reg Delete «HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate» /v SusClientId /f
Reg Delete «HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate» /v SusClientValidation /f
REG DELETE «HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update» /v LastWaitTimeout /f
REG DELETE «HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update» /v DetectionstartTime /f
Reg Delete «HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update» /v NextDetectionTime /f
echo re-registering Windows Update components..
regsvr32.exe c:\windows\system32\wuapi.dll /s
regsvr32.exe c:\windows\system32\wups.dll /s
regsvr32.exe c:\windows\system32\wuaueng.dll /s
regsvr32.exe c:\windows\system32\wucltui.dll /s
regsvr32.exe c:\windows\system32\msxml3.dll /s
regsvr32.exe c:\windows\system32\wuaueng1.dll /s
regsvr32.exe c:\windows\system32\wups2.dll /s
regsvr32.exe c:\windows\system32\wuweb.dll /s
net start wuauserv /y
net start bits /y
echo Initiating Windows Updates detection cycle…
wuauclt.exe /resetauthorization
wuauclt.exe /detectnow
wuauclt.exe /reportnow
pause
All of sudden, all Windows desktops at work started having this issue when trying to connect to WSUS server for Windows updates. On Windows 7, it states that
Windows could not search for new updates
Errors found: Code 80244008
On Windows 10, the error message is slightly different.
There were some problems installing updates, but we’ll try again later…(0x8024401f)
What’s the cause?
I believe it’s this Windows update (KB4025336 – 2017-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems) that caused the issue. Basically, if your WSUS service is running on the default port 8530 you will likely have this issue on your network.
Solutions
Obviously, removing the troublesome KB4025336 should be able to rollback the WSUS server to the last working state.
But if that’s not the option, you can also run the following commands to reset WSUS’ IIS port.
wsusutil.exe usecustomwebsite true wsusutil.exe usecustomwebsite false iisreset /restart
Note that the command line wsusutil.exe is located in the following folder:
C:\Program Files\Update Services\Tools
Once IIS server restarted, try Windows Update again on a workstation. If it fails again with a different error message like below,
Windows could not search for new updates
Errors found: Code 80072EE2
Check the Group Policy setting and specify the port number in the following group setting.
Specify intranet Microsoft update service location
Now everything should be back to normal now.
