fbpx
3 Post Moderation Rule for New Boarders (25 Jan 2021)

New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.

Final Cut won't open - 'resolving windows'

More
16 Jan 2014 14:10 #39057 by giannis911
I had this issue, even though it resolved, now it's back again.

Final Cut Pro X 10.1 opens, but is stuck on the splash opening window, saying 'restoring windows layout'. I can actually work around in the software (til certain extent) but not do things such as exporting movies.

Is there a solution to this problem?

Please Log in to join the conversation.

More
16 Jan 2014 17:20 #39075 by ronny courtens
Hi Giannis,

In the Finder, hold down the Option key and then choose Library from the Go menu.
In the Library folder that opens, go to Application Support > Final Cut Pro.
Drag the Layouts folder from the Final Cut Pro folder to the Trash.
Then launch FCPX.

Does that solve the problem?

- Ronny

Please Log in to join the conversation.

More
16 Jan 2014 17:23 #39077 by giannis911
Hi Ronny,

I've tried that and , unfortunately, it doesn't help.

I also tried reinstalling the software (from the App store) but no difference either.

Please Log in to join the conversation.

More
16 Jan 2014 17:35 #39081 by ronny courtens
Removing and re-installing FCPX is indeed the next step.

But just to make sure: did you also delete the Caches and Prefs folders before re-installing? If you only delete and restore the application this won't help solving any issues. Check this article for full de-installing and re-installing of FCPX in Mavericks:

support.apple.com/kb/HT5149

In the document click on the triangle next to "Removing FCPX in OSX Mavericks".

When FCPX has been completely removed, then try re-installing and see if this solves your issue.

- Ronny

Please Log in to join the conversation.

More
16 Jan 2014 18:04 #39091 by giannis911
I read that article, and followed the instructions. But still no solution.

Please Log in to join the conversation.

More
16 Jan 2014 18:08 #39094 by ronny courtens
Ouch, I'm afraid we are heading for a Mavericks issue that some other people are having as well.

To test this: create a new user account and launch FCPX as the new user. Does FCPX open correctly now?

- Ronny

Please Log in to join the conversation.

More
17 Jan 2014 11:16 #39170 by giannis911
I created a new account and Final Cut opened, once only. Now it's stuck on the same window.

Any ideas?

Please Log in to join the conversation.

More
17 Jan 2014 11:26 #39171 by ronny courtens
Is App Nap disabled for FCPX?

- Ronny

Please Log in to join the conversation.

More
17 Jan 2014 12:37 #39174 by giannis911
I disabled it now, but still the same issue.

Please Log in to join the conversation.

More
19 Jan 2014 12:37 #39298 by ronny courtens
Sorry for the late reply.

When you have installed Mavericks, did you do a clean install (i.e. wipe your boot drive and re-install from scratch), or did you install it over Mountain Lion?

- Ronny

Please Log in to join the conversation.

More
20 Jan 2014 18:39 #39348 by Ferdewyn
I had a similar issue just recently and following these steps fixed it for me:

support.apple.com/kb/TS4169

Best wishes!

Please Log in to join the conversation.

More
08 Feb 2014 09:59 #40761 by giannis911
I missed your replies, so sorry..!

But, I've managed to get Final Cut to open - by creating another user account. Removing the layouts folder didn't help, I already tried that several times.

Ronny, I installed Mavericks on top of Mountain Lion.

It's a strange issue - but creating another user account seems to help though.

Please Log in to join the conversation.

More
08 Feb 2014 10:55 #40764 by ronny courtens
It's a known issue. Many people don't have any problems after having installed Mavericks over an older OS, some do. And if this happens it also affects FCPX in different ways. If everything works correctly with a new user account this often indicates that the issue is related to conflicting preference and .lock files between your Mavericks installation and the old OS, and until now a clean install of Mavericks (after wiping the boot drive clean) seems the only way to really solve this.

- Ronny

Please Log in to join the conversation.