Mojave Unsupported Mac

Install Macos Mojave On Unsupported Mac Macos 10.14 Mojave On Unsupported Macs Thread May 07, 2020 How to Install macOS Catalina on Unsupported Mac; With these much problems that are for Mac users, Windows users might not even think of getting Mac or MacOS somehow. Feb 15, 2021 How To Get Mojave On Unsupported Mac Os How to Install MacOS Mojave on Unsupported Macs with DosDude Mojave Patcher Tutorial: final note. For our visitors: If you have any queries regards the How to Install MacOS Mojave on Unsupported Macs with DosDude Mojave Patcher, then please ask us through the comment section below or directly contact us.

MacBook Pro with Retina display, macOS High Sierra (10.13.6) Posted on Sep 30, 2018 12:38 AM. Unsupported Mac models These Mac models may receive security updates in macOS Mojave, High Sierra or Sierra, but are unable to support the fixes and mitigations due to a lack of microcode updates from Intel.

Catalina (10.15) is the latest stable release of Apple's macOS. You will see some of the recent apps can only work on this version. And you have to upgrade macOS accordingly. However, only a small portion of Mac models are eligible for direct upgrade offered by Apple. What 's to do if you want to use Catalina on an unsupported Mac? This tutorial will show you how to install macOS Catalina on an unsupported Mac model.

1. Why macOS Catalina?

macOS Catalina is the last iteration of the macOS series, after which Apple has now moved to macOS 11 Big Sur. Not all Mac users will install Big Sur so soon after its release because they'll be waiting for all the major bugs to be fixed in an 11.x update. But there's also another reason: Big Sur is only meant for certain models of MacBooks and iMacs.

And some of the apps can not work on an old version of macOS, such as High Serria or Serria. You will receive the following messages if you try to run an app that only supports Catalina and later versions. You have to upgrade macOS to Catalina in such a case if the app is very important for you.

The same is true of Catalina as well, but Catalina is a more mature version and brings a lot of features to the table, such as the improved Siri, customizable smart lists, the new AI-based Photos app, better Notes search, refreshed Safari, and so on. Probably the most important change is the deprecation of iTunes into three separate entities for Music, TV, and Podcasts. That's why a large portion of users still prefer Catalina even if their device is compatible with Big Sur.

2. Official Support List by Catalina

Unfortunately, as in the case of Big Sur, macOS Catalina also does not support very old models of Apple devices. Here is the official support list. If your device is from an older year, you cannot upgrade to macOS Catalina the usual way.

MacBook (Early 2015 or newer)
MacBook Air (Mid 2012 or newer)
MacBook Pro (Mid 2012 or newer)
Mac mini (Late 2012 or newer)
iMac (Late 2012 or newer)
iMac Pro (2017)

In addition, your video card will need to be pre-metal, and it works with specific series of GeForce, Radeon, and Intel graphics cards.

3. Unofficial Support List by Catalina

Thankfully, there's a way to patch macOS Catalina on your older system, which extends the list of supported devices. However, you will need to download macOS Catalina dmg file, burn it to a USB drive, and then install Catalina on your Mac by booting from the USB installer. The process is shown below and it works with the following unsupported Mac models.

MacBook Pro Early 2008 or newer
MacBook Air Late 2008 or newer
Mac Mini Early 2009 or newer
MacBook Early 2009 or newer
iMac Early 2008 or newer

4. How to Create a macOS Catalina Bootable USB

UUByte DMG Editor is a fantastic disk image management utility for Apple's DMG files. Not only can you burn a DMG to a range of media storage devices but you can also extract files without having to mount the DMG as a virtual drive. Besides, it is a cross-platform application that works well on both Windows and macOS. This means you can create a bootable Catalina USB installer on a Windows PC.

Although it is meant for experienced users, the user interface, navigation, and feature layout have been simplified so even beginners can jump right in and get comfortable with the software. Here's the process in the form of steps you can duplicate on your Mac.

Warning: Please back up your Mac first before taking into real actions. This might brick your EFI chip with multiple EEPROM definitions.

Step 1: Download DMG file of macOS Catalina from the following sources. These site offer the latest version of the macOS Catalina, please download a copy to your Mac.

Download Link 1: https://themacgo.com/macdownload/
Download link 2: https://drive.google.com/drive/folders/NW4r628CM

