Scan failed with error = 0x8024000d RRS feed

  • Question

  • Hello Everyone,

    There are some machines which are reporting UNKNOWN status for monthly Windows Patching. ScanAgent.log says that "scan failed with error = 0x8024000d". Can anyone suggest the resolution?

    Friday, May 10, 2019 8:18 PM

All replies

  • What version of Windows is the client?

    Jason | | @jasonsandys

    Friday, May 10, 2019 10:16 PM
  • Hi,

    "0x8024000d= Windows Update Agent could not find required information in the update’s XML data"

    Someone has encountered a similar issue and fixed by deleting third party meta data (Dell, Adobe etc.), here is link for your reference.

    Furthermore, if your client version is windows 10 1703, you can refer to the below link.
    Windows 10 V1703: Update error 0x8024000d

    Best Regards,

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

    Monday, May 13, 2019 4:17 AM
  • It is happening on some of the Win10 1703 workstations only.
    Wednesday, May 22, 2019 1:19 PM
  • Tina,

    Thanks for the articles. I read them thoroughly.

    There are more than 10 solutions in these blogs which you pasted. Shall I try them all one by one? And as I stated earlier, this is a happening on some of the Win10 1703 clients only. On other Win10 1703 clients, windows updates are installing perfectly.

    Wednesday, May 22, 2019 1:22 PM
  • What CU levels are the systems that are having issues? Is this different from those that are working correctly?

    Jason | | @jasonsandys

    Wednesday, May 22, 2019 3:36 PM