Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
Can someone explain me the 'hidden rules' of this forum since I've posted four times about a related to this forum issue I'm having, with zero responses. so far.
Am I doing something wrong?
The obvious rule is: The more often you have to post the very same question the more likely you hit the wrong thread!

Possibly because this is less a Catalina on unsupported Macs than a Macpro3,1 issue - there are several threads around on this site covering your system type. And do not forget: Most Macs cannot be modified at all, so this hardware discussions are really specific to a few models and a smaller number of users.
 
  • Like
Reactions: 0134168

resurrector66

macrumors newbie
Feb 26, 2020
13
17
If you use File Sharing or Screen Sharing, do not D/L 2021 -003, these features are broken. 2021-002 aka 19H1030 is great. To opt-out of Beta, see Details under the sprocket in the Software Update CP, select and Restore Defaults. Now, whatever non-Beta Update that is available will be shown. The procedure is the same as in Beta, apply the OTA update fix, early on. Any time an update fails, go to Library/Updates ƒ and delete everything in the folder. Retry
The newest version of the 2021-003 beta gives you 19H1210. for me again, the smb filesharing works between Mac and pc and pc to Mac. I don't have two Macs in my house to check if it works between two Macs to answer a question you asked. The screen sharing was to much hassle for me for something I don't need, so I gave that up for now.
 
  • Like
Reactions: K two

resurrector66

macrumors newbie
Feb 26, 2020
13
17
Thanks for that detailed explanation!
Got that working and updated succesfully to 19H15!

Now I am failing with the next steps to receive the latest stable updates. I don't want to try the beta releases, just the security updates for Catalina.

