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

update to Ventura tonight. I dread this settings app. Hopefully the other features will make me forget this eye soar.
I haven't updated to latest yet,but I can confirm I could never get used to the new seetings.it's just an inferior experience.100% steps backwards in terms of practicality and "user friendly-ness".I wonder who came up with this idea and how it was approved.it's awful.
probably they don't care because based on rumours their goal is to make Mac OS touch screen and merged with iOS so this should have happened regardless.
 
I haven't updated to latest yet,but I can confirm I could never get used to the new seetings.it's just an inferior experience.100% steps backwards in terms of practicality and "user friendly-ness".I wonder who came up with this idea and how it was approved.it's awful.
probably they don't care because based on rumours their goal is to make Mac OS touch screen and merged with iOS so this should have happened regardless.
Please try to convince all of us that you use system settings frequently? For me it's set it, forget it. I can go days without accessing system settings. :p
 
  • Like
Reactions: eldho and AdamNC
Can someone explain how some have so many problems with 13.2 yet the next person has zero? It makes no sense to me that the code that is written only one way would work differently on different machines. The only logical explanation to me is user error or already corrupted files on a machine that ends up screwing up the new code. Either way that doesn’t mean 13.2 is bad. The machine it’s going on is already messed up.
 
  • Like
Reactions: GlenK
I haven't updated to latest yet,but I can confirm I could never get used to the new seetings.it's just an inferior experience.100% steps backwards in terms of practicality and "user friendly-ness".I wonder who came up with this idea and how it was approved.it's awful.
probably they don't care because based on rumours their goal is to make Mac OS touch screen and merged with iOS so this should have happened regardless.
If you spend some time going through it and learning it is actually really good. I hated it at first but I spent about an hour going through each individual section and bam it all came together and now I like it a lot more than the old one.
 
  • Like
Reactions: eldho and Realityck
Can someone explain how some have so many problems with 13.2 yet the next person has zero? It makes no sense to me that the code that is written only one way would work differently on different machines. The only logical explanation to me is user error or already corrupted files on a machine that ends up screwing up the new code. Either way that doesn’t mean 13.2 is bad. The machine it’s going on is already messed up.

Well, the OS is running on a range of different hardware, which is configured in a range of different ways. When the update happens, it tries to preserve the configuration as best as it can. An error could come from something like a bug in a USB device which is on a port, or a problem in a configuration file which worked under an old OS and doesn’t work under the new.

If you have a relatively new machine which is configured to factory settings, like an M1 iMac which includes all-Apple hardware and hasn’t been heavily used, you are less likely to have a problem than with an old Intel Mac Mini which is being used with separate third-party webcam, monitor, speakers, microphone and dock and which has also been a developers playground for a number of years who enjoyed poking into the settings.

If you’re lucky you will have used mostly well-known products from major brands, it will have all been tested by Apple QA and it will all “just work”.
 
You can use the system settings View pull down menu to see 40 choices without doing much nestled vertical navigation. ;)

Earlier post about that tidbit. Monterey users can use this tidbit.
the pull down menu doesn't really address the issue.it's just another way to access the same cramped structure..
 
Please try to convince all of us that you use system settings frequently? For me it's set it, forget it. I can go days without accessing system settings. :p
actually using it less frequently (like majority) is more problematic because you have too keep looking and seraching for what you need in this cramped nest of rows and menus,whereas it used to be done very easily by just taking a look.
I've been using Macs since Snow Leopard days..it's just backwards.
 
I updated my M1 Mac Ultra Studio and when it restarted, it hung on the Apple bootup screen. I waited 20 minutes and then did a hard restart. Everything seems fine i guess? Anyone have this issue?
 
YouTube in Safari won't play anymore! Right after updating from Ventura 13.1 to Ventura 13.2 on MacBookPro 2021 (chip: Apple M1 Pro), Youtube now says "Your browser can't play this video." inside where it used to play the video. It worked perfectly for Safari playing YouTube on Ventura 13.1.

