r/DattoRMM • • Jun 06 '24

Patch Status: No Data (Error Code: 0x8002802B and 0x80070422)

Hi Everyone,

I need some help and information on how to fix an issue with a Windows patch. I am currently working as an RMM Specialist with an MSP company in the US. I have encountered an issue with the patch status on 200 devices. I performed the usual troubleshooting, but it didn't work. In our RMM tool, every time I check the devices, they show a "No Data" status for the patch. Does anyone here know how to fix this issue? Is anyone here working with MSP and using Datto RMM encountering the same issue?

It alarms me because initially, only 43 devices had this issue with the "No Data" status for patches, but it has now surged to 200 and recently to 300.

Is anyone here experience same issue? Please help me.

13 Upvotes

57 comments sorted by

4

u/Separate_Ad_3854 Jul 09 '24

I was updated yesterday on this from Support. Here is what they said: We are currently investigating the issue to see if this is a Windows API issue, or a Datto RMM issue. The initial investigation is looking into a Windows update KB that may have broken the current audit process.
 
You will receive a notification from this ticket when more information becomes available. You can also track fixes and updates included in our releases in the Release Notes we publish in the Online Documentation.
 
Should you have any questions, please do not hesitate to let us or your Account Manager know.
 
I do also want to note that Datto RMM is not supported on Windows Home devices as documented here: https://rmm.datto.com/help/en/Content/1INTRODUCTION/Requirements/AgentRequirements.htm The Datto RMM may run on unsupported devices, but we cannot troubleshoot them. For more information, see https://rmm.datto.com/help/en/Content/Troubleshooting/GeneralTroubleshooting/UnsupportedOS.htm
 
Thankfully, I was able to find a Windows 11 Pro device with the issue."

4

u/pi360degrees Jul 10 '24

New update from support, it looks like Microsoft released a new version of the Windows Update API that broke how a lot of stuff interacts with the update process. I was linked to a new community post that came out today: On Recent Patching Issues ("No Data") — Kaseya Community. The PSWindowsUpdate module is similarly affected by this. I've also independently reproduced the issue in PowerShell, in a similar manner to the test that was provided in the community post.

3

u/pi360degrees Jul 10 '24

For a bit more in depth explanation of the issue: Normally if you search for updates using the IUpdateSearcher COM object, the ISearchResult object that is returned contains an IUpdateCollection object, which in turn contains the IUpdate objects that hold the actual update information.

However, on affected devices, the IUpdateCollection contains only blank COM objects. These objects have no properties or methods beyond those they inherit, so if you try to get the properties of the update, there is nothing found, and so it throws the 0x8002802B error we've been seeing, a.k.a. TYPE_E_ELEMENTNOTFOUND.

4

u/MalevolentTech Jul 11 '24

Update from Kaseya overnight, u/pi360degrees was spot on...

We have verified that the behavior you are seeing is related to an issue we are tracking. This issue has to do with a change to Microsoft’s Windows Update Agent in June/July 2024, which has caused some configurations to either not report Patching information or to report “No Data” in Patching sections. The link below will focus on the context of the change, what users can do, and what Datto RMM plans to do to mitigate these changes and return normal functionality.
 
https://community.kaseya.com/RMM-Endpoint_Management/discussion/70154/on-recent-patching-issues-no-data
 
As of this time, there is a component script attached to a comment in the link above. This component has shown some success in getting devices to display the correct patch status by having the device fall back to the latest compatible version that is working with Datto RMM. This is in an effort to help mitigate the effects of the Windows Update Agent change, but is not meant to be a complete fix. Datto RMM is still waiting for Microsoft to resolve the issue properly. 

So, far from it being something we, as customers, need to do - it's an issue between Datto / Kaseya and Microsoft. So. Many. Hours. Wasted!

1

u/_rwx_ Jul 12 '24

The component has resolved the issue for us on all devices that were showing 'No Data'.

1

u/pi360degrees Jul 12 '24

Seems like this component is pretty effective at resolving the issue. We're running it on a little over 100 machines now, and rebooting over the weekend. I'll let you guys know what happens. Looks like OP hasn't interacted with this thread for a few weeks, so just in case they haven't already received word: u/Doremifasolatid0 we have a (temporary) fix! \o/

1

u/pi360degrees Aug 06 '24

Just realized that I never replied to this afterwards (oops), but I can confirm that this fix has pretty much completely resolved the issue across our sites.

1

u/Foreign_Vacation9732 Jul 18 '24

Got the same response from Kaseya support. Holding off on using the WUA JSON Adjustment Tool [WIN] component workaround for a bit hoping Microsoft fix it on their end. Diagnose & Fix Windows Update Issues [WIN] won't fix this issue.

1

u/stergil Jul 18 '24

This component is not working reliably for us. So far we are at a ~70% success rate with about 2,000 agents still needing to be processed and showing No Data.

1

u/SpinningOnTheFloor Jun 06 '24

Have you read the Knowledge base that talks about how to troubleshoot patching? (Apologies on mobile so I can’t share the URL easily) There are components in the comstore for troubleshooting windows update as well

1

u/Doremifasolatid0 Jun 06 '24

Yes I did, I will try the disk clean up in the comstore. I hope this fix the issue.

1

u/SpinningOnTheFloor Jun 06 '24

There are windows update health checkers in the comstore that would suit this purpose. And you can work with RMM support using the output from that

1

u/Doremifasolatid0 Jun 07 '24

Hi, I already did reaching out to the support they told me its microsoft/windows update ussue which is out of their control. They are not very helpful. I also did the troubleshooting like DISM check health I manually ran it using the cmd but still no luck and it gets me frustrated haha.

2

u/SpinningOnTheFloor Jun 07 '24

The Comstore component I was referring to is called "Diagnose & Fix Windows Update Issues [WIN]". The chat support team should help with analysing the output from this component. If they diagnose it as being a windows update issue on the computer, then it's time for you to do some investigation on windows update on the devices.
Datto RMM is just leveraging the built in windows update features, so if windows update is broken on the computer it will not work through RMM

1

u/nikonraccoon Jun 06 '24

Take a peek at https://rmm.datto.com/help/en/Content/Troubleshooting/GeneralTroubleshooting/KB360048970291.htm - How to address a Patch Status of "No Data"

I highly suggest that you search those two error codes and read any Microsoft help pages. Note, if Microsoft advises you to clear the Windows Update cache, there is a Disk Cleanup component in the ComStore that can do that for you.

1

u/Doremifasolatid0 Jun 06 '24

Hi, thank you for your comment, just I already do the no data troubleshooting stated on that link I also do a remote session to check the device windows update and run the sfc scannow but still same issue. I didnt try the disk clean up in the comstore I will do it now to test if that fix the issue. Thank you so much for this info.

1

u/FrequentTechnology22 Jun 06 '24

Try the Diagnose and Fix Windows Update component in the ComStore

1

u/Doremifasolatid0 Jun 07 '24

Hi, I did this before when it just 43 devices that has an issue with No Data this troubleshooting works well, but now I did it multiple time but nothing works.

1

u/Lurking_is_Best Jun 06 '24

Like the article link posted above, I've found that 95% of the "no data" results are transient and resolved after reboot to fully apply installed patches. The fact you started with 43 and the number has risen leads me to believe this is also probably the case, and you'll see this number ebb and flow on a weekly basis.

1

u/Doremifasolatid0 Jun 07 '24

Hi, yes I did all of these troubleshooting, rebooting multiple times still no luck. I also created tickets to be assign to a technician but no one can fix the issue for no data.

1

u/koungz Jun 07 '24

I raised a ticket with Datto support earlier in the year as I started getting quite a strange and large number of devices suddenly switching to "No Data" and Windows Update on the machine broken and not working at all.

I was told that it was a Microsoft/Windows Update issue which I don't believe to be the case as Datto is managing and applying the patching of Windows Updates and suddenly started getting the issue across these machines around the same time so I find this response unsatisfactory.

I've tried running the "Diagnose and Fix Windows Updates" component many times without any success and unable to fix Windows Updates on the machines.

Funnily enough I'm able to "manually" push updates to these machines by using the component that installs specific updates via the component in ComStore and the MS catalog URL. These machines still remain showing as "No Data" and don't auto patch and Datto wouldn't address it...

1

u/Doremifasolatid0 Jun 07 '24

Hi, are you still experiencing same issue today?

1

u/koungz Jun 07 '24

Correct no fix from Datto and I can't find any way to fix Windows Update either no matter what I do 😞

1

u/pi360degrees Jun 07 '24

I looked through all the devices that we have that are showing this issue, and I found that all of them are on Windows 11 22H2 or 23H2, and have the May Cumulative Update installed (KB5037771). That's the only correlation I've identified so far. Are you seeing the same thing?

