Finder broken after (July 2013) 10.8.4 security update

Help!
After installing the recent security update (via the app store updates) I have no finder windows and my desktop shows only the background, the menubar, and the dock. None of my desktop files show and I can't open any finder windows.
Everything else appears ok: I can start apps, the notification center functions,
My system log shows the following error message associated with the finder:
7/5/13 6:53:08.233 PM Finder[202]: *** setObjectForKey: key cannot be nil
7/5/13 6:53:08.237 PM Finder[202]: (
          0   CoreFoundation                      0x00007fff8b133b06 __exceptionPreprocess + 198
          1   libobjc.A.dylib                     0x00007fff933053f0 objc_exception_throw + 43
          2   CoreFoundation                      0x00007fff8b1c25b7 -[__NSDictionaryM setObject:forKey:] + 135
          3   Finder                              0x000000010c50bc44 Finder + 1977412
          4   Finder                              0x000000010c35bd7f Finder + 208255
          5   Finder                              0x000000010c35ba17 Finder + 207383
          6   Finder                              0x000000010c35b7ce Finder + 206798
          7   Finder                              0x000000010c35b6cb Finder + 206539
          8   Finder                              0x000000010c35b5cd Finder + 206285
          9   Foundation                          0x00007fff96a5f165 -[NSObject(NSKeyValueCoding) setValue:forKey:] + 408
          10 AppKit                              0x00007fff8b8c1b1c -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] + 1359
          11 AppKit                              0x00007fff8b8ab699 -[NSObject(NSKeyValueBindingCreation) bind:toObject:withKeyPath:options:] + 641
          12 Finder                              0x000000010c35b3ff Finder + 205823
          13 Finder                              0x000000010c3589b7 Finder + 194999
          14 Finder                              0x000000010c355071 Finder + 180337
          15 Finder                              0x000000010c35481d Finder + 178205
          16 Finder                              0x000000010c35423d Finder + 176701
          17 Finder                              0x000000010c34a964 Finder + 137572
          18 Finder                              0x000000010c34a598 Finder + 136600
          19 Finder                              0x000000010c34a32c Finder + 135980
          20 Finder                              0x000000010c34a25b Finder + 135771
          21 Finder                              0x000000010c34a222 Finder + 135714
          22 libdispatch.dylib                   0x00007fff94794f01 _dispatch_call_block_and_release + 15
          23 libdispatch.dylib                   0x00007fff947910b6 _dispatch_client_callout + 8
          24 libdispatch.dylib                   0x00007fff947960c8 _dispatch_main_queue_callback_4CF + 275
          25 CoreFoundation                      0x00007fff8b0d5b4c __CFRunLoopRun + 1644
          26 CoreFoundation                      0x00007fff8b0d50e2 CFRunLoopRunSpecific + 290
          27 HIToolbox                           0x00007fff9043feb4 RunCurrentEventLoopInMode + 209
          28 HIToolbox                           0x00007fff9043fc52 ReceiveNextEventCommon + 356
          29 HIToolbox                           0x00007fff9043fae3 BlockUntilNextEventMatchingListInMode + 62
          30 AppKit                              0x00007fff8b773533 _DPSNextEvent + 685
          31 AppKit                              0x00007fff8b772df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
          32 AppKit                              0x00007fff8b76a1a3 -[NSApplication run] + 517
          33 AppKit                              0x00007fff8b70ebd6 NSApplicationMain + 869
          34 Finder                              0x000000010c32eb56 Finder + 23382
          35 libdyld.dylib                       0x00007fff903827e1 start + 0
          36 ???                                 0x0000000000000001 0x0 + 1

Unfortunately Apple has lost serious control of Mountain Lion. This version of OS X is highly erratic.
Finder is totally unsafe to use in a network. Will lead to loss of files, dropped network, Still visible Network Shares even though DCHP and Ethernet cables have been removed...
All in all 10.8 is a nice system for checking mails and browsing a bit... But for critical and paid work it should be completely avoided - unless you wanna face a premature heart attack ;-)
Hopefully 10.9 is going to improve all this... Although I doubt it. iOS has precedence it seems. At least that is the only explanation I can find to why OS X has been continuously deteriorating since 10.7

