macOS Tahoe patch appears as Sequoia and fails with update classification mismatchSolved

Hello @eduardo ,

This can involve two separate behaviors:

1. Patch label mismatch in the portal

If a macOS Tahoe update appears with a Sequoia label, it is usually a display/classification mismatch in the patch listing. Once corrected, the patch should no longer appear under the wrong macOS label.

2. Patch deployment failure on specific devices

The deployment failure can be unrelated to the label mismatch. In some cases, Apple may expose the same macOS update through different update channels or endpoints. For example, one device may report the update through an Enforce Patch channel, while other devices report it through AvailableOSUpdates.

Hexnode UEM can force-push an OS update only when that update is listed under the device’s Patches and Updates tab. If the automation is targeting a different update identifier than the one available on the affected Mac, the deployment can fail or show a classification mismatch.

To check this:

1. Go to Manage > Devices and open the affected Mac.
2. Open the Patches and Updates tab.
3. Under Applicable patches, open the macOS Tahoe 26.6 patch details.
4. Note the patch Identifier.
5. Open the automation profile used for the macOS update.
6. Edit the macOS 26.6 patch entry and open View Details.
7. Compare the GUID or identifier in the automation profile with the identifier shown under the affected device’s applicable patch.

If the identifiers are different, create a separate manual patch automation using the identifier shown under the affected device’s Applicable patches, then apply that automation to the affected Mac.

Regards,
Simon Scott
Hexnode UEM

We saw something similar with a macOS point release. A mislabeled patch disappeared after the next macOS update became available, and the devices moved on to the newer patch instead of staying marked as missed.