Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases OS X 10.10.5 With DYLD Vulnerability Patch, Bug Fixes
- Thread starter MacRumors
- Start date
- Sort by reaction score
By the way, you didn't actually destroy the Apple products did you? I hope you meant that you sold them.
Yah I know. I still would have destroyed everything. If I had kept all my thunderbolt displays and the dozens of airport time capsules, and all the computers it just would have reminded me everyday of my anger towards them. I still love them, but they have let me down big time.
Yep. Destroyed. Hammer+Gasoline+Matches=Now in some dumpster behind Chipotle waiting to be taken to the landfill.
I installed the update through the app store. Then I installed iMovie and it won't start.
My Windows phone app from the mac store also refuses to start.
iMovie gives this error:
14/08/15 22:43:10,000 kernel[0]: int _validateCodeDirectoryHashInDaemon(const char *, off_t, uint8_t *, int *): verify_code_directory returned 0xfffffed0
14/08/15 22:43:10,000 kernel[0]: proc 630: load code signature error 4 for file "iMovie"
14/08/15 22:43:10,450 taskgated[92]: killed com.apple.iMovieApp[pid 630] because its use of the com.apple.developer.maps entitlement is not allowed (error code -67063)
14/08/15 22:43:10,451 com.apple.xpc.launchd[1]: (com.apple.iMovieApp.56548[630]) Service exited due to signal: Killed: 9
14/08/15 22:43:22,172 Console[635]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
14/08/15 22:43:30,000 kernel[0]: int _validateCodeDirectoryHashInDaemon(const char *, off_t, uint8_t *, int *): verify_code_directory returned 0xfffffed0
14/08/15 22:43:30,000 kernel[0]: proc 638: load code signature error 4 for file "iMovie"
14/08/15 22:43:30,886 taskgated[92]: killed com.apple.iMovieApp[pid 638] because its use of the com.apple.developer.maps entitlement is not allowed (error code -67063)
14/08/15 22:43:30,886 com.apple.xpc.launchd[1]: (com.apple.iMovieApp.56548[638]) Service exited due to signal: Killed: 9
And the windows phone app gives:
15/08/15 23:39:25,000 kernel[0]: int _validateCodeDirectoryHashInDaemon(const char *, off_t, uint8_t *, int *): verify_code_directory returned 0xfffffed0
15/08/15 23:39:25,000 kernel[0]: proc 947: load code signature error 4 for file "Windows Phone"
15/08/15 23:39:25,844 com.apple.xpc.launchd[1]: (com.microsoft.Windows-Phone-7-Connector.50584[947]) Service exited due to signal: Killed: 9
It won't start any more.
Did my update went wrong? Should I try to do it again with the combo update?
My Windows phone app from the mac store also refuses to start.
iMovie gives this error:
14/08/15 22:43:10,000 kernel[0]: int _validateCodeDirectoryHashInDaemon(const char *, off_t, uint8_t *, int *): verify_code_directory returned 0xfffffed0
14/08/15 22:43:10,000 kernel[0]: proc 630: load code signature error 4 for file "iMovie"
14/08/15 22:43:10,450 taskgated[92]: killed com.apple.iMovieApp[pid 630] because its use of the com.apple.developer.maps entitlement is not allowed (error code -67063)
14/08/15 22:43:10,451 com.apple.xpc.launchd[1]: (com.apple.iMovieApp.56548[630]) Service exited due to signal: Killed: 9
14/08/15 22:43:22,172 Console[635]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
14/08/15 22:43:30,000 kernel[0]: int _validateCodeDirectoryHashInDaemon(const char *, off_t, uint8_t *, int *): verify_code_directory returned 0xfffffed0
14/08/15 22:43:30,000 kernel[0]: proc 638: load code signature error 4 for file "iMovie"
14/08/15 22:43:30,886 taskgated[92]: killed com.apple.iMovieApp[pid 638] because its use of the com.apple.developer.maps entitlement is not allowed (error code -67063)
14/08/15 22:43:30,886 com.apple.xpc.launchd[1]: (com.apple.iMovieApp.56548[638]) Service exited due to signal: Killed: 9
And the windows phone app gives:
15/08/15 23:39:25,000 kernel[0]: int _validateCodeDirectoryHashInDaemon(const char *, off_t, uint8_t *, int *): verify_code_directory returned 0xfffffed0
15/08/15 23:39:25,000 kernel[0]: proc 947: load code signature error 4 for file "Windows Phone"
15/08/15 23:39:25,844 com.apple.xpc.launchd[1]: (com.microsoft.Windows-Phone-7-Connector.50584[947]) Service exited due to signal: Killed: 9
It won't start any more.
Did my update went wrong? Should I try to do it again with the combo update?
If by that you mean it's damn fugly, I agree.
Changing everything to be flat and ugly looking isn't a matter of "skimping". It's a matter of bad taste. Clearly, Johnny Ive's aesthetic skills lie in hardware design, not GUIs. Even so, I could tolerate Yosemite if they hadn't killed the classic stoplight "gem" buttons and turned them into Crayola Crayon flat color garbage. But as such, I never bothered to "upgrade" to something that has no real feature improvements (seeing as I don't own an iPhone, continuing on a Mac for a cheese ball mobile app has zero appeal to me and even less functionality).
You rate Mavericks lower than Yosemite and Mountain Lion and Snow Leopard and that makes no sense what-so-ever. Mavericks may have slightly less visual appeal than Mountain Lion (the opaque lighter colored dock bar mostly) but it added vastly improved multi-monitor support and that's a real improvement. Snow Leopard was fine, but it's OLD and it lacks a lot of features Mavericks has. Yosemite's new "features" were pretty much that iPhone continue your app on OSX and answer calls there plus ugly graphics. I saw no other real improvements. Where El Capitain has a chance to change all that (despite being ugly) is with METAL. A real solid graphics improvement and speed up for 3D in particular could potentially entice me to upgrade even with the ugly GUI.
Create a new user account, reboot and login to the new user account. See if the issues you are having happen in the new user account. The other thing you can try is boot into safe mode (hold shift key while booting) and see if the issues happen.
If by that you mean it's damn fugly, I agree.
Changing everything to be flat and ugly looking isn't a matter of "skimping". It's a matter of bad taste. Clearly, Johnny Ive's aesthetic skills lie in hardware design, not GUIs. Even so, I could tolerate Yosemite if they hadn't killed the classic stoplight "gem" buttons and turned them into Crayola Crayon flat color garbage. But as such, I never bothered to "upgrade" to something that has no real feature improvements (seeing as I don't own an iPhone, continuing on a Mac for a cheese ball mobile app has zero appeal to me and even less functionality).
You rate Mavericks lower than Yosemite and Mountain Lion and Snow Leopard and that makes no sense what-so-ever. Mavericks may have slightly less visual appeal than Mountain Lion (the opaque lighter colored dock bar mostly) but it added vastly improved multi-monitor support and that's a real improvement. Snow Leopard was fine, but it's OLD and it lacks a lot of features Mavericks has. Yosemite's new "features" were pretty much that iPhone continue your app on OSX and answer calls there plus ugly graphics. I saw no other real improvements. Where El Capitain has a chance to change all that (despite being ugly) is with METAL. A real solid graphics improvement and speed up for 3D in particular could potentially entice me to upgrade even with the ugly GUI.
So you need to be in agreement with a poster before you think their opinion makes sense? I don't agree with your assessment does that also mean that what you posted does not make any sense?
You don't like something, and you have made it very clear, (o the point that it just sounds like your ragging) about that regarding Yosemite, but that does not mean everyone else shares your opinion. In fact, I bet millions of people don't think Yosemite is ugly and I happen to be one of them. It's just that you won't see those people posting here because people that don't have problems with Yosemite don't usually post in this forum.
Last edited:
You realize that you could have clean installed OS X on the hardware and sold it. Such a waste. I really hope you were kidding.
I tried clean installs of OS X on all computers and they each failed multiple times on every device. I would wait several hours on each device before canceling and restarting the install process. My internet connection is ridiculously fast, my network connection is perfect and I worked with Apple support for so many countless hours to no avail.
Interestingly, I just began investigating Apple support and have discovered some very upsetting details. Apparently tech support does not work for Apple. I paid Apple a large warranty fee to give me tech support. I did not pay a third-party company to give me tech support.
Was it a waste? Yup. But contractually my devices cannot be resold. They must be terminated permanently after I am done using them.
It sounds like you were using the recovery partition to do the clean installs. Why not just download the Yosemite installer and create a bootable installer on a USB drive and install using that. Don't need a Internet connection to install, that is how I do clean installs. Can you provide a source where you found that Apple tech support does not work for Apple. I would be interested in reading about that.
What type of work do you do that require you to terminate the equipment on completion of use?
Last edited:
It would have been nice if I had a USB drive with Yosemite on it. But I didn't, and the App Store wouldn't download the Yosemite installer. It just wouldn't. It would sit there and get trapped in an infinite loop of downloading, restarting back to 0 bytes, and downloading again. I was getting blazing fast speeds elsewhere, it was just the App Store. I suppose I could have torrented a copy of Yosemite real quick and gone from there. But again...I pay the Apple premium because I expect it to just work. I pay extra so I don't have to find backdoor work-around fixes every couple months like I've been doing.
I can't provide a source, because my methods are less than legitimate. But perhaps someone that works for Apple can chime in and verify the following. From what I found Apple pays a company called Concentrix to independently train a team of tech support staff. They are trained to say "I work for Apple" but they do not. They use a program called iLog to create our case numbers that can be connected to Apple. And they use a program called iDesk to basically search for the problem we are calling about. iDesk essentially functions as a google search of the problem, except it is proprietary and internal. So basically I wasted my time with a company that lied and pretended to be Apple. And then after lying to me, they basically do a google search on iDesk while I wait on hold, and they search to find people with similar problems and give me a fix that they googled.
Again, do not accept this as true. This is just information that I gathered that has not been verified yet.
___________
Consulting
I ran into a similar problem since I was running the cache service in OS X Server. I dumped the cache and my endless update problem disappeared
The fact you just posted that opinion you claim no one posts disproves your own point.
Beyond that, what I was getting at could be stated as, what "massive departure" was he talking about? Yosemite is just a GUI modified version of Mavericks with a couple of small additions like the changeover mode from iOS App to OSX. In other words, other than the 2D look, what's so radically different about it? Or do you agree the look is the radical change, only that you happen to like the flat-world Crayola look with hard to read text?
The fact you just posted that opinion you claim no one posts disproves your own point.
Beyond that, what I was getting at could be stated as, what "massive departure" was he talking about? Yosemite is just a GUI modified version of Mavericks with a couple of small additions like the changeover mode from iOS App to OSX. In other words, other than the 2D look, what's so radically different about it? Or do you agree the look is the radical change, only that you happen to like the flat-world Crayola look with hard to read text?
Might want to figure out how to post without just sounding angry to the point that its comes across as ragging. I never said anyone had to agree with my opinion about Yosemite, and certainly I don't go into a continual angry diatribe.
Found out it was FileVault that prevented iMovie and some other apps from starting after updating to 10.10.5.
Turned FileVault of, re-installed the combo patch 10.10.5 and now it all works again
Turned FileVault of, re-installed the combo patch 10.10.5 and now it all works again
If I had your type of $, I would have done the exact same thing. My three Apple computers that I use for school/research have been out of commission all weekend and I've been on the phone with tech support for hours all weekend and received absolutely zero help.
For those of us still with the infinite download loop problem and the unresponsively slow App store installer downloads, I have a fix. I kept trying to reinstall OS X through Disk Utility but it would say "Estimated Time: Thousands of Hours." And every time I tried to download an installer through the App store it would download 1-2 kb/sec and then restart to zero bytes after a little while. Here is my fix.
1. Log into your router.
2. Change primary DNS to 8.8.8.8 and secondary DNS to 8.8.4.4 (These are the google DNS servers, write down default DNS to change back later if you want)
3. Restart computer, Command+R to boot into Disk Utility
4. Run a complete reinstall of OS X
5. Should bring you back up online to the latest OS X update 10.10.5
Nota Bene: This does not address the infinite download loop problem. This solution is basically a "**** it, let's start over" solution. I have no ****ing idea why I keep having to deal with infinite download loops on the App Store with every update. Thankfully, changing the DNS server to the google DNS brought my speeds back to normal when reinstalling on Disk Utility and when downloading through the App Store.
Note to Apple: Get yo **** together. Apple should=seamless user experience. You making all yo damn fancy watches and minis, and pros, and nano's, and macbooks. You should be throwing gajillions of dollars to make your bread and butter laptops and desktops a wonderfully easy and simple experience.
Oh. And can anyone explain why changing the DNS servers would have such a dramatic improvement in speed??? The rest of my network is fine. My speeds are crazy fast. It is just the App Store and reinstalling through Disk Utility that drags me down to 1-2 k/sec with an infinite download loop. I can't understand how changing my DNS would fix this.
Why don't you just get the standalone installers instead?
delta: https://support.apple.com/kb/DL1833?viewlocale=en_US&locale=en_US
or combo: https://support.apple.com/kb/DL1832?viewlocale=en_US&locale=en_US
Then you won't have to bother with the mac app store at all!
delta: https://support.apple.com/kb/DL1833?viewlocale=en_US&locale=en_US
or combo: https://support.apple.com/kb/DL1832?viewlocale=en_US&locale=en_US
Then you won't have to bother with the mac app store at all!
Apple uses cached servers in different geographic locations to host these downloads. The theory is that you are assigned to one of those servers based on the DNS server you use. So for example, if you use a DNS server from your local ISP in Dayton, Ohio, Apple would pipe you to their cached server that is closest to Dayton, Ohio. So if you are using some DNS server other than the default ISP DNS server, Apple's servers may get confused and think you are in a different geographic location than you really are, and pipe your download to a cached server that is far far away from you.
Like I said, this is the theory. I'm not really sure it it correct or not.
I know changing the DNS server helps with this issue for some people, but it has never helped me at all. I sometimes get ridiculously slow downloads of iOS apps in iTunes and changing DNS servers has never helped. I mean even if a DNS mixup caused Apple to think I was in New York instead of Los Angeles, the downloads should not be as slow as they are sometimes.
Uh ma gerd!!!! I wish I had come to this forum first. Thank you thank you thank you! I kept asking the tech support for a standalone installer over and over and over each time I called. They said there was one for the iTunes patch on iTunes.com which worked perfectly for me, but they said there was nothing I could do about the security patch. ARRGGHHH! My whole weekend wasted. Sad times.
Thanks for responding Weaselboy! I suppose that Apple servers might get confused on my geographic location. But I wasn't using a VPN. And I was able to download their iTunes patch from their website directly and very quickly with no issues. So I'm inclined to think there is an issue with the App Store/Disk Utility.
I definitely agree with your second point. I could be living on the other side of the world in China and my speeds should still not be slowing to 1-2 kb/sec with the connection I have. And they should definitely not be going through an infinite download loop.
I'm sorry to hear you are having the same problem and that the DNS trick didn't help. I have only had this issue of slow speeds and infinite download loops with certain security updates from Apple, but never for 3rd party apps on the App Store. So your issue may have a different cause. I know my phone was freaking out after I changed the DNS on my router and I had to reset my iphone to be able connect to the wifi. And changing the DNS under system preferences in Network settings didn't work when I did a reinstall through disk utility, I had to do change the DNS in my router. Either way, very frustrating all around.
Apple needs to work on procedures and the user interface when things go wrong. If they want to improve the user experience then they should institute error-checking procedures that actually make some sort of sense, and suggest a sensible course of action to correct the error. Instead we get some indecipherable error in the logs, like '&000f145 error: mysteryprocess id error WTF and a partridge in a pear tree', or error messages that make no sense, like my personal favourite 'Cannot backup iPhone because it has disconnected' when it is still connected.
My iMac had a red disk error when I reinstalled (can't remember what it was, sorry). I ran disk utility and repaired the error. I wasn't able to boot back into the startup disk after numerous attempts, so I had to do an erase and lost all of my data. I reinstalled OS X and there is no longer a fault, but it is now showing a Metadata Volume with a double redundancy. The login screen background also turned a weird shade of red...wtf? Edit: the red background was from booting into safe mode. But after multiple restarts in normal mode the red background persisted. Also the words "Safe Mode" were not at the top right corner when I booted normally, so I'm pretty sure I wasn't in safe mode even though the login background remained red after multiple restarts.
My other computers are now showing metadata double redundancy, but they didn't have any disk errors that were red when I reinstalled.
I don't know what this means, but from some googling, I have read that it is not necessarily bad. But I couldn't boot into OS X at first and I had to delete the drive and lost all my data, so I'm concerned. Should I be concerned?
My other computers are now showing metadata double redundancy, but they didn't have any disk errors that were red when I reinstalled.
I don't know what this means, but from some googling, I have read that it is not necessarily bad. But I couldn't boot into OS X at first and I had to delete the drive and lost all my data, so I'm concerned. Should I be concerned?
Last edited: