Software Update macOS - SpecificVersionUnavailable

KennethJ
New Contributor II

Hi,

We have been testing out the Software Update feature the in the last few macOS updates and have run into a few problems with it not triggering on some devices.

We are using the "Download and schedule to install" but we can see in the "Operating System History" that around 200 out of 650 Macs running Sequoia has a failed entry in the history. One of the errors we have not been able to find anything about is "Error reasons: SpecificVersionUnavailable" on a device running 15.1.0 and 15.1.1 is available in Software Update on the device. We are using "Latest minor version" when trying to push the install.

Anyone seen that error before and have a solution or reason for why that would happen?

Screenshot 2024-11-26 at 12.29.20.png

Screenshot 2024-11-26 at 12.29.13.pngScreenshot 2024-11-26 at 12.29.31.png

4 REPLIES 4

obi-k
Valued Contributor III

Yes, we see similar results in the History tab. I usually rely on two things:

1. Click the Management tab Instead of going to the History tab. Click Operating System Update. Do you have a DDM log here or is nothing going on?

2. If nothing is going on, turn off and on the Software Update feature to reset the logs. Re-run the DDM scheduled update. Repeat step 1. 

KennethJ
New Contributor II

1. In the "Operating System" tab there is nothing, just "No updates in progress".

Screenshot 2024-11-27 at 13.24.51.png

2. We actually tried that yesterday to clear the history as I read that in another post with another problem we also had. Looks like it has worked on most of the remaining Mac's. The deadline is set to tomorrow at 16:00, so we are waiting to see friday morning if devices have failed again. But this specific error I have only seen on one Mac so far (I have not gone through all 200 devices that had failed 😁)

obi-k
Valued Contributor III

Cool. Let us know how it goes. 

My experience is that it'll catch most, but some lagger.

AJPinto
Honored Contributor III

I wonder what the install log says on an impacted device. I wonder if there are some network shenanigans going on.