This meant it unloaded the loginwindow, waited and then re-loaded it. Irritating to say the least.įrom a predecessor, we had a legacy LaunchDaemon that was set to delay the loginwindow to ensure network and AD were active before the login window was. hang! As Apple has a horrible tendency to put firmware updates within their OS updates these days, I suspect its a firmware patch being applied that causes the initial problem, until the Mac is booted into single user mode or Safe boot mode, and then it seems OK.

Just curious, but do you tend to see this after a Mac gets updated with any software updates? That seems to be when we see it most frequently, like a Mac running 10.10.4 that updates using the 10.10.5 Combo Updater. Something with the combination of these settings causes this boot hang problem, but I'll be damned if I know exactly what it is. In rare cases I've need to go in and disable FV2 and the firmware password from Recovery HD and reboot and then it would come right up. And yes, our Macs are all joined to AD and have FileVault 2 enabled.

Other times we need to do SUM and run a disk check (for us that means booting to Recovery HD and disabling the firmware password first) its incredibly annoying. As you stated, sometimes a reboot will fix it. Oddly, 10.10.3 and 10.10.4 improved the situation and then 10.10.5 came along and things blew up again for us. Although its gotten a bit better under 10.11 for us, almost all versions of 10.10 exhibited this problem from time to time.

Yes, its an unfortunate consistent issue we face here as well.

Mac el capitan update stuck at startup