And Posted November 2, 2022 Share Posted November 2, 2022 Alfred 5.0.4 Build 2095 MacOS Ventura 13.0 (22A380) Happens almost every time I'm using ejectall command Link to comment
vitor Posted November 7, 2022 Share Posted November 7, 2022 I’m unable to reproduce. Could you:Update Alfred.Press the Reset from your last image.Reboot.Try again. Link to comment
And Posted November 10, 2022 Author Share Posted November 10, 2022 Alfred is the latest version now 5.0.5 [2096] Reset done Right after reboot everything is fine. When I do "eject all" after couple of hours, I've got the same What else can I try? Link to comment
vitor Posted November 11, 2022 Share Posted November 11, 2022 (edited) Under Eject, change it to Removable Media and see if that solves it. Also, when you do eject do you see any volumes mounted on the system disks? What’s on that list is what Alfred will try to eject. Edited November 11, 2022 by vitor Chris Messina 1 Link to comment
Chris Messina Posted November 14, 2022 Share Posted November 14, 2022 I often use the Eject All command to eject my external SSDs. However, after updating to macOS Ventura 13.0.1 (22A400) and running Alfred 5.0.5 (Build 2096), when I use the command, I get errors for many more disks, many of which probably shouldn't be ejected, including my startup disk! Did something change? Link to comment
Vero Posted November 14, 2022 Share Posted November 14, 2022 33 minutes ago, Chris Messina said: Did something change? Nothing in Alfred has changed, but Ventura is brand new and still quirky. In Features > System, try changing which types of media is included in the Eject keyword's scope, then try using the "eject" keyword. What list of drives do you see then? Link to comment
Stephen_C Posted November 14, 2022 Share Posted November 14, 2022 I appreciate this may not help very much but, running the same macOS and Alfred versions, I have no problem with the "ejectall” command. I make the comment merely to indicate it may not be a universal problem. Stephen Link to comment
And Posted November 14, 2022 Author Share Posted November 14, 2022 In my case the problem seems to be solved by adding "Recovery" to the list of exclusions Link to comment
Chris Messina Posted November 14, 2022 Share Posted November 14, 2022 Ok, thanks again! @Vero my Eject setting was set to this: I've changed it to "Removable media". Link to comment
Stephen_C Posted November 14, 2022 Share Posted November 14, 2022 Just to muddy the water even further, my "Eject” setting is also "Local Mounted Volumes” and the exclusions include "Macintosh HD” (i.e., that works for me as indicated in my previous post). Stephen Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now