Mojave Unsupported

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

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. But that's not true. With all those problems, there's still some workaround in the underground to make it work. That is install macOS Mojave on Windows.

MacOS Mojave Patcher is an application that lets you run macOS 10.14 on unsupported hardware. It is developed by developer Dosdude who also developed similar patches for Sierra and High Sierra firmware. It automatically downloads the latest Public Beta version from Apple's servers and creates a bootable image out of it. Music file: any question you have:D. Install Macos Mojave Unsupported Mac Posted By admin On 22/08/21 In this post, we will Download macOS Mojave VMware & VirtualBox Image. MacOS Mojave may be an old version of macOS, but it still has its own lovers and users that wish to download, install, and use macOS Mojave.

1. How to keep older Macs secure: a geeky approach (run Catalina on unsupported Macs) Posted on October 8th, 2019 by Jay Vrijenhoek. Note: This article was originally written for macOS Mojave, and has been adapted for macOS Catalina. From a security standpoint, using the latest version of macOS—the Mac operating system—is always preferred.
2. Allow the installation to proceed and the relevant patches will be applied to your unsupported Mac automatically. Apple could always release a future update to macOS 10.15 that prevents the.

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:

1. Approving AMP macOS Extensions to load
2. Full Disk Access
3. 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.

Mac Connector 1.14 introduces two new macOS system extensions:

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

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:

Install Macos Mojave On Unsupported Mac

Macos Mojave Unsupported Mac

• 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:

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

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 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:

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:

New Directory Structure

1. How to keep older Macs secure: a geeky approach (run Catalina on unsupported Macs) Posted on October 8th, 2019 by Jay Vrijenhoek. Note: This article was originally written for macOS Mojave, and has been adapted for macOS Catalina. From a security standpoint, using the latest version of macOS—the Mac operating system—is always preferred.
2. Allow the installation to proceed and the relevant patches will be applied to your unsupported Mac automatically. Apple could always release a future update to macOS 10.15 that prevents the.

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:

1. Approving AMP macOS Extensions to load
2. Full Disk Access
3. 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.

Mac Connector 1.14 introduces two new macOS system extensions:

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

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:

Install Macos Mojave On Unsupported Mac

Macos Mojave Unsupported Mac

• 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:

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

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 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:

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:

New Directory Structure

Mac Connector 1.14 introduces two changes to the directory structure:

1. The Applications directory has been renamed from Cisco AMP to Cisco AMP for Endpoints.
2. 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

• 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.

Carbon Copy Cloner requires macOS. CCC will not run on Windows.

Carbon Copy Cloner 5 is the latest version available. Users running Yosemite (10.10), El Capitan (10.11), Sierra (10.12), High Sierra (10.13), Mojave (10.14), or Catalina (10.15) should use this version of CCC. If you are having trouble downloading CCC from the link above, try this alternate download location.

Upgrading from CCC 4? CCC 5 is a paid upgrade. CCC 4 Personal and Household licenses purchased prior to May 22, 2017 are eligible for upgrade pricing. When you open CCC 5, it will automatically retrieve your new license or an upgrade coupon that you can use to purchase CCC 5 at 50% off. CCC 4 licenses purchased on or after May 22, 2017 are eligible for a free CCC 5 upgrade license.

CCC 5: Support for macOS 11 Big Sur

CCC 5.1.22 (and later) is qualified for macOS 11 Big Sur. Open CCC and choose 'Check for updates..' from the Carbon Copy Cloner to get the update, or click the 'Download CCC 5' button above. Please take a moment to review the following resources prior to upgrading to macOS Big Sur:

Macos Mojave On Unsupported Mac

Carbon Copy Cloner 4.1.24 is compatible with Mountain Lion (10.8), Mavericks (10.9), Yosemite (10.10), El Capitan(10.11), Sierra (10.12) and High Sierra (10.13). Note that while this version of CCC may work on El Capitan and newer OSes, we recommend that El Capitan+ users upgrade to CCC 5. We offer technical support for CCC 4, but we are no longer actively developing it. If you are having trouble downloading CCC from the link above, try this alternate download location.

Install Macos Mojave On Unsupported Mac

CCC 4 and Mojave+: CCC 4 is qualified up to macOS High Sierra. CCC 4 license holders are welcome to continue using CCC 4 on later OSes with the understanding that this is an untested and unsupported configuration. CCC 5 is fully qualified on macOS Mojave and offers extensive support for APFS, including support for point-in-time restores via APFS filesystem snapshots.

