Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
updated:

Bummer. Read it too late. It is installed. But it's not that bad with .7.x releases, no big deal.
I'll wait till 15.8 release would be out officially and then remove mobileconfig.profile and revert the terminal command. After a reboot I figure I could get all-official 15.8.

Or at least I hope this method woluld serve its purpose at the time.

upd: Thaoe is present again in the updates seqtion, which I suppose was expected
15.8 won't drop until September, at the same time as macOS 27. In the meantime, they will continue offering 15.7.x releases.

It is sounding like this "fix" does prevent Tahoe from showing up, but it also gives you the 15.7.6 pre-release builds? So, not really any different than selecting Sequoia public beta channel from the GUI?
 
15.8 won't drop until September, at the same time as macOS 27. In the meantime, they will continue offering 15.7.x releases.

It is sounding like this "fix" does prevent Tahoe from showing up, but it also gives you the 15.7.6 pre-release builds? So, not really any different than selecting Sequoia public beta channel from the GUI?
I tried the Seq. Beta route after 15.7.6 had been released; Tahoe and the Badge disappeared for about 3 days but 15.7.6 is now showing; it doesn't indicate whether it's a Beta or RC so that adds another issue; having to check whether it's some kind of urgent update that went straight from a Beta to a Public release. I didn't power off the device or search in Software updates so it looks like it was some kind of routine Mac maintenace type of search that caused it.

If some Terminal command can remove it then I suppose it's a reasonably tolerable step to take maybe once a week; I didn't discern whether there is such a Command from this thread as all seemed to have an issue with Tahoe reappearing.
 
I tried the Seq. Beta route after 15.7.6 had been released; Tahoe and the Badge disappeared for about 3 days but 15.7.6 is now showing; it doesn't indicate whether it's a Beta or RC so that adds another issue; having to check whether it's some kind of urgent update that went straight from a Beta to a Public release. I didn't power off the device or search in Software updates so it looks like it was some kind of routine Mac maintenace type of search that caused it.

If some Terminal command can remove it then I suppose it's a reasonably tolerable step to take maybe once a week; I didn't discern whether there is such a Command from this thread as all seemed to have an issue with Tahoe reappearing.
Bogdanw answered that in Post # 26 of this thread. The Terminal command in Post #3 gets rid of the Tahoe badgering, but the 15.7.6 RC (and further Sequoia updates) will appear, with that Post #3 Terminal command alone.
Early betas and RCs may be quite a risk for some, especially on a mission critical, work machine, but for Sequoia, in the late .7.n development stage, no new potentially problematic features are being added, only bug fixes and security related updates. That makes it much more acceptable in my view. You may have a different take on that.
I and others here have installed the 15.7.6 update, with no apparent new issues so far. So I sincerely doubt that that update is an issue. Do you have public betas or developer betas enabled in the Software Update pane?
 
Last edited:
  • Love
Reactions: otetzone
The experiment failed. As soon as the first beta 15.7.6 was released into the public beta catalog, it appeared in Software Update when the MobileAssetAssetAudience was set to c8ba02c8-cc63-4388-99ee-a81d5a593283.

Other MobileAssetAssetAudience values I’ve tested:

98df7800-8378-4469-93bf-5912da21a1e1 macOS 15 developer beta - hides Tahoe, shows Sequoia beta

1831c3e6-1dc4-4f6b-a9dc-7ae6a41d9af4 macOS 15.1 developer beta - hides Tahoe, hides Sequoia updates

374faeda-4d23-457d-9f73-ec84a286f4b3 macOS 15 AppleSeed beta - hides Tahoe, shows Sequoia beta

d422663f-c2c3-4ea0-89ca-b88696cd383a macOS 15.1 AppleSeed beta - hides Tahoe, hides Sequoia updates

60b55e25-a8ed-4f45-826c-c1495a4ccc65 macOS release – shows Tahoe, shows Sequoia updates

02d8e57e-dd1c-4090-aa50-b4ed2aef0062 macOS generic - hides Tahoe, hides Sequoia updates
 
  • Like
