locked
WUA Error - Scan failed with error = 0x80240037 RRS feed

  • Question

  • Hello Guys,

    Receiving following errors when trying to scan the system for patches

    WUAHandler.log

    OnSearchComplete - Failed to end search job. Error = 0x80240037. WUAHandler 06.09.2017 11:21:22 4124 (0x101C)
    Scan failed with error = 0x80240037. WUAHandler 06.09.2017 11:21:22 4124 (0x101C)

    UpdatesDeployment.log

    Job error (0x80240037) received for assignment ({0FEB4210-7296-4454-B33F-61EE7E70AC84}) action

    ---------------------------------------------------------------------------------------------------------------------------------------------

    Actions Taken:

    Rebooting system
    Software Distribution folder renamed
    SCCM client clean removed, reg, ccmclean, folders etc. Reinstalled manually successfully and communicating fine
    Status of client is perfect in SCCM console as well
    but again the same errors as shown above comes up.


    • Edited by Vikram Midha Wednesday, September 6, 2017 10:42 AM
    Wednesday, September 6, 2017 10:42 AM

All replies

  • You'll have to give more information:

    Give some details of your environment

    Is this on all computers or an isolated case?

    What is OS of system?

    Are any updates being applied or is the problem just with one or more updates?

    Can you see updates in Software Center on the device?



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    Wednesday, September 6, 2017 12:55 PM
  • You'll have to give more information:

    Give some details of your environment

    Is this on all computers or an isolated case?

    What is OS of system?

    Are any updates being applied or is the problem just with one or more updates?

    Can you see updates in Software Center on the device?



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    Hello Gerry,

    Standalone SCCM CB1606
    Windows 7 SP1 - x64
    I can see some updates applied on the system almost 10 days back but now when trying to scan for new ones, the errors as above are observed
    No, no updates are visible under Software Center

    Wednesday, September 6, 2017 3:05 PM
  • Hi, what exactly have you done to scan for new updates? Was this issue happening to all your systems? 

    Be sure you've created proper windows 7 x64 software update groups and downloaded and then deployed to your clients.

    Watch wuahandler.log during scan.


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

    Thursday, September 7, 2017 3:08 AM
  • Hi, what exactly have you done to scan for new updates? Was this issue happening to all your systems? 

    Be sure you've created proper windows 7 x64 software update groups and downloaded and then deployed to your clients.

    Watch wuahandler.log during scan.


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

    Its the normal scan which I am performing and the errors observed under the logs are posted above in my starting post. This seems to be the only system as of now with this problem.

    Thursday, September 7, 2017 4:03 AM
  • Hi, did you click "Software Updates Scan Cycle" from Configuration Manager in control panel from client side? What's in wuahandler.log?

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

    Thursday, September 7, 2017 6:03 AM
  • Yes and the logs are what I posted above originally

    WUAHandler.log

    OnSearchComplete - Failed to end search job. Error = 0x80240037. WUAHandler 06.09.2017 11:21:22 4124 (0x101C)
    Scan failed with error = 0x80240037. WUAHandler 06.09.2017 11:21:22 4124 (0x101C)

    UpdatesDeployment.log

    Job error (0x80240037) received for assignment ({0FEB4210-7296-4454-B33F-61EE7E70AC84}) action

    Thursday, September 7, 2017 6:10 AM
  • Have you tried the following: https://blogs.technet.microsoft.com/sus/2012/09/05/additional-note-on-kb-2734608-regarding-wsus-windows-8-and-windows-server-2012/

    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, September 7, 2017 7:20 PM
  • https://answers.microsoft.com/en-us/windows/forum/all/windows-7-update-fails-with-code-80070308/f5b42dbc-3776-4051-beb2-f4d211bb0681?auth=1

    https://gallery.technet.microsoft.com/Windows-Update-Agent-fdcd1774?redir=0

    Since you are encountering on single machine please try the client side solution or workaround manually.


    Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

    Thursday, September 7, 2017 10:26 PM
  • Have you tried the following: https://blogs.technet.microsoft.com/sus/2012/09/05/additional-note-on-kb-2734608-regarding-wsus-windows-8-and-windows-server-2012/

    Jason | https://home.configmgrftw.com | @jasonsandys

    Hello Jason,

    I dont think the link you provided is relevant to this problem as that is for a totally different concern.

    Friday, September 8, 2017 8:32 AM
  • https://answers.microsoft.com/en-us/windows/forum/all/windows-7-update-fails-with-code-80070308/f5b42dbc-3776-4051-beb2-f4d211bb0681?auth=1

    https://gallery.technet.microsoft.com/Windows-Update-Agent-fdcd1774?redir=0

    Since you are encountering on single machine please try the client side solution or workaround manually.


    Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

    Hello Kamala,

    What other action do you suggest apart  from the ones taken below as I conveyed above:

    Actions Taken:

    Rebooting system
    Software Distribution folder renamed
    SCCM client clean removed, reg, ccmclean, folders etc. Reinstalled manually successfully and communicating fine
    Status of client is perfect in SCCM console as well
    but again the same errors as shown above comes up.

    Friday, September 8, 2017 8:33 AM
  • You are correct, not sure what I was thinking or looking at. Please disregard.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, September 8, 2017 11:33 AM
  • Did you look at windowsupdate.log and scaagent.log for more information about the error ? 0x80240037--refers to The functionality for the operation is not supported.

    Eswar Koneti | Configmgr Blog: http://www.eskonr.com | Linkedin: eskonr | Twitter: @eskonr

    Friday, September 8, 2017 2:50 PM
  • Hi!.

    Did you find any solution for this issue? I have  the same problem.

    Thanks!

    Tuesday, December 5, 2017 11:30 AM
  • Check your processor. If you are using a Kaby Lake processor updates will not apply on Windows 7 machines. Kaby Lake ONLY supports Windows 7. 
    • Proposed as answer by Guda Suresh Tuesday, June 19, 2018 2:00 PM
    Thursday, April 5, 2018 7:22 PM
  • Microsoft only officially supports Kaby Lake on computers running Windows per support policies, and windows update blocks updates from being installed on Kaby Lake systems running versions older than Windows 10.
    Tuesday, June 19, 2018 2:09 PM