Install Macos Mojave On Unsupported Macs

Unsupported Versions

Macos 10.14 Mojave On Unsupported Macs Thread

Download CCC 3.5.7 for use on Snow Leopard (10.6) and Lion (10.7). Download CCC 3.4.7 for use on Tiger (10.4) and Leopard (10.5). CCC 3.4.7 and 3.5.7 are provided as-is; we regret that we cannot offer any support for the installation or use of these older versions of CCC.

If you're using macOS Mojave or later, choose Apple menu System Preferences, then click Software Update. If you're using an earlier macOS, use the App Store instead. Learn how to download and install macOS Big Sur Go to the App Store. Upgrade os x mojave. Feb 05, 2021 macOS Mojave 10.14 can upgrade High Sierra, Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion macOS High Sierra 10.13 can upgrade Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion Safari downloads the following older installers as a disk image named InstallOS.dmg or InstallMacOSX.dmg.

Comments

Apple Support Download Mojave

• Hi William; Ref: The Mojave Patcher Tool for Unsupported Macs is available for download from DosDude. This is the same guy that did this for High Sierra, and has supplied a series of other hacks and workarounds for fans of older Apple hardware. The guy's name is dosdude1.
• In addition: i habe a very good experience with running High Sierra on two officially unsupported MBPs, one from 2011 and one from 2009. Also Mojave PB is Running pretty stable on another MBP - which is, however, officially supported. I will do the same like with HS, which is skipping the early versions of DosDude's tool and hen go for it
• Yes, the High Sierra version for unsupported Macs is smooth on my upgraded 2008 unibody. I've had no problems running it, and the experience sure beats being stuck on El Capitan.
• So, is the UI really slow without Metal support?
• Re: 'One more thing. If you do use this patch tool to install macOS Mojave on your main Mac, please remember that you can still read AppleInsider on your iPhone if things go awry.'
  Priceless.
  
• I'm using DosDude's High Sierra patcher on the 2008 MacBook Pro I use for live performance, and it runs flawlessly. It's perky, too! I consider myself very much in his debt.
  I'm definitely going to be making the step to Mojave. I wrote him a while back hoping he would be providing a new patcher, and it sure looks like he resolved the issues he mentioned he was having.
  I won't be installing the beta, but once the Gold Master release has been out for 2 or 3 weeks and the first round of fixes have been made, I'm going for it. I should note that I've got two much more recent desktop Macs I'll be updating the old-fashioned, Apple-approved way… I would not recommend running the patcher on your primary lose-it-and-die computer. There's too much at stake.
  Still, everything's gone smoothly on the High Sierra version. Kudos to DosDude!
  
• Do not tell it outloud. Apple will make all effort to kill that tool to sell more new hardware. It made all effort on the past hardware to make almost impossible to install systems like Linux on their hardware to reuse it. Yes system that in basic form (an many times in competitive form of Ubuntu desktop) can be installed on almost anything you can find in PC scrap. I do not believe it was for perofrmance reasons purely. Also before we jump on conclusion that Apple modern solutions require hardware I have just found out from a freind who just left them that there is a lot to be desired in their system quality area... especially on Macs. Time to listen to expereinced engineers rather than having cocky programmers who do not understand where all it goes and how it always ends.
• While this article is informative, I think there is information you are leaving out.
  I'd give proper attribution to conversation about Mojave on Unsupported Macs being an active discussion hosted by Dosdude on Macrumors.com. Yes, it's a competitor but much of the information needed to be successful about doing this patch is found in the pages and pages of discussion amongst the users as bugs are crushed and more machines are added to the compatibility (or partial compatibility) list. It's no different than when you attribute a store broken by another website or news outlet. Just referring to Dosdude's own download page doesn't get around that fact.