What I did so far:
  • Downloaded CatalinaOTAswufix.app
  • Did the "software Update fix" and successfully got offered the beta updates (macos Big Sur beta 11.4 and when clicking on "Another update is available" I see the Beta 2021-003 Update
  • Clicked on Download and Install on the 2021-003 Update, then after >3% download clicked on "OTA update fix"
  • I get an error message: "WARNING: You need to run first the Sotware Update fix to allow Beta Updates. if you already done it, then the Catalina OTA dist is not yet ready or downloaded"
  • Get that message even after the whole update is downloaded. And by the way, I can't install it. And I know that I do not want to install it. ;)
What am I doing wrong?
How to opt out of the beta updates and only receive the official updates??

Thanks in advance!!!
I had to drag the CatalinaOTAswufix.app to the desktop from the download folder to make it work correctly
 

0134168

Cancelled
May 21, 2009
2,964
2,805
The obvious rule is: The more often you have to post the very same question the more likely you hit the wrong thread!

Possibly because this is less a Catalina on unsupported Macs than a Macpro3,1 issue - there are several threads around on this site covering your system type. And do not forget: Most Macs cannot be modified at all, so this hardware discussions are really specific to a few models and a smaller number of users.
I would also add: "If you don´t have time to search it, I don´t have tiome for answer"
 

kosiko

macrumors newbie
Jan 26, 2010
13
11
I should note that using OpenCore makes things a lot easier.
Hm, in what ways?

Right now I got the CatalinaOTAswufix.app working and did the whole process. Unfortunetaly my iMac never rebooted again. It got stuck on the grey screen after turning on and ended in a loop of reboots. Tried some stuff, did not get it to work. So I restored my time machine backup.
After that I tried to apply the OpenCore Legacy Patcher but I was not able to install it over my system. It said that I can't install it over my Catalina Version. probably because I have a OpenCore version for target system Big Sur? But I didn't find one for Catalina...
Even though it did not work, I still see the Big Sur Beta for downloading in my Software Update pane in macos!?
But I don't see any further updates for Catalina. At least I am now on 19H2!
And I cannot boot anymore without the OpenCore USB stick plugged in.

I am a bit unsecure what the next best or right step would be...
Uninstall OpenCoreLegacyPatcher? (Even though it didn't install correctly)
Apply CatalinaOTAswufix.app again?

Thx!
 

resurrector66

macrumors newbie
Feb 26, 2020
13
17
Hm, in what ways?

Right now I got the CatalinaOTAswufix.app working and did the whole process. Unfortunetaly my iMac never rebooted again. It got stuck on the grey screen after turning on and ended in a loop of reboots. Tried some stuff, did not get it to work. So I restored my time machine backup.
After that I tried to apply the OpenCore Legacy Patcher but I was not able to install it over my system. It said that I can't install it over my Catalina Version. probably because I have a OpenCore version for target system Big Sur? But I didn't find one for Catalina...
Even though it did not work, I still see the Big Sur Beta for downloading in my Software Update pane in macos!?
But I don't see any further updates for Catalina. At least I am now on 19H2!
And I cannot boot anymore without the OpenCore USB stick plugged in.

I am a bit unsecure what the next best or right step would be...
Uninstall OpenCoreLegacyPatcher? (Even though it didn't install correctly)
Apply CatalinaOTAswufix.app again?

Thx!
Posts #13967 and #13969 should help you
 

fredbloggs73

macrumors newbie
May 8, 2021
1
1
Managed to get it all working on 2007 imac 7,1 so thank you everyone
Updated to 19H1030 and definitely needed USBOpenCoreAPFSloader to choose mac installer volume to finish update on restart. Without this it would just reboot into 19H15 as per before update.
Also had the Photos app picture glitch where thumbnails are ok but full photos come up all rainbow-like. This was fixed with SwitchResX changing colours to millions instead of billions.

However i've always had an issue on restarting computer since first trying to install catalina. Under dosdude's patcher on restart, script would hang
dosdude.jpg


and on open core it hangs here still
open core.jpg


where hitting enter just reloads the same screen over and over

Both these issues were/are fixed if i shut down the computer and restart.

When i first installed catalina i installed a brand new ssd plus a 2nd ssd in optical drive bay. Don't know if that would make any difference.

Also is it possible with open core installed to make a bootcamp partition? and if so can i just use the bootcamp installer program or does this mess with open core? I'm a bit confused with all the information around.

Apart from this it works like a dream, might get another 10 years out of it!
 
  • Like
Reactions: K two

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
The newest version of the 2021-003 beta gives you 19H1210. for me again, the smb filesharing works between Mac and pc and pc to Mac. I don't have two Macs in my house to check if it works between two Macs to answer a question you asked. The screen sharing was to much hassle for me for something I don't need, so I gave that up for now.
So, it's not known whether the Sharing features broken in 19H1208 are fixed in 19H1210? With 6 Macs remote Sharing is essential.
 

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
What happens when updating a @dosdude1 patched Catalina without Metal w/ OCLP v.0.1.2 installed on the boot drive? Had to re-install OCLP graphics patches when updating Big Sur to 11.3.1, are the two patching methods mutually compatible? This is a non-Metal GPU question.
 

schreiberstein

macrumors newbie
Oct 12, 2013
17
1
Code:
Sat May  8 21:34:33 2021

*** Panic Report ***
panic(cpu 1 caller 0xffffff802fe48a1a): Kernel trap at 0xffffff80303b8354, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000445f9300, CR3: 0x0000000032c0b000, CR4: 0x00000000000626e0
RAX: 0x0000000021000000, RBX: 0xffffff8041a2b660, RCX: 0x0000000021000001, RDX: 0xffffff8100489000
RSP: 0xffffff813b3a3c30, RBP: 0xffffff813b3a3c30, RSI: 0x00000000445f9300, RDI: 0xffffff8041a2b660
R8:  0x0000000000000001, R9:  0x0000000000000002, R10: 0x0000000000000001, R11: 0xffffff8041b1a720
R12: 0x0000000000000000, R13: 0xffffff8100489000, R14: 0x00000000445f9300, R15: 0xffffff804231a9c0
RFL: 0x0000000000010282, RIP: 0xffffff80303b8354, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00000000445f9300, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 1

Backtrace (CPU 1), Frame : Return Address
0xffffff813b3a3690 : 0xffffff802fd1c63d
0xffffff813b3a36e0 : 0xffffff802fe56ae5
0xffffff813b3a3720 : 0xffffff802fe4866e
0xffffff813b3a3770 : 0xffffff802fcc2a40
0xffffff813b3a3790 : 0xffffff802fd1bd07
0xffffff813b3a3890 : 0xffffff802fd1c0f7
0xffffff813b3a38e0 : 0xffffff80304c0a9c
0xffffff813b3a3950 : 0xffffff802fe48a1a
0xffffff813b3a3ad0 : 0xffffff802fe48718
0xffffff813b3a3b20 : 0xffffff802fcc2a40
0xffffff813b3a3b40 : 0xffffff80303b8354
0xffffff813b3a3c30 : 0xffffff80303b882f
0xffffff813b3a3c60 : 0xffffff80303987b8
0xffffff813b3a3c90 : 0xffffff7fb1a9db6e
0xffffff813b3a3cc0 : 0xffffff7fb304b8ff
0xffffff813b3a3d40 : 0xffffff7fb3065b0c
0xffffff813b3a3d80 : 0xffffff7fb307609f
0xffffff813b3a3de0 : 0xffffff80304065a6
0xffffff813b3a3e40 : 0xffffff80304060e1
0xffffff813b3a3ef0 : 0xffffff803040547e
0xffffff813b3a3f50 : 0xffffff8030407c36
0xffffff813b3a3fa0 : 0xffffff802fcc213e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOSurface(269.11)[64FA5AA1-D63E-30EC-B7D1-D60B2FE78201]@0xffffff7fb1a90000->0xffffff7fb1abefff
         com.apple.driver.AppleIntelHD3000Graphics(10.0.4)[3A47B78B-AF9B-30A4-A5AD-C0B4318C9665]@0xffffff7fb3049000->0xffffff7fb30a9fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[8AE063C6-3413-3892-B413-EAFE16B9D270]@0xffffff7fb0902000
            dependency: com.apple.iokit.IOGraphicsFamily(519.15)[D5F2A20D-CAB0-33B2-91B9-E8755DFC34CB]@0xffffff7fb226c000

BSD process name corresponding to current thread: kernel_task
Boot args: -no_compat_check amfi_get_out_of_my_way=1

Mac OS version:
19H1210

Kernel version:
Darwin Kernel Version 19.6.0: Fri Apr 16 11:14:10 PDT 2021; root:xnu-6153.141.31~1/RELEASE_X86_64
Kernel UUID: C1222E6F-6463-3AE9-A84B-D3585059290D
Kernel slide:     0x000000002fa00000
Kernel text base: 0xffffff802fc00000
__HIB  text base: 0xffffff802fb00000
System model name: MacBookPro8,1 (Mac-CENSORED)
System shutdown begun: NO
Panic diags file available: YES (0x0)

I installed macOS Catalina 10.15.7 (19H15) on an Early 2011 MacBook Pro (MacBookPro8,1) using dosdude's patcher.
However, I was unable to upgrade to any of the later supplemental updates or security updates.
The manual Installer PKG patching did not work.
The OTA software fix enabled me to attempt an upgrade to both the 2021-02 (Release) and the 2021-03 (Developer) security upgrade, but both failed.
After the update installer finished and the reboot occurred, it always ended in a kernel panic. Apparently at the moment it attempted to start the GUI. Manually running the patcher application again did not change anything.
System Integrity is disabled - confirmed by running csrutil status in single user mode.

Do you have any idea how to fix this?
Thank you!
schreiberstein
 
  • Like
Reactions: K two

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
Code:
Sat May  8 21:34:33 2021

*** Panic Report ***
panic(cpu 1 caller 0xffffff802fe48a1a): Kernel trap at 0xffffff80303b8354, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000445f9300, CR3: 0x0000000032c0b000, CR4: 0x00000000000626e0
RAX: 0x0000000021000000, RBX: 0xffffff8041a2b660, RCX: 0x0000000021000001, RDX: 0xffffff8100489000
RSP: 0xffffff813b3a3c30, RBP: 0xffffff813b3a3c30, RSI: 0x00000000445f9300, RDI: 0xffffff8041a2b660
R8:  0x0000000000000001, R9:  0x0000000000000002, R10: 0x0000000000000001, R11: 0xffffff8041b1a720
R12: 0x0000000000000000, R13: 0xffffff8100489000, R14: 0x00000000445f9300, R15: 0xffffff804231a9c0
RFL: 0x0000000000010282, RIP: 0xffffff80303b8354, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00000000445f9300, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 1

Backtrace (CPU 1), Frame : Return Address
0xffffff813b3a3690 : 0xffffff802fd1c63d
0xffffff813b3a36e0 : 0xffffff802fe56ae5
0xffffff813b3a3720 : 0xffffff802fe4866e
0xffffff813b3a3770 : 0xffffff802fcc2a40
0xffffff813b3a3790 : 0xffffff802fd1bd07
0xffffff813b3a3890 : 0xffffff802fd1c0f7
0xffffff813b3a38e0 : 0xffffff80304c0a9c
0xffffff813b3a3950 : 0xffffff802fe48a1a
0xffffff813b3a3ad0 : 0xffffff802fe48718
0xffffff813b3a3b20 : 0xffffff802fcc2a40
0xffffff813b3a3b40 : 0xffffff80303b8354
0xffffff813b3a3c30 : 0xffffff80303b882f
0xffffff813b3a3c60 : 0xffffff80303987b8
0xffffff813b3a3c90 : 0xffffff7fb1a9db6e
0xffffff813b3a3cc0 : 0xffffff7fb304b8ff
0xffffff813b3a3d40 : 0xffffff7fb3065b0c
0xffffff813b3a3d80 : 0xffffff7fb307609f
0xffffff813b3a3de0 : 0xffffff80304065a6
0xffffff813b3a3e40 : 0xffffff80304060e1
0xffffff813b3a3ef0 : 0xffffff803040547e
0xffffff813b3a3f50 : 0xffffff8030407c36
0xffffff813b3a3fa0 : 0xffffff802fcc213e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOSurface(269.11)[64FA5AA1-D63E-30EC-B7D1-D60B2FE78201]@0xffffff7fb1a90000->0xffffff7fb1abefff
         com.apple.driver.AppleIntelHD3000Graphics(10.0.4)[3A47B78B-AF9B-30A4-A5AD-C0B4318C9665]@0xffffff7fb3049000->0xffffff7fb30a9fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[8AE063C6-3413-3892-B413-EAFE16B9D270]@0xffffff7fb0902000
            dependency: com.apple.iokit.IOGraphicsFamily(519.15)[D5F2A20D-CAB0-33B2-91B9-E8755DFC34CB]@0xffffff7fb226c000

BSD process name corresponding to current thread: kernel_task
Boot args: -no_compat_check amfi_get_out_of_my_way=1

Mac OS version:
19H1210

Kernel version:
Darwin Kernel Version 19.6.0: Fri Apr 16 11:14:10 PDT 2021; root:xnu-6153.141.31~1/RELEASE_X86_64
Kernel UUID: C1222E6F-6463-3AE9-A84B-D3585059290D
Kernel slide:     0x000000002fa00000
Kernel text base: 0xffffff802fc00000
__HIB  text base: 0xffffff802fb00000
System model name: MacBookPro8,1 (Mac-CENSORED)
System shutdown begun: NO
Panic diags file available: YES (0x0)

I installed macOS Catalina 10.15.7 (19H15) on an Early 2011 MacBook Pro (MacBookPro8,1) using dosdude's patcher.
However, I was unable to upgrade to any of the later supplemental updates or security updates.
The manual Installer PKG patching did not work.
The OTA software fix enabled me to attempt an upgrade to both the 2021-02 (Release) and the 2021-03 (Developer) security upgrade, but both failed.
After the update installer finished and the reboot occurred, it always ended in a kernel panic. Apparently at the moment it attempted to start the GUI. Manually running the patcher application again did not change anything.
System Integrity is disabled - confirmed by running csrutil status in single user mode.

Do you have any idea how to fix this?
Thank you!
schreiberstein
Go to Library/Updates and delete everything in the ƒ. Retry, select the release 2021-002 update, apply the OTA s/w Fix button as soon as you see the D/L progress start. The app will confirm success.
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
I wish somebody finds the right config for Macbook Pro´s 2011.
Download the OCLP and let it generate a config - it detects the hardware in use automatically. If you plan to try older macOS versions like Mojave and Catalina which are both unsupported on your system try to set moderate spoofing instead of the default. I have to use this when using Catalina or Mojave. Since my iMac got in contrary to your MacBook a metal GPU you will not have graphics acceleration with Catalina/Mojave until this inclusion of the older patches from the @dosdude1 patchers are complete (currently only Big Sur is supported with OCLP).
Using the moderate spoofing I can use completely unpatched macOS installers and have a fully compatible (supported unsupported system).
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
What happens when updating a @dosdude1 patched Catalina without Metal w/ OCLP v.0.1.2 installed on the boot drive? Had to re-install OCLP graphics patches when updating Big Sur to 11.3.1, are the two patching methods mutually compatible? This is a non-Metal GPU question.
To my knowledge currently no graphics acceleration patches for Mojave and Catalina are included into OCLP. So your can uses OpenCore or OCLP only on unsupported systems modded with a metal GPU (MacPro and some iMacs) with Mojave and Catalina and Big Sur or your have to use it with Big Sur, only (as the support describes on the OCLP download page).
EDIT:
Reinstalling the graphics acceleration patches on Big Sur with OCLP is essentially the same process as you experience when the @dosdude1 patcher when it has to re-install it‘s patches after each new system installation or more severe update when Apples own macOS installer has purged the patches from the disk, again.
 
  • Like
Reactions: K two

0134168

Cancelled
May 21, 2009
2,964
2,805
Download the OCLP and let it generate a config - it detects the hardware in use automatically. If you plan to try older macOS versions like Mojave and Catalina which are both unsupported on your system try to set moderate spoofing instead of the default. I have to use this when using Catalina or Mojave. Since my iMac got in contrary to your MacBook a metal GPU you will not have graphics acceleration with Catalina/Mojave until this inclusion of the older patches from the @dosdude1 patchers are complete (currently only Big Sur is supported with OCLP).
Using the moderate spoofing I can use completely unpatched macOS installers and have a fully compatible (supported unsupported system).
How can I do that stuff about "spoofing"?
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
How can I do that stuff about "spoofing"?
You need just to read the OCLP docs. This is the very first time we have a real good documentation. Please honor this fact by reading it. It simply does not scale if three people read and know it and thousands ask the very same question again and again. Additionally you are moving „off support“ with your Catalina experiment and you need to know how to work through this on your own.

As I wrote before:
Using OpenCore aka OCLP with Catalina will possibly fix everything except graphics acceleration right now.
 

maxsp97

macrumors regular
Jul 23, 2019
112
189
Some where in LA
Code:
Sat May  8 21:34:33 2021

*** Panic Report ***
panic(cpu 1 caller 0xffffff802fe48a1a): Kernel trap at 0xffffff80303b8354, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000445f9300, CR3: 0x0000000032c0b000, CR4: 0x00000000000626e0
RAX: 0x0000000021000000, RBX: 0xffffff8041a2b660, RCX: 0x0000000021000001, RDX: 0xffffff8100489000
RSP: 0xffffff813b3a3c30, RBP: 0xffffff813b3a3c30, RSI: 0x00000000445f9300, RDI: 0xffffff8041a2b660
R8:  0x0000000000000001, R9:  0x0000000000000002, R10: 0x0000000000000001, R11: 0xffffff8041b1a720
R12: 0x0000000000000000, R13: 0xffffff8100489000, R14: 0x00000000445f9300, R15: 0xffffff804231a9c0
RFL: 0x0000000000010282, RIP: 0xffffff80303b8354, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00000000445f9300, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 1

Backtrace (CPU 1), Frame : Return Address
0xffffff813b3a3690 : 0xffffff802fd1c63d
0xffffff813b3a36e0 : 0xffffff802fe56ae5
0xffffff813b3a3720 : 0xffffff802fe4866e
0xffffff813b3a3770 : 0xffffff802fcc2a40
0xffffff813b3a3790 : 0xffffff802fd1bd07
0xffffff813b3a3890 : 0xffffff802fd1c0f7
0xffffff813b3a38e0 : 0xffffff80304c0a9c
0xffffff813b3a3950 : 0xffffff802fe48a1a
0xffffff813b3a3ad0 : 0xffffff802fe48718
0xffffff813b3a3b20 : 0xffffff802fcc2a40
0xffffff813b3a3b40 : 0xffffff80303b8354
0xffffff813b3a3c30 : 0xffffff80303b882f
0xffffff813b3a3c60 : 0xffffff80303987b8
0xffffff813b3a3c90 : 0xffffff7fb1a9db6e
0xffffff813b3a3cc0 : 0xffffff7fb304b8ff
0xffffff813b3a3d40 : 0xffffff7fb3065b0c
0xffffff813b3a3d80 : 0xffffff7fb307609f
0xffffff813b3a3de0 : 0xffffff80304065a6
0xffffff813b3a3e40 : 0xffffff80304060e1
0xffffff813b3a3ef0 : 0xffffff803040547e
0xffffff813b3a3f50 : 0xffffff8030407c36
0xffffff813b3a3fa0 : 0xffffff802fcc213e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOSurface(269.11)[64FA5AA1-D63E-30EC-B7D1-D60B2FE78201]@0xffffff7fb1a90000->0xffffff7fb1abefff
         com.apple.driver.AppleIntelHD3000Graphics(10.0.4)[3A47B78B-AF9B-30A4-A5AD-C0B4318C9665]@0xffffff7fb3049000->0xffffff7fb30a9fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[8AE063C6-3413-3892-B413-EAFE16B9D270]@0xffffff7fb0902000
            dependency: com.apple.iokit.IOGraphicsFamily(519.15)[D5F2A20D-CAB0-33B2-91B9-E8755DFC34CB]@0xffffff7fb226c000

BSD process name corresponding to current thread: kernel_task
Boot args: -no_compat_check amfi_get_out_of_my_way=1

Mac OS version:
19H1210

Kernel version:
Darwin Kernel Version 19.6.0: Fri Apr 16 11:14:10 PDT 2021; root:xnu-6153.141.31~1/RELEASE_X86_64
Kernel UUID: C1222E6F-6463-3AE9-A84B-D3585059290D
Kernel slide:     0x000000002fa00000
Kernel text base: 0xffffff802fc00000
__HIB  text base: 0xffffff802fb00000
System model name: MacBookPro8,1 (Mac-CENSORED)
System shutdown begun: NO
Panic diags file available: YES (0x0)

I installed macOS Catalina 10.15.7 (19H15) on an Early 2011 MacBook Pro (MacBookPro8,1) using dosdude's patcher.
However, I was unable to upgrade to any of the later supplemental updates or security updates.
The manual Installer PKG patching did not work.
The OTA software fix enabled me to attempt an upgrade to both the 2021-02 (Release) and the 2021-03 (Developer) security upgrade, but both failed.
After the update installer finished and the reboot occurred, it always ended in a kernel panic. Apparently at the moment it attempted to start the GUI. Manually running the patcher application again did not change anything.
System Integrity is disabled - confirmed by running csrutil status in single user mode.

Do you have any idea how to fix this?
Thank you!
schreiberstein
Here is the link and read it will solve your problem.
https://www.reddit.com/r/CatalinaPatcher/comments/mg17w9
 
  • Like
Reactions: TimmuJapan

kosiko

macrumors newbie
Jan 26, 2010
13
11
I am running on 19H1210 for some days and as far as I remember I got there by installing the Beta 2021-003...

Now today I have a new update in my Software Update Pane. One for Safari and one called "macOS Catalina Security Update Developer Beta 2021-003" with 1,42GB.

Since I thought I got that already I am now wondering what that is. Anybody else seeing that update since today?? Already installed?

Thanks!
 

resurrector66

macrumors newbie
Feb 26, 2020
13
17
I am running on 19H1210 for some days and as far as I remember I got there by installing the Beta 2021-003...

Now today I have a new update in my Software Update Pane. One for Safari and one called "macOS Catalina Security Update Developer Beta 2021-003" with 1,42GB.

Since I thought I got that already I am now wondering what that is. Anybody else seeing that update since today?? Already installed?

Thanks!
New beta 2021-003 gives you 19H1213
 
  • Like
Reactions: K two

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
Thanks!

Is it common that they give it the same bundle name than the former...???
I seems that we just confuse the official upcoming name of the security update (2021-003) with the different beta builds created by Apple on a daily bases. These (daily) new builds and tested on special test compute farms automatically, but only a few make it to the public - using this new label or name.
 
  • Like
Reactions: K two
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.