Step 2: Insert a USB drive and install UUByte DMG Editor application on a Mac or PC.

Step 3: Launch UUByte DMG Editor and select the 'Burn' option on the main page.

Step 4: On the inside page, hit the 'Browse' button and select the DMG file from your local storage. Check if your USB drive is displayed in the field below the DMG image field. If not, click on 'Change' button to select the correct drive.

Step 5: All you need to do is name your drive and hit 'Burn' button. You will see the progress as the USB installer is created.

When you see the success message, close UUByte DMG Editor and eject the drive. It is now ready for you to use in the macOS Catalina installation process described in the next section.

5. Install macOS Catalina on Unsupported Mac

Now, follow the steps shown below carefully to load the installer, erase your local disk, and install macOS Catalina from USB drive you created in above step.

Step 1: Boot Mac from USB Installer

To do this, insert the installer and hold down the Option key as you restart your Mac. In the Startup Manager, choose the drive name that you used in the installer creation process. You won't be able to use the mouse here so use the arrow key to select your drive and hit Enter.

Step 2: Wait Catalina Installer to Be Loaded

This could take a few minutes so be patient. Don't worry if the screen goes blank or if the progress bar looks like it's frozen. Don't do anything at this point.

Step 3: Erase Local Hard Drive

When macOS Catalina installation wizard is loaded, you'll be able to see macOS Utilities window with several options. Choose Disk Utility option and then Continue. In Disk Utility, choose your hard drive (usually Macintosh HD) and hit Erase, which you will see in the top menu bar.

In the popup window, make sure the Format is set to APFS and hit Erase, leaving everything else as it is. You may want to change the name of the local HDD but you can leave it as Macintosh HD. Exit Disk Utility, which will take you back to the macOS Utilities window.

Step 4: Start Installing Catalina on Unsupported Mac

This time, in macOS Utilities, please choose Install macOS and then hit Continue. Hit Continue again to confirm the operation. When you see the license terms, hit the Agree option. You may need to do this twice for confirmation. Choose Macintosh HD (or however you renamed your local hard drive) and hit Install.

Wait for the installation to complete. This may take up to an hour or more depending on your system configuration and other factors.

Frequently Ask Questions

There are several known issues when installing macOS Catalina on ansupported Mac. However, it has less impact on daily usage.

No Tab for All Photos in Photos App. You will find this minor issue when using Photos app on Catalina. To fix this, you should right click any photo in Photos app and select 'Show in All Photos' from pop-up menu.

GPU acceleration not available. You will see a performance downgrade when playing games because the full video accleration is not available in Radeon HD 5xxx or 6xxx series video card.

WiFi not working. If you could not join any WiFi network, then you should use this command to fix it manually: sudo networksetup -setairportnetwork en1 SSID PASSWORD

Summary

Definitely, it is not a simple task to install macOS Catalina on an unsupported Mac. You have to complete the task manually, which is more challenging than a direct update being pushed by Apple official. However, the above tutorial proves to be fine on most of unsupported Macs we listed in Section 3. Now, enjoy using macOS Catalina on an officially unsupported device!

This advisory describes the changes and steps administrators can take to deploy Mac Connector 1.14.

The Mojave 10.14.1 update does NOT install properly on unsupported machines, and could result in an unbootable OS. If you want to install the 10.14.1 update (and are not currently running 10.14.1), perform the following steps. Jun 22, 2020 A: If your Mac had official support in macOS Catalina, they will likely be able to be patched to run Big Sur with minimal issues. As of writing, only WiFi appears to be unstable, and even then, not for all users. If your Mac was unsupported before the release of macOS Catalina, support remains to be seen as graphics acceleration may not be.

Mac Connector version 1.14 introduces a number of changes that require user attention. Most notably, this Connector release includes changes to full disk access approvals and adds support for macOS 11 (Big Sur) System Extensions.
Since the inital 1.14 launch, compatibility issues have been discovered with 3rd party applications on macOS 10.15 Catalina when system extensions are in use. Apple will be addressing these issues in future releases of macOS 11 but will not be fixing these issues in macOS 10.15. Consequently, starting with version 1.14.1, the Mac Connector will use legacy kernel extensions instead of system extensions on all versions of macOS 10.15.
Mac Connector 1.14 is required to ensure endpoint protection on macOS 11. Older Mac Connectors will not work on this version of macOS.
It is highly recommended to deploy the Mac Connector with an MDM profile that grants the required approvals. MDM profiles must be installed before installing or upgrading the Mac Connector to ensure the needed permissions are recognized. Refer to the Known Issues section later in this document if MDM cannot be used.