• This is probably a good thing. I'm not sure I will venture to Mojave on my MacBook Pro 5,5 or iMac 12,2, though. I put Sierra on the MacBook Pro to keep it aligned with the iMac, and only because Logic X 10.4 demanded Sierra. I might run it on a test hard drive to see what it's like. Sierra works very well on my machine that Apple arbitrarily dumped.
  Apple keeps shortening the support time. Logic's demand of Sierra or High Sierra was an annoyance to many Logic users.
  This pressure to upgrade has been getting worse because of iOS devices and iOS has an incredibly annoying nag to upgrade. I'm not happy about Apple's choices and it makes it very difficult for their customers to maintain a functioning 'Apple ecosystem' unless they're wealthy enough to repeatedly re-buy effectively the same devices every two or three years. It didn't used to be the case that you had to be wealthy to be an Apple user (just judicious spending and saving), but Apple's ecosystem is exactly designed to encourage, or push, people into multiple Apple devices, and upgrade each one more often. This is bad for consumers and they're too arrogant and too big to notice this. Eventually it will lose them customers and they don't care to watch out for this at this time.
  Granted, they did just take some action to possibly pull back on this a bit, with promoting iOS 12 as being faster on older devices (I've avoided iOS 11 but I might go to iOS 12). They need to do more of this, on all platforms.
• I bet Windows 10 runs perfectly on Boot Camp on a 2008 Mac without any hacks at all.

• I bet Windows 10 runs perfectly on Boot Camp on a 2008 Mac without any hacks at all.

  Runs perfectly on a 2009 (Mac Pro), at least. And you can even use the most modern Boot Camp drivers by bypassing Apple's in-Windows compatibility check.

• While this article is informative, I think there is information you are leaving out.
  I'd give proper attribution to conversation about Mojave on Unsupported Macs being an active discussion hosted by Dosdude on Macrumors.com. Yes, it's a competitor but much of the information needed to be successful about doing this patch is found in the pages and pages of discussion amongst the users as bugs are crushed and more machines are added to the compatibility (or partial compatibility) list. It's no different than when you attribute a store broken by another website or news outlet. Just referring to Dosdude's own download page doesn't get around that fact.

  While I appreciate MR holding the conversation, they didn't break this. When appropriate, we give other sites credit -- including MR. This is a complicated situation for both MR and us, with a history and discussion about it going for pages and pages.
  Users are welcome to -- and should -- use Google to seek information on any workaround we publish, or to seek amplifying information on tips.

  edited July 2018

• So, is the UI really slow without Metal support?

  No, because macOS bases the general UI on the process 'WindowServer', and there was a useful
  discovery that Apple has not rewritten this using Metal, just preferring to delete the OpenGL drivers
  for ye olde 'unsupported' Macs instead. (So far, to Public Beta 3, anyway.)
  Turns out the OpenGL drivers and other kernel extensions (kexts) can be re-animated from older macOS releases
  with the requisite incantations.
  There are some issues with hardware acceleration for certain machines which use AMD GPUs,
  but for stuff like the antique 2010 17' MacBookPro6,1 using Nvidia 330M, or even a garden-variety
  2008 MacBook5,1 using Geforce 9400M it runs great!
  It's amazing that a 10-year-old machine like my 2.4GHz 2008 MacBook using the mighty Intel Core 2 Duo
  (with user-replaceable SSD and maxed-out 8GB memory) can run the new release perfectly fine!
  

  edited July 2018

• While this article is informative, I think there is information you are leaving out.
  I'd give proper attribution to conversation about Mojave on Unsupported Macs being an active discussion hosted by Dosdude on Macrumors.com. Yes, it's a competitor but much of the information needed to be successful about doing this patch is found in the pages and pages of discussion amongst the users as bugs are crushed and more machines are added to the compatibility (or partial compatibility) list. It's no different than when you attribute a store broken by another website or news outlet. Just referring to Dosdude's own download page doesn't get around that fact.

  While I appreciate MR holding the conversation, they didn't break this. When appropriate, we give other sites credit -- including MR. This is a complicated situation for both MR and us, with a history and discussion about it going for pages and pages.
  Users are welcome to -- and should -- use Google to seek information on any workaround we publish, or to seek amplifying information on tips.

  Naw, I use DuckDuckGo as my search engine.
• This type of thing is for enthusiasts only, i.e., people that enjoy computer troubleshooting. People that just blithely say 'it works great' aren't telling the truth.

• This type of thing is for enthusiasts only, i.e., people that enjoy computer troubleshooting. People that just blithely say 'it works great' aren't telling the truth.

  It's two clicks more than a regular install and it works perfectly. Don't say things you don't understand.

• I bet Windows 10 runs perfectly on Boot Camp on a 2008 Mac without any hacks at all.

  Runs perfectly on a 2009 (Mac Pro), at least. And you can even use the most modern Boot Camp drivers by bypassing Apple's in-Windows compatibility check.

  Cool, Good to know I have a spare old 2010 15' i7 MBP complete with SSD internal and maxed out RAM I thought was soon to be a doorstop. As the Boot-Camp work around that is fantastic, I can use it as another opensim server now

  edited July 2018

• This is probably a good thing. I'm not sure I will venture to Mojave on my MacBook Pro 5,5 or iMac 12,2, though. I put Sierra on the MacBook Pro to keep it aligned with the iMac, and only because Logic X 10.4 demanded Sierra. I might run it on a test hard drive to see what it's like. Sierra works very well on my machine that Apple arbitrarily dumped.
  Apple keeps shortening the support time. Logic's demand of Sierra or High Sierra was an annoyance to many Logic users.
  This pressure to upgrade has been getting worse because of iOS devices and iOS has an incredibly annoying nag to upgrade. I'm not happy about Apple's choices and it makes it very difficult for their customers to maintain a functioning 'Apple ecosystem' unless they're wealthy enough to repeatedly re-buy effectively the same devices every two or three years. It didn't used to be the case that you had to be wealthy to be an Apple user (just judicious spending and saving), but Apple's ecosystem is exactly designed to encourage, or push, people into multiple Apple devices, and upgrade each one more often. This is bad for consumers and they're too arrogant and too big to notice this. Eventually it will lose them customers and they don't care to watch out for this at this time.
  Granted, they did just take some action to possibly pull back on this a bit, with promoting iOS 12 as being faster on older devices (I've avoided iOS 11 but I might go to iOS 12). They need to do more of this, on all platforms.

  Dude, I have a machine that can't run Mojave, it's from 2011. That is not a short time for software updates. Does Windows run on some really old hardware? Sure but Apple can't be expected to keep your computer supported for more than 8 years. Now I might try to run Mojave on my old MacBook since I'm running it as a torrent server and heck why not. But the only thing I was pissed off about with the update was that there weren't compelling machines to upgrade to for people who's machines were at the end of being supported. Hopefully they'll have the whole line up upgraded in the fall. If you think about it the original iMac G3 was only supported for something like 4ish years, I remember because by the time I bought my new iBook my iMac was considered ancient.

• This is probably a good thing. I'm not sure I will venture to Mojave on my MacBook Pro 5,5 or iMac 12,2, though. I put Sierra on the MacBook Pro to keep it aligned with the iMac, and only because Logic X 10.4 demanded Sierra. I might run it on a test hard drive to see what it's like. Sierra works very well on my machine that Apple arbitrarily dumped.
  Apple keeps shortening the support time. Logic's demand of Sierra or High Sierra was an annoyance to many Logic users.
  This pressure to upgrade has been getting worse because of iOS devices and iOS has an incredibly annoying nag to upgrade. I'm not happy about Apple's choices and it makes it very difficult for their customers to maintain a functioning 'Apple ecosystem' unless they're wealthy enough to repeatedly re-buy effectively the same devices every two or three years. It didn't used to be the case that you had to be wealthy to be an Apple user (just judicious spending and saving), but Apple's ecosystem is exactly designed to encourage, or push, people into multiple Apple devices, and upgrade each one more often. This is bad for consumers and they're too arrogant and too big to notice this. Eventually it will lose them customers and they don't care to watch out for this at this time.
  Granted, they did just take some action to possibly pull back on this a bit, with promoting iOS 12 as being faster on older devices (I've avoided iOS 11 but I might go to iOS 12). They need to do more of this, on all platforms.

  ...But the only thing I was pissed off about with the update was that there weren't compelling machines to upgrade to for people who's machines were at the end of being supported. Hopefully they'll have the whole line up upgraded in the fall...
  

  
  This!
  Ending support for my 2011 iMac will probably eventually put me on a new Windows machine. It'll start with Boot Camp, and then, at some point, I'll want to stay with what 'I know' but will need something faster.

• Dude, I have a machine that can't run Mojave, it's from 2011.

  As long as it has a Metal-compatible GPU (or you use dosdude's 'add in the old drivers' utility), it should work perfectly.
  

  But the only thing I was pissed off about with the update was that there weren't compelling machines to upgrade to for people who's machines were at the end of being supported.

  Wait, what do you mean here?