Q: Post-update kernel panic (10.11.4)

Back in business after waiting hours for a Time Machine restore. Getting nagged about the update - I don't think so, thank you. I don't even want the iOS one now. I can live without passworded notes. Now a default font size that is not microscopic - that might be worth the risk.

I didn't get a kernel panic screen. I got the Apple logo and progress bar. It went to about 75% and then switched to a blank grey screen for about 30 minutes. I rebooted the machine. After that it would get to the same 75% progress on boot and then it would turn itself off. Maybe that's the ultimate kernel panic.

I checked the disk with Disk Recovery before I did the Time Machine restore and my disk has a clean bill of health.

Well, at least I know Time Machine works. Never used it before. I have a cloned image but it was almost a month old as opposed to the Time Machine version which was 1/2 hour old. Can also vouch for BackBlaze now.  I was able to recover the file I was working on and use an old pc to continue working.

I do have SUIDguard installed, so it's conceivable that's the culprit. It seems as though a safe mode boot shouldn't be affected, but who knows.

I'm keeping my fingers crossed on your behalf, and anxiously awaiting your report.

i also have an immediate  kernel panic after upgrading from 10.11.3 to 10.11.4 on two macs!

on an iMac 13.1 8GB i first tried the combo-update 10.11.4. after restart i got kernel panic, the quickly disappering message contained something like

"NSCFcharakterset toto sanshannuo". i deleted the content of the startup disk and made a clean install of os 10.11.4 : same kernel panic! so i have to assume

that it is an installer problem... PRAM reset did not help.

on a macbook pro 3.1 4 GB with os 10.11.3 i did the combo-update and also got the kernel panic.

after downgrading to 10.11.3 and reinstalling (for hours) the macs are working again.

its the first time i had such a problem with an update from apple and i am not amused

Check in /Library/Extensions for a file called SUIDGuardNG.kext.  If its there, delete it.  The 10.11.4 combo updater should then work. 

Re: Two iMacs will not boot after the 10.11.4 update.

i tried it on my macbook pro and it worked. many thanks! i will also try it later on the iMac.

do you know where this Extension comes from, the info says "Copyright © 2015 SektionEins GmbH"?

It is part of the SUIDGuard 'security extension': https://www.suidguard.com/stories/index.html

Always be careful with stuff like this. Apparently the maker – Mr. Esser – hasn't paid attention. Correction: in his Twitter account he actually advises to uninstall SUIDGUard before upgrading: https://twitter.com/i0n1c/status/712035159302905856

Quite ironic that a security fix causes more problems than it solves..

"SUIDGuard - A kernel extension adding mitigations to OS X to make exploitation harder".

https://github.com/sektioneins/SUIDGuard

thanks for the explanation! i still cannot understand, why a clean install of 10.11.4 on an empty disk could lead to kernel panic, since the file SUIDGuardNG.kext was not there.

a backup of my iMac takes 4 hours, so i prefer to wait for further information

That's why it is so important to open new topics for each separate case: kernel panics can have many different causes.

Removing /Library/Extensions/SUIDGuardNG.kext solved the problem for me.

The file might be hidden.

I'm not sure why safe boot is affected.

SUIDGuard is a third-party tool that mitigated against a vulnerability in earlier versions of OS X. Well worth it in its day.

i tried to install 10.11.4 on my iMac running os 10.11.3 using the combo update without success. the installer stuck for one hour with the message "configuring",

i shut the computer down, and could not restart from external devices. i then did a PRAM and SMC reset and was able to restart from an USB stick containing the os x 10.11.4 installer. to my surprise, this time it worked an i am now with os x 10.11.4! thanks again for your advices.

I have to iMacs. One finished with a blank screen but a shutdown and startup fixed it.

On the other hand my wife's iMac, continuosly shutdown. I twice started using the recovery disk and reinstalled the system. The second time it got fixed

Your wife's iMac sounds like my situation. Good to know that a second install will probably work. It dawned on me that I -will- have to try this again at some point. Will do a disk image prior so a possible reinstall does not take all day. Thanks for posting your results.

I did not have SUIDGuardNG.kext