Minimum OS Requirements

AMP for Endpoints Mac Connector 1.14.0 supports the following macOS versions:

macOS 11, using macOS system extensions.
macOS 10.15.5 and later, using macOS system extensions.
macOS 10.15.0 through macOS 10.15.4, using macOS kernel extensions
macOS 10.14, using macOS kernel extensions.

AMP for Endpoints Mac Connector 1.14.1 supports the following macOS versions:

macOS 11, using macOS system extensions.
macOS 10.15 using macOS kernel extensions.
macOS 10.14, using macOS kernel extensions.

For deployments that include endpoints running older macOS versions, consult the OS Compatibility Table for compatible Mac Connector versions.

Important Changes

Mac Connector 1.14 introduces important changes in three areas:

Approving AMP macOS Extensions to load
Full Disk Access
New Directory Structure

Approving Mac Connector macOS Extensions

The Mac Connector uses either System Extensions or legacy Kernel Extensions to monitor system activities, depending on the macOS version. On macOS 11, System Extensions replace the legacy Kernel Extensions that are unsupported in macOS 11. User approval is required on all versions of macOS before either type of extension is allowed to run. Without approval, certain Connector functions such as on-access file scan and network access monitoring will be unavailable.

Macos catalina for macbook pro 2015. Mac Connector 1.14 introduces two new macOS system extensions:

An Endpoint Security extension, named AMP Security Extension, to monitor system events
A Network Content Filter extension, named AMP Network Extension, to monitor network access

Mojave Not Supported Mac

The two legacy Kernel Extensions, ampfileop.kext and ampnetworkflow.kext, are included for backwards compatibility on older macOS versions that don't support the new macOS System Extensions.

The following approvals are required for macOS 11** and later:

Approve AMP Security Extension to load
Approve AMP Network Extension to load
Allow AMP Network Extension to filter network content

** Mac Connector version 1.14.0 also required these approvals on macOS 10.15. These approvals are no longer required on macOS 10.15 when running Mac Connector 1.14.1 or later.

The following approvals are required for macOS 10.14 and macOS 10.15:

Approve AMP Kernel Extensions to load

These approvals can be granted using the macOS Security & Privacy Preferences on the endpoint, or by using Mobile Device Management (MDM) profiles.

Approving Mac Connector macOS Extensions at the Endpoint

System and Kernel extensions can be approved manually from the macOS Security & Privacy Preferences pane.

Approving Mac Connector macOS Extensions using MDM

NOTE: macOS Extensions cannot be retroactively approved via MDM. If the MDM profile is not deployed prior to installing the Connector then the approvals will not be granted and additional intervention will be required in one of the following forms:

1. Manual approval of the macOS Extensions on endpoints that had the management profile deployed retroactively.
2. Upgrading the Mac Connector to a newer version than the one currently deployed. Endpoints that had themanagement profile deployed retroactively will recognize the management profile after upgrade and gain approval once the upgrade completes.

AMP extensions can be approved using a management profile with the following payloads and properties:

Payload	Property	Value
SystemExtensions	AllowedSystemExtensions	com.cisco.endpoint.svc.securityextension, com.cisco.endpoint.svc.networkextension
	AllowedSystemExtensionTypes	EndpointSecurityExtension, NetworkExtension
	AllowedTeamIdentifiers	DE8Y96K9QP
SystemPolicyKernelExtensions	AllowedKernelExtensions	com.cisco.amp.fileop, com.cisco.amp.nke
SystemPolicyKernelExtensions	AllowedTeamIdentifiers	TDNYQP7VRK
WebContentFilter	AutoFilterEnabled	false
	FilterDataProviderBundleIdentifier	com.cisco.endpoint.svc.networkextension
	FilterDataProviderDesignatedRequirement	anchor apple generic and identifier 'com.cisco.endpoint.svc.networkextension' and (certificate leaf[field.1.2.840.113635.100.6.1.9] /* exists / or certificate 1[field.1.2.840.113635.100.6.2.6] / exists / and certificate leaf[field.1.2.840.113635.100.6.1.13] / exists */ and certificate leaf[subject.OU] = DE8Y96K9QP)
	FilterGrade	firewall
	FilterBrowsers	false
	FilterPackets	false
	FilterSockets	true
	PluginBundleID	com.cisco.endpoint.svc
	UserDefinedName	AMP Network Extension

