Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Don't install on High Sierra without a full system backup!! Hangs on login screen during restart #698
Type of Controller
macOS 10.13.4 High Sierra
Device Name and Info
Response of Controller
Response in Preference Pane
Detailed Explaination of Issue
I installed the drivers (I think the controller might have been already connected? Not sure) and allowed "Drew Mills" in System Preferences then rebooted as instructed. Tried to log in and the progress bar progressively slowed down after ~50% then eventually got all the way to 100% but just got stuck there and wouldn't log me in. Tried force rebooting into safe mode but it wouldn't work so I rebooted into recovery mode and did first aid on the drive (not sure if that did anything). Rebooted again holding shift to try to go into safe mode but it didn't appear to work (didn't say "safe boot" in top right corner, login screen functioned normally). Tried logging in anyways because I was out of ideas, left it alone on the loading screen for a while and when I came back it had magically kicked itself back to the login screen in safe mode. I was then mercifully able to log in and I immediately uninstalled the drivers and now it boots normally. I don't know how it ended up in safe mode but I guess I was lucky that it did because I didn't have enough space on my disk to reinstall macOS. This whole thing took about 2 hours and involved a lot of panic so I wouldn't recommend anyone else install it without a backup or a death wish.
Hi, I had the same problem just now and got really scared. After the Safety Mode, resetting the SMC, and resetting the NVRAM didn't help, I managed to run First Aid via Disk Utilities. I managed to log in afterwards normally and deleted the driver. Hope this will help someone else and helps avoid some stress :)
referenced this issue
Jun 13, 2018
As I've said before many times, I'd love to fix this issue but I simply can't reproduce it to find the error and resolve the issue. Is there any other extension or program on your machine that would run as part of the boot process that may be causing some sort of incompatibility with the driver?
Since we seem to be failing on the Bluetooth coexistence part of boot, here's a version of the driver with none of the Bluetooth controller hooks in it, just for kicks and giggles. The timelines don't quite add up on this being the solution, but it's worth a shot. Let me know what your results are if you give it a shot.
Well that's good enough for me. I've been looking for a legitimate reason to strip the Bluetooth code out of the driver for a while and you've given me a wonderful present.
I'm pushing this change and making a new release. I will leave this issue for a short period for feedback on this change.