Reactions: losthismarbles
Bogdanw answered that in Post # 26 of this thread. The Terminal command in Poat #3 gets rid of the Tahoe badgering, but the 15.7.6 RC (and further Sequoia updates) will appear, with that Post #3 Terminal command alone.
Early betas and RCs may be quite a risk for some, especially on a mission critical, work machine, but for Sequoia, in the late .7.n development stage, no new potentially problematic features are being added, only bug fixes and security related updates. That makes it much more acceptable in my view. You may have a different take on that.
I and others here have installed the 15.7.6 update, with no apparent new issues so far. So I sincerely doubt that that update is an issue. Do you have public betas or developer betas enabled in the Software Update pane?
I failed to mention that I was using OCLP; thus every update is in effect like a full OS install, so not desirable for every Beta/RC - the numbers of which seem to be increasing. Will leave it on the non - developer Beta channel to avoid Tahoe notifications.

Am now working on getting e-mail notifications for Sequioa sourced from Apple (https://support.apple.com/en-us/100100) using "Visualping" which hopefully will send an email when the 15.7.5 line changes.
 
Last edited:
Sequoia.png


I just signed up for a free developer account to get all Beta options and don't get Tahoe offered.

It's every time the same with any Tahoe 26.x Developer Beta a new RC (no Beta) for the next 15.7.x gets released.

Only available with Developer Betas turned on, on that same day.

Every new RC is just a small build number increase. It seems it's already finished with the first one and just waiting for the final 26.x. You don't even notice that it is not a final version. There is no mentioning of RC in Software Update.

I always installed the Safari Betas too. It is not happening automatically. But maybe because I install them very early. They don't drop at the same time/day, normally about one day later. Safari 26.5 Beta 1 is not there yet and 15.7.6 RC1 already came almost five days ago.

The Safari Betas don't show up if Public Beta is selected and the update drops later but is always the same build. The Safari Beta installer can be update automatically and requires at least Sonoma 14.6 or Sequoia 15.4 for 26.4.

The main reason I am writing this is that I wanted to say I never noticed any difference or problems with the newer Safari versions. They are not like the buggy and slow Tahoe versions. And since compact tabs are back there is not even a difference in the UI anymore compared to the older Safari. It seems to be even more optimized and faster.

For anyone who likes to try 15.7.8 with final Safari 26.4 and maybe later 26.5 Betas

Public full installer:


Developer full installer:


There is not really a difference, only the links are different and both are always released together when the Public RC drops a few days later.
 
So, not really any different than selecting Sequoia public beta channel from the GUI?
Probably so. Although I haven't enabled Beta Updates in System Settings. It probably is going along the terminal script.

I can only hope it won't hurt installing 15.7.x releases (or are they RC or public betas?) before September comes and 15.8 is released and then go clean with updating to it (no configs, no terminal).
 
View attachment 2619766

I just signed up for a free developer account to get all Beta options and don't get Tahoe offered.

It's every time the same with any Tahoe 26.x Developer Beta a new RC (no Beta) for the next 15.7.x gets released.

Only available with Developer Betas turned on, on that same day.

Every new RC is just a small build number increase. It seems it's already finished with the first one and just waiting for the final 26.x. You don't even notice that it is not a final version. There is no mentioning of RC in Software Update.

I always installed the Safari Betas too. It is not happening automatically. But maybe because I install them very early. They don't drop at the same time/day, normally about one day later. Safari 26.5 Beta 1 is not there yet and 15.7.6 RC1 already came almost five days ago.

The Safari Betas don't show up if Public Beta is selected and the update drops later but is always the same build. The Safari Beta installer can be update automatically and requires at least Sonoma 14.6 or Sequoia 15.4 for 26.4.

The main reason I am writing this is that I wanted to say I never noticed any difference or problems with the newer Safari versions. They are not like the buggy and slow Tahoe versions. And since compact tabs are back there is not even a difference in the UI anymore compared to the older Safari. It seems to be even more optimized and faster.

For anyone who likes to try 15.7.8 with final Safari 26.4 and maybe later 26.5 Betas

Public full installer:


Developer full installer:


There is not really a difference, only the links are different and both are always released together when the Public RC drops a few days later.
Is that Developer full installer link for Sequoia 15.7.8 as stated above? That must be a typo, and you meant 15.7.6?
 
Last edited:
Interactive script to get Sequoia installers links directly from Apple:

Bash:
#!/bin/zsh
#Created with assistance from OpenAI's Codex/ChatGPT 5.4

set -euo pipefail

SEED_PLIST="/System/Library/PrivateFrameworks/Seeding.framework/Resources/SeedCatalogs.plist"

normalize_catalog_name() {
  local input="${1:-}"

  case "${input:l}" in
    developerseed|developer|dev)
      printf '%s\n' "DeveloperSeed"
      ;;
    publicseed|publicbeta|beta)
      printf '%s\n' "PublicSeed"
      ;;
    customerseed|customer)
      printf '%s\n' "CustomerSeed"
      ;;
    publicrelease|release|public)
      printf '%s\n' "PublicRelease"
      ;;
    *)
      return 1
      ;;
  esac
}