Similar Messages

Beach Balls and freezes after installing Safari 3.1 and security update

Hi,
I just recently installed the safari 3.1 update and the security update. My machine is an iMac 2.4 GHz with 10.5.2. Prior to this, the machine only had one freeze (had to power off) which happened a about a month back. Since the update, 2 days ago, the machine seems to show the beach ball more often. On one specific occasion (happened when my son was using it), the Chess game was running, and the mouse cursor turned into a beach ball and everything froze - can only move the mouse cursor/beach ball but nothing else responded. Even hitting the caps lock key took minutes before the caps lock light came on. Me being a windows user for a long time, I was blindly trying to find the keyboard equivalent of ctrl-alt-del to pull up a process list of some kind so that I can kill the offending app. But was not successful, hence I had to power off.
On another occasion, and this time, it happened to me - the beach ball came up as I was using safari. I could use other stuff in the OS, but any time I brought the cursor over safari, it would turn into a beach ball. After waiting a few minutes and clicking away on the safari window, the beach ball turned into a finger cursor when I clicked on the http address window - and safari started to work like normal again.
I'm wondering if anyone else has had experiences similar to this and if there are any steps I can take to prevent this again.
Thanks in advance.

Welcome to the Apple forums:
Did you perform both updates at the same time? I usually recommend doing them one-at-a-time, so if anything happens you know which update caused the problem.
I especially never do a system update with any other update. I always do that one last, and wait for the dust to settle by reading this board first.
You should run DU and check the HD and repair permissions. That's a start.

No sleep after installing recent java, daylight savings & security updates

After installing the recent java, daylight savings, and the security update, my computer would crash and upon startup would act funny showing a b&W screen with typewriter type asking me to keyboard in directions ie. "shut-down".
I was able to reset the PMU and now it will not sleep on it's own, and when I send it to sleep, it wakes up after a few minutes.

This is for a Mac that won't sleep.
First, read things in Apple doc.#25801 on sleep settings.
Here is Apple doc.#303698 with their tips.
Mine follow;
USB devices and hubs often cause Macs to not sleep or wake quickly from sleep (notably HP printers and scanners, HP all in ones, and Cannon scanners). Disconnect all USB except for keyboard and mouse and try. If it sleeps, add one back at a time testing after each one to find the culprit.
If you've set your Mac to recieve faxes, it may not be able to sleep. It might also have a damaged preferences file.
If you use your Mac for faxing, open System Preferences. click Print & Fax, click the Faxing tab, and uncheck the Recieve Faxes On This Computer box.
If that does'nt work or you've never faxed on your Mac, go to Finder/Hard Drive /Library/Preferences/SystemConfiguration and delete the com.apple.PowerManagement.plist and com..apple.AutoWake.plist files (if your Mac asks, type your admin. password).
If the latter file isn't present in the folder, go to user name(probably your name)/Library/Preferences, delete the com.apple.systemuiserver.plist file, and reboot your Mac.
Hope this helps!
P.S. One member here reported this (Michael Gleason);
"I have had this problem with my IMac G5. It is surprisingly irritating. LaCie's Silverkeeper backup software was the cause. By default it gave itself permission to wake up the computer to check if a backup was needed. Do you have this or a similar program installed which has scheduled activities including wake-up permissions as an option?"
Dave Hamilton provided this link, xlr8yourmac.com, to a member, which addresses failure of deep sleep with some users that updated and added new FireWire and USB cards.
tomhorvat adds this; After few days of messing around I found out that I had desktop background (wallpaper) set to change every 1 minute.
After unchecking "Change picture..." in system preferences (under Desktop/Screen saver), my powerbook went to sleep all by itself.
Cheers!
DALE

IDVD & Roxio Toast not working after APPLE-SA-2009-02-12 Security Update

After installing APPLE-SA-2009-02-12 Security Update 2009-001, iDVD and Roxio Toast will not work.
iDVD will launch, and I can create a project. It starts to render the video, but crashes before it starts to burn the disc.
Roxio Toast will not even launch.
Both applications were working perfectly and reliably before this update.
Anyone else found this problem?
Greg.

