We have to find something to complain about

Edited by billford (Sun 26-Jun-11 17:24:34)

touch�

There was a hiccup on one of the previous updates if you were using encrypted discs.

A couple of years or so ago several people had inconsistent behaviour with PhotoShop on the Mac after running a software update to the then current version of OSX, rumour had it that that some modules had not updated, these then became a prereq for a subsequent update.

Running a Combo update would resolve the PS problem

Even before that occurrence I tended to run combo updates (ie on greater that 90% of occasions )

Ir was from one of the many Mac related forums that I read did I see strong recommendations to use Combo update. Initially when I first migrated to OSX I thought Software Update was the best thing since sliced bread however I have changed my mind as it is too easy to be building a potentially faulty system as a result of a bad incremental update.

I use Software Update, and haven't had any issues with an update for a long time, but this one threw me a curved ball. I noticed that my Dock CPU utilisation was 90%-ish - that's a whole core out of my four. This was impacting the CPU available for Folding@Home, plus it affected system responses generally. I tried shutting down apps, rebooting and so on, then checked out the interwebs and found this:

http://reviews.cnet.com/8301-13727_7-20074173-263/do...

I applied the work-round in the above link (turned off WIndows app icons in the dock) and the problem went away. Even when Parallels wasn't running, it seems it had a daemon polling for Windows application icons to show in the dock.

I doubt if my use of Software Update had any effect, as this looks like a Parallels issue.

MacBook Pro i7 processor top spec...

Just saying Pic

From the comments on your link:

This is NOT a problem with 10.6.8.

In the Parallels user forum, people reported this issue even BEFORE 10.6.8 was released. The problem happens after upgrading Parallels to build 12090.

http://forum.parallels.com/showthread.php?t=111073

Reminds of the Leopard upgrade blue screen - which turned out to be third parties (including Logitech!) using haxies in flat violation of long-standing Apple guidelines. Yet who took the flak?