Jump to content
209 posts in this topic

Recommended Posts

I remember that someone had posted a tutorial on the use of "spoilers" so that threads are not clobbered with long posts that require readers to scroll far to the next post.  Does anyone remember where that spoiler tutorial is located?

 

In brief, the post explained that, instead of posting screen shots one after the other after the other (forcing readers to scroll long distances to the next post), one or more spoilers can be inserted into the post from the InsanelyMac toolbar:

 

Screenshot2026-04-24at7_54_57AM.png.a22fda2a013be12505726f0c0d828f11.png

 

The result is an expandable link that can be clicked by the interested reader to expand content within the post.  This keeps posts short, so that readers of a thread don't need to scroll through long posts just to get to the next post.  The spoiler can contain graphics, text and even other tools (code, other spoilers, etc.)

 

Spoiler

AS8-16-2593_lrg-2603314562.thumb.jpg.cf3f12990420e68759cda554695a3123.jpg

 

 

l-intro-1657650552-1299802632.thumb.jpg.9adea15e723a92891354d55ac7c9c83b.jpg

 

NASA-james-webb-telescope-07-3457551300.thumb.jpg.8c6ff54cc24e7765cb60f7352f4bf0d1.jpg

 

OIP-3039925859.jpg.b671eccb88db011ec5ac876d27f320e1.jpg

 

 

  • Like 3

Hello, I downloaded the beta as a package file and am currently installing it. I would like to participate in the beta program (developer seed or beta seed) as before. Is there a way to do this? I have logged into Apple and registered my beta device, but it does not appear in the Settings update.

 

2026-04-257_50_30.png.27be8fd0e2559f9f3d8805147de94cd7.png

  • Like 2
1 hour ago, Sherlocks said:

Hello, I downloaded the beta as a package file and am currently installing it. I would like to participate in the beta program (developer seed or beta seed) as before. Is there a way to do this? I have logged into Apple and registered my beta device, but it does not appear in the Settings update.

 

2026-04-257_50_30.png.27be8fd0e2559f9f3d8805147de94cd7.png

From Apple’s website

macOS beta

For devices running macOS 13.4 Ventura or later

Go to System Settings > General > Software Update, then click the info button ⓘ next to ”Beta updates“. Choose the macOS Developer beta you’d like to install.

When a new developer beta is available, you can install it from Software Update.

Note: Your Mac must be signed in with the Apple Account you use to sign into to the Apple Developer website in order to access the beta software.

  • Like 3

Fast and painless sequential OTA update (3.5 GB) from macOS 26.5 beta 3 to macOS 26.5 beta 4 (25F5068a)

 

Spoiler

image.png.af4dd1a02417fe513a97f1ea41904e2a.png

 

image.png.340599eff0447fa2af272bc0029b8c6e.png

 

There is no KDK available yet for 26.5 beta 4 (25F5068a). OCLP correctly selects Kernel Debug Kit 26.5 Build 25F5058e (macOS 26.5 beta 3) as the closest match. 

 

AppleHDA, Wi-Fi and AWDL are working flawlessly. 

 

Spoiler

image.png.0daba7cd9c0250e6749c1ada51c8d8dc.png

 

Spoiler

image.png.c8ca86cf91c6c97fadec7d19440770ff.png

 

My system now works perfectly, including sleep/wake - like clockwork. :thumbsup_anim:

Edited by kgp
  • Like 10

Smooth, unattended update to Tahoe 26.5 Beta 4 (25F5068a).  Using VoodooHDA.kext 3.3.4 for audio and itlwm for Wi-Fi, so no root patches.  SIP csr-active-config = <01000000>.

 

Incremental Update

Spoiler

Screenshot2026-04-28at7_59_00AM.png.03c305d32b51c4c6c7289a19af843d26.png

 

Screenshot2026-04-28at8_41_54AM.png.0ecb4907f60478b13cb2e171419fdc37.png

 

 

EDIT: Tahoe 26.5 Beta 4 appears to have fixed the Network Filtering problem with Norton 360 and similar security software.

Edited by deeveedee
  • Like 9

Soooo.  I'm going to have to bow out from the beta program entirely.  I downgraded to the public beta a couple of weeks ago and the next update ran perfectly.  The new one from a couple of days ago screwed things up again.  Initially things go well and I can get onto the desktop move around do stuff.  After shutting down and rebooting I get the usual screen...you have been updated to Tahoe click continue.  As I have posted before this leads nowhere.  Going into recovery mode if I try to reinstall Tahoe without reformatting the hard drive I come to the exact same screen as before...you have successfully upgraded to Tahoe.  If I then format the disk and reinstall I end up with the Tahoe wallpaper and nothing else to click on.

 

So in the end I just put one of my other Tahoe disks in and clone the affected drive to restore it.   So enough.  I'm going to wait only for full releases and hopefully things will go well moving forward.  Sigh.

 

Cheers, Howard 

  • Like 2
6 hours ago, Zevgoli said:

Soooo.  I'm going to have to bow out from the beta program entirely.  I downgraded to the public beta a couple of weeks ago and the next update ran perfectly.  The new one from a couple of days ago screwed things up again.  Initially things go well and I can get onto the desktop move around do stuff.  After shutting down and rebooting I get the usual screen...you have been updated to Tahoe click continue.  As I have posted before this leads nowhere.  Going into recovery mode if I try to reinstall Tahoe without reformatting the hard drive I come to the exact same screen as before...you have successfully upgraded to Tahoe.  If I then format the disk and reinstall I end up with the Tahoe wallpaper and nothing else to click on.

 

So in the end I just put one of my other Tahoe disks in and clone the affected drive to restore it.   So enough.  I'm going to wait only for full releases and hopefully things will go well moving forward.  Sigh.

 

