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

Is anyone going to be a Day 1 upgrader after the Catalina mess?
Day 1?

I've been running the betas since the 4th or 5th one on my only (private) Mac, so - in a way - I've been a Day minus 90 upgrader. :p

Anyway. After this 11.0.1 beta I've unenrolled the Mac from the developer track, and - barring some unforeseen problems - will not upgrade again until the regular 11.0.2 (or thereabouts). :)
 
  • Like
Reactions: dumiku
Apple Music "for you" still not working in this version

"An error has occurred , try again later'

Rolled back to Catalina and its working fine
The (newly renamed) Listen Now works fine for me:

Screenshot 2020-11-06 at 10.03.08.png
 
I've been putting this RC through its paces for hours and I've got to say they put a lot of work into cleaning up most (not all, but most) of all the little irritating bugs. File save dialogues are finally doing the job instead of hanging with the beach ball. The control panel is behaving properly although there's still a bit of a delay in the desktop background panel bringing up the "folders" section. I'm about to try to run first aid on my external drives which did nothing but hang the last two betas. We'll see - I'll edit this if it goes south again.
 
How does it seem that way? They released 14.1 betas before 14 was out. This update will likely just be pre installed on the new macs.
It’s the way their testing works always ahead of public release
If it was MacOS 11.1.0, I’d agree with you. But this is MacOS 11.0.1, so this should be treated like when Apple releases a major iOS software such as iOS 14.0.0, but then makes 14.0.1 the only real public build available on launch day.
 
Nope. My issue has nothing to do with watchOS. Never did.
Also, if that is the case. Why am I (and others) experiencing the issue with 7.1?
Someone posted a screen shot a few posts above.
I also had the unlock problem with my apple watch and ended up getting to a senior software engineer within apple to get it fixed. It turned out it was a kext or protocol that had been affected by another app i had installed.

The way he got me to test it was to just do a total clean install of MacOS in a separate container, hey presto, it worked first time.
 
I also had the unlock problem with my apple watch and ended up getting to a senior software engineer within apple to get it fixed. It turned out it was a kext or protocol that had been affected by another app i had installed.

The way he got me to test it was to just do a total clean install of MacOS in a separate container, hey presto, it worked first time.
I had a problem like that on one specific computer running Catalina. If I had the Paragon Software NTFS driver installed, the watch absolutely would not unlock the computer. This only affected one of my computers but uninstalling the driver resolved the problem completely for me. Even after doing a clean install, if I installed the NTFS driver, the watch unlock would stop working, meanwhile I used a separate computer that wasn't affected by the issue. Eventually it started working again.
 
Hi guys,

I’m enrolled to dev beta on my iMac (10.15.7 actually) and I don’t see any update...

I tried with public beta profile too... still no update showing...

Any help ? Thanks

Franck
 
  • Haha
Reactions: Babygotfont
Anyway. After this 11.0.1 beta I've unenrolled the Mac from the developer track, and - barring some unforeseen problems - will not upgrade again until the regular 11.0.2 (or thereabouts). :)
If I remember correctly from past years, if you're now back on the regular profile, Software Update will offer you the release version when it hits. If you're desiring to run a standalone installer, that will do the trick--again, assuming I'm right. :)
 
If I remember correctly from past years, if you're now back on the regular profile, Software Update will offer you the release version when it hits. If you're desiring to run a standalone installer, that will do the trick--again, assuming I'm right. :)
Last time round, it didn't offer the final realease when that came out, I had to wait for the next minor. And now since I already are on 11.0.1b, suspect I won't get any upgrades before 11.0.2, but that's just me guessing. :)
 
Last time round, it didn't offer the final realease when that came out, I had to wait for the next minor. And now since I already are on 11.0.1b, suspect I won't get any upgrades before 11.0.2, but that's just me guessing. :)
I may actually be thinking of beta software like Xcode, which comes through the MAS, not Software Update. And App Store only knows what you got with App Store.

In such a case, I'll just directly download the release installer. Right now I'm running the Big Sur beta on two Macs in the office. I think I'll keep my daily driver on Catalina for a little while yet. :)
 
11.0 will be pre-installed on the macs announced on tuesday i bet. that's why the 'release' to existing machines will be 11.0.1, as they will have had to bake the new machine images
I think so.
At least one of the Mac announced next week will be available right after the event, with 11.0 pre installed.
I'll stay on Catalina for a while, I'm working from home and don't want to screw up my laptop, can't go to the office to use my other Mac is something bad happens.
 
Which version of Time Machine has macOS Big Sur 11.0.1 (20B5022a) Release Candidate? 1.3 or 2.0? Thanks.
 
I encounter same kernel panic on this RC : com.apple.iokit.IOAcceleratorFamily2(439.35.4)
I never had the same issue on Catalina. I’m considering to downgrade.
 
  • Haha
Reactions: Babygotfont
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.