I re-installed the apps, and they're working now.
Greg.

Huge problem after Safari 3.1 and new security update

I just installed the new SAFARI 3.1 as well as the security update and I am SCREWED! (unless a genius here can help out).
After the install and restart my desktop picture is sligthy blown up but worse -it essentially floats when I move the mouse. As such, it can obscure the top of the image which "hides" the Apple pull down options AND I canot get the dock to reveal at the bottom of the frame. In a word - screwed.
Any thoughts?
thanks
Theo

looks like I figured this out on my own - it was the zoom function that had somehow been activated.
It all seems to be working fine now once I set that

Spotlight & Find Broken after SMC Firewire Update

I recently upgraded to the latest firmwire, iMac SMC Firewire Update 1.0, and now I have no find functionality on my Intel iMac. Soptlight shows, but doesn't search for anything. File find searches and searches but never finds anything.
I tried restarting and repairing permissions and that didn't do anything. I tried deleting com.apple.spotlight.plist and no luck either.
Any advice is greatly appreciated.

I had the same issue, spotlight dead after I installed then de installed BootCamp.
I only had one account so I created another, logged into it and spotlight worked, logged out and in my account spotlight worked again.
Thanks
Mini - Intel Duo Mac OS X (10.4.6) 512mg/80gb/SyncMaster 940MW

PDF prints from Acrobat 9 formatting off and security limitation after mac 10.9.2 OS security update

When I print to Acrobat from Word, the output formatting gets messed up (single lines turn to doubles, column to right shifts to the left) ; I can't combine two documents; AND I get a security erro message when I try to reduce file size.

This type of problem is best solved by submitting a formal support case with our developer support staff...

Lost Wirless network icon after security update

I lost my wireless network icon at teh top of the finder bar after i upgraded to the newest security update via software update. Did anyone else have this problem, and if so, did you find a fix? I have no bars visible and can not switch between networks as I can no longer see them

HI
Also, once you mark it Solved, you can't award points
I am confused by this. Where in Terms of Use does it say you can't? Do you have personal experience of this (as an OP who asked a question)?
I asked a question months ago, marked it answered. After closing it I awarded a green star, months later Helpful button still available.
I suppose OP could always have remarked question as 'unanswered', awarded the points, then marked it 'Answered' again IF you are correct.
Steve

VPN broken after 10.6.4 Update / Security Update 2010-005

