Filed under: Software Update, Troubleshooting, Leopard
Apple tech note responds to 10.5.6 problems
Following up on the 10.5.6 upgrade: The most common issue people seemed to have upgrading to Leopard 10.5.6 was that the install would get stuck at 'configuring installation'. It happened to me, and judging by the Apple support boards and others, it was a pretty widespread 
bug. We reported the problem Tuesday.
Apple has now responded and acknowledged the issue with a support note. It says that the problem can be caused by getting an update that "was only partially downloaded". Of course, what was not explained was how Apple provided only a partial update, and why and how this got past Apple QA?
For most people, installing the combo update solves the install freeze. Apple is recommending that people use Software Update, so most likely the bad package has been removed from the servers. There are still some nagging issues with Mail, mounting network volumes, Safari, and the other all too usual issues following an OS update.
Of course, for many, the update went just fine.
Thanks to all who wrote in and shared their experiences.
![TUAW [Cafepress]](http://www.blogsmithmedia.com/www.tuaw.com/media/tuaw-cafepress-promo.png)
Reader Comments (Page 1 of 2)
mark said 3:12PM on 12-18-2008
I have zero respect for companies that can not own up to their own mistakes.
Reply
Wezel said 3:18PM on 12-18-2008
Well then you must really respect Apple, because they always seem to own up to their mistakes. Even here, they tell people what caused the problem, and solutions for fixing it. The most obvious example of this would be the MobileMe fiasco. They made plenty of mistakes, owned up to them, and improved their services accordingly. I really respect them for that.
Of course you weren't talking about not respecting Apple though - you were just stating that you hate when companies do that in general. I understand.
Mike said 4:56PM on 12-18-2008
Does software update not do a SHA/MD5 hash comparison to make sure the file is complete? Why did this not fail numerous integity checks that should be in place?
Reply
Swimatm said 3:18PM on 12-18-2008
It just goes to show that nothing, even Apple software updates, is perfect.
Reply
James Donevan said 3:19PM on 12-18-2008
"Of course, what was not explained was how Apple provided only a partial update, and why and how this got past Apple QA."
Surely you grasp the fact that Apple is referring to partial downloads due downloading problems at the user's end, not the company's end. No mystery about Apple providing partial downloads, just users who don't realise their download failed to complete. When the servers get hit hard with users trying to update, this happens. It is nothing new, nor is it exclusive to Apple updates. If the user was downloading the combo update they would realise the file had not completely downloaded (looking at its size and its failure to launch). With Software Update it isn't readily apparent as the file is opening and installing in the background.
A bug? Hardly.
Reply
Devon said 3:35PM on 12-18-2008
If it was a partial download due to networking issues, Software Update should NOT install the update. It should be doing some sort of CRC check and I thought it actually did. So either this is a bug in Software Update or perhaps something else.
In any case, a failed download should NEVER be used to attempt the install.
A Bug? DEFINITELY
Athtart said 5:26PM on 12-18-2008
Thanks... took the words right out of my mouth ;-)
christof.lapd said 3:27PM on 12-18-2008
I have another Problem: My System keeps is freezed in a way that I can just use the one Acclication I used when the freezing occuderd. I postet at apple board but no response so far.
http://discussions.apple.com/thread.jspa?threadID=1828860&stqc=true
Can anyone here help? Otherwise I will re-install this weekend. Kind of sucks...
Reply
Jesse said 3:48PM on 12-18-2008
I can't see Software Update NOT using CRC. It's too critical a component to not being doing on software updates to core components and services.
Reply
nikster said 9:23AM on 12-19-2008
It's a bug. Obviously, they'll do some form of CRC, and obviously this bug was something that got around that, probably a bug in the CRC mechanism.
Software Update's ability to recover from a lost connection is so awful that I get any larger and/or important updates via direct download. Lucky for me, in this instance, downloaded the combo and it worked.
Not without some drama of course - with Apple, it's never boring. The system restarted, got to the grey screen progress circle.... and rebooted again, leaving me to wonder whether it was now stuck in a reboot cycle and my workday a write-off
A dialog saying "We are now getting to the second scheduled reboot of this update, all is going according to plan" would have been nice.
Bill said 3:57PM on 12-18-2008
It worked perfectly for me on an iMac and an original MacBook. Smooth as silk and no follow-on problems.
Reply
alansky said 4:06PM on 12-18-2008
Apple may recommend using Software Update to update Leopard, but I've noticed that those who manually download and install the Combo Update rarely have the problems that are sometimes reported after the release of a new OS X update. Personally, I always download the Combo Update and have never had any trouble whatsoever with any OS X update.
Reply
The Jones Boy said 2:46PM on 12-21-2008
My Octocore MacPro got stuck in endless boot mode on grey screen, hung, rebooted itself, hung for over 20 mins. Zapped PRAM, tried to boot in safe mode and eventually I got in.
Repaired permissions, loads all out, now (touch wood) ok.
Reply
Catapult said 4:27PM on 12-18-2008
CRC ? Well that would be better than nothing...
But I thought Apple sometime in the past claimed to have introduced something less ancient and more secure - digital signatures, a thing integrated into Windows Update many years ago.
So, if there is anything like checksums for updates, I hope Apple will sometime (maybe in the "stability" release 10.6 ? just kidding) make sure that they are indeed verified and that such updates can be installed if and only if integrity can be guaranteed with sufficient confidence, and that the system automatically/semi-automatically re-downloads the patches otherwise.
Reply
OwlBoy said 4:32PM on 12-18-2008
I have never had an issue with a system software update, Includeing this one.
But now that I have said that, 10.5.7 will prolly eat my computer alive.
Reply
Scott said 4:54PM on 12-18-2008
I can say that I have never had a single problem updating any of the 5 Macs in my house (ranging from a Mac Pro to a PowerBook G4) and this goes back to 10.3 I sometimes question whether or not the people that have issues are causing them through "user error" themselves....
phlavor said 4:30PM on 12-18-2008
A big thanks to everyone who suffered through a bad upgrade so I didn't have to. You all rock.
Reply
Moose said 5:16PM on 12-18-2008
Count me among the many many many people posting in the Apple Forums whose versions of Suitcase took a nosedive after 10.5.6 for a variety of bizarre reasons. Unexpected/unusual for a second dot update...
http://discussions.apple.com/thread.jspa?messageID=8635060
Reply
Arv said 5:25PM on 12-18-2008
When updating the update got stuck. Apple support walked me through the archive and install and then I downloaded and installed the combo updated. Everything is good now.
Reply
Tim said 8:53AM on 12-19-2008
It doesn't matter whose network has the problem. If the file isn't done or correct, it should not install.
If I put my finger in a food processor and lose the tip of it, it's not the manufacturer's fault, but they should at least have a guard there so I don't do it accidentally. It is my mistake, but it doesn't excuse them.
Personally, I think this is a good argument for the updater to validate and run a hash check of files (are they the same thing? I really never learned) before installing them, and perhaps they should verify the hash from two Apple servers first, just for safety/security's sake. This is a glaring flaw.
While we are discussing overhauls, bit torrent transfers divide the files into parts which are shared and hash checked individually, and the torrent's whole files are also hash checked in many clients. Perhaps the update client should offer bit torrent transfers, so the servers have an easier time, but still offer HTTP downloads for those with poor or heavily restricted connections so that Apple doesn't have to explain port forwarding to every user.
Reply