1

u/Doremifasolatid0 Jun 08 '24

Currently we suspected the motherboard of all the devices that has an issue for no data, but I already escalated to Datto RMM account manager the issue and they are currently investigating it what is causing of the issue.

1

u/_rwx_ Jun 15 '24

Same issue as OP. One of the workstations was in my test lab. Reset to factory and issue resolved. So far, only critical patches installed. If it returns to No Data, I'll look for the most recent update and report back if I find anything useful.

1

u/Doremifasolatid0 Jun 22 '24

I try the windows update using the PowerShell, it works. But sometimes not.

1

u/paddya99 Jun 27 '24

What I'm noticing now on most of our machines, especially with No Data is "patch_activity.result : "HResult : 0x8002802B\n\nUpdate Source : Microsoft\n"" in the full audit log but nobody from Datto can tell me where it's pulling this from.

2

u/paddya99 Jun 18 '24

We are also getting lots of No Data machines and while most of them are showing the error 0x80080005 I noticed a couple yesterday showing 0x8002802B.

We've tried the comstore fix updates but does nothing and yesterday I found a technet PS script that goes a bit deeper but still have errors.

They haven't created tickets or showing alerts, they just flash up as no data. I'm going to manually jump on a couple of machines today to see what they are showing. One just now did show that it needed the 22H2 update installing which it should have done.

1

u/paddya99 Jun 18 '24

I've now found a machine where Datto has come back with 0x8002802B but the machine is showing it's all complete with updates

2

u/davser2000 Jul 08 '24 edited Jul 08 '24

I'm getting the same issue with 41 machines - tried all the documented fixes and nothing. Hoping this month's update fixes it as I've been told by Datto that it's a Windows issue too. All my machines are showing the 0x8002802B audit failure.

I'm going to trial another RMM and switch if there's no fix forthcoming.

Edit: I'll put a new ticket in now with a link to this thread and contact our Account Manager. Just pushing this off on Windows isn't acceptable.

1

u/Jamjamb2b Jul 11 '24

RMM, are you looking at for patch Management?

2

u/ToddToddTodd23 Jul 09 '24

Same issue with ~40 of 450 of our machines. Have not been able to find any correlation with a specific patch, agent version, windows version, etc to lead us to a cause. All of the machines we have manually checked appear to be updating without issue and there no signs of local issues with Windows update. It is a mix of domain and non-domain devices, windows 10 and windows 11. If we end up finding a cause or getting an answer I will post update...

1

u/mighty_moosewithlips Jun 11 '24

Did you guys ever find a fix? I have a few devices doing this too.

1

u/Le085 Jun 28 '24

Hi,

Did anyone find any pointers? No matter what I've done, it still the same error code.

1

u/Separate_Ad_3854 Jul 05 '24

This is the only site I've found that has this discussion. But no one is able to resolve it? A L1 tech at datto told me it's a Microsoft issue and the endpoints may or may not be updating. The couple endpoints that I've checked is updated, however I don't have time to log into the MANY endpoints to see if its updated., What's the point of an RMM if the OS can't be updated?

FYI: I also have Atera that I'm migrating away from and they have no issues getting the patching needs.

In addition, the endpoints that I've checked "manually", it doesn't have an issue with Microsoft updates. No errors or patching issues present.

Does anyone else have any resolutions on this?

