I have a Macbook Pro 2018 15' running Mojave (latest update). After updating to the latest Little Snitch and restarting my machine it now fails to boot.I boot up and can enter my password (I'm running FileVault so I'm not sure if this is the HD unlock login or actual account login). Once I've entered my password the loading bar appears and gets to about 75% before the screen goes blank (black but with backlight), with no cursor.If I try to boot in safe mode, the same thing happens, but instead of a completely blank screen I see the white loading spinner (on black background). After a few seconds a see the cursor blink briefly but then then it reverts to a blank screen and the process starts again (with the spinner showing, curosr blinking briefly etc. ).I've tried:. Reinstalling the OS from recovery. Starting in verbose mode (no useful info I can make out).
Little Snitch 4 - Gift Card Edition Runs on macOS 10.11 up to 10.14 (Mojave) The gift card comes with coupon code that must be redeemed in order to receive the personal Little Snitch license key. May 18, 2019 Little Snitch also lets you set timing for the rule, which lets you minimize access to apps or services you may not fully trust to have unfettered access. While Forever is the default, holding down Shift toggles the menu choice to Once, and pressing Control toggles it to Until Quit.
![Little Snitch Mojave Little Snitch Mojave](/uploads/1/2/5/6/125633069/468039248.jpg)
Starting in safe mode (above). Clearing PRAM/NVRAM. Clearing SMC. Running first-aid on the boot drive.
Removing the Little Snitch kext file via this link:It feels like there is something wrong with the Windows Server (which is mentioned in the above Little Snitch article) and that there has been an issue building the kernel while updating Little Snitch but I'm not sure how to diagnose further and/or fix it. I have a MacBook pro running MacOS Mojave.For the past year or so, every time a new MacOS update rolls out, and is attempted to be installed on my MacBook, it ends up displaying the circle slash (Prohibitory Symbol). Rebooting still produces a prohibitory symbol.
I’m still able to boot into recovery mode ( command- R at startup), however running disk repair on my MacBook HD does NOT solve the problem. I have also tried:. specifying the startup disk (problem still persists);. attempting to start in safe mode (problem persists);. doing the NVRAM reset (problem persists).In the past, the only way I was able to get around the problem, is by re-formatting my HD, installing latest version of Mojave OS, and then migrating all my data from my Time Machine backup.This happened again the other day with the recent Mojave 10.14.2 update.My computer automatically installed the update overnight, and in the morning, my screen was showing circle slash.
This time I did some more research, and discovered that the issue may be caused by unsigned kernel extension (KEXT) files existing on my HD.Kernel Extensions are pieces of code that extends the capability of the base kernel of an operating system. The kernel typically manages Input / Output (I/O) requests, and in macOS the file ends in.kext.Starting with Yosemite, kernel extensions must be code-signed by the developer with Apple authorization or macOS won’t load them.