choose_catalog() {
  local selected="${1:-}"

  if [[ -n "$selected" ]]; then
    normalize_catalog_name "$selected"
    return
  fi

  echo "Select a catalog:" >&2
  select selected in DeveloperSeed PublicSeed CustomerSeed PublicRelease; do
    if [[ -n "${selected:-}" ]]; then
      printf '%s\n' "$selected"
      return
    fi
    echo "Invalid selection. Choose 1, 2, 3, or 4." >&2
  done
}

resolve_catalog_url() {
  local catalog_name="$1"
  local resolved_url

  resolved_url="$(plutil -p "$SEED_PLIST" | sed -nE "s/^  \"$catalog_name\" => \"(.*)\"$/\\1/p")"
  resolved_url="${resolved_url%.gz}"

  if [[ "$catalog_name" == "PublicRelease" ]]; then
    resolved_url="$(plutil -p "$SEED_PLIST" | sed -nE 's/^  "CustomerSeed" => "(.*)"$/\1/p')"
    resolved_url="${resolved_url%.gz}"
    printf '%s\n' "${resolved_url/15customerseed-/}"
    return
  fi

  printf '%s\n' "$resolved_url"
}

extract_catalog_entries() {
  local catalog_url="$1"

  curl -fsL "$catalog_url" | \
    grep 'com_apple_MobileAsset_MacSoftwareUpdate.plist' | \
    grep -Ev 'integrityDataV1' | \
    sed -e 's#<string>##g' -e 's#</string>##g' -e 's/[[:space:]]//g' | \
    awk '!seen[$0]++'
}

extract_field() {
  local parsed_plist="$1"
  local key="$2"

  sed -nE "/\"$key\" => \"/{s/.*\"$key\" => \"([^\"]*)\".*/\\1/p;q;}" <<< "$parsed_plist"
}

main() {
  local catalog_name catalog_url found_any=0
  local plist_url parsed_plist os_version build pkg_url

  if [[ "${1:-}" == "-h" || "${1:-}" == "--help" ]]; then
    usage
    exit 0
  fi

  if ! catalog_name="$(choose_catalog "${1:-}")"; then
    echo "Unknown catalog: ${1:-}" >&2
    usage >&2
    exit 1
  fi

  catalog_url="$(resolve_catalog_url "$catalog_name")"
  if [[ -z "$catalog_url" ]]; then
    echo "Unable to resolve catalog URL for $catalog_name." >&2
    exit 1
  fi

  echo "Catalog: $catalog_name"
  echo "Source: $catalog_url"
  echo

  while IFS= read -r plist_url; do
    [[ -n "$plist_url" ]] || continue

    if ! parsed_plist="$(curl -fsL "$plist_url" | plutil -p - 2>/dev/null)"; then
      echo "Skipping unreadable plist: $plist_url" >&2
      continue
    fi

    os_version="$(extract_field "$parsed_plist" "OSVersion")"
    [[ "$os_version" == 15* ]] || continue

    build="$(extract_field "$parsed_plist" "Build")"
    pkg_url="${plist_url/com_apple_MobileAsset_MacSoftwareUpdate.plist/InstallAssistant.pkg}"

    echo "macOS $os_version${build:+ ($build)}"
    echo "$pkg_url"
    echo

    found_any=1
  done < <(extract_catalog_entries "$catalog_url")

  if [[ "$found_any" -eq 0 ]]; then
    echo "No macOS 15 InstallAssistant.pkg links were found in $catalog_name." >&2
    exit 1
  fi
}