I have a MacMini Server that was running 10.6.3 in use as a gateway for the last 3 or 4 months and everything has been working just fine. However, after applying 10.6.4 and Security Update 2010-005 the iChat and VPN services broke.
I was able to fix the iChat service by using serveradmin in Terminal - Server Admin was showing the correct name of the iChat server, but serveradmin reported a different (incorrect) name. My only guess is that one of the updates somehow changed that setting behind the scenes.
I have yet to be able to fix the VPN (L2TP) issue, though. I can connect internally (to 10.0.1.1) with no problem. I can connect with via iPhone over 3G no problem. I cannot connect externally from a 10.5.8 or a 10.6.4 client - any attempt always fails with a timeout. The VPN log shows nothing, but the system log shows:
Sep 24 14:18:33 gateway racoon[90950]: Connecting.
Sep 24 14:18:33 gateway racoon[90950]: IKE Packet: receive success. (Responder, Main-Mode message 1).
Sep 24 14:18:33 gateway racoon[90950]: IKE Packet: transmit success. (Responder, Main-Mode message 2).
Sep 24 14:18:36 gateway racoon[90950]: IKE Packet: transmit success. (Phase1 Retransmit).
Sep 24 14:19:03: --- last message repeated 8 times ---
Sep 24 14:19:03 gateway racoon[90950]: IKEv1 Phase1: maximum retransmits. (Phase1 Maximum Retransmits).
Sep 24 14:19:03 gateway racoon[90950]: Disconnecting. (Connection tried to negotiate for, 29.171451 seconds).
Sep 24 14:19:03 gateway racoon[90950]: IKE Phase1 Failure-Rate Statistic. (Failure-Rate = 100.000).
It would seem that the response to the initial handshake is being blocked. However, serveradmin has this to say about ipfilter:
gateway:/ *******$ sudo serveradmin settings ipfilter|grep VPN
ipfilter:ipAddressGroupsWithRules:array_id:any:rules:_arrayid:VPN ISAKMP/IKE:action = "allow"
ipfilter:ipAddressGroupsWithRules:array_id:any:rules:_arrayid:VPN L2TP - Layer-Two Tunneling Protocol:action = "allow"
ipfilter:ipAddressGroupsWithRules:array_id:any:rules:_arrayid:VPN L2TP\: IKE NAT Traversal:action = "allow"
ipfilter:ipAddressGroupsWithRules:array_id:any:rules:_arrayid:VPN L2TP\: ISAKMP/IKE:action = "allow"
ipfilter:ipAddressGroupsWithRules:array_id:any:rules:_arrayid:VPN L2TP\: ESP - Encapsulating Security Payload protocol:action = "allow"
ipfilter:standardServices:arrayid:VPN PPTP\: GRE - Generic Routing Encapsulation protocol:readOnly = yes
ipfilter:standardServices:arrayid:VPN PPTP\: GRE - Generic Routing Encapsulation protocol:protocol = "gre"
ipfilter:standardServices:arrayid:VPN PPTP\: GRE - Generic Routing Encapsulation protocol:name = ""
ipfilter:standardServices:arrayid:VPN PPTP\: GRE - Generic Routing Encapsulation protocol:dest-port = ""
ipfilter:standardServices:arrayid:VPN L2TP\: ESP - Encapsulating Security Payload protocol:readOnly = yes
ipfilter:standardServices:arrayid:VPN L2TP\: ESP - Encapsulating Security Payload protocol:protocol = "esp"
ipfilter:standardServices:arrayid:VPN L2TP\: ESP - Encapsulating Security Payload protocol:name = ""
ipfilter:standardServices:arrayid:VPN L2TP\: ESP - Encapsulating Security Payload protocol:dest-port = ""
ipfilter:standardServices:arrayid:VPN L2TP - Layer-Two Tunneling Protocol:oldDescription = "Layer-Two Tunneling Protocol (L2TP)"
ipfilter:standardServices:arrayid:VPN L2TP - Layer-Two Tunneling Protocol:protocol = "udp"
ipfilter:standardServices:arrayid:VPN L2TP - Layer-Two Tunneling Protocol:readOnly = no
ipfilter:standardServices:arrayid:VPN L2TP - Layer-Two Tunneling Protocol:name = ""
ipfilter:standardServices:arrayid:VPN L2TP - Layer-Two Tunneling Protocol:dest-port = "1701"
ipfilter:standardServices:arrayid:VPN PPTP - Point-to-Point Tunneling Protocol:oldDescription = "PPTP VPN"
ipfilter:standardServices:arrayid:VPN PPTP - Point-to-Point Tunneling Protocol:protocol = "tcp"
ipfilter:standardServices:arrayid:VPN PPTP - Point-to-Point Tunneling Protocol:readOnly = no
ipfilter:standardServices:arrayid:VPN PPTP - Point-to-Point Tunneling Protocol:name = ""
ipfilter:standardServices:arrayid:VPN PPTP - Point-to-Point Tunneling Protocol:dest-port = "1723"
ipfilter:standardServices:arrayid:VPN L2TP\: ISAKMP/IKE:readOnly = no
ipfilter:standardServices:arrayid:VPN L2TP\: ISAKMP/IKE:protocol = "udp"
ipfilter:standardServices:arrayid:VPN L2TP\: ISAKMP/IKE:name = ""
ipfilter:standardServices:arrayid:VPN L2TP\: ISAKMP/IKE:dest-port = "500"
ipfilter:standardServices:arrayid:VPN L2TP\: IKE NAT Traversal:readOnly = no
ipfilter:standardServices:arrayid:VPN L2TP\: IKE NAT Traversal:protocol = "udp"
ipfilter:standardServices:arrayid:VPN L2TP\: IKE NAT Traversal:name = ""
ipfilter:standardServices:arrayid:VPN L2TP\: IKE NAT Traversal:dest-port = "4500"
Which seems to be correct to me.
As with the iChat problem, everything seems to be correct as reported by Server Admin. I have been hunting for the incorrect setting using serveradmin, but so far everything there seems to be correct as well.
One last item that I just discovered today, and which is probably a huge hint (and I just don't know how to connect the dots), is that when I stop the VPN service (it's running on the gateway server), the entire office loses it's connection to the internet. Turn VPN back on, and the internet is back.
I think my server is deeply, deeply disturbed, but I am not ready to wipe it clean and start over again. I sure would appreciate any insights on this one....