Full Disk Access

MacOS 10.14 and later require approval before an application can access parts of the filesystem that contain personal user data (e.g. Contacts, Photos, Calendar, and other applications). Certain Connector functions such as on-access file scan will be unable to scan these files for threats without approval.

Previous Mac Connector versions required the user to grant Full Disk Access to the ampdaemon program. Mac Connector 1.14 requires Full Disk Access for:

'AMP for Endpoints Service' and
'AMP Security Extension'

The ampdaemon program no longer requires Full Disk Access starting with this new Mac Connector version.

Full Disk Access approvals can be granted using the macOS Security & Privacy Preferences on the endpoint, or by using Mobile Device Management (MDM) profiles.

Approving Full Disk Access at the Endpoint

Full Disk Access can be approved manually from the macOS Security & Privacy Preferences pane.

Approving Full Disk Access Using MDM

1. Manual approval of the macOS Extensions on endpoints that had the management profile deployed retroactively.
2. Upgrading the Mac Connector to a newer version than the one currently deployed. Endpoints that had the management profile deployed retroactively will recognize the management profile after upgrade and gain approval once the upgrade completes.

Full Disk Access can be approved using a management profile's Privacy Preferences Policy Control payload with a SystemPolicyAllFiles property with the following two entries, one for the AMP for Endpoints Service and one for the AMP Security Extension:

Description	Property	Value
AMP for Endpoints Service	Allowed	true
	CodeRequirement	anchor apple generic and identifier 'com.cisco.endpoint.svc' and (certificate leaf[field.1.2.840.113635.100.6.1.9] /* exists / or certificate 1[field.1.2.840.113635.100.6.2.6] / exists / and certificate leaf[field.1.2.840.113635.100.6.1.13] / exists */ and certificate leaf[subject.OU] = DE8Y96K9QP)
	Identifier	com.cisco.endpoint.svc
	IdentifierType	bundleID
AMP Security Extension	Allowed	true
	CodeRequirement	anchor apple generic and identifier 'com.cisco.endpoint.svc.securityextension' and (certificate leaf[field.1.2.840.113635.100.6.1.9] /* exists / or certificate 1[field.1.2.840.113635.100.6.2.6] / exists / and certificate leaf[field.1.2.840.113635.100.6.1.13] / exists */ and certificate leaf[subject.OU] = DE8Y96K9QP)
	Identifier	com.cisco.endpoint.svc.securityextension
	IdentifierType	bundleID

If your deployment includes computers running AMP Connector version 1.12.7 or older, the following additional entry is still required to grant full disk access to ampdaemon for those computers:

Description	Property	Value
ampdaemon	Allowed	true
	CodeRequirement	identifier ampdaemon and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists / and certificate leaf[field.1.2.840.113635.100.6.1.13] / exists */ and certificate leaf[subject.OU] = TDNYQP7VRK
	Identifier	/opt/cisco/amp/ampdaemon
	IdentifierType	path

New Directory Structure

Install Macos Mojave On Unsupported Mac

Mojave Unsupported Mac

Mac Connector 1.14 introduces two changes to the directory structure:

The Applications directory has been renamed from Cisco AMP to Cisco AMP for Endpoints.
The command-line utility ampcli has been moved from /opt/cisco/amp to /Applications/Cisco AMP for Endpoints/AMP for Endpoints Connector.app/Contents/MacOS. The directory /opt/cisco/amp contains a symlink to the ampcli program at its new location.

The complete directory structure for the new AMP Connector is as follows:

Known Issues with macOS 11.0 and Mac Connector 1.14.1.

Guidance for fault 10, 'Reboot required to load kernel module or system extension,' may be incorrect if four or more Network Content Filters are installed on the computer. Refer to the AMP For Endpoints Mac Connector Faults article for more details.

Known Issues with macOS 10.15/11.0 and Mac Connector 1.14.0.

