Is Aperture Quitting After 3.4.2 or 3.4.3 Update? Here’s the Fix.
By PhotoJoseph
November 15, 2012 - 4:39pm
There have been reports of Aperture quitting after an update via the Mac App Store, and it turns out that Apple posted a KB (Knowledge Base) article about it a few days ago.
In a nutshell, if you are quitting on launch, then just throw away the Aperture app itself (not your Library!), and re-download from the App Store.
Here are the complete instructions, as posted at support.apple.com/kb/TS4471. Let us know in the comments if this is something you’ve run into, and if this helps!
Symptoms
After updating to Aperture 3.4.2 via the Mac App Store, Aperture may quit when you open it.
Resolution
To resolve the issue, follow these steps to reinstall Aperture:
- In the Finder, choose Applications from the Go menu.
- Move the Aperture application to the Trash. Note: This will not remove or affect any of your photos or Aperture libraries.
- Open the App Store. Make sure you are logged in with the same Apple ID you used to purchase Aperture. If not, choose Sign In from the Store menu.
- Click the Purchases button at the top of the App Store window.
- In the list of your purchased apps, click the Install button to the right of Aperture. Note: If you don’t see Aperture listed you may have hidden it. See Mac App Store: Hiding and unhiding purchases for more information.
Comments
on November 16, 2012 - 9:03am
Is it not better to wait until Apple resolve the issue rather than reinstall. I only have the disc version & to have to install this & all of the updates again seems a lot of work.
I think I may hang on for this update.
on November 16, 2012 - 9:49am
John,
If you installed from a DVD originally, then it’s my understanding that this issue can not affect you. If you’re crashing on launch, and your original purchase/install was from a DVD, then you may have a different issue.
And as far as Apple fixing the issue — it is fixed, and that’s why you need to re-download. A future update won’t fix it. There is something wrong with the binary (the app itself) that happened during update and the only solution is to download another copy.
Incidentally the updater itself appears to have been fixed, so if you haven’t yet updated, it should be safe to do so now.
@PhotoJoseph
— Have you signed up for the mailing list?
on November 24, 2012 - 6:16am
Many thanks Joesph. I will get on with the update now.
John