topic Re: EOS Utility 3 and macOS Mojave in Camera Software

EOS Utility 3 and macOS Mojave

yosser29 — Fri, 09 Nov 2018 10:56:53 GMT

Hi had a look through the forum and cannot see anything that might help so have to ask for assistance.

Just purchased a 5D Mk4 and loaded the latest EOS Utility 3, my macbook is running the latest version of macOS Mojave 10.14 but as soon as the camera is connected the EOS Utility crashes.

Downloaded the latest version of Utlity 3 from the canon website but still crashes.

Seems there is incompatabilty betweet Mojave and Uitility 3.

Is there a solution to this or is it Canon dragging their heels with a viable software update?

Re: EOS Utility 3 and macOS Mojave

RobertTheFat — Fri, 09 Nov 2018 13:52:09 GMT

It appears (to a Windows user who has been reading this forum for several years) that every version of macOS is incompatible with its predecessor. If so, that's hardly Canon's fault.

Re: EOS Utility 3 and macOS Mojave

ebiggs1 — Fri, 09 Nov 2018 13:52:41 GMT

It isn't Canon, it is Apple. This happens every time they "update" the OS. No surprise this time either.

Re: EOS Utility 3 and macOS Mojave

Waddizzle — Fri, 09 Nov 2018 15:14:34 GMT

Apple’s version of virus protection means periodically breaking the codebase, which kills most viruses.

Re: EOS Utility 3 and macOS Mojave

RobertTheFat — Fri, 09 Nov 2018 17:36:38 GMT

@Waddizzle wrote:
Apple’s version of virus protection means periodically breaking the codebase, which kills most viruses.

Whereupon the hastily added modifications that application writers are forced to incorporate into their code may help to restore the risk.

Re: EOS Utility 3 and macOS Mojave

yosser29 — Fri, 09 Nov 2018 17:36:57 GMT

Thanks for the responses, however it does not affect Utility 2 I have for my 70d that still works perfectly, so I assumed it was the Canon software. I will run it past Apple techs to see if anything can be resolved.

Re: EOS Utility 3 and macOS Mojave

RobertTheFat — Fri, 09 Nov 2018 17:43:21 GMT

@yosser29 wrote:
Thanks for the responses, however it does not affect Utility 2 I have for my 70d that still works perfectly, so I assumed it was the Canon software. I will run it past Apple techs to see if anything can be resolved.

Be sure you install the version of EOSU 3 that includes a re-installation of EOSU 2. The idea is that when you call EOSU 3, there's a control program that decides, based on the camera you're using, whether you need EOSU 3 or EOSU 2. If it doesn't all match up properly, bad things can happen. At least that's how it works in Windows. YMMV.

Re: EOS Utility 3 and macOS Mojave

yosser29 — Fri, 09 Nov 2018 17:59:23 GMT

Thanks Bob latest sw from canon does indeed include u2 and u3. Which is what I have loaded.

Re: EOS Utility 3 and macOS Mojave

TCampbell — Fri, 09 Nov 2018 23:13:28 GMT

I'm not sure why anytime someone posts a question about macs, it turns into an OS bashing session (which really isn't helpful). I find this interesting considering those casting aspersions don't actually seem to be qualified to do so.

