"OS patching failed: Object reference not set to an instance of an object" since last update?

[JohnnyJoker]

We use Pulseway to automatically patch our servers and since last weekend the history shows the above error for each system - the weekend before everything was fine - and they have pending updates ("2023-07 CU for .NET 3.5, 4.7.2 and 4.8" mostly).

A manually triggered installation via App and Webapp worked fine - updates were installed successfully on a system that showed the message in the topics title when executed through the schedule.

Our Policy is as follows - OS Rules are "approve and install" for critical, important and optional updates and we don't use 3rd party patching.

 

Screenshot of the history.
As you can see everything was fine the weekend before and I've noticed that the agents got updated on 21.07.2023 - maybe a coincidence, maybe not.

We have a mix of Server 2016-2022, with some (legacy) 2008R2 and 2012R2 sprinkled in between.

Help and/or input is very much appreciated.

Cheers!

Edited July 25 by JohnnyJoker
additional info + tagging

[LeonLi]

Hello,

I am having the same issue on a new Windows 11 Desktop. 

[at26574]

 

Same problem here across the board, nothing is working with Windows Update now. 

[Paul]

Hello everyone,

We're investigating the issue and will come back with an update as we hear back from the development team.

-Paul

[StevenB]

Something where a notification to all users of Pulseway should have occurred, we've had weekend patching not work and technicians and account managers now trying to put out fires from our customers.

[Paul]

We have identified the issue and have released the Windows Agent version 9.3.1 with the fix. This seems to be localized to users who have never set up global rules through the WebApp.

We apologize for the inconvenience caused.

-Paul

[JohnnyJoker]

Thanks Paul!

I'll try it out with a custom/test schedule as soon as i notice the new agent version on our machines.

In our case your assumption is right: We've never setup global Patch Policy rules.

 

Edit: Tested it on Agent 9.3.1 and it works just as it should

 

Edited August 3 by JohnnyJoker
Tested it

[at26574]

What needs to be done to get this working again? All our machines are still failing. I assumed the hotfix would be applied automatically to agents but that doesn't seem to be the case.

[Paul]

It does get applied to all systems automatically unless you have turned off automatic agent updates. Does your systems not have the 9.3.1 windows agent?

-Paul