my desktop files & folders open correctly, but all apps (aliases) here, on both my silicon & intel macs, open terminal as well. will report in feedback app right now...
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.
macOS Ventura 13.1 Beta 2 - Bug Fixes, Changes, and more!
- Thread starter WilliApple
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Appreciate your reports. Is there any chance you can download and test the latest version of Malwarebytes (can do it for free) to see if the issue with V13.0 and security software still exists?
I'm thinking of downloading V13.01.1 of Ventura and testing it, as it seems V13.1 will not be released until at least the middle of December. But would much prefer V13.1.
don't want to install malwarebytes, but am sure there are others here who run it, and hopefully, can report back about the security issues (am not running any such apps). apologies!
Understand, and thanks for the quick reply. I actually downloaded and ran Malwarebytes earlier today on my M1 Mac Mini running OS 12.6.1 without any issues, and also effectively removed it (and all its "pieces"). I also own ClamXAv, and did run it yesterday on both of my Macs (found some weird suspicious files. They are now gone).
I just completed downloading the full Ventura V13.0.1 Installer from the App Store, and will this afternoon install it on my new Samsung T7 1 TB SSD, migrate all my apps, settings, etc. from the mini, and then start testing. I will also test Malwarebytes in that environment.
In any event, thanks again.
weird, the terminal thing. again, just effects app aliases on the desktop; files & folders are fine (i keep 2 apps on my desktop for worthwhile reasons 👍), but can work around that for now.
wonder how many others are seeing this? i don't know anyone who otherwise keeps app icons on the desktop...
Just did a test for you. Same. Opens terminal, even if the alias is elsewhere in my filesystem. This is quite fun
If you want the app to launch (*and* the terminal though, but can't have everything) then shortcut/alias the application itself within the .app package.
for now, will do things the old fashioned way... launchpad (macbook only, sigh), spotlight, app folder... etc. full disclosure: i've had the dock locked away since os x 10.3.9, never use it 🤯Just did a test for you. Same. Opens terminal, even if the alias is elsewhere in my filesystem. This is quite fun
If you want the app to launch (*and* the terminal though, but can't have everything) then shortcut/alias the application itself within the .app package.
anyway, reported it in feedback app (sternly worded 🤣)
Last edited:
Apparently not fixed in 13.1 b2, as it's mentioned in the release notes:
Endpoint Security
Known Issues
- Third-party security products using the Endpoint Security API might lose Full Disk Access authorization and stop functioning, even though the product remains visible in System Settings. This issue doesn't affect authorization granted via MDM. (100857507)
Workaround: Go to System Settings > Privacy & Security > Full Disk Access, select the security product, use the minus (-) button to remove, and then use the plus (+) button to re-add the affected security product. A system restart might be required to restore expected functionality.
Thanks. Wonder if it's fixed in V13.0.1?
BTW, I thought Apple would use the KISS philosophy regarding the easy installation of Ventura onto an external SSD. But alas, not the case, and as cumbersome as with Monterey (at least the initial versions). One needs to first create a bootable USB drive, and then it can be installed on an external SSD. I am in the process of doing that now, and it sure is S...L...O...W. OTOH, I was recently having an issue with V12.6 of Monterey on my Mac Mini, so I downloaded V12.6.1, did a SuperDuper! backup (containing the OS 12.6.1 installer), restarted the Mini from that backup, then went through the old, efficient way of doing the installation of 12.6.1:
1. Use Disk Utility to Erase and Format the internal SSD on the Mini.
2. Navigated to the V12.6.1 installer, launched it, and successfully installed it onto the internal SSD.
3. As usual, then migrated all my apps, settings, etc. from the backup to the internal SSD.
4. Rebooted from the internal SSD, and all was good.
Understand.
But I give up. After all that, I am getting this error message for that external SSD:
"SDErrorDomain error 108.". Don't know how to proceed, but sure is frustrating!
I actually have tried twice to install Ventura (first, V13.0, and just a little while ago, V13.0.1), and in both instances I have lost the startup chime on my main internal SSD Monterey partition. And no matter what I do with the Sound, etc. settings, it remains that way. The only way I've managed to get it back was to download V12.6.1 of Monterey from the app store within my SuperDuper! backup, launch Disk Utility to erase and format the internal SSD, do a clean, fresh installation of Monterey V12.6.1 to the internal SSD, migrate all my apps, settings, etc. from the backup to te internal SSD, then restart the internal SSD. Works like a champ. Cannot understand why I can't install Ventura on a properly formatted external SSD, either like the method I described above, or what I did earlier today: make a bootable Ventura installer on a flash drive, boot the mini from that bootable flash drive, then attempt to install Ventura onto the external SSD. For both attempts, got the "SDErrorDomain error 108." error.
I guess what I could do is do a SuperDuper! backup to my new Samsung T7 1TB external SSD, then do an update form Monterey V12.6.1 to Ventura V13.0.1. But still much prefer a clean, fresh installation of Ventura onto that external SSD. Any ideas why it is not working?
Thanks, I'll watch this and like you just do the work around.
I can confirm the problem. I never use app aliases as I am using Alfred to launch my apps but I just created and alias and put it on the desktop as a test. And yes, it opens terminal.
Same thing happening for me (aliases, not Alfred) Came here to see if it was just me.
The latest update 13.1 Beta 4 (22C5059d) fixed this problem for me.