You're also supposing that a person wouldn't have these problems if they ran Windows (they'd have more problems).

Quite a bit of research has been done in this area of mac vs. PC stability, security, total cost of ownership, etc. The mac wins ... and usually by quite a wide margin.

Some of this is Apple's corporate culture of being fanatical about quality. But there's also a lot to be said for the fact that it runs a Unix variant (Unix is inherently a lot more stable.)

With all the bashing, nobody actually knew enough to offer helpful advice.

I've been running Mac OS X since version 10.2 (2002). I have never had an upgrade break a system nor any software. This includes when Apple switched from using IBM 'POWER' processers to Intel processors and yet still continued to support "universal binaries".

Apple has had all 64-bit hardware and software for many years. There are application developers who have really lagged at rebuilding for 64-bit (often that just ammounts to a recomplile). Apple has announced the end of 32-bit support. Apple announced in 10.13 (High Sierra) that they'll be ending support for 32-bit apps (10.13 and 10.14 still support it) but they promise that 10.15 will NOT support 32-bit apps (which is fair considering developers have had a couple of years of notice.)

Canon's mac software is all 64-bit as long as you've been keeping up with updates ... and it should be working fine. If not, make sure you update to the latest versions. macOS Mojave wants everything to be 64-bit (although it is possible to run 32-bit ... it is no longer recommended.)

There are some simple tests to debug issues with problematic software on a Mac.

Macs don't really have a concept of a "registry" like Windows PCs (where a single file maintains configuration of everything). Instead, each application uses something called a ".plist" file. It is possible for an application to corrupt a plist. Unofrunately applications don't really tell you the name(s) of the files they use (but you can figure it out). The nice thing about these being separate files is that it's easy to reset the file without impacting any other application (on Windows, where all these settings are in the global registry, this is much more difficult problem to solve.)

The easiest thing to do is to create a temporary user on the machine, log in as that user, and test the software. If it works fine on a different user account, that tells you there's nothing wrong with the mac, there's nothing wrong with the application... the issue is either (a) a corrupt plist file or (b) some *other* software running at the same time which is creating a conflict.

plist files are generally located in the /Users/<your_username>/Library/Preferences (plist means "property list" ... it's the "settings" file for the application.)

On my own mac (under the user's ~/Library/Preferences folder), I see:

com.canon.Digital Photo Professional Batch.plist

com.canon.Digital Photo Professional.LSSharedFileList.plist

com.canon.Digital Photo Professional.plist

com.canon.Digital-Photo-Professional-4-Batch.plist

com.canon.Digital-Photo-Professional-4.plist

com.canon.EOS Utility 2.plist

com.canon.EOS-Utility-3.plist

com.canon.EOS-Utility.plist

com.canon.EOSMOVIEUtility.plist

com.canon.GpsDeviceSetter.plist

com.canon.GpsLogFileImporter.plist

com.canon.MapUtility.plist

com.canon.PhotoStitch.plist

com.canon.PictureStyleEditor.plist

jp.co.canon.CNPSPMAIN.plist

jp.co.canon.Easy-PhotoPrint EX.plist

jp.co.canon.IJNetworkTool.plist

jp.co.canon.PluginInstallerforPrintStudioPro.plist

jp.co.canon.ic.camerasurveyprogram.plist

jp.co.canon.ij.easy-guide-viewer.plist

An easy way to get the list is to launch the "Terminal" utility, then type

cd ~/Library/Preferences

ls *canon*

The names give away the app they are associated with. I've highlighted the EOS Utility related files in red. You can (a) make sure the applications that use these files aren't running (quit out of EOS Utility), (b) drag these files out of the folder (e.g. drag them to the desktop, etc.) then (c) re-launch the application. This will force the application to create a new replacement plist file with all default settings.

Most of the time that fixes the problem... but if you see no difference in behavior, you can drag the originals back into the folder. If it does fix the problem, you know the old plist file was the problem and can just delete the old files (no need to save them.)

Applications *can* put important configuration files elsewhere and, just occasionally, I run into that (in other words clearing the plist files in the "preferences" folder doesn't clear the problem even though it is a problem local to that user -- the developer just used a different location to keep their files.)

Sometimes a different application can create a problem (e.g. when more than one application tries to grab the same device). You would want to make sure no other camera-related software is running nor will be auto-launched when you connect the device.

There are a few more advanced troubleshooting techniques which I'll skip for now. Since the Mac is a Unix system, there are lots of Unix utilities that can help track down what the system is doing.

I should add... anytime there is an issue with a device connected via USB (PC or Mac), make sure there is no "USB hub" involved. Connect the device directly to the computer. While you would think using a hub shouldn't be a problem (and if it's a good hub, it wont be a problem), there are a lot of flakey USB hubs that cause problems.

Re: EOS Utility 3 and macOS Mojave

yosser29 — Fri, 09 Nov 2018 23:37:23 GMT

Thank you for the very comprehensive solution, I intend to follow your advice and will report back in due course.

Re: EOS Utility 3 and macOS Mojave

Waddizzle — Sat, 10 Nov 2018 00:10:10 GMT

“I'm not sure why anytime someone posts a question about macs, it turns into an OS bashing session (which really isn't helpful). I find this interesting considering those casting aspersions don't actually seem to be qualified to do so.“

If it sounded like I was bashing the OS, that was not my intent. I think Apple’s approach is highly effective against rouge software.

Re: EOS Utility 3 and macOS Mojave

johwiltb — Sat, 24 Nov 2018 22:14:11 GMT

This worked perfectly. Thank you, and yes, I agree, the bashing is very unhelpful...I wish this was just at the top and I didn't have to wade the hateful waters to find it

Re: EOS Utility 3 and macOS Mojave

larrylilac — Fri, 14 Dec 2018 11:42:05 GMT

Worked for me too on 10.14 Mojave, using the latest version (3.9.0) of Canon EOS Utility.

Re: EOS Utility 3 and macOS Mojave

sonny1751 — Sat, 15 Dec 2018 14:52:02 GMT

I also cannot use the Remote shooting Utility with a 7Dii or a 5Diii useing any Canon softwear on MacOS 10.14 Mojave. As of 15 Dec 18 Canon support site states

"This software is not supported with the operating system selected and is not available for download."

Anyone know a work around in order for me to get back to work?

Re: EOS Utility 3 and macOS Mojave

yosser29 — Sun, 30 Dec 2018 15:54:35 GMT

The canon site now says this software is now supported by your OS Mojave? How is that? not updated any software from either apple or canon yet they suggest you do not need any additional drivers. Rubbish, still doesn't work Utility 3 still crashes as soon as I turn the camera on.

Re: EOS Utility 3 and macOS Mojave

sonny1751 — Sun, 30 Dec 2018 17:40:06 GMT

Canon site states
“Canon has not yet determined if this product will be compatible with the operating system selected. Please refer back to this site in the near future for updates”
But don’t hold your breath, as of 30/12/18 that have only got this far,
“Mac OS X 10.6 (Snow Leopard)
Mac OS X 10.7 (Lion)
OS X 10.10 (Yosemite)
OS X 10.11 (El Capitan)
OS X 10.8 (Mountain Lion)
OS X 10.9 (Mavericks)

Re: EOS Utility 3 and macOS Mojave

trthigp — Mon, 31 Dec 2018 16:11:16 GMT

How does this solve the issue if this is your first canon camera and you dont have any previous versons of the canon utility app and you are running mojave? I have not been able to get my computer to work with my canon m50 since the begining.

Re: EOS Utility 3 and macOS Mojave

RahulBhide — Sat, 19 Jan 2019 12:18:40 GMT

Tim, you seems to have a lot of knowledge on this subject. I am having issues with DPP on mojave. I cannot delete photos and the program shuts down unexpectedly. Would you know what the issue is and if so is there a solution. Based on the Canon website there is no DPP version compatible with Mojave. Also do you know if Canon is updating DPP to work with Mojave? Thanks in advance.

Re: EOS Utility 3 and macOS Mojave

ManiT — Sun, 20 Jan 2019 17:37:54 GMT

All,

For Mac OS Mojave, I have reinstalled EOs utility from https://support-in.canon-asia.com/contents/IN/EN/0200544302.html

This works !!

Try this.

Regards,

Mani

Re: EOS Utility 3 and macOS Mojave

RahulBhide — Mon, 21 Jan 2019 07:22:08 GMT

Hi Mani,

Thank you so much for your help regarding the EOS utility. Does the same apply to DPP and are you having any issues with DPP?

Thanks Rahul