Skip to main content
Question

The package could not be verified on macOS Monterey 12

userjamf
Forum|alt.badge.img+3

Hello,

I have deployed a package through Jamf and made it available in Self Service. However, the installation fails for users running macOS Monterey 12.

The logs show the following error :

Verifying DMG...
Verifying package integrity...
Installation failed. The package could not be verified.

The package installs successfully on other macOS versions, but fails specifically on macOS Monterey 12. I have already tried re-uploading the package to Jamf, but the issue still occurs.

Could you please advise on what might be causing this issue and how we can resolve it ?

Thank you.

2 replies

Chubs
Forum|alt.badge.img+26
  • Chubs
  • Jamf Heroes
  • October 21, 2026

Hello,

I have deployed a package through Jamf and made it available in Self Service. However, the installation fails for users running macOS Monterey 12.

The logs show the following error :

Verifying DMG...
Verifying package integrity...
Installation failed. The package could not be verified.

The package installs successfully on other macOS versions, but fails specifically on macOS Monterey 12. I have already tried re-uploading the package to Jamf, but the issue still occurs.

Could you please advise on what might be causing this issue and how we can resolve it ?

Thank you.

Without knowing what software it is, I’d say it’s an OS limitation on the software vendor side.  That’s an awfully old OS to be deploying software to as well.

I find your lack of faith disturbing
userjamf
Forum|alt.badge.img+3
  • userjamf
  • Author
  • Contributor
  • October 21, 2026

Yes, just to clarify, I’m aware that it’s an old system. The reason I’m running this older version of macOS is that I need to use software that only works on this version, so unfortunately I can’t upgrade macOS.

Also, this doesn’t seem to be related to any specific application. I’m seeing the same behavior with all applications. For example, Google Chrome 150 on Monterey gives me the same result.

What’s strange is that this only started happening a few weeks ago. That’s why I was wondering if something might have changed on the Jamf side recently that could be causing this behavior.

Terms & ConditionsAccessibility statement