Cheers, Howard 

 

I haven't been following your efforts at getting Tahoe working but what you are describing certainly sounds a lot like what I once faced with file vault automatically taking over and encrypting my drive.  That process took about 4-5 hours to complete during which time, I couldn't access anything on that partition.  Just for sh*ts and giggles, do you by chance sign in to iCloud as part of your installation of updates?  I always skip that and find it was unnecessary because, when I log in to Tahoe, I'm already logged in to iCloud.  Maybe one last try if you haven't considered that . . . .

  • Like 2
3 hours ago, fantomas said:

Screenshot 2026-04-29 at 20.06.26.png

 

Kernel Debug Kit 26.5.4 (build 25F5068a) is also available on the Dortania mirror.
OCLP now automatically downloads and installs the correct KDK for macOS 26.5 Beta 4.

 

image.png.4c546569fb08f66648fda02acdc9fb2d.png


Apple’s KDK naming is once again a bit confusing.


AppleHDA, Wi-Fi, and AWDL are working flawlessly.

 

Spoiler

image.png.ca9394ca1d2547d0e76cf4f31370a46e.png

 

Spoiler

image.png.36933b3a49e794f0fbe63b1608f3fe8f.png

 

 

 

  • Like 6
13 hours ago, mnfesq said:

 

I haven't been following your efforts at getting Tahoe working but what you are describing certainly sounds a lot like what I once faced with file vault automatically taking over and encrypting my drive.  That process took about 4-5 hours to complete during which time, I couldn't access anything on that partition.  Just for sh*ts and giggles, do you by chance sign in to iCloud as part of your installation of updates?  I always skip that and find it was unnecessary because, when I log in to Tahoe, I'm already logged in to iCloud.  Maybe one last try if you haven't considered that . . . .


No.  File vault is not the issue here.  It is always never activated.  I do get prompted to sign into iCloud and I have tried it both ways.  Signing in and not signing in.  Makes no difference.  Beta updates were fine till around 26.2 then mixed success to no success.  It's a real mystery.

 

Cheers, Howard 

  • Like 3
  • Confused 1
  • Sad 2
Posted (edited)

Clockwork-like sequential OTA update (3.36 GB) from macOS 26.5 Beta 4 to macOS 26.5 RC (25F71).

 

Spoiler

image.png.1b84015d5a21b4a1273a836135d02fed.png

 

image.png.022d2a79e37e0c4c7db57c86dc8b5f40.png

 

So far, Apple has not released a Kernel Debug Kit for macOS 26.5 RC (25F71).

OpenCore Legacy Patcher 3.0.0 Nightly (amfipassbeta variant) selects Kernel Debug Kit 26.5 Build 25F5058e (Beta 3) as the closest match, due to Apple’s inconsistent naming of Kernel Debug Kit 26.5.4 Build 25F5068a (Beta 4).

 

image.png.535fdd1bcddc32eafb5432c32e946cac.png

 

I’ve submitted detailed feedback to Apple regarding the inconsistent KDK naming across the macOS 26.5 beta cycle, as this clearly affects deterministic matching and tooling workflows.

For reference, here is the feedback I sent:

 

Spoiler

Subject: Inconsistent and misleading Kernel Debug Kit naming breaks deterministic matching in macOS 26.5

 

On macOS 26.5 RC (build 25F71), there is currently no dedicated Kernel Debug Kit available.

 

This issue impacts development and automated tooling workflows and requires repeated manual intervention during each beta cycle.

 

During the macOS 26.5 beta cycle, KDK naming has been inconsistent and, at times, misleading. The naming does not reliably correspond to the associated macOS version or build number, introducing unnecessary ambiguity.

 

Examples:

  • macOS 26.5 beta 1 (25F5042g)

→ KDK labeled as Kernel Debug Kit 26.5.1 build 25F5042g

  • macOS 26.5 beta 4 (25F5068a)

→ KDK labeled as Kernel Debug Kit 26.5.4 build 25F5068a

 

n both cases, the KDK versioning suggests a different release track (26.5.1 / 26.5.4), even though the KDK is clearly tied to macOS 26.5 beta builds.

 

This is problematic because:

  • KDK version numbers no longer reflect the actual macOS version
  • There is no reliable or predictable mapping between KDKs and OS builds
  • Tooling and workflows cannot depend on version naming for deterministic matching

 

As a result, tools are forced to rely on heuristic “closest match” logic instead of deterministic selection. While this may work in practice, it is fragile, undocumented, and error-prone.

 

Previous KDK releases were significantly more consistent, with naming that aligned closely to macOS versioning and build numbers. The current scheme appears to be a regression in clarity and usability.

 

Request:

Please address this inconsistency by implementing one of the following:

  1. Align KDK naming strictly with the corresponding macOS version and build (e.g. Kernel Debug Kit 26.5 beta 4 (25F5068a))
  2. Provide an official and reliable mapping between KDK versions and supported macOS builds
  3. Ensure that each macOS beta and RC build has a clearly matching and consistently named KDK

 

Additional note:

 

On macOS 26.5 RC (25F71), tools currently fall back to earlier KDKs (e.g. build 25F5058e). While this works in practice, it is not guaranteed behavior and lacks official guidance.

 

A predictable and consistent naming scheme would eliminate this ambiguity, reduce manual intervention, and significantly improve reliability for development, debugging, and automated tooling workflows.

 

Modern Audio, Wi-Fi and AWDL are working flawlessly.

 

 

Spoiler

image.png.2f27d7fff93601166b17b05b45e8f6af.png

 

Spoiler

image.png.f545f005481480bbd96a8d765539bbb6.png

 

 

Edited by kgp
  • Like 4
Guest
This topic is now closed to further replies.
×
×
  • Create New...