I have a MacMini Server that was running 10.6.3 in use as a gateway for the last 3 or 4 months and everything has been working just fine. However, after applying 10.6.4 and Security Update 2010-005 the iChat and VPN services broke.
I was able to fix the iChat service by using serveradmin in Terminal - Server Admin was showing the correct name of the iChat server, but serveradmin reported a different (incorrect) name. My only guess is that one of the updates somehow changed that setting behind the scenes.
I have yet to be able to fix the VPN (L2TP) issue, though. I can connect internally (to 10.0.1.1) with no problem. I can connect with via iPhone over 3G no problem. I cannot connect externally from a 10.5.8 or a 10.6.4 client - any attempt always fails with a timeout. The VPN log shows nothing, but the system log shows:
Sep 24 14:18:33 gateway racoon[90950]: Connecting.
Sep 24 14:18:33 gateway racoon[90950]: IKE Packet: receive success. (Responder, Main-Mode message 1).
Sep 24 14:18:33 gateway racoon[90950]: IKE Packet: transmit success. (Responder, Main-Mode message 2).
Sep 24 14:18:36 gateway racoon[90950]: IKE Packet: transmit success. (Phase1 Retransmit).
Sep 24 14:19:03: --- last message repeated 8 times ---
Sep 24 14:19:03 gateway racoon[90950]: IKEv1 Phase1: maximum retransmits. (Phase1 Maximum Retransmits).
Sep 24 14:19:03 gateway racoon[90950]: Disconnecting. (Connection tried to negotiate for, 29.171451 seconds).
Sep 24 14:19:03 gateway racoon[90950]: IKE Phase1 Failure-Rate Statistic. (Failure-Rate = 100.000).
It would seem that the response to the initial handshake is being blocked. However, serveradmin has this to say about ipfilter:
gateway:/ *******$ sudo serveradmin settings ipfilter|grep VPN
ipfilter:ipAddressGroupsWithRules:array_id:any:rules:_arrayid:VPN ISAKMP/IKE:action = "allow"
ipfilter:ipAddressGroupsWithRules:array_id:any:rules:_arrayid:VPN L2TP - Layer-Two Tunneling Protocol:action = "allow"
ipfilter:ipAddressGroupsWithRules:array_id:any:rules:_arrayid:VPN L2TP\: IKE NAT Traversal:action = "allow"
ipfilter:ipAddressGroupsWithRules:array_id:any:rules:_arrayid:VPN L2TP\: ISAKMP/IKE:action = "allow"
ipfilter:ipAddressGroupsWithRules:array_id:any:rules:_arrayid:VPN L2TP\: ESP - Encapsulating Security Payload protocol:action = "allow"
ipfilter:standardServices:arrayid:VPN PPTP\: GRE - Generic Routing Encapsulation protocol:readOnly = yes
ipfilter:standardServices:arrayid:VPN PPTP\: GRE - Generic Routing Encapsulation protocol:protocol = "gre"
ipfilter:standardServices:arrayid:VPN PPTP\: GRE - Generic Routing Encapsulation protocol:name = ""
ipfilter:standardServices:arrayid:VPN PPTP\: GRE - Generic Routing Encapsulation protocol:dest-port = ""
ipfilter:standardServices:arrayid:VPN L2TP\: ESP - Encapsulating Security Payload protocol:readOnly = yes
ipfilter:standardServices:arrayid:VPN L2TP\: ESP - Encapsulating Security Payload protocol:protocol = "esp"
ipfilter:standardServices:arrayid:VPN L2TP\: ESP - Encapsulating Security Payload protocol:name = ""
ipfilter:standardServices:arrayid:VPN L2TP\: ESP - Encapsulating Security Payload protocol:dest-port = ""
ipfilter:standardServices:arrayid:VPN L2TP - Layer-Two Tunneling Protocol:oldDescription = "Layer-Two Tunneling Protocol (L2TP)"
ipfilter:standardServices:arrayid:VPN L2TP - Layer-Two Tunneling Protocol:protocol = "udp"
ipfilter:standardServices:arrayid:VPN L2TP - Layer-Two Tunneling Protocol:readOnly = no
ipfilter:standardServices:arrayid:VPN L2TP - Layer-Two Tunneling Protocol:name = ""
ipfilter:standardServices:arrayid:VPN L2TP - Layer-Two Tunneling Protocol:dest-port = "1701"
ipfilter:standardServices:arrayid:VPN PPTP - Point-to-Point Tunneling Protocol:oldDescription = "PPTP VPN"
ipfilter:standardServices:arrayid:VPN PPTP - Point-to-Point Tunneling Protocol:protocol = "tcp"
ipfilter:standardServices:arrayid:VPN PPTP - Point-to-Point Tunneling Protocol:readOnly = no
ipfilter:standardServices:arrayid:VPN PPTP - Point-to-Point Tunneling Protocol:name = ""
ipfilter:standardServices:arrayid:VPN PPTP - Point-to-Point Tunneling Protocol:dest-port = "1723"
ipfilter:standardServices:arrayid:VPN L2TP\: ISAKMP/IKE:readOnly = no
ipfilter:standardServices:arrayid:VPN L2TP\: ISAKMP/IKE:protocol = "udp"
ipfilter:standardServices:arrayid:VPN L2TP\: ISAKMP/IKE:name = ""
ipfilter:standardServices:arrayid:VPN L2TP\: ISAKMP/IKE:dest-port = "500"
ipfilter:standardServices:arrayid:VPN L2TP\: IKE NAT Traversal:readOnly = no
ipfilter:standardServices:arrayid:VPN L2TP\: IKE NAT Traversal:protocol = "udp"
ipfilter:standardServices:arrayid:VPN L2TP\: IKE NAT Traversal:name = ""
ipfilter:standardServices:arrayid:VPN L2TP\: IKE NAT Traversal:dest-port = "4500"
Which seems to be correct to me.
As with the iChat problem, everything seems to be correct as reported by Server Admin. I have been hunting for the incorrect setting using serveradmin, but so far everything there seems to be correct as well.
One last item that I just discovered today, and which is probably a huge hint (and I just don't know how to connect the dots), is that when I stop the VPN service (it's running on the gateway server), the entire office loses it's connection to the internet. Turn VPN back on, and the internet is back.
I think my server is deeply, deeply disturbed, but I am not ready to wipe it clean and start over again. I sure would appreciate any insights on this one....