main "$@"

Get-Sequoia-Installers-Interactive.sh
https://gist.github.com/b0gdanw/62864a735ab972726b7d0a6640d974d8

How to use the script video:
 
Last edited:
If time/mood allows, perhaps you could explain what you mean by "directly"?
Directly from Apple being literally the way you'd get them anyway, can't do it from anywhere else, can't even do it offline?
 
Last edited:
If time/mood allows, perhaps you could explain what you mean by "directly"?
Since macOS Big Sur, Apple has included the links for the macOS full installers (InstallAssistant.pkg) into the seed catalogs, the links where macOS looks for updates.

The seed catalogs are listed into /System/Library/PrivateFrameworks/Seeding.framework/Resources/SeedCatalogs.plist

You can open the SeedCatalogs.plist in TextEdit, access one of the catalogs in Safari and search for InstallAssistant.pkg.

The script simplifies the process.

By directly I meant without having to consult a third-party resource, like the excellent https://mrmacintosh.com/macos-sequoia-full-installer-database-download-directly-from-apple/
 
--asking this not because i'm difficult, but because being new to macs, there may be things i'm missing, entirely--

Very grateful for the explanation, albeit still wondering.
One click away from getting it from the Apple Store.
So why all this, especially if i then need to run the pkg to make the app that would already have been there, had i just downloaded it straight from the Store?

Needless to say, am thankful for your time and contribution, the above notwithstanding; have learned a lot reading your posts, so kindly do not mistake this for antagonism or whatever. Asking in case there's an obvious answer to all this i'm just to daft to grasp on my own.
Or.. refrain from replying entirely as well, no offense taken 🙂
 
Alas the 15.7.6 update kills the code and Tahoe is again visible in software update and so the Red dot, sigh

Could be just the code string that needs to be updated?

sudo defaults write /private/var/root/Library/Preferences/com.apple.MobileAsset.plist MobileAssetAssetAudience -string c8ba02c8-cc63-4388-99ee-a81d5a593283
 
I can't advise anyone else to do the same, as I don't know what are the implications, but I set my Macs to 02d8e57e-dd1c-4090-aa50-b4ed2aef0062 macOS generic - hides Tahoe, hides Sequoia updates
https://forums.macrumors.com/threads/experimental-no-tahoe-for-sequoia.2480020/post-34526279
I'll delete it when 15.7.6 will be officially released.
15.7.6 is official

Still working is the notification badge code, but I had to update the number that changes with the latest update

And deleting all the old profiles and installing just the basic one SoftwareUpdate.mobileconfig, it works again 🙂
Screenshot.jpg
 
Last edited:
15.7.6 is official
It is not. If you have it installed, you have a pre-release version that came from the Sequoia beta channel. (If you used the terminal command from earlier in this thread, you have put your Mac on the beta channel.) There is no indication that it is a "beta" or "release candidate" if you check "About this Mac" or Settings or whatever (this is normal), but it is a virtual certainty that there will be additional 15.7.6 pre-release builds made available before the final release drops alongside Tahoe 26.5 in mid-May.
 
  • Like
Reactions: katbel
Without having to sign into Beta updates:
Code:
sudo defaults write /private/var/root/Library/Preferences/com.apple.MobileAsset.plist MobileAssetAssetAudience -string c8ba02c8-cc63-4388-99ee-a81d5a593283

+

