macOS 10.14 Mojave on Unsupported Macs Thread

[alphascorp]

Hi alphascorp,

thanks for all that, but wondering what your opinion is for the "solution" I found at https://tinyapps.org/blog/202005070700_remove_catalina_notification_badge.html

defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier && softwareupdate --list

Main question is it gets rid of the red badge for Catalina, but unsure if red badge notification will still appear for a subsequent "real" non-catalina update?

I posted above at https://forums.macrumors.com/thread...unsupported-macs-thread.2121473/post-28510524

Hi @RK78
Yes, the red badge appears during a "non-Catalina" update notification
I tested it on iMac8,1 (10.14.6 build 18G5033) on which Safari was at version 13.1, after replacing "SoftwareUpdate.framework" I ran an update search via System Preferences and I got the red badge telling me that an update was available, in this case Safari 13.1.1, (I also confirm that the update went without any problem and that the red badge disappeared after installation of the Safari update 13.1.1) see for yourself on the following screenshot the presence of the red badge on System Preferences:

The solution on "tinyapps.org" is the same as my message #18,478 to remove the red badge but it is only temporary, the notification of "catalina" will come back as soon as we re-run a new update search via System Preferences.
And I think that with this solution ("tinyapps.org" and #18,478) if we do not disable automatic updates, each time Mojave is started we will get a red badge (this is only a guess because not tested...)

Whereas if you replace the "SoftwareUpdate.framework" the automatic updates can remain activated and the system can also update automaticaly MRT and Xprotect.

For those who do not trust a file from someone on the internet it is easy for everyone to get "SoftwareUpdate.framework"

First solution:
Copy the file from a system 10.14.6 build 4032 not updated to build 5033.

Second solution:
Install 10.14.6 build 18G103 on an external drive, update it to Security Update 2020-002 build 18G4032
Go to this external drive in the /System/Library/PrivateFrameworks/ folder and copy the "SoftwareUpdate.framework" file to reinject it into your system (build 18G5033).

Third solution:
Restore the framework from a Time Machine.
Thanks to @franciscodavid for this clarification, in order to check the correct version of the system go and have a look at the "SystemVersion.plist" file in /System/Library/CoreServices/ (in Time Machine...)
You must have:
...
<key>ProductBuildVersion</key>
<string>18G4032</string>
...

For information, the extraction (with an app like Pacifist.app) of "SoftwareUpdate.framework" in the installation package of 10.14.6 build 103 should work too (although it has been updated since with the build 18G1012, 18G2022, 18G3020 and 18G4032), I only tested it on MBP5,3 which was completely up to date and didn't get the notification from Catalina.

EDIT:

More complicated and also works very well (@bogdanw tested it here: #94), the use of "SoftwareUpdate.framework" extracted from SecUpd2020-002Mojave.pkg (with Pacifist.app).
But beware, it is not complete, all languages translations folders are missing. If you don't want to have Software Updates Prefpane in English only:
So before replacing the framework of your system it is imperative to make a backup in order to be able to recover all the ".lproj" folders, and as long as you do, the "SoftwareUpdate.icns" file and the 4 ".plist" files contained in SoftwareUpdate.framework/Versions/A/Resources/


Of course, after replacing the framework, as we have done until now, we have to use the Terminal command:

sudo softwareupdate --ignore "macOS Catalina"

REMINDER:
After replacing "SoftwareUpdate.framework" and executing the command "--ignore" above, if you still have the red badge on the System Preferences icon of the Dock, open Terminal and Copy/Paste the following command line and press Enter (you will need the admin password):

sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier && defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier && defaults write com.apple.systempreferences AttentionPrefBundleIDs 0 && killall Dock

 

[TimothyR734]

[automerge]1591071450[/automerge]
Successfully install the latest dev beta security update

 

[mwakious]

I have one, but I use it as my main laptop so it stays on High Sierra until mojave is released or until most the bugs are worked out.

I know that dosdude1 also has at least one of these, so I'm sure he's just as interested as we are to have it working perfectly. Mine currently has zero flaws running HS, I did however change the wifi card out about a year ago because the one it had didn't work in 10.12+

i use MB 5,2 ,id 2009. i was in catalina and it was working good but very slow...i now passed to mojave and i see it works great, everything works except continuity/handoff and i tryed CAT but then the os goes in panik after reboot. i would advise you to replace the AppleGVA.framework file from HS for better FPS, CatalinaAutoMountWritable.plist, Mojave10145DualGpuFix and zoomnonmetal.sh(if you have installed zoom). untill now seems stable and the trackpad is fully working! a very important difference for me is that in mojave the 2 USB are working (in catalina only 1)

 

[franciscodavid]

Hi @RK78
Yes, the red badge appears during a "non-Catalina" update notification
I tested it on iMac8,1 (10.14.6 build 18G5033) on which Safari was at version 13.1, after replacing "SoftwareUpdate.framework" I ran an update search via System Preferences and I got the red badge telling me that an update was available, in this case Safari 13.1.1, (I also confirm that the update went without any problem and that the red badge disappeared after installation of the Safari update 13.1.1) see for yourself on the following screenshot the presence of the red badge on System Preferences:

View attachment 920644

The solution on "tinyapps.org" is the same as my message #18,478 to remove the red badge but it is only temporary, the notification of "catalina" will come back as soon as we re-run a new update search via System Preferences.
And I think that with this solution ("tinyapps.org" and #18,478) if we do not disable automatic updates, each time Mojave is started we will get a red badge (this is only a guess because not tested...)

Whereas if you replace the "SoftwareUpdate.framework" the automatic updates can remain activated and the system can also update automaticaly MRT and Xprotect.

For those who do not trust a file from someone on the internet it is easy for everyone to get "SoftwareUpdate.framework"

First solution:
Copy the file from a system 10.14.6 build 4032 not updated to build 5033.

Second solution:
Install 10.14.6 build 18G103 on an external drive, update it to Security Update 2020-002 build 18G4032
Go to this external drive in the /System/Library/PrivateFrameworks/ folder and copy the "SoftwareUpdate.framework" file to reinject it into your system (build 18G5033).

For information, the extraction (with an app like Pacifist.app) of "SoftwareUpdate.framework" in the installation package of 10.14.6 build 103 should work too (although it has been updated since with the build 18G1012, 18G2022, 18G3020 and 18G4032), I only tested it on MBP5,3 which was completely up to date and didn't get the notification from Catalina.

EDIT:

More complicated and also works very well (@bogdanw tested it here: #94), the use of "SoftwareUpdate.framework" extracted from SecUpd2020-002Mojave.pkg (with Pacifist.app).
But beware, it is not complete, it will miss all languages translations. If you don't want to have Software Updates Prefpane in English only:
So before replacing the framework of your system it is imperative to make a backup in order to be able to recover all the ".lproj" folders, and as long as you do, the "SoftwareUpdate.icns" file and the 4 ".plist" files contained in SoftwareUpdate.framework/Versions/A/Resources/


Of course, after replacing the framework, as we have done until now, we have to use the Terminal command:

sudo softwareupdate --ignore "macOS Catalina"

I recovered SoftwareUpdate.framework (build 18G4032) from a TimeMachine backup and works pretty nice. Thank you!

In case anyone tries, you can find the build version of the backup in /System/Library/CoreServices/SystemVersion.plist

 

[mwakious]

Hi all
Following the modification made by Apple by the 2020-003 update and especially the depreciation of the "softwareupdate --ignore" command I have 2 solutions:

The first, for those who do not want to modify the system files, is:

1) Uncheck the automatic update search in the system preferences.
2) Regularly use the excellent utility "SilentKnight.app" in order to update MRT and XProtect. (download direct link)

The second: (replace the "SoftwareUpdate.framework" file with version 18G4032) I joined the framework in a .zip archive below

1) Make a backup of "SoftwareUpdate.framework" existing in /System/Library/PrivateFrameworks/
2) Copy the file "SoftwareUpdate.framework" (uncompressed) in the folder /System/Library/PrivateFrameworks/ (overwrite the existing one, DO NOT MERGE)
3) With terminal:

sudo chmod -R 755 /System/Library/PrivateFrameworks/SoftwareUpdate.framework
sudo chown -R 0:0 /System/Library/PrivateFrameworks/SoftwareUpdate.framework

4) Restart

It worked for me on MBP5,3 and iMac 8,1

View attachment 920351

I can confirm that after replacing the framework, the update works perfectly because on iMac8,1 Safari was only at version 13.1
After replacing the framework I ran an update from the system preferences and the result is there, "an update is available: Safari 13.1.1" but no notification for Catalina!!!

View attachment 920386

i did this and

sudo softwareupdate --ignore "macOS Catalina"

now that anoying msg desapered but i see the red button on system preferences

 

[alphascorp]

i did this and

sudo softwareupdate --ignore "macOS Catalina"

now that anoying msg desapered but i see the red button on system preferences

Hi @mwakious

To remove the red badge from the System Preferences icon, just open Terminal and copy/paste the following command line and press enter (you will need to enter your admin password):

sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier && defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier && defaults write com.apple.systempreferences AttentionPrefBundleIDs 0 && killall Dock

 

[mwakious]

Surely it's a too high jump from .3 to .6 beta 1 especially for a Beta where the official Combo package hasn't been released officially by apple even if it's in sucatalog, and consider also that a manual update has some side effects versus an official pkg installer update, anyway I guess it could be fixable with next update to .6 PB2 .

