Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds Second Beta of macOS 13 Ventura to Developers
- Thread starter MacRumors
- Start date
- Sort by reaction score
Yeah sometimes I don't get notifications or sounds for them.
I am running a Parallels VM...don't know how it fairs on actual hardware. Didn't want to take the chance on my daily driver and I don't have another test unit.Oh sure, all web browsers don't scroll.
I maintain ASR backups so if something happens to either desktop or laptop I can do a DFU restore as needed. It's a rare occurrence that necessitates that type of restore against AS MacOS/System FW installation. I was only able to get a kernel panic one time when I sequenced through messing with Safari to see if it was capable of 8K HDR yet by enabling experimental feature VP9 SW Decoder on battery. Tried multiple YouTubes. Later I was playing a Netflix HDR and a few mins of play it had a kernel panic. It booted with the usual send report to Apple message. I disabled that P9 SW Decoder on battery and haven't seen it reoccur.
So the weirdness with browser not scrolling might relate to what you are using in the VM as far as working with BT or USB-C connected accessories. I can do wired mouse, Magic Mouse and TouchPad haven't seen that issue.
Usually, I download the full installer and create a bootable disk to perform clean installation when new beta arrives. When I erased Montery volume and tried to install Ventura Beta2, a message box poped up saying an administrator account name and password was needed to unlock the disk. The installation log looked like the target disk was treated as FDE(full disk encryption?), In fact the filevault was always off.
For comparison， Montery and Ventura Beta1 never have this issue. Is it a bug of Ventura Beta2?
For comparison， Montery and Ventura Beta1 never have this issue. Is it a bug of Ventura Beta2?
As you say, it's either a bug in beta 2, or it could be a new way of upgrading only changed files.
My suggestion (copied from a recent post in the "Ventura on unsupported hardware" or whatever that thread is officially called) is to install Monterey and then install beta 2 of Ventura. You can give it the admin password you used for the Monterey install.
Or install beta 1 then upgrade with beta 2. Your issue is that you're using beta 2 as a clean install, and this isn't working. Whether this is a permanent feature, or beta 3 will allow clean installs again, you'll need to wait a couple of weeks to find out
My suggestion (copied from a recent post in the "Ventura on unsupported hardware" or whatever that thread is officially called) is to install Monterey and then install beta 2 of Ventura. You can give it the admin password you used for the Monterey install.
Or install beta 1 then upgrade with beta 2. Your issue is that you're using beta 2 as a clean install, and this isn't working. Whether this is a permanent feature, or beta 3 will allow clean installs again, you'll need to wait a couple of weeks to find out
I don't have a recent backup. Hoping a future release will allow it to recover properly.
From a community post
See if you can boot into Safe Mode.
Try booting into Recovery Mode (Command + R) and Internet Recovery Mode (Command + Option + R) and run Disk Utility First Aid. Make sure to examine the "Details" to see if there are any unfixed errors listed (even if First Aid says everything is Ok. If there are unfixed errors, then you will need to erase the drive and reinstall macos or restore from a backup. If after running First Aid the Mac won't boot normally, then boot into Recovery Mode and select "Reinstall macOS" to install macOS over top of itself. This should not affect your data.
What is the exact model of your Mac?
