Finder can't open moved files on SMB/AFP without relaunching Finder etc.

Good News,

i reported the bug to Apple and was getting this mail today:

the latest update, Build 22F5049e, includes changes that may resolve this issue.

I installed this version on our macOS Ventura 13.4 Beta mac and it seems fixed. I will do some more tests but for now the issue is looking to be solved.

We are seeing the same issue as described.

We are running an Editshare EFS network storage for video editing.

Files that are remotely uploaded to the network storage via Signiant Media Shuttle open fine if the file is left in place. As soon as the file is moved to another location, the file will fail to open.

The only fix we have is to rename the file. For example, by add a hyphen onto the end of the file name. That or we have to unmount the storage share and remount for the file to work again.

Zip files are also problematic with. Using the Mac Archive tool to unzip we are seeing files failing to open. Using Keka is a workaround as Keka must be updating Finder properly with file information.

We have a mix of PC's and Mac's - Our M1 Mac Studio's are the only systems affected by this bug. Our PC system has no problem opening up files that the Mac will refuse to launch.

Select the file and press [return] four times to enter and exit rename mode.

Don't know how I found it, but it's better than actually renaming.

etresoft wrote:

sparrow__hawk wrote:

If this were affecting all Mac users who access shared network volumes, then surely Apple would confirm the issue and be working on it?

It is extraordinarily rare for Apple to ever comment on such problems. There is no way to tell if Apple is "working on it". If they are, I can absolutely guarantee that any "fix" will arrive in some future update. Given that it is almost May, that likely means macOS 14.

Your comments suggest that you are expecting Apple to behave like typical enterprise vendors. That isn't going to happen. Apple has little interest in enterprise customers. I don't blame them. There's a lot of baggage there.

I recommend some other collaboration method. Personally, I don't think anyone should be using traditional network shares in the modern age of ransomware. Macs haven't had useable network shares for years. So while this issue doesn't surprise me, it does surprise me that people have been able to make it this far to begin with.

You are of course, utterly and unquestionably correct. We are moving to Egnyte, but it will take time so we still need the Windows file servers for the time being. Egnyte is great, but it's also had its share of issues, some caused by Apple's new File Provider framework. I like Egnyte and am trying to encourage my colleagues to adopt it as soon as possible. There is the small task of sorting through the 25TB of data the business has accumulated over the last 15 years first though. Trying to get people to throw stuff away can be very difficult sometimes! :-)

Hi lapster81,

It sounds like you've isolated and tested the issue pretty well. If all sharing settings are correct, Set up file sharing on Mac, reach out to Apple Support directly to report the issue and further assist.

Contact - Official Apple Support

Contact Apple for support and service - Apple Support

Cheers.

sparrow__hawk wrote:

If this were affecting all Mac users who access shared network volumes, then surely Apple would confirm the issue and be working on it?

It is extraordinarily rare for Apple to ever comment on such problems. There is no way to tell if Apple is "working on it". If they are, I can absolutely guarantee that any "fix" will arrive in some future update. Given that it is almost May, that likely means macOS 14.

Your comments suggest that you are expecting Apple to behave like typical enterprise vendors. That isn't going to happen. Apple has little interest in enterprise customers. I don't blame them. There's a lot of baggage there.

I recommend some other collaboration method. Personally, I don't think anyone should be using traditional network shares in the modern age of ransomware. Macs haven't had useable network shares for years. So while this issue doesn't surprise me, it does surprise me that people have been able to make it this far to begin with.

This is really a big issue to us. We also have slow transfer speeds, locked files and a few other problems. I bought an Apple Care Support Plan only for this case but i have waited over 2 weeks without any response to my order. I'm happy that i got some of the broken things fixed by disabeling file-IDs. I hope, Apple will give us a solution to this in the near feature. If not, we need to bring our 900 Devices to Windows....

Workaround Tipp: You can still open files by moving them into the Dock-Icon....

I really searched everywhere to get rid of this problem. I ran different tests and disabled Spotlight, .DS_Store files and malware protection but this behavior still exist. The only solution for a working text export from InDesign was to add the following informations to /etc/nsmb.conf

[default]
file_ids_off=yes

Unfortunately, this is no working solution for the topic here in this thread. I tried nearly every setting in the /etc/nsmb.conf file but without any success. Maybe you guys are running a machine where you can make changes like this:

https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X

I found this information on the NetApp Website, which is also very interesting.

https://kb.netapp.com/onprem/ontap/da/NAS/Ventura_MAC_OS_clients_experience_file_access_anomalies

If this were affecting all Mac users who access shared network volumes, then surely Apple would confirm the issue and be working on it? So if it only affects a small number of users, the what are the common factors? Are we all using a specific combination of software for example? I've tested Windows 2012 and 2016 here, with the same results. We run Sophos AV as well.

We have Acronis Connect running on our Windows server and this issue also affects users when connected using AFP.

Un fortunately I have a perfectly running Mac but which cannot upgrade to Ventura: I am on Monterey and experience the very same issue described in this thread when moving files mounted from my Sinology NAS using SMB.

So the Ventura fix does not help.