After Security Update 2010-001: Airport Card Not Detected

Currently running OS X 10.5.8 on a Mid 2009 MacBook Pro.
Here's the issue. When I boot up the machine and click the AirPort drop down it tells me that there is no airport card detected. Under system profiler it says the same thing. If I boot to a 10.6 Mac OS Install DVD and open system profiler, the AirPort card is detected. This occurred after a reboot prompted by the Security Update 2010-001.
So far I have repaired permissions and repaired disk. No fix.
I reset the PRAM/NVRAM and SMC. No fix.
I booted to an OS X image on an external drive. No fix.
I cannot boot to the Apple Hardware Test (D at startup) because my company requires PGP disk encryption. I could decrypt but this would take at least 6 hours (not counting re-encrypting afterwards).
I tried replacing the extensions. No fix.
There were no firmware updates applied or any other major OS updates.
Anyone have anything else I can attempt?

anyone else see that??
Yes, Already covered in full here. Strange but no problem.
http://discussions.apple.com/thread.jspa?threadID=2310982&tstart=15

Safari won't start after installing security update 2006-001

today i updated my computer with the latest Security patch. Now my computer wont start the browser
i deleted the preference file on my preferences folder to try to solve the problem, but i still wasn't able to start the browser.
i created a new user and tried to start safari once more, but still the progam crashes before it even starts.
this is the output that i get from the crash reporter
Date/Time: 2006-03-02 16:44:55.777 -0500
OS Version: 10.4.5 (Build 8H14)
Report Version: 4
Command: Safari
Path: /Applications/Safari.app/Contents/MacOS/Safari
Parent: WindowServer [63]
Version: 2.0.3 (417.8)
Build Version: 1
Project Name: WebBrowser
Source Version: 4170800
PID: 445
Thread: 0
Exception: EXCBADINSTRUCTION (0x0002)
Code[0]: 0x00000002
Code[1]: 0x95aadd70
... also the Sofware update softare wont start. It will crash before it even starts.
this is the output from the crash reporter
Date/Time: 2006-03-02 16:43:46.431 -0500
OS Version: 10.4.5 (Build 8H14)
Report Version: 4
Command: Software Update
Path: /System/Library/CoreServices/Software Update.app/Contents/MacOS/Software Update
Parent: WindowServer [63]
Version: 2.0.5 (2.0.5)
Build Version: 24
Project Name: SoftwareUpdate
Source Version: 1360000
PID: 439
Thread: 0
Exception: EXCBADINSTRUCTION (0x0002)
Code[0]: 0x00000002
Code[1]: 0x95aadd70
any ideas how to fix it?
Powerbook G4 12" 1.5GHz Mac OS X (10.4.5)

