File "Can't be Found" prompts after Ventura 13.1

Just had this too on Ventura 13.2.1 on MacBookPro i7. Still investigating, but quick workaround [for me at least], do a:

file "filename"

and then double click on the document and it will open correctly... Strangely, what doesn't seem to work is something like:

foreach file (*)

foreach> file $file

foreach> end

Odd...

No! Is a bug somewhere in the file system.

Rebuilding the Launch Services Database should do the trick.

Unfortunately, there is no simple way to rebuild your Launch Services database, unless you have a - free - disk utility such as OnyX (or Maintenance) which includes this as a feature.

I am now updated all the way to 13.3 and have experienced the same "File cannot be found" message since my initial upgrade to Ventura.

At first I was thinking it was related to Dropbox, which I use with the client-side app which integrates directly into Finder. I also use the Dropbox Backup tool to backup my Documents, Downloads, user home folder and Desktop. But I dispelled that after reading the initial post on this thread.

I use Preview pretty much all day long for reading and managing PDFs. I wondered if it was a bug with Finder and Preview, thinking maybe there was something in the Preview meta-data or potentially some other issue at the ACL level.

However, now seeing that this thread has so many similar yet unrelated complaints it has become clear to me that this is a Finder issue. The first suggestion to reboot into Safe Mode was a good one, but the more I thought about it the more it made me realize that there is nothing different about the way that I am operating on my system going all the way back to High Sierra. I am using Dropbox, Preview, and basic productivity apps.

I also thought about whether it was an issue with folder nesting, because I manage a massive archive of team files and they are deeply nested based upon workflows. But the problem persists between 4-5 level deep nested folders and my desktop.

The only factor I have not closed the book on yet is that I am now working on a MacBook Pro with an M2 chip, my first Apple Silicon system. I have never experienced the issue of "File cannot be found" on any of my Intel Macs. However, that gets muddied quickly because this is the only Mac I have owned that supported MacOS 13. So I leave open that there is a slim chance it's related to the M2, but have no way to verify or deny.

So I go back to the one commonality in all of these posts on this thread, it's something in Ventura that is the issue.

yep moved them around into subfolder back and into a new one every time I try to open it works first time since the reindexing. I did think originally it was due to it not indexing fast enough but there's no real way to tell what its doing or where its up to.

Btw, a workaround for me is to open Terminal and do

killall Finder

Killing the Finder beats a reboot every time. :)

A quicker solution is to restart the Finder, which makes all files that have been created, moved or renamed accessible with a double-click.

My only solution is just to duplicate the file... delete the original

viola... all better.. other than you have to delete the original and then maybe delete "Copy" from the duplicated file name.

As @bobfromcarlisle says, we all need to open support tickets.

You do that here: https://getsupport.apple.com/

Even without Dropbox, do you have iCloud saving / sharing turned on? If so, you are into the same set of issues. It does happen with only iCloud involved.

Have you put in a ticket / complaint with Apple? As noted above, that's what needs to be done to get more attention paid to the issue on their end.

It's a Finder bug. Apple are aware of it and and are (allegedly) fixing it.

It's also worth reaching out to @AppleSupport if your on Twitter and quote the thread URL to try and get this prioritised. Public tweets copying them in usually get things moving.

I have the same problem, just local files, no network storage or anything attached then my monitor. these popups are annoying. i have done several reboots also in safe mode, disk repair from the recovery, nothing helped. So i was downgrading back to monterey and hope that more people here point out that there is a problem in this OS 13,1 version. Or it is again some special intel thing, and m1 works? Because of the focus from the developers just to do new stuff to run best on m1...

Mac Pro (2019)

3,3 GHz 12-Core Intel Xeon W | 96 GB RAM

2 MPX AMD Radeon Pro Vega II Duo 32 GB

A few days ago, I reluctantly updated my Intel iMac from Catalina to Ventura and encountered this issue today. Was attempting to open PDF files on my desktop and got the same message on every file I tried to open. After clicking ok and trying again files would open. While annoying, I can live with it until Apple fixes this obvious glitch in their new OS.