WUAHandler.log reporting "Scan failed with error = 0x8024000f"

%3CLINGO-SUB%20id%3D%22lingo-sub-754705%22%20slang%3D%22en-US%22%3EWUAHandler.log%20reporting%20%22Scan%20failed%20with%20error%20%3D%200x8024000f%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754705%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20using%20SCCM%20CB%201902%20on%20Windows%202016.%20WUAHandler.log%20in%20all%20clients%20is%20reporting%20error%20since%20almost%20a%20month%20back.%20Following%20is%20the%20last%20few%20lines%20from%20log%3B%3C%2FP%3E%3CPRE%3EIts%20a%20WSUS%20Update%20Source%20type%20(%7B7BDC6D42-1BB8-4DBD-AD96-E288D3E2E79A%7D)%2C%20adding%20it.%20WUAHandler%2013%2F07%2F2019%2003%3A04%3A13%2017304%20(0x4398)%3CBR%20%2F%3EThis%20device%20is%20not%20enrolled%20into%20Intune.%20WUAHandler%2013%2F07%2F2019%2003%3A04%3A13%2018876%20(0x49BC)%3CBR%20%2F%3EDevice%20is%20not%20MDM%20enrolled%20yet.%20All%20workloads%20are%20managed%20by%20SCCM.%20WUAHandler%2013%2F07%2F2019%2003%3A04%3A13%2018876%20(0x49BC)%3CBR%20%2F%3ESourceManager%3A%3AGetIsWUfBEnabled%20-%20There%20is%20no%20Windows%20Update%20for%20Business%20settings%20assignment.%20Windows%20Update%20for%20Business%20is%20not%20enabled%20through%20ConfigMgr%20WUAHandler%2013%2F07%2F2019%2003%3A04%3A13%2018876%20(0x49BC)%3CBR%20%2F%3EExisting%20WUA%20Managed%20server%20was%20already%20set%20(https%3A%2F%2Fmycompany.contoso.com%3A8531)%2C%20skipping%20Group%20Policy%20registration.%20WUAHandler%2013%2F07%2F2019%2003%3A04%3A13%2017304%20(0x4398)%3CBR%20%2F%3EAdded%20Update%20Source%20(%7B7BDC6D42-1BB8-4DBD-AD96-E288D3E2E79A%7D)%20of%20content%20type%3A%202%20WUAHandler%2013%2F07%2F2019%2003%3A04%3A13%2017304%20(0x4398)%3CBR%20%2F%3EScan%20results%20will%20include%20all%20superseded%20updates.%20WUAHandler%2013%2F07%2F2019%2003%3A04%3A13%2017304%20(0x4398)%3CBR%20%2F%3ESearch%20Criteria%20is%20(DeploymentAction%3D*%20AND%20Type%3D'Software')%20OR%20(DeploymentAction%3D*%20AND%20Type%3D'Driver')%20WUAHandler%2013%2F07%2F2019%2003%3A04%3A13%2017304%20(0x4398)%3CBR%20%2F%3EAsync%20searching%20of%20updates%20using%20WUAgent%20started.%20WUAHandler%2013%2F07%2F2019%2003%3A04%3A13%2017304%20(0x4398)%3CBR%20%2F%3EAsync%20searching%20completed.%20WUAHandler%2013%2F07%2F2019%2003%3A13%3A16%2022532%20(0x5804)%3CBR%20%2F%3EOnSearchComplete%20-%20Failed%20to%20end%20search%20job.%20Error%20%3D%200x8024000f.%20WUAHandler%2013%2F07%2F2019%2003%3A13%3A16%201880%20(0x0758)%3CBR%20%2F%3EScan%20failed%20with%20error%20%3D%200x8024000f.%20WUAHandler%2013%2F07%2F2019%2003%3A13%3A16%201880%20(0x0758)%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETried%20googling%20about%20this%20error%20and%20found%20that%20it's%20about%20%22%3CSPAN%3ECircular%20update%20relationships%20were%20detected%20in%20the%20metadata%22.%20I%20followed%20below%20thread%20and%20did%20exactly%20as%20suggested%20(yes%2C%20I%20had%20installed%20SUP%20around%203%20months%20back%20for%20the%20sake%20of%20Dell%20driver%20and%20software%20updates)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2Fb1901803-1a53-4aa8-bbdd-897881fbd17d%2Fsccm-2012-1606-onsearchcomplete-failed-to-end-search-job-error-0x8024000f%3Fforum%3Dconfigmanagersecurity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESCCM%202012%20(1606)%20-%20OnSearchComplete%20-%20Failed%20to%20end%20search%20job.%20Error%20%3D%200x8024000f%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EBut%20above%20effort%20didn't%20help%20me.%20Error%20still%20appears%20and%20as%20a%20result%2C%20I'm%20not%20able%20to%20apply%20latest%20Microsoft%20updates.%20Any%20help%20to%20fix%20this%20issue%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-754705%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECM%20current%20branch%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESoftware%20Update%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-756335%22%20slang%3D%22en-US%22%3ERe%3A%20WUAHandler.log%20reporting%20%22Scan%20failed%20with%20error%20%3D%200x8024000f%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-756335%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20issue%20is%20resolved%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20those%20who%20are%20having%20the%20same%20issue%3A%20Denying%20third%20party%20updates%20alone%20wouldn't%20resolve%20the%20issue.%20They%20have%20to%20be%20deleted%20from%20WSUS%20database.%20I%20used%20script%20from%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgallery.technet.microsoft.com%2FDelete-3rd-Party-Updates-e5bf19fe%2Fview%2FDiscussions%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgallery.technet.microsoft.com%2FDelete-3rd-Party-Updates-e5bf19fe%2Fview%2FDiscussions%3C%2FA%3E%26nbsp%3Bto%20delete%203rd%20party%20updates.%20Since%20script%20is%20using%20only%20WSUS%20Powershell%20library%20exposed%20interface%20for%20operation%2C%20I%20think%20the%20script%20is%20safe%20to%20be%20run.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20do%20share%20thoughts.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-777935%22%20slang%3D%22en-US%22%3ERe%3A%20WUAHandler.log%20reporting%20%22Scan%20failed%20with%20error%20%3D%200x8024000f%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-777935%22%20slang%3D%22en-US%22%3EFollow%20Prajwals%20instructions%20and%20you%20will%20be%20able%20to%20solve%20it%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fforums.prajwaldesai.com%2Fthreads%2Fwuahandler-log-reporting-scan-failed-with-error-0x8024000f.2648%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fforums.prajwaldesai.com%2Fthreads%2Fwuahandler-log-reporting-scan-failed-with-error-0x8024000f.2648%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

 