DeferUpdates60.mobileconfig (defers software updates for 60 days)
Code:
<?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>PayloadContent</key>
    <array>
        <dict>
            <key>PayloadDisplayName</key>
            <string>Restrictions</string>
            <key>PayloadIdentifier</key>
            <string>com.apple.applicationaccess.D1704303-D96B-4BAE-A4B3-35D20060AE37</string>
            <key>PayloadType</key>
            <string>com.apple.applicationaccess</string>
            <key>PayloadUUID</key>
            <string>D1704303-D96B-4BAE-A4B3-35D20060AE37</string>
            <key>PayloadVersion</key>
            <integer>1</integer>
            <key>enforcedSoftwareUpdateDelay</key>
            <integer>60</integer>
            <key>forceDelayedSoftwareUpdates</key>
            <true/>
        </dict>
    </array>
    <key>PayloadDisplayName</key>
    <string>DeferUpdates60</string>
    <key>PayloadIdentifier</key>
    <string>iMazing-Profile-Editor.6A1E770C-AC98-4BDD-82E7-469806BB98F3</string>
    <key>PayloadScope</key>
    <string>System</string>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadUUID</key>
    <string>6A1E770C-AC98-4BDD-82E7-469806BB98F3</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
    <key>TargetDeviceType</key>
    <integer>5</integer>
</dict>
</plist>

+

SoftwareUpdate.mobileconfig (disables AutomaticDownload & AutomaticallyInstallMacOSUpdates)
Code:
<?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>PayloadContent</key>
    <array>
        <dict>
            <key>AutomaticDownload</key>
            <false/>
            <key>AutomaticallyInstallMacOSUpdates</key>
            <false/>
            <key>PayloadDisplayName</key>
            <string>Software Update</string>
            <key>PayloadIdentifier</key>
            <string>com.apple.SoftwareUpdate.DAD08779-CA16-4ECC-B809-CC505B4EBF68</string>
            <key>PayloadType</key>
            <string>com.apple.SoftwareUpdate</string>
            <key>PayloadUUID</key>
            <string>DAD08779-CA16-4ECC-B809-CC505B4EBF68</string>
            <key>PayloadVersion</key>
            <integer>1</integer>
        </dict>
    </array>
    <key>PayloadDisplayName</key>
    <string>SoftwareUpdate</string>
    <key>PayloadIdentifier</key>
    <string>iMazing-Profile-Editor.781142C3-EA49-4407-8229-926A7AD6788E</string>
    <key>PayloadScope</key>
    <string>System</string>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadUUID</key>
    <string>781142C3-EA49-4407-8229-926A7AD6788E</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
    <key>TargetDeviceType</key>
    <integer>5</integer>
</dict>
</plist>
 
  • Like
Reactions: losthismarbles
It is not. If you have it installed, you have a pre-release version that came from the Sequoia beta channel. (If you used the terminal command from earlier in this thread, you have put your Mac on the beta channel.) There is no indication that it is a "beta" or "release candidate" if you check "About this Mac" or Settings or whatever (this is normal), but it is a virtual certainty that there will be additional 15.7.6 pre-release builds made available before the final release drops alongside Tahoe 26.5 in mid-May.
I’m not in the beta program, this is something I would have liked to do but I don’t have the pref for Beta in my System settings . This is why I eliminated all my profiles because I thought this could be the reason. Then I installed just the profile to stop Tahoe.

Look at someone else who has installed the 15.7.6 without being in the beta program like myself
What happened? Where can I see it’s beta?

Screenshot 2026-04-06 .jpg
 
Last edited:
  • Like
Reactions: losthismarbles
Although it shouldn’t be, running the command sudo defaults write /private/var/root/Library/Preferences/com.apple.MobileAsset.plist MobileAssetAssetAudience -string c8ba02c8-cc63-4388-99ee-a81d5a593283 is the same as enrolling into the Sequoia Public Beta program.

To “unenroll”, run sudo defaults delete /private/var/root/Library/Preferences/com.apple.MobileAsset.plist MobileAssetAssetAudience

To open the Beta menu in Software Updates, run from Terminal open "x-apple.systempreferences:com.apple.Software-Update-Settings.extension?action=showBetaUpdates"
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.