Some faults raised by the Mac Connector may be raised unexpectedly. Refer to the AMP For Endpoints Mac Connector Faults article for more details.
- Fault 13, Too many Network Content Filter system extensions, may be raised after upgrading. Rebooting the computer will resolve the fault in this situation.
- Fault 15, System Extension requires Full Disk Access, may be raised after reboot due to a bug in macOS 11.0.0. This issue is fixed in macOS 11.0.1. The fault can be resolved by re-granting full disk access in the Security & Privacy pane in macOS System Preferences.
During installation, the Security & Privacy pane may display 'Placeholder Developer' as the application name when granting permission for the Mac Connector system extensions to run. This is due to a bug in macOS 10.15. Check the boxes beside 'Placeholder Developer' to allow the Mac Connector to protect the computer.
- The systemextensionsctl listcommand can be used to determine which system extensions are awaiting approval. System extensions with the state [activated waiting for user]in this output are displayed as 'Placeholder Developer' in the macOS preferences page shown above. If more than two 'Placeholder Developer' entries are showin in the above preferences page, uninstall all software that uses system extensions (including the Mac Connector) so that no system extensions are awaiting approval, and then reinstall the Mac Connector.
  The Mac Connector sysem extensions are identified as follows:
  - The Network Extension is shown as com.cisco.endpoint.svc.networkextension.
  - The Endpoint Security extension is shown has com.cisco.endpoint.svc.securityextension.
During install, the prompt to allow the Mac Connector's Content Filter to monitor network traffic may display '(null)' as the application name. This is caused by a bug in macOS 10.15. The user needs to select 'Allow' to to ensure protection of the computer.
If the prompt was dismissed by clicking 'Don't Allow' it can be displayed again by clicking the AMP Agent menulet icon in the menu bar and selecting 'Allow Network Filter.'
Once enabled, the AMP Network Extension filter will be listed in the Network Preferences page.
On macOS 11, when upgrading from Mac Connector 1.12 to Mac Connector 1.14, Fault 4, System Extension Failed to Load, may be raised temporarily while the Connector is transitioning from the kernel extensions to the new system extensions.

Revision History

Dec 1, 2020

Mac Connector 1.14.1 no longer uses system extensions on macOS 10.15.
Additional guidance on using terminal check which 'Placeholder Developer' System Extensions are awaiting approval when using Mac Connector 1.14.0.

Nov 9, 2020

Corrected bundle ID in full disk access CodeRequirement MDM payload.

Nov 3, 2020

Macos 10.14 Mojave On Unsupported Macs

Release date for 1.14.0 Mac Connector is November 2020.
The 1.14.0 Mac Connector will use System Extensions starting with macOS 10.15.5. Previously this was 10.15.6.
Added Known Issues section.
Updated directory structure outline.

Welcome to Mr. Macintosh.com. If you are part of one of the following groups, Mac Admins, Mac Support, Mac Developer, Mac in Education or Mac User, then this is the site for you. Each group is important, yet has different needs.

Mac Admin = This tag is for anyone in who is in Macintosh Architecture, Engineering, System Administration, or MDM Administrators.
Mac Support = Someone who supports or fixes Macintosh issues. This group includes anyone who works in a Macintosh Helpdesk role. You could be level 1-3 or even a Subject Matter Expert (SME) or Team Lead or Management.
Mac in Education = This group is for anyone working in K-12 or Higher Education. You could be a teacher, Helpdesk Analyst, or Administrator.
Mac Developer = A Mac Developer, covers anyone who develops software on the Mac, including macOS iOS, iPadOS, watchOS, and tvOS.
Mac User = This could be anyone who uses a Mac. You want to learn more about how the Mac works. You could be an everyday user, enterprise user, student, collector, or even an enthusiast.

I have at one time or another been a part of 4 of 5 groups. I started as a Mac User when I got my first Mac (Blue and White PowerMac G3). Then I got my first job in Mac EDU (Mac Higher Education). After that, I moved on to Mac Support (Mac Enterprise IT Support). Today I am a member of Mac Admins (Macintosh Architecture & Engineering).

If you are just getting started and are thinking of getting into a career supporting Apple devices, knowledge and learning is critical. Read and learn as much as you can along the way.

Macos Mojave On Unsupported Macs

Mojave Unsupported Mac Bootcamp

Be sure to check out my latest blog posts! If you have any comments or questions, feel free to contact me. Thank you for visiting my website.