I tried restarting computer (it will play for 30 seconds, then hang, then same "your browser can't play this video".
I tried reinstalling Ventura 13.2 (holding power button while powered off and click options gear to get the reinstall option).

So those above did not fix it. I don't think there is an option to reset VPRAM or Memory or whatever for M1 Macs, so didn't try those. I hear Ventura 13.2 doesn't have same problem for intel Macs.
 
YouTube in Safari won't play anymore! Right after updating from Ventura 13.1 to Ventura 13.2 on MacBookPro 2021 (chip: Apple M1 Pro), Youtube now says "Your browser can't play this video." inside where it used to play the video. It worked perfectly for Safari playing YouTube on Ventura 13.1.

I tried restarting computer (it will play for 30 seconds, then hang, then same "your browser can't play this video".
I tried reinstalling Ventura 13.2 (holding power button while powered off and click options gear to get the reinstall option).

So those above did not fix it. I don't think there is an option to reset VPRAM or Memory or whatever for M1 Macs, so didn't try those. I hear Ventura 13.2 doesn't have same problem for intel Macs.
In Safari -> Develop menu ->empty cache, wait a few seconds check to if anything changed. Try booting in safe mode
 
Last edited:
Try booting your Mac in safe mode to see if its some startup or extension issue.
Thanks but I previously tried that. I spent over an hour on the phone w/ support for 13.1 and tried lots of different things including reinstall & safe mode. Support suggested I totally wipe my SSD Data vol and do a recovery from scratch. That is not something I'm prepared to do for this bug. There must be a better solution.
 
the pull down menu doesn't really address the issue.it's just another way to access the same cramped structure..
I can just as easily used SIri or spotlight search to open specific system setting hierarchy. The reason they went to a vertical style is obvious that they intend to grow the amount of configuration options MacOS provides and also because it works better on smaller size screens then the older icon based grouping of setting categories each with its own hierarchy.
 
Can someone explain how some have so many problems with 13.2 yet the next person has zero? It makes no sense to me that the code that is written only one way would work differently on different machines.

User behavior and apps and connected peripherals differ among users. Some push systems more than others. Some use more features than other. Some have old user habits that can break in new systems if there is a feature change or certain APIs or drivers are buggy or depracated.
 
Thanks but I previously tried that. I spent over an hour on the phone w/ support for 13.1 and tried lots of different things including reinstall & safe mode. Support suggested I totally wipe my SSD Data vol and do a recovery from scratch. That is not something I'm prepared to do for this bug. There must be a better solution.
It's quite possible if you just install the next MacOS 13.3 beta coming next week it might fix this for you. But using the factory reset (DFU-restore) and migration assistant which automatically moves anything system wide that is not compatible into a separate folder is something I had to use very occasionally as a beta tester. I use Carbon Copy to make a snapshot on external Volume that acts as a ASR source. That is all you need to get right back to where you were after DFU-restore.
 
Can someone explain how some have so many problems with 13.2 yet the next person has zero? It makes no sense to me that the code that is written only one way would work differently on different machines. The only logical explanation to me is user error or already corrupted files on a machine that ends up screwing up the new code. Either way that doesn’t mean 13.2 is bad. The machine it’s going on is already messed up.
The variation of hardware along with software can sometimes cause a MacOS update to leave some code/files that causes an application not to work as it should. This can happen also because unknown to the user he had a write/save that corrupted something and it manifested when he updates the MacOS. Some problems are corrected by MacOS after it reboots and just repairs on its own and it starts to work. Example I had a G-Hub startup app that works at a low level for controlling a gaming mouse, I update to a beta and suddenly find its not able to draw the apps interface, its blank. I tried to remove and reinstall, no change, then a few boots later its working again. The vast majority of beta installs going back several years have been rarely problematic. Occasionally something is incompatible temporary until the developer or the next beta update fixes the issue.
 
It's quite possible if you just install the next MacOS 13.3 beta coming next week it might fix this for you. But using the factory reset (DFU-restore) and migration assistant which automatically moves anything system wide that is not compatible into a separate folder is something I had to use very occasionally as a beta tester. I use Carbon Copy to make a snapshot on external Volume that acts as a ASR source. That is all you need to get right back to where you were after DFU-restore.
I gave up on beta's a decade ago. Don't have time to fiddle with that stuff anymore. I waited for 13.2 to fix this and it didn't. I've already spent 2 full days beating my head against the keyboard in frustration. I'm chasing one little thing after another. Thanks for the DFU comment. It's starting to seem like I may need to go that way.
 
Please try to convince all of us that you use system settings frequently? For me it's set it, forget it. I can go days without accessing system settings. :p
I am wondering why it matters how many times its needed? It's horrible. So much easier to use the old SP interface. I absolutely hate the vertical layout on my iOS devices. But each to their own.......
 
Anyone know if 13.2 finally fixes the issue that causes VPNs to disable iCloud Private Relay and cause major lag in SP>Apple ID?
 
I gave up on beta's a decade ago. Don't have time to fiddle with that stuff anymore. I waited for 13.2 to fix this and it didn't. I've already spent 2 full days beating my head against the keyboard in frustration. I'm chasing one little thing after another. Thanks for the DFU comment. It's starting to seem like I may need to go that way.
The Apple Store personnel with an appointment are pretty nice in helping you do that with an another laptop they normally usually use for that. Just make sure store personnel don't use a Thunderbolt 3/4 cable that looks like a USB-C cable it has to be USB-C to USB-C cable for DFU to work. The Timing is tricky for it to work, but it is an amazing means to an end when you need to totally expunge gremlins as it totally redoes the MacOS and system FW ;)
 
Well, still disappointed that this update didn't fix the Nikon tethering issue with Lightroom. Four months in since the Ventura update broke it. Still no resolution from Nikon/Adobe/Apple...
 
Well, still disappointed that this update didn't fix the Nikon tethering issue with Lightroom. Four months in since the Ventura update broke it. Still no resolution from Nikon/Adobe/Apple...
I don't blame them. Didn't Nikon announce they stopped making cameras? No point in supporting dead end technology
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.