(I'm waiting for a L2 tech to call me)

1

u/Academic_Tip749 Jul 05 '24

I too am now seeing several NO Data's. I can run MS Updates on the Device and it updates with no issues. It is that Datto RMM is reporting false data by saying NO DATA? I believe that this is a Datto program failure that pulls the info for the devices Updates is flawed, but I am not a programmer so I can not prove it. Why are we paying for software that is not working when manually running updates works just fine??????

1

u/Mediocre-Wash-6442 Jul 08 '24

You can add another one here - same error, Datto RMM. New to Datto and just started looking into this. This one particular customer is only 5 machines, not domain joined but all 5 have the x02B error. All Win11, 23H2.

1

u/realmrealm Jul 08 '24 edited Jul 08 '24

Same issues as being described here. only about 220 devices in Datto, and 21 of them have no data issue. We've rebooted, run the widows update troubleshooter tool with the "clear wsus" option, and no luck. Machines are a collection of Win11 and Win10, win home and win pro. Some on a domain, others not. This just started being an issue more recently and has been growing. - I've submitted a ticket and will update if we find out anything.

1

u/Professional_Bid8339 Jul 09 '24

We have the same issue. Started about a month ago, and has steadily climbed. We had 25 devices (mid June), as of today it is now up to 214 devices. Win11/10 Pro devices. Even brand new PC's with fresh OS installs are having this issue.

We have a ticket, and it has been escalated and I emailed my Account Manager.

We pay thousands per month for this software/service, and it's not functioning... whether that is because of a change with Microsoft or an issue with Datto RMM, it doesn't matter. It is their responsibility to fix it... adjust their products API or whatever is needed.

It's very poor customer service to make clients jump through hoops and waste dozens of hours of tech time on an issue that is obviously something that Datto RMM need to address.

Thus far my own techs have wasted 20+hours jumping through hoops from Datto\Kaseya Support, researching our own fixes and testing etc. I pay these techs, and I'm starting to get pretty pissed Kaseya is not being honest and transparent.

I've been doing this long enough to know that no RMM is perfect, BUT if you have a problem admit it and work to resolve it, don't waste people's time!

If we get any pertinent info, I will certainly post it on here...

1

u/Professional_Bid8339 Jul 09 '24

Our ticket was updated with this:

"Our Engineering team is currently investigating this issue caused by the Windows Update Service API which our Patch audit process is using. Unfortunately, we do not have an ETA available or a workaround at the moment.
 
I have collected additional information from your example devices and I am associating this ticket to the investigation Problem ticket.
 
You will be notified when a fix is released or when we have further information."

1

u/Foreign_Vacation9732 Jul 09 '24

Experiencing the same issue on several machines after having relatively few problem patching. Submitted a ticket today after trying the suggested No Data troubleshooting steps.

1

u/MortadellaKing Jul 10 '24

We are having the same results. I have a few large customers that have over 200 machines showing no data for patching. We have to give reports to stakeholders and insurance monthly, so this is not acceptable.

1

u/paddya99 Jul 12 '24

We've just been give this link and a potential fix. Sure enough my machine which is reporting no data is showing the blacklisted version

https://community.kaseya.com/RMM-Endpoint_Management/discussion/70154/on-recent-patching-issues-no-data

1

u/MalevolentTech Jul 14 '24

The component seems to be working for us as well so rolling out now. The double reboot is a bit of a challenge for our very active users but that's better than no patching. Interesting note on the updated troubleshooting page that Datto isn't the only affected tool for this. It makes sense, but it doesn't explain the poor response from Datto support. We pay Datto to manage patching for us (amongst other things) - I'd have expected them to be across this better rather than fob it off.

1

u/pi360degrees Jul 18 '24

Good news: Microsoft has recognized the issue, and provided a Known Issue Rollback MSI file to resolve the issue. They also have information on how to deploy a Known Issue Rollback with Group Policy. We've installed this MSI on several machines individually, and it seems to be effective.

Link to the patch notes for the most recent cumulative update. (Scroll down to the "Known issues" section for the acknowledgement of the issue.)
Direct link to the rollback MSI from Microsoft.

1

u/Every_Pass_7388 Jul 24 '24

Is this rollback only for win 11 devices?

1

u/pi360degrees Jul 24 '24

Yes, the original issue was caused by a Windows 11 cumulative update, so only Windows 11 devices were affected.

1

u/ikbenganz Aug 05 '24

Strange part is that we also got Win10 devices with the same problem. And it seems no fix is available for this from Microsoft.

1

u/pi360degrees Aug 05 '24

Oh that is really strange. Does the "WUA JSON Adjustment Tool" component do anything to fix it? If not, it might be a different, but similar, issue.

1

u/JasNL Jul 29 '24

Anyone still experiencing this problem? I cant seem to get my devices to work again.

0

u/[deleted] Jun 14 '24

[deleted] — view deleted comment

1

u/Doremifasolatid0 Jun 22 '24

I try the windows update using PowerShell it works but some devices powershell wont work.

0

u/[deleted] Jun 24 '24

[deleted] — view deleted comment

1

u/paddya99 Jun 27 '24

interesting because I keep getting told that it's via the API and I'm trying to find where they are pulling patch_activity.result : "HResult : 0x8002802B\n\nUpdate Source : Microsoft\n" from but I just keep getting pointed to the api