locked
Patching failing with error 0x80244022 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I have several servers

    Operating System: Windows Server 2016

    WSUS Server: Windows Server 2012

    which are failing during the launch of "Check for updates"

    The process has been tried several time and alwys the same error in return.

    Some other fixes have been tried:

    sfc /scannow
---------------------------------------------------------------
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

    Reboot

    same error afterwards...

    also

    Press Windows key + R, type "services.msc" (without quotes) in start run box and press Enter. 
b. Locate Windows Update service.
c. Right click on the Windows Update service and select Properties.
d. In Start-up type, select Enable.
e. Click Start under Service status.
f. Click OK.
g. Repeat the steps c to f for the following services also:
Background Intelligent Transfer Service & Cryptographic Service.

    No luck either...

    I am providing also the ReportingEvents.log from the SoftwareDistribution folder...

    {8C52BA2A-F087-47BF-9F19-29DEFBFFEB57}	2019-11-25 06:26:30:628-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{EC9723E1-26D1-4926-8F06-A3A74DDD80AC}	2019-11-25 06:32:46:670-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	<<PROCESS>>: CompatTelRunner.exe	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{65AC11E2-A706-4B72-AEC0-E1E8951EA011}	2019-11-25 06:34:28:955-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	<<PROCESS>>: CompatTelRunner.exe	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{01FFC349-F3EF-4B99-9388-27DE58B47CD0}	2019-11-25 06:45:27:969-0800	1	147 [AGENT_DETECTION_FINISHED]	101	{00000000-0000-0000-0000-000000000000}	0	0	Device Driver Retrieval Client	Success	Software Synchronization	Windows Update Client successfully detected 3 updates.
{769AD491-D914-41BE-AF69-21511ADB9365}	2019-11-25 06:45:32:359-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{0B8DF465-E8EA-4A15-9365-E2D31FDCC843}	2019-11-25 06:46:11:343-0800	1	147 [AGENT_DETECTION_FINISHED]	101	{00000000-0000-0000-0000-000000000000}	0	0	Device Driver Retrieval Client	Success	Software Synchronization	Windows Update Client successfully detected 3 updates.
{86B94752-AA43-4A11-B57F-C0B583E6D80E}	2019-11-25 06:52:30:612-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{AC0E2638-E6F9-493D-874B-50F267F01D96}	2019-11-25 07:03:33:633-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{F7970FD0-CFA8-44E5-9D7E-5CC2E7CDD84B}	2019-11-25 07:06:26:711-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{DB7CF3B2-D758-43FD-855E-C3D674B850C8}	2019-11-25 07:46:50:208-0800	1	147 [AGENT_DETECTION_FINISHED]	101	{00000000-0000-0000-0000-000000000000}	0	0	Device Driver Retrieval Client	Success	Software Synchronization	Windows Update Client successfully detected 3 updates.
{EF19D8A6-6C43-4B38-84FA-A6D6E78F33A0}	2019-11-25 07:47:21:338-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{02F6707B-3688-4145-9ADC-6FDE60203FEA}	2019-11-25 08:01:57:200-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	TrustedInstaller FOD	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.

    Any idea?

    Thanks,
    Dom

    Security / System Center Configuration Manager Current Branch / SQL


    • Edited by Felyjos Monday, November 25, 2019 4:16 PM
    Monday, November 25, 2019 4:15 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Check WSUS app pool from your WSUS server and start the WSUS app pool,

    You can refer below also,

    https://gallery.technet.microsoft.com/scriptcenter/Reset-Windows-Update-Agent-d824badc

    https://blog.pcrisk.com/windows/13064-windows-update-error-0x80244022

    https://www.urtech.ca/2018/06/solved-what-does-error-0x80244022-mean-in-windows-update/

    https://www.ajtek.ca/wsus/wsus-system-requirements-what-should-i-plan-for/

    Monday, November 25, 2019 10:33 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Dom,
       

    Please check if the Group Policy applied to this part of the client is configured correctly:
       

    • Windows Components - Windows Update
      [Specify intranet Microsoft update service location] Please check if the configured WSUS server address is the correct "FQDN:PortNUM" address? 
         

    Then, please confirm that this "FQDN:PortNUM" can be accessed. You can access the following locations through a browser on the client:
       

    • http://WSUSserverFQDN:8530/selfupdate/iuident.cab
    • https://WSUSserverFQDN:8531/selfupdate/iuident.cab (When SSL Available)
        

    Normally you will download to a file.
    If you have access issues, consider performing an IIS check.
       

    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.

    Tuesday, November 26, 2019 5:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Check WSUS app pool from your WSUS server and start the WSUS app pool,

    You can refer below also,

    https://gallery.technet.microsoft.com/scriptcenter/Reset-Windows-Update-Agent-d824badc

    https://blog.pcrisk.com/windows/13064-windows-update-error-0x80244022

    https://www.urtech.ca/2018/06/solved-what-does-error-0x80244022-mean-in-windows-update/

    https://www.ajtek.ca/wsus/wsus-system-requirements-what-should-i-plan-for/

    Hello,

    WSUS Application Pool is started...

    Thanks,

    Dom

    Security / System Center Configuration Manager Current Branch / SQL

    Tuesday, November 26, 2019 3:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Dom,
       

    Please check if the Group Policy applied to this part of the client is configured correctly:
       

    • Windows Components - Windows Update
      [Specify intranet Microsoft update service location] Please check if the configured WSUS server address is the correct "FQDN:PortNUM" address? 
         

    Then, please confirm that this "FQDN:PortNUM" can be accessed. You can access the following locations through a browser on the client:
       

    • http://WSUSserverFQDN:8530/selfupdate/iuident.cab
    • https://WSUSserverFQDN:8531/selfupdate/iuident.cab (When SSL Available)
        

    Normally you will download to a file.
    If you have access issues, consider performing an IIS check.
       

    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.

    Hello Yic,

    • Windows Components - Windows Update
       
    • http://WSUSserverFQDN:8530/selfupdate/iuident.cab
    • https://WSUSserverFQDN:8531/selfupdate/iuident.cab (When SSL Available)

    So far not good!!!

    Thanks,

    Dom

    Security / System Center Configuration Manager Current Branch / SQL

    Tuesday, November 26, 2019 3:31 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Dom,
      

    Thank you for your reply.
    As you can see, there is currently no correct Group Policy applied to the client and the WSUS site in IIS also seems to be configured incorrectly. I recommend that you perform a configuration check on the WSUS server from scratch:
      

    • You can refer to Microsoft article for step-by-step check of WSUS configuration steps: "Deploy Windows Server Update Services".
         
    • You can also consider an article written by some experts and compare it step by step: "WSUS Complete Guide To Install And Configure WSUS On Windows Server 2019". Although this is an article for the 2019 system, the configuration of 2012 R2 is basically similar to this.
         
      * 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.
         

    Please focus on the Group Policy and IIS sections.
    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.

    Wednesday, November 27, 2019 2:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    For the GPO it is strange as the GPO is for the OU and there are servers in the same OU which are patched with no problem...

    1 (not the same OU) 3-4-5-8 are patched and no problem...

    6-7-9-10-11 failed!!!

    They are on the same subnet, which should exclude the firewall issue.

    I even just noticed that 3 for example was okay on 11/25/2019

    But is failing today ...

    This is inconsistent!!!

    Checking the Client side ...

    Thanks,
    Dom

    Security / System Center Configuration Manager Current Branch / SQL






    • Edited by Felyjos Thursday, November 28, 2019 12:54 AM
    Thursday, November 28, 2019 12:15 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    6-7-9-10-11 failed!!!

    It can be seen from the registry that you seem to have alternate download server configured. Please consider cancelling this entry and waiting for the client to apply the updated Group Policy before performing the update check.
       


         

    Regards,
    Yic

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, November 28, 2019 2:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    And I recommend setting the alternative download server

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-4-creating-your-gpos-for-an-inheritance-setup/

    Is the private memory limit in IIS set to the default 1.8GB? You should change that to 4GB. See the bottom of (and may as well read the whole page):

    https://www.ajtek.ca/wsus/wsus-system-requirements-what-should-i-plan-for/

    From either the WAM Shell if you have WSUS Automated Maintenance (WAM) © installed or an Administrative PowerShell instance run:

    Write-Output "Proxy: $(netsh winhttp show proxy))"
    Does this look right? Should there be one? should there not be one? (that's network dependent)

    Have you restarted the WSUS Server? Is the client actually reporting back to WSUS? If not, review and follow the troubleshooting in:

    https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/

    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT


    • Edited by AJTek.caMVP Thursday, November 28, 2019 3:05 AM Adjust for code
    Thursday, November 28, 2019 3:04 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,
     

    Any update is welcome here.
    If the issue is resolved, share your solution or find the helpful response "Mark as Answer" to help other community members find the answer.
     

    Thank you for your cooperation, as always.
     

    Regards,
    Yic

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, December 6, 2019 5:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Yic

    So far 1,2,3,4,5 are done sucessfully done after multiple attempts.

    6,7,8,9,10,11 are planned for next week.

    BUT last night I was doing patching on some other servers and sporadically the error 0x80244022 appears.

    I applied a set of patches then reboot then check if they were installed --> yes they were

    then I click "Check for updates" to confirm there is no more patch pending to be applied for a potential second round and then I got the error.


    Thanks,
    Dom

    Security / System Center Configuration Manager Current Branch / SQL


    • Edited by Felyjos Friday, December 6, 2019 3:09 PM
    Friday, December 6, 2019 5:34 AM