Lightroom has blank dialog after splash screen, cannot create new catalog

[XploreDesign]

After upgrading to LR 2015.7 (*CC) (Mac OS 10.10.5) I now get a blank grey start box, cannot create a new catalog I can select this option, but it renders no new dialog box, cannot access preferences, the app is essentially useless. I have uninstalled and re-installed now twice, same result.

[F. McLion]

Please try to reset your preferences: Resetting Preferences in Lightroom CC/6

They are NOT reset by uninstalling and reinstalling.

[XploreDesign]

I am sorry I neglected to mention that I did this prefs reset step already. I tried it again, but I still net the exact same grey screen result.

[F. McLion · Accepted solution]

How about holding down the Opt key while starting LR?

What happens if you try to start LR by (double-)clicking on an existing catalog (*.lrcat)?

[mike_morrison]

I am having the same issue.

I tried to launch LR with the catalog as you suggested and that did not work either.  So far this is everything I have tried.

1. Reset preferences

2. Uninstalled LR and re-installed.

3. Tried starting LR from the catalog file.

4. Renamed the creative cloud db file in the library and restarted.

Photoshop, Bridge and Camera Raw work fine.   Lightroom on my Windows pc works fine after the upgrade, only issue is with my Mac.

-Mike

[dj_paige]

As an experiment, disconnect from the Internet, turn off the firewall and virus checker, and then try launching Lightroom.

[mike_morrison]

That was a good thought but, it didn't work.

I now removed LR CC and installed LR6.  Still the same issue.  This was working fine before the recent update.

[mike_morrison]

I have it working.

I removed LR6 and re-installed LR CC.  Then opened LR and held down CMD + SHFT + O which forces LR to open a different catalog.  It re-launched LR and all is well.  I assume my original catalog is corrupt.

-Mike

[XploreDesign]

I did not re-install, but held opt/alt  (As recomm by FC.McLion)  and it seems to have solved the problem. Terribly frustrating issue. Finally solved, thanks to all who chimed in.