automount SMB in Tahoe 26 no longer working

MacBook Pro M1, MacBook mini M1 Tahoe 26.


I have mapped 6 shares from my NAS (Public, Photo, backups etc). This has been working for almost 10 years in all MacOs versions. Just open finder, and the shares appeared by auto-mounting.


In Tahoe, it no longer works, I need to manually remount on each restart. ( by open the network devices, drag each share to the finder favorites bar).

Adding the shares to the Settings, General, Loginitems does work, but this opens 6 folders on startup that I have to close, as I do not need all shares on the desktop.

What has happened? Has Apple forgotten that (business) users have auto mounts on network servers?


How to get this annoyance fixed?


MacBook Pro 13″

Posted on Sep 19, 2025 1:02 AM

Reply
Question marked as Top-ranking reply

Posted on Sep 24, 2025 11:08 AM

I think I've found a pretty good workaround for this issue. The key seems to be to prevent MacOS from using the usual /Volumes mount point.


  • Remove any favourites for the network drives that may exist in the Finder side bar from previous attempts. Make sure none of them are mounted (reboot if necessary).


  • Using the terminal (or Finder itself I guess), make a new mount directory in your home directory (I made mine a hidden directory using a dot):
  mkdir /Users/Stuart/.mnt


  • Make further directories beneath it to serve as mount points for your shares:
  mkdir /Users/Stuart/.mnt/Stuart


  • In the terminal, edit the /etc/auto_master file (I'm using vim to do it):
  sudo vim /etc/auto_master

... and add the following line at the end of the file:

  /-          auto_smb


  • Then create/edit the /etc/auto_smb file:
  sudo vim /etc/auto_smb

Add your shares in here, one on each line, to have them mount at the mount points you created for them earlier. For example:

  /Users/Stuart/.mnt/Stuart       -fstype=smbfs,soft,noowners,nosuid,rw   ://<user>:<password>@<server host or IP>/<share>


  • After editing, run the following to mount the shares:
  sudo automount -vc


  • Then, in Finder use the Go menu and: Go > Go to Folder...

Type the path of the directory you created earlier, for example:

  /Users/Stuart/.mnt


  • Press Enter to go to that directory and you should see one or more other directories in there which, if all has gone well, will be your mounted network drives. Click on them and Finder should show you their contents as normal.


  • Make sure the path bar is visible in your Finder (View > Show Path Bar) and then drag the little icon for your share from the bottom of the Finder window into the Finder side bar under Favourites to create a 'favourite' for your network drive. You can then use Finder to access your share via this as before.


  • I've tried rebooting the Mac and then clicking on the favourites after reboot and they automount instantly and flawlessly, just like they used to do before Tahoe.


I hope this helps someone until Apple fix this problem.


36 replies

Dec 21, 2025 7:42 AM in response to EAZ1964

I was a little confused, but I think we're mostly talking about the same issue, but different use cases. If I understand you correctly, by startup you really mean rebooting the machine. That is usually not a problem for me. The main issue I have is that I have some shell scripts the rely on the location of the shared folder being stable in the file system and the issue typically happens randomly during usage. It also reconnects randomly for whatever reason.


I will say that while not ideal, I have had great success with NFS and while it's a little basic, the performance is actually quite good. It of course doesn't support Time Machine, but if all you want is share files, it's an option worth considering.

Dec 12, 2025 5:00 PM in response to EAZ1964

Right, but it relies on you having to click on a link if I understand it correctly? In my case, I find unmounting is much faster since auto mount will remount it immediately. Ideally, I would want my share to be just there. The issue, at least in my case, is that it seems that there is a point where MacOS loses the connection to the share and resets its permissions to be only available to root, basically the default for automount before you cd into it, but in this case, it is stuck in that case and you get a permission denied, even though the share is fine. It's like automount is stuck thinking that the is unavailable until you unmount it and it brings it back to life.

Dec 12, 2025 9:42 AM in response to wombat2k

Months of testing and debugging and I've made no progress in figuring out what the issue is. The only reliable way of being able to use my NAS to share files through a stable folder location is with NFS, which is not ideal and obviously means no Time Machine, although I believe AutoMounter might be good enough for Time Machine since it might not need a stable link to the share.

Nov 25, 2025 6:38 AM in response to EAZ1964

I'm surprised by the amount of people who were successful with this. When I implemented this, it worked, however after a while, typically on a wake up, but also sometimes during usage, the macOS will change the permissions on the directory to be accessible to root only and make it inaccessible. The only way to remedy this is to unmount, and then auto mount remounts it automatically (and successfully).


Even the Automounter app has similar issues, in that it cannot access the original folder, so it creates a new one by appending `-1` to the original folder name.. This works if you are using the Finder to access your share, but not if you are relying on a stable location.


It's as if there is a disconnect somewhere and autmount isn't triggered, so it doesn't change the permissions on the share to make it accessible..

automount SMB in Tahoe 26 no longer working

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.