edit: and you had also a .5 T2 Chip unwanted update applied, I guess
[doublepost=1558791214][/doublepost]

Without the Mojave USB Post-Install in the pocket it's not so agile, but to enable the non-metal acceleration you need to do this:

1) Download and apply this: non-metal OpenGL
but do NOT reboot/restart yet

2) You need to replace also CoreDisplay.framework from .3 but this can only be done from single user mode CMD+S if you replace it on-the-fly your system won't be more bootable
you can download it from CoreDisplay.framework.zip

3) You need to replace also the IOGraphicsFamily.kext , IONDRVSupport.kext, IOAccel*.kext with those from HighSierra and rebuild a kextcache with them you can download them from Mojave10145DualGpuFix.zip

What I can suggest is to rename the downloaded CoreDisplay.framework in CoreDisplay.framework2 and copy it in your Mojave /System/Library/Frameworks/

then from single user mode booting with CMD+S you can replace it in this way:

mount -uw /
cd /System/Library/Frameworks

ls CoreDisplay.*

(Checking that you have two CoreDisplay folders means you are in the right mount point)

mv CoreDisplay.framework CoreDisplay.backup
mv CoreDisplay.framework2 CoreDisplay.framework
exit


I know it's a long story doesn't worth it, better to re-download and make again a full Mojave Patcher.

i need to ask this
is this necessary to do even if i used the latest mojave patcher or it is obsolete? i mean, i did everything after clean install, but i wanted to know if this is included with the patcher

 

[brmarinho]

Why do you say that? I always do mine from the prefpane.

It won't boot if you install it automatically...

 

[mrploppy]

It won't boot if you install it automatically...

Well, having installed automatically, you have to then boot immediately into the patcher and re-apply the post-install patches. It then boots fine. Still easier than doing the manual install. Either way, you have to re-apply the post-install patches.

 

[philricelle]

Hi everyone! When I'm installing Skype or trying to make a video call from Edge, the camera and mic are not working on both of them. And they simply don't appear in Security & Privacy Settings. Tried to reinstall them with no success. Any tips to make them work? Thanks!

 

[RK78]

