Jump to content
366 posts in this topic

Recommended Posts

ESP Mounter is broken on Tahoe.

 

The latest version (2.5?) when it installs does NOT work on Tahoe  (25C5048a).  What happens is that when I ask to mount a device, it asks for an admin password, which I enter, it goes away, does not issue an error, or any communication at all and as it turns out, it has done nothing.  In the security section, there is no password.  Entering there (in settings/security) does not work, as it does not save it there either.

 

I have changed the update feature to none and will wait this out.

 

EDIT:  I have reverted to EFI Agent, which I've used for a long time.  I did this for two reasons.  1. The app not saving authentication, as noted in the above paragraph and 2. I could not stop ESP Mounter from pounding me with a splash screen asking me to update even though I set it to ignore this update, and even though I went into settings to make sure the check box for checking for updates was not enabled, but again, nothing worked and it continually, at login, hit me with this splash screen about updating.

Edited by meg2014
2 hours ago, eSaF said:

Hiya, sorry to hear you're experiencing a problem with the latest version.

It is functioning normal on my system, maybe you need to uninstall the App, reboot, clean NvRAM and install it again.

  Reveal hidden contents

Screenshot2025-11-29at21_37_33.png.3de401debed964a62c49d1cf9433c329.pngScreenshot2025-11-29at21_38_05.png.b8632c409db705876597a848fd780787.pngScreenshot2025-11-29at21_38_24.png.76be2934e11bf6ccf4ff3c5c85be00e6.png

 

 

 

 

So, I've done all that - many, many times over.  I will admit that this Tahoe Beta seems to have more idiosyncracies (meaning minor bugs) than other MacOS software I've installed.  However, I will say that EFI Agent is working just fine, so I don't really have a lot of answers right now.

 

It does seem that the app (ESP Mounter) just isn't writing changes properly, but I don't know why.  I think it has something to do with security on these newer MacOS platfroms, like Sequoia and Tahoe.

5 hours ago, meg2014 said:

It does seem that the app (ESP Mounter) just isn't writing changes properly, but I don't know why.  I think it has something to do with security on these newer MacOS platfroms, like Sequoia and Tahoe.

As far as I (and others) have tested, ESP Mounter works just fine with all the versions on macOS from Big Sur to Tahoe released version 26.1, but as it appears Tahoe beta 26.2 seems to be having issues on some rigs, you are the first person to repost such issue.

What I suggest is to open the Keychain Access, look for com.efimounter.adminauth and com.espmounter.adminauth then remove them, open the app which triggers the admin authentication once more and see if that stores the password correctly.

  • Like 2
20 hours ago, meg2014 said:

ESP Mounter is broken on Tahoe.

 

The latest version (2.5?) when it installs does NOT work on Tahoe  (25C5048a).  What happens is that when I ask to mount a device, it asks for an admin password, which I enter, it goes away, does not issue an error, or any communication at all and as it turns out, it has done nothing.  In the security section, there is no password.  Entering there (in settings/security) does not work, as it does not save it there either.

 

I have changed the update feature to none and will wait this out.

 

EDIT:  I have reverted to EFI Agent, which I've used for a long time.  I did this for two reasons.  1. The app not saving authentication, as noted in the above paragraph and 2. I could not stop ESP Mounter from pounding me with a splash screen asking me to update even though I set it to ignore this update, and even though I went into settings to make sure the check box for checking for updates was not enabled, but again, nothing worked and it continually, at login, hit me with this splash screen about updating.

 

Fun, Fun, Fun with Tahoe 26.2 Beta.....

 

So, I have resolved the issue (I think).  EFI agent does not use Keychain, that's why it worked.  ESP Mounter uses Keychain and that's why it didn't work (for me).

I could not delete anything in Keychain so I was forced to rename the two Keychain directories (in the respective Libraries - both of them), which meant I had to re-enter some passwords, but then it started working.

I am not having this problem in Ventura, but in Tahoe, well, I was screwed....until I got rid of those Keychain directories - then all was fine, except I had to spend a lot of time re-entering password for various utilities.

 

So, at least now it seems to be working just fine.

  • Like 2
1 hour ago, meg2014 said:

I could not delete anything in Keychain so I was forced to rename the two Keychain directories

I guess that's where the issue lies, for some reason, most likely a bug or another security reason if you can't manually remove the keychain properties yourself then the app can't store the password in the keychain that's why it prompted you to re-enter the password over and over.

My guess is that there is some issue in your macOS, because from what I see @eSaF and probably many other users also have the same version of macOS as you do and they don't have any issues with the keychain.

  • Like 2

What is imaginary for some is real for others, and vice versa.
Without beta testing, we would not be able to improve systems.

 

From my point of view, participating in forums means trying things out and sharing your experience.

It's also fun to hear other opinions that may seem, again from my point of view, bizarre.

 

Getting back to the topic, I have this problem in Tahoe (release and Beta), which I updated from Ventura.
I don't use the app because I don't need to mount the EFI often, but I think it's right to help the developer understand what might be wrong at the app or user level.

:)

 

  • Like 4
  • Thanks 1
1 hour ago, eSaF said:

@meg2014 - Hiya, I may be clutching at straws here but it may help by running 'First Aid' in Disk Utility on every Tahoe volume especially the Data Volume and see if there are any errors.

Any Errors present in any of the Volumes will suggest the installation is borked and cannot be repaired and will warrant a clean Install.

 

I am hoping that's not the case as it is a PITA but to me, it seems your installation is somehow misaligned.

As I suggested perhaps 'First Aid' will provide some kind of clue about the installation.

 

Good luck.

Cheers.

 

Been there and done that (no errors).  Did it from Recovery.  No issues, but thanks for the thought.

  • Like 1
×
×
  • Create New...