I'm using SCCM CB 1902 on Windows 2016. WUAHandler.log in all clients is reporting error since almost a month back. Following is the last few lines from log;

Its a WSUS Update Source type ({7BDC6D42-1BB8-4DBD-AD96-E288D3E2E79A}), adding it. WUAHandler 13/07/2019 03:04:13 17304 (0x4398)
This device is not enrolled into Intune. WUAHandler 13/07/2019 03:04:13 18876 (0x49BC)
Device is not MDM enrolled yet. All workloads are managed by SCCM. WUAHandler 13/07/2019 03:04:13 18876 (0x49BC)
SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 13/07/2019 03:04:13 18876 (0x49BC)
Existing WUA Managed server was already set (https://mycompany.contoso.com:8531), skipping Group Policy registration. WUAHandler 13/07/2019 03:04:13 17304 (0x4398)
Added Update Source ({7BDC6D42-1BB8-4DBD-AD96-E288D3E2E79A}) of content type: 2 WUAHandler 13/07/2019 03:04:13 17304 (0x4398)
Scan results will include all superseded updates. WUAHandler 13/07/2019 03:04:13 17304 (0x4398)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 13/07/2019 03:04:13 17304 (0x4398)
Async searching of updates using WUAgent started. WUAHandler 13/07/2019 03:04:13 17304 (0x4398)
Async searching completed. WUAHandler 13/07/2019 03:13:16 22532 (0x5804)
OnSearchComplete - Failed to end search job. Error = 0x8024000f. WUAHandler 13/07/2019 03:13:16 1880 (0x0758)
Scan failed with error = 0x8024000f. WUAHandler 13/07/2019 03:13:16 1880 (0x0758)

 

Tried googling about this error and found that it's about "Circular update relationships were detected in the metadata". I followed below thread and did exactly as suggested (yes, I had installed SUP around 3 months back for the sake of Dell driver and software updates)

SCCM 2012 (1606) - OnSearchComplete - Failed to end search job. Error = 0x8024000f

 

But above effort didn't help me. Error still appears and as a result, I'm not able to apply latest Microsoft updates. Any help to fix this issue?

2 Replies
Highlighted

The issue is resolved now.

 

For those who are having the same issue: Denying third party updates alone wouldn't resolve the issue. They have to be deleted from WSUS database. I used script from https://gallery.technet.microsoft.com/Delete-3rd-Party-Updates-e5bf19fe/view/Discussions to delete 3rd party updates. Since script is using only WSUS Powershell library exposed interface for operation, I think the script is safe to be run.

 

Please do share thoughts. :)

 

Regards,

Highlighted