cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

(In)compatibility of EOS Utility with MacOS Ventura

Stefan1
Contributor

I updated last night to MacOS Ventura. Unfortunately, the EOS Utility does not seem to be compatible with the latest version of MacOS. Because of this, I cannot connect with my Canon EOS R6. This is quite disastrous for me, since I use my R6 amongst others as a webcam. Why? In my profession and role, presentation matters a lot. 

 

When will this be resolved? Why is Canon seemingly incapable of keeping their software up-to-date?

De facto, the almost brand-new camera is now not useable anymore.

94 REPLIES 94

Yes.  Unfortunately, the threads title didn't say that.

(In)compatibility of EOS Utility with MacOS Ventura

~Rick
Bay Area - CA


~R5 C (1.0.9.1), ~R50v (1.1.1) ~RF Trinity, ~RF 100 Macro, ~RF 100~400, ~RF 100~500, ~RF 200-800 +RF 1.4x TC, BG-R10, 430EX III-RT ~DxO PhotoLab Elite ~DaVinci Resolve Studio ~ImageClass MF644Cdw/MF656Cdw ~Pixel 8 ~CarePaks Are Worth It

shadowsports
Legend
Legend

This is nothing new.  It happens every time Apple releases a new OS.  Camera's stop connecting, printer's stop printing, and webcams stop running.  We all know this.  It happens over and over.  A conservative approach might be to test or wait.

Software development.  "Canon should have had this working on day 1".  Maybe they did, maybe Apple added a feature or changed something that broke the WebCam Utility?  We don't know, so its unfair to blame a vendor who doesn't control what Apple releases.     

It's ok to be an early adopter, but you need to accept that some stuff may not work or that some software and/or devices might have issues.  No vendor can test every software and hardware scenario prior to a operating system's release.  With this in mind, I do not recommend upgrading a software environment on a mission critical or production system (one you depend on for income or work) until you've had a chance to test or ensure all of the hardware and software applications you depend on function properly.  You can take steps to avoid these situations.  A great way to mitigate this risk is by making a time machine back up of your working environment so you can revert back (just in case) things don't go as planned.

~Rick
Bay Area - CA


~R5 C (1.0.9.1), ~R50v (1.1.1) ~RF Trinity, ~RF 100 Macro, ~RF 100~400, ~RF 100~500, ~RF 200-800 +RF 1.4x TC, BG-R10, 430EX III-RT ~DxO PhotoLab Elite ~DaVinci Resolve Studio ~ImageClass MF644Cdw/MF656Cdw ~Pixel 8 ~CarePaks Are Worth It

“Software development.  "Canon should have had this working on day 1".  Maybe they did, maybe Apple added a feature or changed something that broke the WebCam Utility?  We don't know, so its unfair to blame a vendor who doesn't control what Apple releases.”

I agree.  Every camera vendor is probably riding the same merry-go-round.  A new OS more than likely means negotiating a new licensing agreement for the new OS.  That is the Apple business model.  

Furthermore, it should be obvious that it is NOT in Apple’s best interests for third party camera software to work properly.  Apple would prefer that you purchased your next camera from Apple, not Canon, Sony, or Nikon.  Apple would prefer that you kick third party gear to the curb entirely.

For the record, this is at least the 4th time that Apple has broken their own codebase in the past 12 months or so alone.  Any software developer would tell you that breaking your existing codebase is a major no-no, a cardinal sin.  Apple does it all the time to manufacturer’s of third party cameras.  All the time.

[EDIT]. What good is a software development package release 6-12 months ago when there have 3-4 major updates since the release of that version of the development package?  

Every time Apple releases an OS upgrade, third party manufacturers have BUY the upgraded software development package from Apple.  I have no idea how much an Enterprise level license from Apple would cost, but I am sure that it would be on the order of tens of thousands of dollars per seat/developer.

--------------------------------------------------------
"Enjoying photography since 1972."

johnrmoyer
Whiz
Whiz

