P: After the new version "update” today — “Unexpected error opening catalog.”

Same here. Freshly installed Adobe Creativity Cloud (including a lot of other acc apps - Ps Ai In and so on). Restart doesn't help. Optimizing of the Catalog in 9.4 doesn't help. Same on moving catalog to another place ... nothing helps.

EVEN CREATING A NEW CATALOG DOESN'T WORK!
Starting of Version 10 isn't possible at all!

Great work Adobe! 😉

I'm using macOS 10.15.7 on an iMac 2019

No solution to offer, just commiseration. LRc10 works fine on my Late 2016 MacBook Pro and it will convert LRC9.4 .lcat to LRc10.

Problem with my 2019 Mac Pro - initial upgrade to LRc10 app and .lcat went fine, no problems for perhaps a week. Then restarted 2019 Mac Pro and immediately ran into the 'can't open catalog' error - any and all .lcats. Copied 9.4 primary .lcat from 2019 Mac Pro to MacBook Pro laptop; it converted and opened primary .lcat in LRc10 (no images of course - an experiment not a solution). So it seems to me not to be a catalog problem.

Have had three, hours-long tech support sessions with Adobe tech support, to no avail. They tried everything it seems, without success. At the moment they are running diagnostics on my primary .lcat.

So, reinstalled LRc9.4 and continue to import/edit/print. Lightroom Sync does not work for me with LRc9.4 - other Adobe tech support issue they couldn't resolve. It worked for many months and then one day, gone. May have to go back to LRc9.3 and see if Lightroom Sync is there.

Not the end of the world, can get my work done, but a big sinkhole of time.

(Negative) update: Big Sur beta 2 does not fix this.

Just tried the same since I have tagged most of the known faces in my catalog and it works as expected in LR 10 for me, but, I also have all the xmp files that I export for 3rd party apps.

Latest Catalina on a MacBook Pro. Catalog was upgraded to v10 from 9.4.

A rollback won't work for me, since I move the disk with catalog + masters between two computers, one of which successfully upgraded to v10, and one of which didn't.

niallm: Most people here want advice on a fix, so pardon my confusion. You could just contact Adobe support also. You don't have to get snippy about your currency.

Agree! That's the spirit. Helping each other that way. 👍

Dear Carlos,

1) My currency is not the dollar.

2) I am, in some sense, an "IT guy"; this is not an "IT guy" problem, it is an application level problem.

3) I post here, not particularly in the hope of receiving actionable advice, but in the spirit of letting Adobe know that more people are suffering from this problem.

NRM

Best advice: call a Mac IT guy to come over. It’ll be the best $200 you ever spent!