Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

macOS 13 is still in preview beta release at this time; this document is a work in progress

Table of Contents

Support Changes

Login Items UI controls

The new Login Items UI feature in Ventura Beta 1 is a significant blocker for deployment; we have opened tickets with Apple about this issue.

Application Management limitations

The new changes to application management - which prevents Munki from installing updates - is a significant blocker for deployment; we have opened tickets with Apple about this issue.

...

Table of Contents
minLevel1
maxLevel7

Support Changes

System Preferences is now called “System Settings” and is different than any previous version of macOS. User guidance and documentation may need to be edited.

Applications

As of February 21, 2023

  • The following list of applications either have issues launching on macOS 13.0 (Ventura)

...

  • .

  • Please note that older versions of applications were not tested

...

  • here, only the most current versions available in Managed Software Center were checked

...

  • .

  • We do not have the ability to

...

This list is a work in progress (last updated 9-13-2022 as applications are being validated against new beta releases).  This list will be updated as newer versions of these applications come out.

...

  • check every feature in every application. If you have a critical application, we recommend getting clarification from that app’s vendor.

Applications that currently do not install successfully on Ventura (macOS 13):

  • Camtasia – ACE audio driver can’t be installed on 13. May not be fixed until after Ventura is released.

  • Parallels Desktop 17 – and 18 – do not license properly for ITAM installs (reported to vendor)None currently!

Applications that currently do not launch successfully or have issues on Ventura (macOS 13

...

):

  • Ableton Live – application indicates it is “Damaged” and can’t be launched (NOTE – the builder has been fixed and just waiting for the next version.)

  • Examplify (reports Damaged) (NOTE – the builder has been fixed and just waiting for the next version.)

  • FinalCut complains the following audio drivers “did not pass the Apple AU validation”: Examplify

    • Previous versions will present as “Damaged”.

      • If you see this, trash the app and reinstall via MSC as that has been fixed.

  • Ozone 9 Audio Plug-Ins

    • Nimbus, R4, Izotope (Nectar 3, Neutron 2 and 3) and Foundry M7 Link

    --- these cause GarageBand, FinalCut and Premiere Pro to hang on launch while scanning audio drivers…) OF NOTE: 12.4 FinalCut complains about Nimbus, R4 and M7 Link as well.
  • Lightwright 6 – crashes unexpectedly at quit and at launch sometimes (bug filed with Apple – Apple says to be fixed in a future update)

  • Xcode 13 does not run on Ventura – we are not (at this time) packaging the beta of Xcode 14 for deployment along with Ventura

Applications that are not installing updates via Managed Software Center (not an authoritative list) – different apps fail with different betas (running list for beta 6) – it’s possible these updates may install if the apps are trashed before the updates are installed:

  • BlackMagic Desktop Video – still a problem – may be the only application left with an installation issue?

...

    • Final Cut, GarageBand, Logic, Premiere Pro, Audacity, and other audio apps may complain or hang with an error “did not pass the Apple AU validation”. FinalCut Pro 10.6.5 may handle this better after a force-quit and relaunch to display the “Incompatible Audio Units Found”

System Settings is the new name for System Preferences:

  • With its new name, System Settings looks more like your iPhone

...

  • Profiles has moved under Privacy & Security

  • Erase All Content and Settings (EACS) is now under General / Transfer or Reset pane

macOS 13.1 may present a prompt to “Update Apple ID Settings” (fixed in 13.2):

  • Some users may see the prompt to update a “(null)” AppleID after updating to macOS 13.1. This has been fixed in macOS 13.2. If you are still seeing this on 13.2 (or later), just hit “Cancel” and that should resolve it.

...