10.12.6 update problems when restarting imac

Beyond the kext becoming clearly suspicious ... we need that to be handle from Apple, come on, and the issue to be fixed in a new update. I cannot guess which precise kext I should think eliminating, there's no clear criteria for that, and from the names you can't infer which one(s) should be removed. I would really like and appreciate getting an answer from someone from Apple, at least acknowledging that the problem exist, that they're working on solving it, and that we can rely in having (sooner enough) a solution.

Is that possible?

French MacBook mid 2010 with SSD

Same problem after 10.12.6 update

I follow your procedure,

I found in the Extensions folder kext file named hp_io_enabled_compound.kext

After moving it away the boot process was solved

French users :

Le probleme de démarrage après la mise à jour 10.12.6 est résolu en ne conservant que les kext par défauts du dossier /Library/Extensions

Pour ma part le fichier hp_io_enabled_compound.kext posait problème suite à cette mise à jour

...

It certainly IS a .kext problem. At least in my case.

Following GionDschember advice, I did not like the deleting approach, so I renamed my suspect:

hp_io_enabler_compound.kext

to a harmless:

hp_io_enabler_compoundkext.bak.

It rebooted flawlessly afterwards.

OK so looking through the various replies here's what worked for me:

Navigate to Volumes/Macintosh HD/Library/Extensions.

Deleted the BJUSB and CIJUSB kext files completely.

Found hp_io_enabler_compound.kext and renamed to hp_io_enabler_compoundkext.bak.

Backed-up the m/c and launched the macosupdcombo10.12.6.dmg file downloaded from Apple.

Worked fine.

One work-around, admittedly a hack, is to login to the mac in question via another mac on your home network via screen share. This allows you to "login" to the mac and to get to overcome the stalled installation completion. Worked for me.

I had a similar problem when I kept getting restart prompts with the OS version showing 10.12.6.

Despite at least 10 restarts the update process seemed to be in an endless loop with the App Store stating the update had not completed because the Mac needed restart. Called Apple Support and was advised to

1) Shutdown the Mac.

2) Restart in Safe Mode by having one finger on the Shift button and the other on the restart button.

3) Checked in App Store if there were any updates available. System prompt was there were "No updates available"

4) Restarted normally.

Above sequence resolved the issue for me.

I'm new to Mac so I'm not sure what normal boot up looks like. I'm running OS 10.12.6. After turning it on the white screen with the logo shows, then another white screen with the loading bar which gets about half way. Then the screen goes black for 10-15 seconds followed by the log in. Once I enter the password its fine..Is this normal?

I too have spent the last 3-4 days trying to rectify this issue. I am now trying to re-build slowly - since I foolishly didn't back up before hand.

I don't have a Canon printer but and Epson Stylus R200 and when I updated the driver for this today I did get a message flash up that something relating to it was no longer supported. Alas I did not write this down. I do have a file named EpsonUSBPrintClass.kext I wonder whether this could be the issue on my machine.

I will not now update this version of Sierra - I just don't trust it.

What a total waste of my time and Apple help-team's time this has been.

Running a 2015 MacBook Pro Retina 2.5Ghz Intel Core i7

I have a stupid question. It seems the solution is to delete the culprit kext files. But if the computer isn't starting, and it's stuck on the screen with the Apple logo and the progress bar isn't moving, how are you getting into the computer to delete the kext files? Would the answer be by booting into safe mode?

You have to boot into recovery mode (command R) and then use terminal to delete the nasty files. Not for the faint hearted but it does fix the problem. It will also teach you a little bit about the underlying unix based os which is never a bad thing!

Hi GionDschember, In the terminal, I cannot rename or delete files in the /Library/Extensions/ even after disabling the Apple protection (by csrutil). It states always "read-only file system". How can I overcome this? Thanks.

This is what I know. What happened during the beta testing? What?

I have had Apple computers since Apple was about three years old, and I have four generations of products I use to date. What I learned back in the days of a Performa was....never install an update for at least a month. Then, look at the Apple community to see if there are issues. If there are issues installing the update, just be patient and wait.

Yes, I use Apple because I had to only turn it on. No, I have no interest in learning about BJUSB, kext files, or ever spending another three days of my life trying to "repair" my computer after an Apple update.

Apple.

What happened to being excellent?

I've had exactly the same problem. I had to restore from Time Machine. A bit of a disaster because my last backup was under a different operating system as I had not upgraded to sierra at that point.

Now every time it asked me to upgrade to Sierra, which I do and then it locks up again. Complete disaster three days out of work. My bad for not having the latest update

Hi,

Thanks a lot for this precious informations.

But, I have a lot of .kext files in both "Volumes/Macintosh HD/Library/Extensions" and "Volumes/Macintosh HD/System.Library/Extensions"

How did you find (determine) those specifics "problematic - none rebooting" .kext files ?

Still waiting @ 10.12.5 level

Benoit.

Hello,

I spent days on this issue and I go crazy.

When starting in verbose mode (cmd-V), it indeed seems to be a kext issue. I get some garbage characters after a line mentioning kextwait or something similar.

After a restore to 10.12.5 from a Time Machine backup, I removed all kext in the MacIntosh/Library/Extension (not the system folder which contains the default apple kext).

It did not solve anything. I am still stuck on the boot loop when restarting after updating to Sierra 10.12.6.

This in on a MacBook Pro late 2013. No problem on my iMac.

My only way out is a Time Machine 10.12.5 reinstall after reformatting the hard drive.

The most frustrating is the total absence of any information from Apple.

Phil