Hi @RK78
Yes, the red badge appears during a "non-Catalina" update notification
I tested it on iMac8,1 (10.14.6 build 18G5033) on which Safari was at version 13.1, after replacing "SoftwareUpdate.framework" I ran an update search via System Preferences and I got the red badge telling me that an update was available, in this case Safari 13.1.1, (I also confirm that the update went without any problem and that the red badge disappeared after installation of the Safari update 13.1.1) see for yourself on the following screenshot the presence of the red badge on System Preferences:

View attachment 920644

The solution on "tinyapps.org" is the same as my message #18,478 to remove the red badge but it is only temporary, the notification of "catalina" will come back as soon as we re-run a new update search via System Preferences.
And I think that with this solution ("tinyapps.org" and #18,478) if we do not disable automatic updates, each time Mojave is started we will get a red badge (this is only a guess because not tested...)

Whereas if you replace the "SoftwareUpdate.framework" the automatic updates can remain activated and the system can also update automaticaly MRT and Xprotect.

For those who do not trust a file from someone on the internet it is easy for everyone to get "SoftwareUpdate.framework"

First solution:
Copy the file from a system 10.14.6 build 4032 not updated to build 5033.

Second solution:
Install 10.14.6 build 18G103 on an external drive, update it to Security Update 2020-002 build 18G4032
Go to this external drive in the /System/Library/PrivateFrameworks/ folder and copy the "SoftwareUpdate.framework" file to reinject it into your system (build 18G5033).

Third solution:
Restore the framework from a Time Machine.
Thanks to @franciscodavid for this clarification, in order to check the correct version of the system go and have a look at the "SystemVersion.plist" file in /System/Library/CoreServices/ (in Time Machine...)
You must have:
...
<key>ProductBuildVersion</key>
<string>18G4032</string>
...

For information, the extraction (with an app like Pacifist.app) of "SoftwareUpdate.framework" in the installation package of 10.14.6 build 103 should work too (although it has been updated since with the build 18G1012, 18G2022, 18G3020 and 18G4032), I only tested it on MBP5,3 which was completely up to date and didn't get the notification from Catalina.

EDIT:

More complicated and also works very well (@bogdanw tested it here: #94), the use of "SoftwareUpdate.framework" extracted from SecUpd2020-002Mojave.pkg (with Pacifist.app).
But beware, it is not complete, all languages translations folders are missing. If you don't want to have Software Updates Prefpane in English only:
So before replacing the framework of your system it is imperative to make a backup in order to be able to recover all the ".lproj" folders, and as long as you do, the "SoftwareUpdate.icns" file and the 4 ".plist" files contained in SoftwareUpdate.framework/Versions/A/Resources/


Of course, after replacing the framework, as we have done until now, we have to use the Terminal command:

sudo softwareupdate --ignore "macOS Catalina"

REMINDER:
After replacing "SoftwareUpdate.framework" and executing the command "--ignore" above, if you still have the red badge on the System Preferences icon of the Dock, open Terminal and Copy/Paste the following command line and press Enter (you will need the admin password):

sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier && defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier && defaults write com.apple.systempreferences AttentionPrefBundleIDs 0 && killall Dock

Sorry for the delayed reply, tried installing the 2020-003 from the standalone modified.pkg, which went perfectly on iMac, but caused major issues on Mac Mini. So was buried under for several days trying to get back to something normal.

About the red badge disable: replaced the softwareupdate.framework with the 18G4032, and restored correct permissions. Then used

sudo softwareupdate --ignore "macOS Catalina"

after running the Safari 13.1.1. That command sometimes works, sometimes not to remove the red badge -- unable to figure out why.

(Also, after running that command, when it does work to remove the red badge, running softwareupdate --list to find any new updates inexplicably returns the red badge.) This does remove the Catalina nag, which is some good news, as far as it goes. However, per your instructions, if red badge reappears anyway, ran

sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier && defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier && defaults write com.apple.systempreferences AttentionPrefBundleIDs 0 && killall Dock

This doesn't appear to be working for me at all. Checked syntax of that command from my copy, and it is exactly what you posted. Terminal output from that is:

2020-06-04 09:27:10.748 defaults[1006:27059]
Domain (/Library/Preferences/com.apple.SoftwareUpdate.plist) not found.
Defaults have not been changed.

Finally, what does seem to reliably remove the red badge is the tiny apps command, which I ran successfully on the iMac, and now the Mini. Thereafter, checking for updates from the command line, does not return the red badge, unlike the random behavior I've described above from runnning

sudo softwareupdate --ignore "macOS Catalina"

And note, with the tiny apps command a restart does not appear to bring back the red badge.

Wondering what your take on all of this is? And question still lingers if that tiny apps command, which seems I will have to continue to use, at least for now, will prevent seeing the red badge for any "non-Catalina" updates? I suppose I won't be able to be certain of that until there is another "real" update available. Many thanks.

 

[jasoncarle]

Nevermind.

 

[alphascorp]

Sorry for the delayed reply, tried installing the 2020-003 from the standalone modified.pkg, which went perfectly on iMac, but caused major issues on Mac Mini. So was buried under for several days trying to get back to something normal.

About the red badge disable: replaced the softwareupdate.framework with the 18G4032, and restored correct permissions. Then used

sudo softwareupdate --ignore "macOS Catalina"

after running the Safari 13.1.1. That command sometimes works, sometimes not to remove the red badge -- unable to figure out why.

(Also, after running that command, when it does work to remove the red badge, running softwareupdate --list to find any new updates inexplicably returns the red badge.) This does remove the Catalina nag, which is some good news, as far as it goes. However, per your instructions, if red badge reappears anyway, ran

sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier && defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier && defaults write com.apple.systempreferences AttentionPrefBundleIDs 0 && killall Dock

This doesn't appear to be working for me at all. Checked syntax of that command from my copy, and it is exactly what you posted. Terminal output from that is:

2020-06-04 09:27:10.748 defaults[1006:27059]
Domain (/Library/Preferences/com.apple.SoftwareUpdate.plist) not found.
Defaults have not been changed.

Finally, what does seem to reliably remove the red badge is the tiny apps command, which I ran successfully on the iMac, and now the Mini. Thereafter, checking for updates from the command line, does not return the red badge, unlike the random behavior I've described above from runnning

sudo softwareupdate --ignore "macOS Catalina"

And note, with the tiny apps command a restart does not appear to bring back the red badge.

Wondering what your take on all of this is? And question still lingers if that tiny apps command, which seems I will have to continue to use, at least for now, will prevent seeing the red badge for any "non-Catalina" updates? I suppose I won't be able to be certain of that until there is another "real" update available. Many thanks.

Hi @RK78
The error you had, just means that the file "com.apple.SoftwareUpdate.plist" that the command want to modify is not present in your system, which is logical after a reinstallation for example because the file "com.apple.SoftwareUpdate.plist" is only created after launching Software Update Prefpane at least once.
In this case it is necessary to go further in the understanding of the command line that I gave, it comprises 4 commands one behind the other (for more ease of use with a Copy/Paste), all these commands are separated by "&&" but if one of these commands returns an error (which was your case) the following commands will not be executed. this is why your red badge has not disappeared because it is the last 2 command lines that do it.
In your case it would have been necessary to launch the 4 commands one by one and the red badge would have disappeared.

For information I wrote these lines one by one in the message #18,478

But you still managed to get rid of the red badge, that's the main thing.

 

[mwakious]

hi guys!!
has anyone tryed this adaptor https://www.ebay.it/itm/New-PCI-E-M...998192?hash=item19f6cfd5b0:g:FisAAOSwwFlcuo-4
on a MB5,2?
if yes, which module combo BT4LE and WiFi did you get? i saw in the internet that adding this handoff ecc work out of the box

 

[RK78]

Hi @RK78
The error you had, just means that the file "com.apple.SoftwareUpdate.plist" that the command want to modify is not present in your system, which is logical after a reinstallation for example because the file "com.apple.SoftwareUpdate.plist" is only created after launching Software Update Prefpane at least once.
In this case it is necessary to go further in the understanding of the command line that I gave, it comprises 4 commands one behind the other (for more ease of use with a Copy/Paste), all these commands are separated by "&&" but if one of these commands returns an error (which was your case) the following commands will not be executed. this is why your red badge has not disappeared because it is the last 2 command lines that do it.
In your case it would have been necessary to launch the 4 commands one by one and the red badge would have disappeared.

For information I wrote these lines one by one in the message #18,478

But you still managed to get rid of the red badge, that's the main thing.

Thanks, the short story is that after running that tinyapps command (see above), in combination with the softwareupdate.framework 18G4032, and who knows what else I threw at it -- have almost completely lost track of it all -- I was able to check SU from SysPrefs, and did not get the red badge. Hooray! (Was all set to run those 3 commands separately, but seems not needed now -- I did realize that all those commands were strung together.)

However, kind of puzzled: Even before running the SU pref pane, I did see that file /Library/Preferences/com.apple.SoftwareUpdate.plist where it should be, with the following, which to my not that well educated eye looks OK

(Unless I misunderstood, I thought you said it should not be present, based on the error from the output of that longish command I ran):



<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>AnonymousUUID</key>
<string>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</string>
<key>AutomaticCheckEnabled</key>
<true/>
<key>AutomaticDownload</key>
<false/>
<key>AutomaticallyInstallMacOSUpdates</key>
<false/>
<key>CriticalUpdateInstall</key>
<true/>
<key>DidRegisterLocalUpdates</key>
<true/>
<key>EvaluateCriticalEvenIfUnchanged</key>
<true/>
<key>IgnoringUnseenRamped</key>
<false/>
<key>InactiveUpdates</key>
<array>
<string>MacBook Pro Supplemental Update</string>
<string>macOS Catalina</string>
</array>
<key>LastAttemptBuildVersion</key>
<string>10.14.6 (18G5033)</string>
<key>LastAttemptSystemVersion</key>
<string>10.14.6 (18G5033)</string>
<key>LastBackgroundSuccessfulDate</key>
<date>2020-06-03T20:15:23Z</date>
<key>LastFullSuccessfulDate</key>
<date>2020-06-04T13:33:33Z</date>
<key>LastRecommendedUpdatesAvailable</key>
<integer>0</integer>
<key>LastResultCode</key>
<integer>1</integer>
<key>LastSessionSuccessful</key>
<true/>
<key>LastSuccessfulDate</key>
<date>2020-06-04T13:33:33Z</date>
<key>LastUpdatesAvailable</key>
<integer>0</integer>
<key>OneTimeForceScanEnabled</key>
<true/>
<key>PrimaryLanguages</key>
<array>
<string>en</string>
<string>en-US</string>
</array>
<key>RecommendedUpdates</key>
<array/>
<key>SkipLocalCDN</key>
<false/>
</dict>
</plist>

 

[saxfun]

I'm running a iMac 8,1 from 2008, patched with Dosdudes patcher, but my iMac won't show me the update. After downloading it manually there's an error, " this computer is not qualified to run the update". Any advice on this? Thanks.

 

[george1984]

I have a mac mini 3,1 8G, internal SSD, and internal HD with sierra 10.12.6 installed and working.
Orig wifi does not work and thats ok as I don't need.

I am tired of the bugs with pdfs and sierra so I was thinking of going to high sierra.

But if I am going to upgrade should I go to Mojave instead.

Software should not be a issue I think.
I probably will copy the current SSD to an internal HD then upgrade in place, if it works then copy it all back to the internal SSD.

But… I also have a Mac mini 4,1 Mid 2010 Internal SSD with 10.12.6.
And also, I cannot risk bricking either mac with APFS so probably would stay HFS.

Which to upgrade to?

 

[TheRV]

Hang on ... I've a vague recollection, something to do with APFS. I'm on APFS using the post-install APFS patch. You?

Indeed, I am not on AFPS, maybe that is why I can't see the security update. So I will install it manually according the instructions page 740

 

[Rob1n]

I have a mac mini 3,1 8G, internal SSD, and internal HD with sierra 10.12.6 installed and working.
Orig wifi does not work and thats ok as I don't need.

I am tired of the bugs with pdfs and sierra so I was thinking of going to high sierra.

But if I am going to upgrade should I go to Mojave instead.

Software should not be a issue I think.
I probably will copy the current SSD to an internal HD then upgrade in place, if it works then copy it all back to the internal SSD.

I think you should go to Mojave, I'm also on mojave on a mac pro 2008. I have my drive formatted in apfs so that I can get all the software updates no problem. I haven't experienced any issues so far with the apfs patch. If you just back up your data before updating I don't think it should be a problem. Make sure everything works before completely switching to mojave. But it should be fine.

 

[george1984]

I think you should go to Mojave, I'm also on mojave on a mac pro 2008. I have my drive formatted in apfs so that I can get all the software updates no problem. I haven't experienced any issues so far with the apfs patch. If you just back up your data before updating I don't think it should be a problem. Make sure everything works before completely switching to mojave. But it should be fine.

Thanks for the opinion.

I already went with high sierra, keeping ssd HFS. so far no major issues!
It feels a little slower...

Maybe I will go ahead in a few weeks.

 

[Rob1n]

Thanks for the opinion.

I already went with high sierra, keeping ssd HFS. so far no major issues!
It feels a little slower...

Maybe I will go ahead in a few weeks.

Yeah high sierra is fine too, it doesn't really matter. The only major upgrade in mojave is dark mode in my opinion.

 

[TimothyR734]

Successfully installed macOS Mojave 10.14.6 Security update Dev Beta 2

 

[jackluke]

Hi everyone! When I'm installing Skype or trying to make a video call from Edge, the camera and mic are not working on both of them. And they simply don't appear in Security & Privacy Settings. Tried to reinstall them with no success. Any tips to make them work? Thanks!

View attachment 921446

Try use this to manually add app permissions: tccplus gui to add camera and mic permissions for third party app

or you could remove from /Library/Extensions/DisableLibraryValidation.kext

 

[FarmerBob]

. . . And also, I cannot risk bricking either mac with APFS so probably would stay HFS.
Which to upgrade to?

Just to reply to your post:
I have a 3,1 with 4 2TB HHDs and have been ping ponging with APFS formatting on partitions on the drive I have for OSs: 10.5.8, 10.6.8, 10.9.5, 10.12.6 & 10.14.6 now. Also had 10.13.x but it felt no different than 10.12.x. I have gone back and forth on a partition that is in the middle of a drive and no issues with APFS although I'm back in HPS with the last install of 10.14.6. Have several more that I haven't moved to a new HDD . . .

Now my post that may help you, solve my problems and warn of ones people may find:
. . . I haven't had any issues, EXCEPT, I have 3 Thumb Drives: 10.12.6, 10.14.4, 10.15Bx. I saw the new Patchers that dd1 has out and downloaded and redid the Mōjāv and Catalina Installers to the latest as of two days ago. The TDs both will boot and install the OSs and Patches, but after the install is all done nothing but trouble. I'm mostly interested in Mōjāv. With the 10.14 install and one of the drive formats I got the "verbose" bootup, but then dead stop, black screen. Today it only goes far enough for a black screen and when I press the power button to shutdown, I only have to barely touch it to make the machine go off. Mostly either the installs won't boot or I have problems with something I didn't with the installs I didn't have to deal with in the earlier installers. 10.14.4 ran great, both video cards worked and no problems with apps or other hardware. So I didn't think there'd be many problems with 10.14.6. I finally got the Recovery Drive to work. It's been hit and miss with all the OSs that I have played with. I'd like to take the 3,1 to Mōjāv although I have been flawlessly happy and perfect in 10.12.6. As some mentioned the only thing about Mōjāv is the Dark Mode. That's what I need. After 30+ years I am having problems with monitors. I'm down to three now, using add-ons that kinda help with bright white web pages (why do people do that?!) and after x amount of time they blend into the ether and I go into Allostatic Overload.

I have gotten the 10.14.6 install to kinda work, when it'll boot. But only one of my two Nvidia GT 8800 Video Cards work. Both worked in 10.14.4, but won't in 10.14.6, otherwise I'd be there and not here writing a novel. Are there any FWs or Patches in addition to what the earlier Patchers did or from what I have seen people needed to do in the roll up to 10.14.6? Are there certain other things that needed to be done or have all that been wrapped up with the new installers? I have used the 10.12.6 over and over with no issues.

Love the new Catalina Installer. Probably won't use it, but . . .

Any assistance will be greatly appreciated.

Stay Smart, Safe & Well . . .
. . . fb

 

[TheRV]

Indeed, I am not on AFPS, maybe that is why I can't see the security update. So I will install it manually according the instructions page 740

I downloaded and installed manually the update according the instructions page 740. I am running under HFS+ on a MacBook Alu 2008 and I couldn't see the update in the pref pane.

It works perfectly I am now on 10.14.6 (18G5033).

But you have to rebuild caches from the USB key (or the recovery partition should work as well if previously patched), it is mandatory (i got a crash the first time, but now everything is fine). However, you just need to change the all command lines in the instructions containing "SecUpd2020-002Mojave" to "SecUpd2020-003Mojave" otherwise the package name won't match. I will post the updated command in the next post :
[automerge]1592131588[/automerge]

HOW TO INSTALL SECURITY UPDATE 3 - MOJAVE (UNSUPPORTED MACS)
10.14.6 (version 18G5033)​

1° DOWNLOAD MANUALLY THE UPDATER FROM APPLE SUPPORT WEBSITE :
https://support.apple.com/kb/DL2042?viewlocale=en_US&locale=en_US


2° MODIFY THE UPDATE PACKAGE IN ORDER TO INSTALL IT ON UNSUPPORTED MACS :
In order to install SecUpd2020-003Mojave, you must expand the .pkg file and then modify the "distribution" file.
Like this:
Move "SecUpd2020-003Mojave.pkg" file to the desktop
Open Terminal and writes this:
cd ~/Desktop
Press enter
pkgutil --expand SecUpd2020-003Mojave.pkg NewFolder
Press enter
Wait a few minutes for the package to expend


Go to the "NewFolder" folder created on your desktop and open the "Distribution" file with a text editor
Add: return true;
at the end of this line: function InstallationCheck(prefix) {
Like this: function InstallationCheck(prefix) {return true;

Add: return true;
at the end of this line: function VolumeCheck(prefix) {
Like this: function VolumeCheck(prefix) {return true;

Save the file


If you have not closed the terminal, write or simply copy this:
pkgutil --flatten NewFolder SecUpd2020-003MojaveModified.pkg
Press enter and wait a few minutes for the package to re-create

But if you closed the terminal, re-open it and writes this:
cd ~/Desktop
Press enter
pkgutil --flatten NewFolder SecUpd2020-003MojaveModified.pkg
Press enter and wait a few minutes for the package to re-create


3° UPDATE WITH THE MODIFIED UPDATER
Once the operation is completed, launch the file "SecUpd2020-003MojaveModified.pkg" The message "This software is not supported on your system" should no longer appear and the update should install.


4° RUN THE POST-INSTALL PATCH AGAIN FROM THE USB KEY
AFTER INSTALLATION YOU MUST RESTART ON THE USB KEY AND RE-APPLY THE POST-INSTALL PATCH WITH CACHE REBUILD OTHERWISE MOJAVE WILL NOT START

Be careful if you have several OS on more disks/partitions in your mac because these modifications make it possible to install this update on any OS disk/partition.
AT THE BEGINNING OF THE INSTALLATION BE CAREFUL TO CHOOSE THE DISK/PARTITION OF MOJAVE AND NO OTHER.