X

Security Update 2006-007 (#3): General fixes; Startup problems (cont.); Device connectivity lost; Slow volume access; more

Security Update 2006-007 (#3): General fixes; Startup problems (cont.); Device connectivity lost; Slow volume access; more

CNET staff
8 min read

General workarounds to try first If you are experiencing a host of issues after application of Security Update 2006-007 (including "illegal instruction" messages, application launch failures, etc.), there are a few blanket workarounds you can try first before investigating specific fixes.

Re-apply the Mac OS X 10.4.8 combo updater Once again, re-application of the current combination updater (Mac OS X 10.4.8 for PowerPC or Intel) has proven useful in the case of Security Update 2006-007. Doing so overwrites potentially problem-causing files.

Re-apply the Mac OS X 10.4.8 combo updater from an alternate startup volume Failing the above, a more involved process that requires applying the combo updater from a separate startup drive can clear various issues.

  1. Download and save the Mac OS X 10.4.8 combo updater (PowerPC or Intel).
  2. Startup from an alternate boot volume, such as an external FireWire drive, or use another Mac to boot the problematic system in FireWire target disk mode (connect the two machines via a FireWire cable, and boot the target [problematic] system while holding down the "T" key)
  3. Once booted from an alternate drive, select the problematic volume in the Finder, and "Get Info" -- either by pressing the Command-I keyboard combination or accessing the "Get Info" option in the File menu. Check the box marked "Ignore ownership permissions on this volume."
  4. If you have a third-party disk repair utility like DiskWarrior, use it to re-build the directory on the problematic volume (this step may not be necessary)
  5. Re-install the Mac OS X 10.4.8 combo updater on the problematic drive.
  6. Re-attempt booting from the problematic volume (hold down the option key at startup to select the desired drive)
Delete kernel extension caches, other caches for some issues A number of common issues that crop up after major system updates (including security updates) can be resolved by deleting specific cache files -- specifically kernel extension caches -- and restarting.

This can most easily be accomplished with a shareware utility like Tiger Cache Cleaner, but also bears a manual process which involves dragging the following files to the trash:

  • com.apple.kernelcaches (a folder in /System/Library/Caches)
  • Extensions.kextcache (a file in /System/Library)
  • Extensions.mkext (a file in /System/Library/)
  • com.apple.ATS (a folder in /Library/Caches/)
  • Files that start with com.apple.LaunchServices (in /Library/Caches)

You will be prompted to enter your administrator password when dragging these files to the trash. You may need to restart after moving them to the trash.

Startup problems (cont.) Meanwhile, users continue to report problems starting up after applying Security Update 2006-007.

MacFixIt reader Jannis writes: "After applying the update and pressing the shutdown button (you know, after the update where you can choose to shut down or restart) my MacBook gives me a blank screen (even though it 'flashes' after turning the computer on). PMU and NVRAM reset did not show any effect, it's rendered useless."

Again, many instances of startup issues after Security Update 2006-007 may be resolved by procedures listed in our tutorial "Startup fails (particularly after a system or security update); solving." As presented in the tutorial, one of the first things you should do when experiencing startup issues after an update is a Safe Boot (accomplished by holding the Shift key down during startup). If your Mac boots successfully, you can then perform specific troubleshooting routines to eliminate the problem -- particularly removal of potentially problematic startup items from /Library/StartupItems.

Getting the update off your Mac If you are unable to properly startup or experiencing other dire issues after applying Security Update 2006-007 that cannot be resolved by already posted workarounds, you may need to uninstall the update.

This can be accomplished via the following process, adapted from our tutorial on reverting to a previous iteration of Mac OS X. Note, however, that reverting your system will remove any refinements brought by the update and leave your system open to potential vulnerabilities.

First, make a backup of your current Mac OS X installation with the Security Update applied, problematic as it may be. If there is an issue along the way, your valuable data will be safely intact in its current form.

Next, you'll need to perform an Archive and Install process to remove all of the Security Update's (and potentially problem-causing) components, and replace them with the components of a fresh copy provided by the Mac OS X disc that shipped with your system, or a retail Mac OS X disc. Unfortunately, this means you will lose some system settings and some or all third-party system add-ons.

To begin the process, insert your Mac OS X CD or DVD, as indicated above. Restart your machine and hold down the "C" key to boot from the newly inserted disc. Follow the on-screen instructions, and after accepting the license agreement, click "Options." Select "Archive and Install," and check the "Preserve User and Network Settings" option if you'd like to do so.

After the installation process is complete, you will be left with an earlier Mac OS X system that (hopefully) does not suffer from the problems generated by the Security Update. Use Software Update or Apple's download page to download the update that brings your system to a state directly prior to the Security Update

Font Book crashes Presumably because of the refinements made to the security of Apple Type Services in update 2006-007, Font Book has been updated to version 2.0.3, or a new version of 2.0.2 (depending on whether installation takes place on a PowerPC or Intel-based Mac). The new version is significantly smaller than the old release, and unfortunately is crashing repeatedly for some users.

One reader writes: "Font Book was replaced with this update. It lost its icon in the process, which is why I noticed and immediately tested it. The new one 2.0.3 was 412kb. An older one, also 2.0.2, on a backup drive was 6.4mb. It works. I replaced the one broken by the update with the older 6.4 MB version. All I can say is: make a backup copy of Font Book before using this update."

If you've noticed a similar issue, please let us know.

Misc. USB/FireWire device connectivity issues Some users are reporting issues with device connectivity (generally USB and FireWire) after applying Security Update 2006-007.

One reader writes:

"After installation of Security Update 2006-007, I cannot connect or disconnect my USB scanner (HP Scanjet 4070) without freezing my computer. Rebooting results in a high fan speed and stop at blank blue screen (May 1005 PM Dual 2.7 GHz, OS 10.4.8). Solution so far has been to connect to scanner before boot and leave connected until shutdown."

Other users are reporting issues with iPod recognition after the update.

The solution for some cases of this problem is to simply unplug the afflicted device(s), restart and re-connect them.

In other cases, clearing system caches with a utility like AppleJack, Cocktail or Tiger Cache Cleaner can often restore accessibility to FireWire devices that otherwise refuse to mount.

Outdated firmware or drivers may be precluding recognition for some devices. Try checking your device manufacturer's Web site for the latest downloads.

If you are experiencing a similar issue, please let us know.

Excessive iMac fan speed Some users are reporting a marked increase in iMac (both G5 and Intel-based) fan activity after installing Security Update 2006-007.

MacFixIt reader Lawrence Orenstein writes: "Since downloading the security update fan on my G5 IMac has been running at an excessive speed."

In some cases, resetting an SMU or SMC (depending on the iMac model) can resolve this issue.

For G5-based iMacs, the SMU reset process is as follows:

  1. Turn off the system
  2. Unplug all cables, including power
  3. Wait 10-30 seconds.
  4. Plug in the power cord while simultaneously pressing and holding the power button on the back of the computer.
  5. Let go of the power button.
  6. Press the power button once more to start up your iMac.

For Intel-based iMacs, the SMC reset process is as follows:

  1. Turn the system off
  2. Unplug all cables, including the power cord then wait 15 seconds
  3. Plug the power cord back in (Apple notes that you should make sure the power button is not being pressed at the time of power cord connection) then reconnect other devices.
  4. Turn the system back on.

Entourage problems Some users are reporting issues with unexpected quits in Microsoft Entourage.

MacFixIt reader J writes: "Looks like all my users who pulled down yesterday's update now aren't able to run Entourage, it crashes about 3 seconds after launch.

"The environment is a mix of Intel and PPC Macs, all using current version of Entourage. note that the app version below is in fact the latest updated version of Microsoft Office 11.3."

If you are experiencing a similar issue, please let us know.

Automatic login/keychain issues Some users are reporting keychain problems after the update -- having to manually login to sites with stored credentials and other issues.

One reader writes: "It may be totally unrelated but I just applied the update, rebooted and my Google Notifier application (Gmail and Gcal) seems unable to log in properly, asking me for credentials every 30 seconds."

Potential fixes for this issue can be found in our tutorial "Keychain issues; resolving"

In some cases, the solution is easy as navigating to ~/Library/Keychains/ (this is the Library folder inside your user home folder), then finding the file named "login.keychain" and double-clicking it.

AirPort card not recognized Some users have reported loss of AirPort card recognition after applying Security Update 2006-007.

One reader writes: "I applied the update to my MacBook Pro.  Upon reboot, it failed to load the Airport driver card, and the system no longer recognizes that it has the card."

In many cases, resetting the NVRAM can resolve this issue. The process is as follows: Shut down your Mac, then start it back up while immediately holding the following keys: Command, Option, P and R. Hold the keys down until the computer restarts and you hear the startup sound for the third time.

Slow access to network drives Some users have reported slow access to network drives after the update.

James Crossett writes: "I downloaded the newest Mac OS X security update a few hours ago and I swear its slowed my mounted disk speed. Working in Textmate is now really slow as it is mapped to a network drive and when I go back to it after working in other apps it takes like 20 seconds to start responding again, OSX even panicked at one point as I saved a doc to the mounted disk and I had to switch it off with the power button. Also, navigating network drives is dog slow and transferring files intermittently takes forever as it 'prepares to copy files' for about 5 minutes."

If you are experiencing a similar issue, please let us know.

Previous coverage:

Resources

  • PowerPC
  • Intel
  • Tiger Cache Cleaner
  • "Startup fails (particularly after a system or security update); solving."
  • reverting
  • Apple's download page
  • let us know
  • AppleJack
  • Cocktail
  • let us know.
  • "Keychain issues; resolving"
  • Security Update 2006-007 (...
  • Security Update 2006-007 r...
  • More from Late-Breakers