- FOR OS VERSION UPDATES YOU CAN ROLL THEM BACK
have to trash the UPDATE10.4.?.PKG file that is located in:
Hard drive> Library> recipts folder> ??.pkg file. (check spotlight search if you cant navigate to the Recipts folder for .pkg files to take out the one for the latest update you have done.
Basically the only way to "roll back" any applications or drivers that are updated is to do an entire Archive and Install of your OS (can do preserving user and network settings and WILL NOT LOOSE ANY DATA) see knowlege base article 107120 for A&I how to. You can always do the software updates later after the A&I.
That particular security update may have been faulty so of course, mabye try the DL again to see what happens and by all means CHECK THE SUPPORT TAB of this site for software updates if you want to do them. IF IT AINT BROKE, DONT FIX IT. most software updates do little or nothing for the application and somtimes they could cause problems LIKE loosing your itunes library when going from 5.0 to 6.0 and so on...

Contribute will not edit web page after installing Security Update 2007-004

I have been unable to edit my web site with Contribute 3.11 after I installed the 2007-004 Security update. When I select the web page to edit the spinning beach ball appears and if I look in top it shows Contribute using 100% of the system. I have to do a force quit on it to be able to do anything.
Has anyone else noticed a problem with this or have a possible solution? Thank you.
Intel 20 in iMac Mac OS X (10.4.9) Powerbook 15in 1.67

You might want to ask in the forums where Contribute users and Adobe hang out, if you haven't already:
http://www.adobe.com/support/forums/

MacBookPro Freezes after Installing Latest Security Update 2006-003

After downloading and installing the latest security update 2006-003, MacBook Pro freezes when trying to do anything. Seems to do ok in safe mode but did freeze when trying to verify disk with Disk Utility. (did not try to repair as I am out of town at a motel without Tiger disks). Any suggestions before calling apple?
MacBook Pro 15 Mac OS X (10.4.6)

Since my post, I think I have solved the problem. At least MyMacBook is working ok so far. What I did is started up in safe mode (for the third time) then I went through the "Library" and looked for stuff that looked like it wouldn't work on a MacBook. This included some Norton Utility things. Also went through preferences and Application Support and did the same thing. By the way I had transferred all this stuff from my old Mac using the transfer app and connecting the two with firewire.
Anyway, it's been working for about an hour. I'll keep this post open for a couple of days to see if it keeps working.
Bill

Restoring after Security Update damage

After downloading and installing the latest security update (2007-004) my wife's G4 iMac (OS 10.4.9) has failed to respond to anything. It now appears to start, the grey Apple logo appears and then five seconds later the screen goes black, and the computer powers off. I have tried
a) resetting the PRAM
b) starting from OSX Installer DVD (will not repair disk)
c) starting with a safe boot (no effect at all)
d) running Disk Warrior 3.0.3 (says directory too badly damaged)
e) booting it in Target Disk mode (icon does not appear on screen of other computer)
My wife depends on this iMac for her business. Now she is completely stranded.
I have to try something today to get it back in shape for her starting work tomorrow (she runs her own business and the Mac is vital to her). If I do a Tiger Archive and Install installation from the original DVD would that be a fix? Or has the volume directory been so badly damaged by the update that there would be nothing recognisable to archive?
Any suggestions appreciated.

