Currently Being ModeratedSep 7, 2013 8:22 AM (in response to Alvin Koh)
Perhaps the Mavericks installer will not contain the bug that is causing our problems. We may just have to wait for that to get both QuickTime functioning with the desired level of security.
Currently Being ModeratedSep 7, 2013 2:30 PM (in response to Alvin Koh)
The trouble seems to be that those components get installed by the Security Update or the way you are doing it, but then they somehow get removed and QuickTime crashes when it needs the missing resources.
For some reason the pre Security Update version of those components are not similarly affected.
I am baffled. You, me, and several, perhaps many others, are experiencing this problem, but the vast majority of users are not.
Currently Being ModeratedSep 7, 2013 2:38 PM (in response to Linc Davis)
I agree. Do you think the a clean install might allow the installation of the security update without a future incident? I would try it, but I do not understand the details of a clean install and I find that daunting. For example: Will I have to set up my users again? Will I have to redo all f my setting such as the Network setting? Or could I migrate those things from my other startup drive?
I've got things working without crashes now, albeit without the latest security improvements, and I don't want to make further changes unless I know exactly what is entailed. The Apple description of a clean install is silent on these points.
Currently Being ModeratedSep 7, 2013 3:38 PM (in response to kingfisher500)
A clean install means that you erase the boot volume and reinstall the OS. None of your data is preserved. You have to restore it from a backup. I don't know whether that procedure will have any effect. This thread has been going on so long I don't remember whether I suggested it.
Currently Being ModeratedSep 8, 2013 10:53 AM (in response to Linc Davis)
You conditionally suggested it in your second message on page 2 of this thread.
I have a Time Machine backup, but I am not eager to do a clean install and then restore third party applications one by one.
Currently Being ModeratedSep 8, 2013 4:46 PM (in response to kingfisher500)
I agree. In my case, and I believe for most of the others as well, the problem only started after applying that Security Update. The update may have corrupted our installation for some reason but it is not feasible to do a clean install every time such things happen. Apple needs to fix this.
Currently Being ModeratedSep 8, 2013 5:14 PM (in response to Alvin Koh)
Download and reinstall security update 2013-003. If this is previously suggested, apologies. This only worked for me a few days at a time, then something triggered it again. This ultimately bothered me so much, I clean installed 10.8.4. Make sure you have a good backup and deauthorize itunes, deactivate your licenses, back up your emails, etc. and have all the license keys. So far, so good.
Currently Being ModeratedSep 8, 2013 6:03 PM (in response to themacjedi.com)
Before I started using Pacifist to install just the Frameworks portion, I used to run the Security Update to fix the issues. What I found is that you do not need to restart. I just force quit the Security Update installer once it is done.
Currently Being ModeratedSep 9, 2013 2:01 AM (in response to Alvin Koh)
I believe my 2008 mac pro came with Leopard on it. I upgraded to SL, then L, then ML. Once this security update thing started to happen, ML and some programs really began to misbehave. QT or Pro would not play videos, iTunes was funny, Office 2011 would not save new files correctly, and some of my hard drives began to thrash for no reason at all - were not indexing in Spotlight.
I thought it may have been hardware, but the clean install fixed everything. The machine is amazingly quiet and remarkably fast. Too much happens over 5 years I guess and 3 OS upgrades on top of it all.
I may do a clean for Mavericks when it comes out.
Currently Being ModeratedSep 9, 2013 2:24 AM (in response to TStam)
Interesting. I'm also using a 2008 Mac Pro. With ML I started see application crashes in Mail, Microsoft Office, Safari and now QuickTime Player. I don't have such issues with ML on my 2010 Macbook Pro or Macbook Air. Perhaps there is some conflict with the older Macs.
Currently Being ModeratedSep 9, 2013 3:07 AM (in response to kingfisher500)
I have tried the clean install and brought everything up to date including Skype and the Security Update, and QuickTime still broke after about two days.
My solution was to do an install of 10.8.0 Mountain Lion over the top of my current install, and install Skype 6.3 (which does not cause QT to break) and as a precaution, I skipped installing Security Update 2013-003.
Since mid-July, my big cat has been purring along nice and smooth, just the way it's meant to be
Currently Being ModeratedSep 9, 2013 3:28 AM (in response to XENiCraft)
Interesting. I have not reinstalled Skype (don't really use it much) since my clean install of 10.8.4+Security and all is good so far (about a week). However, previously when I was trying the reinstalls on top of ML and reinstalling the security update versus clean install I had completely uninstalled Skype (before reinstall to 10.8.4) and it DID break again. I did not try leaving it at 10.8.0 like you. From your info it seems like there may be more than one culprit/combo related to 10.8.4 and the security update. I'm not sure what to make of Skype.
Also, I have a 2009 macbook pro, with 10.8.4+Security, no Skype ever with no problems at all.
Too many variables so far for a controlled experiment, but getting closer I think.
Currently Being ModeratedSep 9, 2013 3:37 AM (in response to TStam)
Oops. Sorry I wasnt clear.
I reinstalled 10.8.0 over the top, then updated to 10.8.4, and installed Sype 6.3.
Originally I thought it was Skype as there was another huge thread i contributed to on the Skype forums where evidence observed by myself and another user seemed to point to Skype version 6.6 as the cultprit, but now as others are having the same symptoms without any Skype, my finger has now swung to point the blame on Security Update 2013-003.
I always suspected it due to the many notes in it about QuickTime, but I was never sure until now.
I have a late 2009 27-inch iMac Core2Duo 3.06ghz 8gb RAM
and an early 2009 MacBook Pro 17-inch 2.93ghz 4gb RAM.
They both experienced the same issues.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points