Mac 10.13 Some System Software Was Blocked From Loading Rating: 7,3/10 1967 reviews

Best antivirus and malware software for mac computer. Macs may be a far less tempting target for malware and viruses, but they’re not immune from attack.

Apr 15, 2020  This article was co-authored by our trained team of editors and researchers who validated it for accuracy and comprehensiveness. WikiHow's Content Management Team carefully monitors the work from our editorial staff to ensure that each article is backed by trusted research and meets our high quality standards. The wikiHow Tech Team also followed the article's instructions and verified that. Apr 07, 2017  macOS has a feature called “Gatekeeper” designed to lock down your Mac, forcing it to only run Apple-approved software by default. But a Mac is locked down in the same way Android is locked down–you’re still free to run any application you want. Gatekeeper works a little differently depending on which version of macOS you’re running.

Modifying this control will update this page automatically

Safari User Guide

If you can’t open a website, try these suggestions.

  1. In the Safari app on your Mac, check the message that appears when a page fails to open.

    It may suggest ways to solve the problem or include information you need to solve it.

  2. Make sure you’re using the correct address for the webpage.

    If you copied and pasted the address, make sure it doesn’t have extra characters or missing characters at the beginning or end.

  3. If the website requires a VPN connection, make sure it’s functioning properly.

    See Connect your Mac to a VPN.

  4. Try entering /index.html or /index.htm at the end of the address.

  5. Choose View > Reload Page.

    If the page still won’t open, quit Safari, reopen it, then try again.

  6. Try again at a different time.

    The website server may be busy, or the website may be unavailable temporarily.

  7. Contact your network administrator for help.

    If you connect to the internet using a corporate or enterprise network, the network may have a firewall that prevents you from opening the webpage.

  8. If your computer or network is protected by a firewall, you may need to specify proxy servers to access some internet sites.

    See Set up a proxy server using Safari.

  9. Contact the website’s owner to find out if the web server has a problem, or if the website is incompatible with Safari.

    For example, Safari can’t open a website that uses a protocol other than http or https.

  10. Choose Apple menu > App Store, then click Updates.

    Use the latest version of Safari. See Keep your Mac up to date.

  11. Click and hold the Reload button , then choose Reload Without Content Blockers.

    The page might be blocked by a Content Blocker you have installed.

See alsoIf an app freezes or quits unexpectedly on MacIf you can’t open a Safari window on MacIf features on a webpage don’t work in Safari on Mac
Technical Note TN2459

macOS High Sierra 10.13 introduces a new feature that requires user approval before loading new third-party kernel extensions. This feature will require changes to some apps and installers in order to preserve the desired user experience. This technote is for developers who ship kernel extensions to users and system administrators who need to install kernel extensions.


macOS High Sierra 10.13 introduces a new feature that requires user approval before loading newly-installed third-party kernel extensions (KEXTs). When a request is made to load a KEXT that the user has not yet approved, the load request is denied. Apps or installers that treat a KEXT load failure as a hard error will need to be changed to handle this new case.

Approval is automatically granted to third-party KEXTs that were already present when upgrading to macOS High Sierra.

Note that approval doesn't guarantee that a KEXT is compatible and won't panic the system. The reason this feature exists is to give users more control over what KEXTs will load, which should reduce the number of panics.

In-Depth Explanation

This feature enforces that only kernel extensions approved by the user will be loaded on a system. When a request is made to load a KEXT that the user has not yet approved, the load request is denied and macOS presents the alert shown in Figure 1.

This prompts the user to approve the KEXT in System Preferences > Security & Privacy as shown in Figure 2.

This approval UI is only present in the Security & Privacy preferences pane for 30 minutes after the alert. Until the user approves the KEXT, future load attempts will cause the approval UI to reappear but will not trigger another user alert.

The alert shows the name of the developer who signed the KEXT so the user has some information to decide whether to approve the KEXT. This name comes from the Subject Common Name field of the Developer ID Application certificate used to sign the KEXT. Because of this, developers are encouraged to provide an appropriate company name when requesting KEXT signing identities.

When the user approves a KEXT, they are at the same time approving these other KEXTs signed by the same Team ID:

  • If the approved KEXT is located in an application's bundle, all other KEXTs signed by the same Team ID in the same application's bundle are also approved.

  • If the approved KEXT is located in the app's sub-directory inside /Library/Application Support, all other KEXTs signed by the same Team ID found in that same sub-directory are also approved.

  • All KEXTs in /Library/Extensions signed by the same Team ID are also approved.

Mac 10.13 Some System Software Was Blocked From Loading

Once approved, the KEXT will immediately be loaded or added to the prelinked kernel cache, depending on what action was blocked. Subsequent requests to load the KEXT will proceed silently as on previous macOS versions.

Approved KEXTs are tracked in a system-wide policy database through the team identifier in the KEXT's code signature and the bundle identifier from the KEXT's Info.plist, so updating a KEXT that has already been approved will not trigger a new approval request.

How This Affects KEXT Developers

Installers and applications that load kernel extensions may need to be revised to gracefully handle the kernel extension failing to load. Many products treat a KEXT loading failure as a hard failure. Some prompt the user to reinstall, some present a cryptic error message, and some simply don't function.

Starting with macOS High Sierra, installers and apps that load KEXTs should expect that KEXT loading will fail if the user hasn't approved their KEXT. Instead of treating this as an error, the user should be informed that they may need to approve the KEXT.

To determine if a KEXT has failed to load because it does not have user approval:

  • If you are using kextutil or kextload, check for the exit code 27. In addition, kextutil will produce the error message System policy prevents loading the kernel extension.

  • If you are using the KextManager APIs in IOKit/kext/KextManager.h, check for the result code kOSKextReturnSystemPolicy.

How This Affects Enterprise App Distribution

For enterprise deployments where it is necessary to distribute software that includes kernel extensions without requiring user approval, there are two options:

  • If your workflow is based on imaging, boot into Recovery OS and use the spctl kext-consent command. For detailed information about the spctl command, run the command spctl help. This command can either disable the user approval requirement completely or specify a list of Team IDs whose KEXTs may be loaded without user approval. The spctl command works in any installation environment, including Recovery OS and from NetBoot/NetInstall/NetRestore images.

    Note that the Team ID list maintained by spctl is separate from the system-wide policy database.

  • For workflows that leverage Mobile Device Management (MDM), please see the AppleCare support article Prepare for changes to kernel extensions in macOS High Sierra.

To reiterate, all third-party KEXTs that were already installed at the time of upgrading to macOS High Sierra are automatically approved and don't require any user action.

Document Revision History


Updated for MDM changes in macOS 10.13.4.


Updated for macOS High Sierra beta 8.


Updated for macOS High Sierra beta 4.


Updated for macOS High Sierra beta 3.


New document that describes the user-approved kernel extension loading feature introduced in macOS High Sierra.

Mac 10.13 Some System Software Was Blocked From Loading Iphone

Copyright © 2018 Apple Inc. All Rights Reserved. Terms of Use Privacy Policy Updated: 2018-04-19