Problems downloading through Software Update (Security Update 2005-001 and others)
Problems downloading through Software Update (Security Update 2005-001 and others)
We continue to cover an issue where some users are unable to install items through Apple's Software Update delivery system, receiving the error:
Some of the checked updates could not be installed. Make sure you have permission to write to /tmp/501/TemporaryItems/com.apple.SoftwareUpdate, then try again. (This error may also appear as The update could not be verified and expanded correctly. Make sure you have permission to write to /tmp/501/temporaryitems/com.apple.SoftwareUpdate, then try again or The update "Security update 2005 001" could not be verified and expanded correctly. Make sure you have permission to write to /tmp/501/TemporaryItems/com.apple.SoftwareUpdate, then try again.
This has been any issue for many users since the release of Mac OS X 10.3.0, but has increased in frequency recently, appearing for many users attempting to install Security Update 2005-001, and others attempting to install iMovie 5.0.1.
MacFixIt reader Anthony Kassir writes
"I too experienced the /tmp/501/temporaryitems/com.apple.SoftwareUpdate issue, but when using Software Update to install an iDVD 4 update, and an iTunes update.
"I tried repairing permissions; didn't work. However, I found that if I just waited a few hours, the update magically worked.
Indeed, simply waiting and trying the update again at a later time has proved successful for a number of readers.
A number of other workarounds also exist.
Modifying temp folder permissions MacFixIt reader Sven solved his instance of this problem by using the Finder to search for specific Temp folders, then using the shareware utility BatChmod to modify their permissions.
He writes:
"The quickest way around it I have found is to do a search for name contains 501 or 502 with second criteria both visible and invisible then drag the enclosing invisible Temp folder on to BatChmod 1.33 select the 'Apply Ownership and Privileges' tick box then hit the 'Apply' button and then OK - This is the only sure fast way I have found to resolve this issue. But you can be certain the next time you want to apply another update you will need to repeat the process."
Repair Permissions As previously reported, using Apple's Disk Utility (located in Applications/Utilities) to repair permissions can resolve this issue in a number of cases.
/tmp link broken, 'pax' missing MacFixIt reader Steven D. Kapplin offers two workarounds, one which involves re-creating the logical link for the /tmp folder, and another that requires extracting the system component 'pax' from your original Mac OS X Install media.
Kapplin writes:
"Sometimes the /tmp logical link is broken for one reason or another. Here is a procedure to recover from this problem.
- Start the Terminal program from the Utilities menu
- Copy and paste the following two commands into the Terminal window. You will be asked for an admin password after the first command. Enter it (it is not echoed in any way) and press return. Note that the "l" character is an "el" and not "eye".
- sudo mv /tmp /tmp_old
- sudo ln -s /private/tmp /tmp
- ls /bin/pax (followed by a return)
"If you get the response '/bin/pax', you have the program. If you do not have the program, you can install it from your Panther install CD with the aid of the Pacifist program."
[See instructions below for using Pacifist]
What is causing the issue John Davidson offers an interesting theory on what might be causing the issue:
"After checking the directories noted in the error I was convinced the permissions on them were correct. The error appears to come from a failure to match the hash value used to validate the download. This is most likely an issue on the calculation of what components need to be included in the download, get them actually downloaded and the calculation of the appropriate hash value. Once the download is completed from Software Update it keeps using the already download files and values, even when those have failed to work previously. After talking with the Apple Tech Rep it was clear that this is a known issue, and I was directed to download the full update from the Update page. I had the problem on 2 Macs and this corrected the problem on both."
Developer Tools removal to blame? It appears that in some cases, this issue is caused by the installation, and subsequent removal of Apple's Developer Tools.
MacFixIt reader Brad writes: "I started having this issue several months ago. It came down to the fact that at one point I had installed the Developer Tools, and then uninstalled them. What happens is that the uninstall script also uninstalls tar and other compression/decompression applications. The work around for me was using Pacifist to reinstall the programs that were removed without installing the entire Developer Tools package again."
The process Brad describes (using Pacifist to install specific components from the Mac OS X install CD) requires first downloading and installing the Pacifist application.
Next, launch Pacifist and insert your Mac OS X Installer Disk 1. Click "Open Mac OS X Install Packages" and you'll be prompted to insert the other install disks in order. Control-click on your desired application(s) to install to the default location.
Resources