Asked by:
PC can't download window update from WSUS Server

Question
-
Hi everyone,
Recently, all of our company window 7 PC are having issue downloading window update from wsus server.
When i check on one of the pc windowupdate.log, it has below error message:-
Report 80244019 - Automaticupdatewuapp failure content download error: download failed.
Any advise as to what i should troubleshoot? is it wsus server have problem? where should i navigate the problem?
Please help.
Thanks!
Tuesday, December 24, 2019 11:28 AM
All replies
-
Hi, Can you try to reset Windows Update components in the client side:https://docs.microsoft.com/en-us/windows/deployment/update/windows-update-resources
"Vote or mark as answer if you think useful" "Marquer comme réponse les réponses qui ont résolu votre problème"
Tuesday, December 24, 2019 1:00 PM -
Hi,
Try do this on one workstation and you can see if after that downloads and update start working it's mean workstation problem
net stop bits net stop wuauserv net stop appidsvc net stop cryptsvc Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\*.*" rmdir %systemroot%\SoftwareDistribution /S /Q rmdir %systemroot%\system32\catroot2 /S /Q sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU) sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU) cd /d %windir%\system32 regsvr32.exe /s atl.dll regsvr32.exe /s urlmon.dll regsvr32.exe /s mshtml.dll regsvr32.exe /s shdocvw.dll regsvr32.exe /s browseui.dll regsvr32.exe /s jscript.dll regsvr32.exe /s vbscript.dll regsvr32.exe /s scrrun.dll regsvr32.exe /s msxml.dll regsvr32.exe /s msxml3.dll regsvr32.exe /s msxml6.dll regsvr32.exe /s actxprxy.dll regsvr32.exe /s softpub.dll regsvr32.exe /s wintrust.dll regsvr32.exe /s dssenh.dll regsvr32.exe /s rsaenh.dll regsvr32.exe /s gpkcsp.dll regsvr32.exe /s sccbase.dll regsvr32.exe /s slbcsp.dll regsvr32.exe /s cryptdlg.dll regsvr32.exe /s oleaut32.dll regsvr32.exe /s ole32.dll regsvr32.exe /s shell32.dll regsvr32.exe /s initpki.dll regsvr32.exe /s wuapi.dll regsvr32.exe /s wuaueng.dll regsvr32.exe /s wuaueng1.dll regsvr32.exe /s wucltui.dll regsvr32.exe /s wups.dll regsvr32.exe /s wups2.dll regsvr32.exe /s wuweb.dll regsvr32.exe /s qmgr.dll regsvr32.exe /s qmgrprxy.dll regsvr32.exe /s wucltux.dll regsvr32.exe /s muweb.dll regsvr32.exe /s wuwebv.dll netsh winsock reset netsh winsock reset proxy net start bits net start wuauserv net start appidsvc net start cryptsvc
thank youTuesday, December 24, 2019 8:23 PM -
Hi Min777,
If your clients are located in a domain environment, the clients will receive the WSUS configuration information by receiving Group Policy, then check the configuration of the following Group Policy:
- Windows Components > Windows Update > [Specify intranet Microsoft update service location]
Please check if the intranet server you entered is the FDQN and port number of the WSUS server.
For example, "http://wsusserver.mydomain.local:8530".
If your clients are in a workgroup environment, the clients will obtain the WSUS configuration information through the registry, then check the configuration of the following key values:
- [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
Please check WUServer & WUStatusServer fill in the FQDN and port number of the WSUS server, or the IP and port number.
For example, "http://10.1.1.51:8530".
Reply back with the results would be happy to help.
Regards,
Yic
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Edited by Yic LvMicrosoft contingent staff Wednesday, December 25, 2019 2:04 AM Paragraph format.
Wednesday, December 25, 2019 2:03 AM - Windows Components > Windows Update > [Specify intranet Microsoft update service location]
-
Followup the given steps in this guidance,
https://gallery.technet.microsoft.com/Troubleshooting-WSUS-d63da113?redir=0
Wednesday, December 25, 2019 10:47 AM -
Hi,
Try do this on one workstation and you can see if after that downloads and update start working it's mean workstation problem
net stop bits net stop wuauserv net stop appidsvc net stop cryptsvc Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\*.*" rmdir %systemroot%\SoftwareDistribution /S /Q rmdir %systemroot%\system32\catroot2 /S /Q sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU) sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU) cd /d %windir%\system32 regsvr32.exe /s atl.dll regsvr32.exe /s urlmon.dll regsvr32.exe /s mshtml.dll regsvr32.exe /s shdocvw.dll regsvr32.exe /s browseui.dll regsvr32.exe /s jscript.dll regsvr32.exe /s vbscript.dll regsvr32.exe /s scrrun.dll regsvr32.exe /s msxml.dll regsvr32.exe /s msxml3.dll regsvr32.exe /s msxml6.dll regsvr32.exe /s actxprxy.dll regsvr32.exe /s softpub.dll regsvr32.exe /s wintrust.dll regsvr32.exe /s dssenh.dll regsvr32.exe /s rsaenh.dll regsvr32.exe /s gpkcsp.dll regsvr32.exe /s sccbase.dll regsvr32.exe /s slbcsp.dll regsvr32.exe /s cryptdlg.dll regsvr32.exe /s oleaut32.dll regsvr32.exe /s ole32.dll regsvr32.exe /s shell32.dll regsvr32.exe /s initpki.dll regsvr32.exe /s wuapi.dll regsvr32.exe /s wuaueng.dll regsvr32.exe /s wuaueng1.dll regsvr32.exe /s wucltui.dll regsvr32.exe /s wups.dll regsvr32.exe /s wups2.dll regsvr32.exe /s wuweb.dll regsvr32.exe /s qmgr.dll regsvr32.exe /s qmgrprxy.dll regsvr32.exe /s wucltux.dll regsvr32.exe /s muweb.dll regsvr32.exe /s wuwebv.dll netsh winsock reset netsh winsock reset proxy net start bits net start wuauserv net start appidsvc net start cryptsvc
thank youTried this before, and PC still having the same issue..
Thursday, December 26, 2019 3:03 AM -
Hi Min777,
If your clients are located in a domain environment, the clients will receive the WSUS configuration information by receiving Group Policy, then check the configuration of the following Group Policy:
- Windows Components > Windows Update > [Specify intranet Microsoft update service location]
Please check if the intranet server you entered is the FDQN and port number of the WSUS server.
For example, "http://wsusserver.mydomain.local:8530".
If your clients are in a workgroup environment, the clients will obtain the WSUS configuration information through the registry, then check the configuration of the following key values:
- [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
Please check WUServer & WUStatusServer fill in the FQDN and port number of the WSUS server, or the IP and port number.
For example, "http://10.1.1.51:8530".
Reply back with the results would be happy to help.
Regards,
Yic
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Hi, yes all pc is domain joined, and previously they have been able to download wsus update from wsus server through port 8531 without problem, just recently, only window 7 pc having problem..
from Client PC (With Problem), i'm able to telnet wsus server with port 8531, but can't access through web browser..
any idea?
thanks!
Thursday, December 26, 2019 3:10 AM - Windows Components > Windows Update > [Specify intranet Microsoft update service location]
-
Followup the given steps in this guidance,
https://gallery.technet.microsoft.com/Troubleshooting-WSUS-d63da113?redir=0
Thursday, December 26, 2019 5:58 AM -
from Client PC (With Problem), i'm able to telnet wsus server with port 8531, but can't access through web browser..
Has the certificate used for SSL connection encryption been added to the client's "Trusted Root Certification Authorities" directory?
Regards,
YicPlease remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Friday, December 27, 2019 1:24 AM -
from Client PC (With Problem), i'm able to telnet wsus server with port 8531, but can't access through web browser..
Has the certificate used for SSL connection encryption been added to the client's "Trusted Root Certification Authorities" directory?
Regards,
Yic
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Hi Yic,
Yes, I checked mmc in the PC with problem, there's SSL certificate in the trusted root certification authorities.
Friday, December 27, 2019 7:05 AM -
Hi Min,
Please determine if you have SSL enabled only for the web pages of the following WSUS administration sites:
- ClientWebService
- DssAuthWebService
- ServerSyncWebService
- SimpleAuthWebService
In addition, please do not enable SSL for other web pages and main sites.
Regards,
Reply back with the results would be happy to help.
YicPlease remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Friday, December 27, 2019 8:49 AM -
Hi Yic,
Thanks for your swift respond, did you mean to check the web pages in IIS of the WSUS Server?
If yes, then all web services in WSUS Server IIS, the SSL setting did not require SSL and client certificate is selected ignore.
Thanks!
Friday, December 27, 2019 9:50 AM -
Hi ,
Could you tell me please your version of WSUS?
thank you
Friday, December 27, 2019 2:36 PM -
Hi Min,
Sorry I didn't express clearly.
If you need to enable SSL access to your WSUS site, you need to enable SSL on those pages I mentioned:
- ClientWebService
DssAuthWebService
ServerSyncWebService
SimpleAuthWebService
and:
- ApiRemoting30
The opening method can refer to the following snapshot:
If you have questions about how to enable SSL configuration, you can refer to the steps mentioned in this article: "Enabling SSL on Windows Server Update Services."
* Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Hope the above can help you.
Regards,
YicPlease remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Monday, December 30, 2019 1:38 AM - ClientWebService
-
Hi ,
Could you tell me please your version of WSUS?
thank you
Monday, December 30, 2019 3:49 AM -
Hi Min,
Sorry I didn't express clearly.
If you need to enable SSL access to your WSUS site, you need to enable SSL on those pages I mentioned:
- ClientWebService
DssAuthWebService
ServerSyncWebService
SimpleAuthWebService
and:
- ApiRemoting30
The opening method can refer to the following snapshot:
If you have questions about how to enable SSL configuration, you can refer to the steps mentioned in this article: "Enabling SSL on Windows Server Update Services."
* Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Hope the above can help you.
Regards,
Yic
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Hi Yic,
Not sure if this is the correct direction we heading, because other PC that is window 10 are not having any issue downloading the window update.
Monday, December 30, 2019 3:52 AM - ClientWebService
-
Hi Min,
The 0x80244019 error means a 404 error for HTTP, which happens when some resources cannot be found. If we first rule out issues that are not SSL, consider the following checks:
- On the Win7 client where 80244019 appears, you can find the location of the problem by retrieving 80244019 in WindowsUpdate.log.
- Usually, the context of these locations should include a record of obtaining some update files, but an error occurs because it is not available. Please consider checking that these mentioned files are actually stored in the content folder of the WSUS server.
- You can also try decline these problematic updates in the WSUS console and re-approve.
- There may also be problems caused by other reasons, refer to the explanation from Lawrence in
this thread.
Hope the above can help you.
Regards,
Yic
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Edited by Yic LvMicrosoft contingent staff Monday, December 30, 2019 7:49 AM Paragraph format.
Monday, December 30, 2019 7:49 AM -
Hi Min,
The 0x80244019 error means a 404 error for HTTP, which happens when some resources cannot be found. If we first rule out issues that are not SSL, consider the following checks:
- On the Win7 client where 80244019 appears, you can find the location of the problem by retrieving 80244019 in WindowsUpdate.log.
- Usually, the context of these locations should include a record of obtaining some update files, but an error occurs because it is not available. Please consider checking that these mentioned files are actually stored in the content folder of the WSUS server.
- You can also try decline these problematic updates in the WSUS console and re-approve.
- There may also be problems caused by other reasons, refer to the explanation from Lawrence in
this thread.
Hope the above can help you.
Regards,
Yic
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Hi Yic,
Thanks for the feedback,for item no3, how can i decline the problematic window update?
I selected the window update in wsus console, and when i click on the declide button, below alert appears.
here are the windowupdate.log captured.
2019-12-30 17:54:22:299 804 324c Report REPORT EVENT: {8E1D6878-9084-49A2-926D-335540327F28} 2019-12-30 17:54:03:244+0800 1 161 101 {ECAF8036-92F9-4F9F-8C20-CC4E381E9CDC} 202 80244019 AutomaticUpdatesWuApp Failure Content Download Error: Download failed.
2019-12-30 17:54:22:299 804 2474 AU >>## RESUMED ## AU: Search for updates [CallId = {60B27BA6-FB23-4DE2-A63F-470DE896A211}]
2019-12-30 17:54:22:299 804 2474 AU # 5 updates detected
2019-12-30 17:54:22:299 804 324c Report REPORT EVENT: {84B570D6-A25B-4839-80F3-1D8E44326EC5} 2019-12-30 17:54:03:861+0800 1 161 101 {1B9EA75E-B216-4B3C-AF63-2A03FE2800FF} 200 80244019 AutomaticUpdatesWuApp Failure Content Download Error: Download failed.
2019-12-30 17:54:22:300 804 2474 AU #########
2019-12-30 17:54:22:300 804 2474 AU ## END ## AU: Search for updates [CallId = {60B27BA6-FB23-4DE2-A63F-470DE896A211}]
2019-12-30 17:54:22:300 804 2474 AU #############
2019-12-30 17:54:22:300 804 2474 AU Featured notifications is disabled.
2019-12-30 17:54:22:301 804 2474 AU Successfully wrote event for AU health state:0
2019-12-30 17:54:22:303 804 2474 AU Successfully wrote event for AU health state:0
2019-12-30 17:54:22:305 804 1118 AU Getting featured update notifications. fIncludeDismissed = true
2019-12-30 17:54:22:305 804 1118 AU No featured updates available.
2019-12-30 17:54:22:306 804 324c Report WARNING: CWERReporter finishing event handling with error = 800700a1
2019-12-30 17:54:22:306 804 324c Report REPORT EVENT: {8E1D6878-9084-49A2-926D-335540327F28} 2019-12-30 17:54:03:244+0800 1 161 101 {ECAF8036-92F9-4F9F-8C20-CC4E381E9CDC} 202 80244019 AutomaticUpdatesWuApp Failure Content Download Error: Download failed.
2019-12-30 17:54:22:306 804 324c Report REPORT EVENT: {84B570D6-A25B-4839-80F3-1D8E44326EC5} 2019-12-30 17:54:03:861+0800 1 161 101 {1B9EA75E-B216-4B3C-AF63-2A03FE2800FF} 200 80244019 AutomaticUpdatesWuApp Failure Content Download Error: Download failed.
2019-12-30 17:54:22:312 804 324c Report WARNING: CWERReporter finishing event handling with error = 800700a1
2019-12-30 17:54:22:312 804 324c Report REPORT EVENT: {8E1D6878-9084-49A2-926D-335540327F28} 2019-12-30 17:54:03:244+0800 1 161 101 {ECAF8036-92F9-4F9F-8C20-CC4E381E9CDC} 202 80244019 AutomaticUpdatesWuApp Failure Content Download Error: Download failed.
2019-12-30 17:54:22:312 804 324c Report REPORT EVENT: {84B570D6-A25B-4839-80F3-1D8E44326EC5} 2019-12-30 17:54:03:861+0800 1 161 101 {1B9EA75E-B216-4B3C-AF63-2A03FE2800FF} 200 80244019 AutomaticUpdatesWuApp Failure Content Download Error: Download failed.
2019-12-30 17:54:22:319 804 324c Report WARNING: CWERReporter finishing event handling with error = 800700a1
2019-12-30 17:54:22:329 804 324c Report Uploading 32 events using cached cookie, reporting URL = http://dc04/ReportingWebService/ReportingWebService.asmx
2019-12-30 17:54:22:336 804 324c Report Reporter successfully uploaded 32 events.Kindly advise.
Thanks.!
Monday, December 30, 2019 10:30 AM -
I selected the window update in wsus console, and when i click on the declide button, below alert appears.
Please clicking "Yes" in the window will decline the update.
And than, you can then filter the "Approval" attribute to "Declined" in the update view of the WSUS console, find KB4525233, and re-approve.
Reply back with the results would be happy to help.
Regards,
YicPlease remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Tuesday, December 31, 2019 1:27 AM -
I selected the window update in wsus console, and when i click on the declide button, below alert appears.
Please clicking "Yes" in the window will decline the update.
And than, you can then filter the "Approval" attribute to "Declined" in the update view of the WSUS console, find KB4525233, and re-approve.
Reply back with the results would be happy to help.
Regards,
Yic
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Hi Yic,
Thanks for your feedback, i tried declined the update then reapproved it, afterward in the client pc i tried redownload the window update, but it is still showing same error message.
Hmm,...any idea where i can check if the window update is re-download successfully?
Thanks.
Tuesday, December 31, 2019 10:47 AM -
you can import this update KB4525233 from Microsoft catalog
Click on USUS Updates and from Right side hits Import Updates after that in IE catalog.update.microsoft.com search you update KB4525233 and click Add and Import after that you will know exactly what uploaded successfully
thank you
Tuesday, December 31, 2019 2:46 PM -
Hi Min,
Please consider running "regedit" on the WSUS server and navigating to the following location in the Registry Editor:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup
Check if the address configured by "ContentDir" is canonical, don't lack the necessary colons and slashes.
Then navigate to IIS-WSUS Administration-Content-Advanced Settings. Notice the value of 'Physical Path' and don't lack the necessary colons and slashes.
If these values are inconsistent or abnormal, it may cause the update file to fail to download.
Regards,
Reply back with the results would be happy to help.
YicPlease remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Wednesday, January 1, 2020 2:59 AM - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup
-
Hi Yic,
I checked the mentioned path, it look tallied:-
Regedit of WSUS Server
IIS:-
Thursday, January 2, 2020 5:45 AM -
Hi everyone,
any idea where i can further troubleshoot on this?
I'm able to download the .cab file from client PC through browser that it using port 80.
thanks!
Saturday, January 4, 2020 4:36 PM -
I'm able to download the .cab file from client PC through browser that it using port 80.
On WSUS 6.2 and later (at least Windows Server 2012 ), port 8530 for HTTP and 8531 for HTTPS are used.
If the port number is changed to 80 after the WSUS configuration is completed, this may be the cause of the fault. If the conditions work, consider adjusting the port number of WSUS to 8530.
Hope the above can help you.
Regards,
YicPlease remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Monday, January 6, 2020 1:25 AM -
Hi Yic,
Thanks for your feedback.
The weird part is pc that are OS window 10 doesnt have this problem, and the OS window 10 PC cant telnet 8530 as well.
This means it shouldn't be port number 80 problem right? because our OS Window 10 PC is able to download window update, in the wsus console it is showing 100% for all OS 10 pc.
Thanks for your help Yic, but look like we are going back to the starting point.
Monday, January 6, 2020 8:27 AM