Thanks, but I have this problem - when I set the
damaged iMac to Target Disk mode, the Firewire symbol
comes up on its screen OK, but on the connected
MacBook there is no sign of the iMac's drive
appearing. No icon, in other words. So I cannot even
access the faulty iMac's HD.
When you hook up via Target Disk mode, can you see the iMac's hard drive in the Disk Utility? In other words, can the other Mac see it, but just not mount it? That's a crucial difference, because if so, then you could try Data Rescue to at least get the data off the drive.
I've had several hard drives fail in a G5 iMac and I've had excellent luck with Data Rescue. You can download a free trial and see if it'll see any files at all on the affected drive. If it doesn't, you're not out anything. If it does, you're golden. My drives wouldn't mount, but Disk Utility would at least recognize they were there. Data Rescue doesn't have to be able to mount the drive, it just has to be able to see it.
Why do we have to go through all this? PCs get
viruses, Mac users get flawed security updates.
Like the others, I don't thing the security update in this case was the cause in the sense that if you had never done the update, this wouldn't have happened. More likely, something else would have triggered the problem. If not an update, then installing an update to a third party application, or something else.
One of the things about drives that I've learned over the years: S.M.A.R.T. is, in some ways, meaningless. It can flag a drive that's failing slowly, but if it has a sudden failure, you'll never know it. If it shows "Failing" in Disk Utility, believe it, but just because it shows "Verified" doesn't mean there isn't a potential problem just a few sectors down the drive that will take out the whole thing once you try to access those blocks.
charlie

Security update zapped Finder, now I can't get to permissions

The security update has screwed up one more item in my Mac: now I can't open Finder.
I had posted two other issues (Dashboard quitting) and inability to see the Apple.
Mike and Nerowolfe had suggested that I fiddle with the permissions from within DU, but I now can't open Finder, even though Finder seems to be open, when I mouse over it on the Dock (it has the little triangle). I right click on it and suggests I hide it or relaunch (a faded "not responding" is on top).
I also lost Mail. A message says The application Mail quit unexpectedly and asks me to relaunch, ignore or report.
How am I going to get to DU without being able to open Finder?
Thanks.
Roxy

Jose Abreu wrote:
The security update has screwed up one more item in my Mac: now I can't open Finder.
I had posted two other issues (Dashboard quitting) and inability to see the Apple.
Mike and Nerowolfe had suggested that I fiddle with the permissions from within DU, but I now can't open Finder, even though Finder seems to be open, when I mouse over it on the Dock (it has the little triangle). I right click on it and suggests I hide it or relaunch (a faded "not responding" is on top).
I also lost Mail. A message says The application Mail quit unexpectedly and asks me to relaunch, ignore or report.
How am I going to get to DU without being able to open Finder?
Thanks.
Roxy
Just a point. Your profile indicates you are running Tiger. Do you also have a box running Leopard or is your profile just out of date?
I assumed you were running Leopard when I posted a reply to your question.

Finder broken after (July 2013) 10.8.4 security update

Similar Messages

Maybe you are looking for