ThisCalculator

Everyday

Legacy System Extension Mac: What It Is & How to Fix

Updated · Standard formula, shown below

Average pace 5.00 min/km
Average speed
12.00 km/h
Result
Finish time
50 min
You entered
Distance
10 km
You entered

If you see a “System Extension Blocked” or “Legacy System Extension” message on your Mac, it means an older kernel extension (kext) that loads into macOS’s core is no longer fully supported. This article explains what legacy system extensions are, why macOS flags them, and how to manage them safely.

What Is a System Extension on macOS?

System extensions are software components that extend the capabilities of macOS at a low level. They can interact with network traffic, storage devices, or system events in ways ordinary apps cannot. Apple introduced a modern framework called System Extensions in macOS Catalina (10.15) to replace the older kernel extensions (kexts). The modern ones run in user space, meaning they don’t have direct access to the kernel, which improves security and stability.

Legacy system extensions are the old-style kexts that load directly into the kernel. They were common before macOS Catalina. Many hardware drivers, antivirus tools, and virtualization software used them. Apple has been deprecating kexts since 2019, and newer macOS versions block them by default unless the user explicitly approves them in System Settings.

Why Does macOS Show a Legacy System Extension Warning?

When you install an app that includes a legacy kext, macOS may show a message like “System Extension Blocked” or “Legacy System Extension” in System Settings. This happens because the operating system detects that the software wants to load code into the kernel, which is a security risk. Apple’s goal is to force developers to update their software to the modern extension model.

The warning appears when you try to open the app for the first time, or when you connect a device that uses the kext. macOS gives you the option to allow the extension, but you must do it manually in System Settings. The exact location varies by macOS version: in Ventura and later, it’s under System Settings > General > Privacy & Security. In older versions, it’s under System Preferences > Security & Privacy.

How to Allow a Legacy System Extension

If you trust the software and need to use it, here’s how to allow the legacy extension:

  1. Open System Settings (or System Preferences on older macOS).
  2. Go to General > Privacy & Security (or just Security & Privacy).
  3. Scroll down to the “Security” section. You should see a message about the blocked extension.
  4. Click “Allow” or “OK” next to the message.
  5. Restart your Mac if prompted.

If you don’t see the message, try opening the app again. Sometimes the prompt only appears after you launch the software. Also, make sure the software is up to date; many developers have released updates that use the modern system extension framework.

How to Remove a Legacy System Extension

If you no longer need the software, you can remove the legacy extension to keep your Mac secure. The easiest way is to uninstall the app that installed it. But sometimes the kext remains. Here’s how to remove it manually:

  1. Quit the app that uses the extension.
  2. Open Finder and go to the folder /Library/Extensions. (Note: this is the system library, not your user library.)
  3. Look for files with the extension .kext. They often have the name of the software.
  4. Move those files to the Trash. You may need to enter your administrator password.
  5. Restart your Mac.

Be careful: only remove kexts that you know belong to software you no longer use. Removing a needed kext can break hardware or apps.

Common Problems and Troubleshooting

One common issue is that the “Allow” button is greyed out or missing. This can happen if the kext is not signed by a valid developer certificate. Apple requires all kexts to be signed and notarized. If the software is old or unsigned, macOS won’t let you enable it at all. In that case, the only safe option is to contact the developer for an updated version.

Another problem is that after allowing the extension, the app still doesn’t work. This could be due to a different issue, such as the kext not being compatible with your macOS version. Check the software’s documentation for system requirements. Also, try restarting your Mac after allowing the extension—some kexts only load at boot.

If you see a message that the extension is “damaged” or “unable to verify,” it might be corrupted or tampered with. Do not force-load it. Instead, download a fresh copy from the official source.

Legacy vs. Modern System Extensions: Key Differences

Understanding the difference helps you decide whether to allow a legacy extension. Here’s a quick comparison:

  • Kernel access: Legacy kexts run in kernel space, which means they have full access to the system. Modern extensions run in user space, so they are sandboxed and less risky.
  • Security: A bug in a legacy kext can crash the entire Mac. A bug in a modern extension only affects that extension.
  • Approval: Legacy kexts require manual user approval after installation. Modern extensions are approved during the app’s installation process.
  • Compatibility: Apple plans to completely remove kext support in future macOS versions. Modern extensions will continue to work.

For most users, allowing a legacy extension is safe if the software comes from a reputable developer and you need the functionality. But if you have a choice, prefer software that uses modern system extensions.

How to Check Which Extensions Are Loaded

You can see which legacy extensions are currently loaded on your Mac. Open Terminal and run:

kextstat | grep -v com.apple

This shows all non-Apple kexts. If you see something you don’t recognize, you can investigate further. To get more details about a specific kext, use:

kextutil -show-all

But be careful: don’t unload kexts without knowing what they do. Unloading a needed kext can cause system instability.

Frequently Asked Questions

Is it safe to allow a legacy system extension?

It depends on the source. If you trust the developer and the software is essential, allowing it is generally safe. But legacy extensions have more power and can cause system crashes if they have bugs. Always keep the software updated and remove extensions you no longer use.

Why can’t I see the “Allow” button for the extension?

The “Allow” button appears only after you try to open the app that uses the extension. If it’s still missing, the kext may be unsigned or not notarized, which macOS refuses to load. In that case, you cannot allow it, and you should look for an updated version.

Will legacy system extensions stop working in the future?

Yes. Apple has said that kexts are deprecated and will be removed entirely in a future macOS release. Many developers have already switched to the modern system extension framework. If you rely on legacy kexts, plan to migrate to newer software soon.

How do I update a legacy system extension?

You don’t update the extension itself; you update the app that installed it. Check the app’s website or the Mac App Store for updates. Developers typically release new versions that use the modern framework, which removes the need for a legacy kext.

Can I delete a legacy system extension manually?

Yes, you can delete a kext file from /Library/Extensions, but you should only do that if you know it’s not needed. It’s safer to uninstall the app that installed it. If you delete a required kext, the associated hardware or software will stop working.

Related

Formula used
in t | Finish time | min | 50 | 0
in d | Distance | km | 10 | 0
out pace | Average pace | min/km | t / d | 2
out speed | Average speed | km/h | d / (t / 60) | 2

Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.