Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Same thing with current shipping versions of LittleSnitch (4.4.3) and AdGuard (2.3.2.710). My other computer also complained about the .kext for an USB3 → Ethernet adapter with ASIX AX88179 chipset.


I got the same message for Little Snitch as well.
 
The warning only appears the first time you use the app or kext.
Unfortunately, the warning will appear from time to time just as the 32-bit warnings appeared periodically in Mojave.
Until the transition is complete, your Mac displays a message when a legacy system extension first loads, and again periodically while the extension remains in use. This gives you advance notice that existing software on your system loaded a system extension that will be incompatible with a future version of macOS...
 
  • Like
Reactions: Barry K. Nathan
I'm getting frustrated at Apple doing this constantly.

Just the other day on my Windows 10 gaming computer I fired up Quake 3 Arena. The binary is dated 2002. It still worked, and worked perfectly. I played an 18 year old update for a 21 year old game without issues.

Meanwhile MacOS deprecates software from only five years ago.

I wish Apple would finalize stabilize the ABI so we don't have to deal with this annoyance going forward anymore.
 
OP wrote:
"I thought of creating a new volume with a second copy of 10.15, but I don’t know how or where to create the volume."

1. Get an external drive.
2. Get CarbonCopyCloner (or SuperDuper)
3. Use either of the above to create a bootable cloned copy of your existing OS setup.

That's really all you have to do...
 
Malwarebytes has announced they will be updated before the release comes out. It is a security issue to eliminate the extentions.
 
I would sure hope so!
I received the same notice after upgrading to 10.15.4. Simple fix, Log on to your account in Malwarebytes and make sure you have version 4, once you have version 4, go to Apple, Preferences, privacy, scroll to "Full Disk Access" check "Malwarebytes Protection". Ths information is on the Malwarebytes website.
 
I received the same notice after upgrading to 10.15.4. Simple fix, Log on to your account in Malwarebytes and make sure you have version 4, once you have version 4, go to Apple, Preferences, privacy, scroll to "Full Disk Access" check "Malwarebytes Protection". Ths information is on the Malwarebytes website.
Not sure what you are telling us. I have MWB v4, I have given it full disk access already and I got the warning about not running in future. In other words, your fix isn't a fix.
 
My AnyConnect VPN server is now gone and I will let me use it
 

Attachments

  • Screen Shot 2020-03-30 at 12.43.40 AM.png
    Screen Shot 2020-03-30 at 12.43.40 AM.png
    418 KB · Views: 89
Applied the OS 10.15.4 Combo Updater to both of my Macs previously running OS 10.5.3, and have not seen any such warnings. Also, so far (knock on wood!), things are good.

Chances are high you will. There are heaps of good apps out there that currently rely on kext files to work their magic.
 
I'm getting frustrated at Apple doing this constantly.

Just the other day on my Windows 10 gaming computer I fired up Quake 3 Arena. The binary is dated 2002. It still worked, and worked perfectly. I played an 18 year old update for a 21 year old game without issues.

Meanwhile MacOS deprecates software from only five years ago.

I wish Apple would finalize stabilize the ABI so we don't have to deal with this annoyance going forward anymore.

The alternative is the litany of Kernal Panic errors that inevitably pop up each major release, and the subsequent blame directed at Apple as a result.
 
The alternative is the litany of Kernal Panic errors that inevitably pop up each major release, and the subsequent blame directed at Apple as a result.

One solution, rather than killing kexts completely, would be to automatically disable a kext after it causes more than two kernel panics in a short period.

This is far better than breaking software, particularly hardware drivers.
 
One solution, rather than killing kexts completely, would be to automatically disable a kext after it causes more than two kernel panics in a short period.

This is far better than breaking software, particularly hardware drivers.
Kernel panics aren't the only issue around having software that runs at kernel level. This would provide no protection against a potentially malicious extension.
 
One solution, rather than killing kexts completely, would be to automatically disable a kext after it causes more than two kernel panics in a short period.

This is far better than breaking software, particularly hardware drivers.

Far easier said than done when A) kexts can cause the system to fail in a way where the system can't record what failed, B) because of the lack of memory protection in kernel mode, extensions can cause other innocent extensions to fail, e.g. by overwriting their memory, C) you can't tell if the thing you're disabling is critical for system function, e.g. killing a VPN when the system is configured to require network login. Finally, D) it doesn't solve the problem of malicious kernel-mode software or bugs in kernel-mode drivers exposing security vulnerabilities, the Intel side-channel attacks being a prime example of the latter.

The Microsoft solution, which is on by default in suitably new hardware, is to wrap the entire OS into a virtual machine and only allow trusted software to run on bare metal. Called Virtualization Based Security/Hypervisor Enforced Code Integrity, it does solve some of the security issues, but it doesn't solve stability issues, you pay ~10% in performance hit, and you can't use any non-Microsoft VM software.
 
Last edited:
  • Like
Reactions: TiggrToo
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.