EOS Utility 3 no longer works with EOS R5 camera after upgrade to macOS Ventura. The USB C cable is configured to charge only and not data.

The Android file transfer app also cannot access the USB C port.

The EOS 3 utility does more than transfer photos. It can also set the date/time on the camera from the computer date time and change various camera settings. It is a pain for it not to be working. It appears to me to be a permission problem with the USB port. Plugging the USB cable into the camera disables all of the menus on the camera and does charge only.

 

NVRAM reset fixed Android File Transfer but not EOS Utility 3. Image Capture app does see the camera when the USB cable is connected.

Missing functionality for me is ability to use EOS Utility 3 to change Date/time in camera and update IPTC info in camera.

Both Android File Transfer and Canon EOS Utility 3 were broken by the update to Ventura. Resetting NVRAM fixed Android File Transfer, but not EOS Utility 3.

I have the free Apple Developer login and development tools, but do not pay to have any software on the App Store.

Apple needs to work on their software testing and release. This is just poor software engineering.

 

How is it Apple's problem?  Apple provides ample developer previews along with public betas of the OS each year.  It's up to Canon and actual software vendors to test ahead of time.

And to file bugs with Apple for those cases where bugs were introduced by Apple.

There are basically two types of companies out there regarding software: proactive and reactive.  Hopefully Canon will become proactive in the future.

--
Ricky

Camera: EOS R5 II, RF 50mm f/1.2L, RF 135mm f/1.8L
Lighting: Profoto Lights & Modifiers

It is an Apple problem because when I contacted Apple support I was told to reset NVRAM. Resetting NVRAM fixed Android File transfer and enabled the image capture app to talk to my camera. That should have been done during the upgrade if necessary. The last time I produced such a bug in released software was 1985.

Apple broke applications with their update.

 

johnrmoyer
Whiz
Whiz

After resetting NVRAM on my iMac, deleting EOS Utility3, downloading and installing EOS Utility 3 for macOS 11, now it works again. I hope this might be helpful for someone else.

Holiday
Announcements
12/15/2025: New firmware update available for EOS C50 - Version 1.0.1.1

11/20/2025: New firmware updates are available.

EOS R6 Mark III - Version 1.0.1

EOS R3 - Version 2.0.0

EOS R1 - Version 1.2.0

EOS R5 Mark II - Version 1.2.0

EOS R5 - Version 2.2.1

PowerShot G7 X Mark III - Version 1.4.0

PowerShot SX740 HS - Version 1.0.2


10/21/2025: Service Notice: To Users of the Compact Digital Camera PowerShot V1

10/15/2025: New firmware updates are available.

Speedlite EL-5 - Version 1.2.0

Speedlite EL-1 - Version 1.1.0

Speedlite Transmitter ST-E10 - Version 1.2.0


07/28/2025: Notice of Free Repair Service for the Mirrorless Camera EOS R50 (Black)

07/24/2025: New firmware updates are available.


07/23/2025: New firmware updates are available.

EOS R5C - Version 1.1.1.1

EOS C80 - Version 1.0.3.1


7/17/2025: New firmware updates are available.

EOS R7 - Version 1.7.1

EOS R10 - Version 1.7.0

EOS R8 - Version 1.5.0

EOS R50 - Version 1.4.0

Powershot V10 - Version 1.4.0

Powershot V1 - Version 1.1.0

EOS R50V - Version 1.1.1


05/21/2025: New firmware update available for EOS C500 Mark II - Version 1.1.5.1

02/20/2025: New firmware updates are available.

RF70-200mm F2.8 L IS USM Z - Version 1.0.6

RF24-105mm F2.8 L IS USM Z - Version 1.0.9

RF100-300mm F2.8 L IS USM - Version 1.0.8

RF50mm F1.4 L VCM - Version 1.0.2

RF24mm F1.4 L VCM - Version 1.0.3


01/22/2024: Canon Supports Disaster Relief Efforts in California
01/14/2025: Steps to resolve still image problem when using certain SanDisk SD cards with the Canon EOS R5 Mark II