@DMH2000 - OK, I created a policy and scoped a couple troubled Macs to it...will report back. 

So, the Macs I ran the script on seem to be cured for the moment...

Thanks for the info, but I hope this goes away with Jamf 10.40.0.

@scottb macAdmin slack knows/thinks it's a Apple/macOS issue and has happened on the past three or four version of macOS.

C

Seeing this too. We're rolling out the 'Nudge' framework to enforce software updates, documentation states to include an 'Update Inventory' command as part of the Nudge policy. Noticed I have a lot of computers failing on the collecting inventory part. Google search of the error lead me to this thread (though we do have Jamf Pro). 

Rolling out a 

 to all computers to see if it helps.

+1 for hoping Jamf 10.40.0 fixes this.

I recently updated my on premise JSS from 10.37.2 to 10.40.  I am now seeing the error “Software update timed out after 300 seconds.” a LOT during (2) specific tasks (not including any MDM software update commands):

1 When a policy includes an update inventory payload (after installing a pkg for example).

2. When a managed Mac checks in to upload its inventory as part of a scheduled routine (daily).

This appears to be mainly affecting macOS 11.x Big Sur Macs, but I think I have seen it on macOS 12 Monterey as well.

I do not see that  PI109755 is resolved in 10.40.1

Still seeing some of these, even on Macs I ran the script on.  Not as many, but still...

FWIW, it is on 11.x and 12.x Macs.

After talking to Jamf Support (on an unrelated call) they indicated that this timeout issue should be affecting mainly Jamf Pro customers running 10.39 and 10.40 (I think) and only affecting macOS 11 Macs (that has a known documented issue of softwareupdate getting 'stuck') but I have seen it on macOS 12 too To remediate, I am running a simple one-liner script to kickstart the macOS softwareupdate process on a regular schedule (set to weekly but might run it daily).

 sudo launchctl kickstart -k system/com.apple.softwareupdated

Jamf 10.40. Saw recon hang at "Locating hardware information" on a Big Sur machine, and kickstart fixed it. Monterey machine running 12.15.0 hung, and kickstart didn't resolve it. Upgraded to 12.15.1 and kickstart still didn't resolve the hang on "Locating hardware information. Ran recon with --verbose and it seems to hang after Gatekeeper status. Machine has the default Gatekeeper configuration though, so not sure what the issue would be.

This problem has plagued my environment for many months to a point that I stopped collecting software updates in the the inventory.  Apparently, Jamf hasn't fixed this yet as of v10.44.1.

We are still running periodical kickstarts here at my org which certainly cuts down on the errors in inventory but I still see a few each day.

Each round of recons (daily) shows a few as well.  Not a huge issue, but would like to see no errors on this...

That command helped me today! 

Be aware that as of macOS Sonoma 14.4 Apple will not run a launchctl kickstart -k command against most system services, including com.apple.softwareupdated

I was running against a Ventura laptop. 

But thank you for the info, appreciated.