Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

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

Since updating to Ventura 13.1, at random times, when I double-click on a file to open it, I get a prompt that the file can't be found. If I click OK then double-click the file again, it opens as it should. It happens randomly to files of all types. I have never created aliases to any of these files and they are stored locally on a desktop folder. This has never happened before 13.1. Any ideas?


iMac 2020 3.6 GHz 10-Core Intel Core i9

AMD Radeon Pro 5700 XT 16 Gb


131 replies

Give this a try: boot into Safe Mode according to How to use safe mode on your Mac and test to see if the problem persists. Reboot normally and test again.


NOTE 1: Safe Mode boot can take up to 3 - 5 minutes as it's doing the following; 

• Verifies your startup disk and attempts to repair directory issues, if needed

• Loads only required kernel extensions (prevents 3rd party kernel/extensions from loading)

• Prevents Startup Items and Login Items from opening automatically

• Disables user-installed fonts 

• Deletes font caches, kernel cache, and other system cache files


NOTE 2: if you have a wireless keyboard with rechargeable batteries connect it with its charging cable before booting into Safe Mode. This makes it act as a wired keyboard as will insure a successful boot into Safe Mode.


I think I've found the way the bug works, and some clue about why it could happen.


If I create a new user, as Apple Support suggested me, everything works.

But with my current user, I cannot open some files when the current folder (a folder that existed before Ventura 13.1) has some regional character on it. I'm Spanish, so my folders have á, é, í, ó, ú, ñ, etc in their names. For example: "Descripción del proceso".


If I try to open a file inside a folder with those characters using double click, the app won't open them.

BUT if I rename that folder even using the same characters, IT WORKS. I mean, the previous name was "Descripción del proceso". If I rename the folder replacing the "ó" with another "ó" (same character, so the folder still is named "Descripción del proceso"), now it works!


It would seem that Ventura can't recognize UNICODE characters (or something similar) that where typed before Ventura 13.1 (or Ventura 13, because I suffered errors opening files before). But if I type the characters again, Ventura transforms it to a coding that it can understand.


I've written this to @AppleSupport on Twitter, so I hope they finally acknowledge the bug, because it's a really big problem. As you can imagine, I have tons of files and folders with those regional characters that worked before Ventura, and I can't rewrite all of them.


I have by no means made a thorough test about this, so surely there's more I've missed, but I hope this can be useful to someone (and to someone with more technical knowledge)

It's almost 100% certainly a Finder bug. Try just restarting the Finder after you move, create or rename a file/folder. The quickest way is to option-click on the Finder icon in the Dock and select 'Relaunch'. Let's just hope that Apple sort this annoying bug out soon as it's become an embarrassment for their latest OS.

I also has this problem, but it has become even worse after the last update (13.3.1). Now when I try to open some files (with a long path) they won't open. For example, opening pdfs with Preview or doc files with Libreoffice.

If I move the files to the Documents folder and they have long names, they won't open. If I rename it to a short name (test.pptx, por example), it will open. Also, if I open the files from the app itself (File - Open - etc) they will open.

Also, when using the sidebar shortcuts it gives me an error.

In 13.3, sometimes it just gave me an error when I clicked on a file, but on the second click it worked. And now, this.

So it seems indeed a Finder problem, and a really big problema that makes the OS quite hard to use. I wonder how Apple testers didn't notice this HUGE bug. Hoping they solve it really soon.

Troyjack,


I have the same Mac as you and the same issue. None of the trouble shooting repairs below help. However, if I drag the non-opening file to the desktop, then drag it back to its original location, the problem is fixed. Really seems like an OS bug to me.

I found a couple of useful suggestion on a thread on MacRumors.


1) Remove remnants of uninstalled apps in LaunchAgents and LaunchDemons. Please note this is in the Library directly in the root directory of your disk (not the user Library, but you might want to check there too).

https://forums.macrumors.com/threads/updated-to-13-1-and-now-file-cant-be-found.2373951/post-31917372

2) Run Onyx with these settings:

https://forums.macrumors.com/threads/updated-to-13-1-and-now-file-cant-be-found.2373951/post-31920767


Did it last night. A few hours of use and seems to be gone... for now. :-)


Hi Original Gazza,


I just tried most of the things listed here, including restarting my very nice M1 iMac with Ventura 13.2.1, and nothing did remedy the situation.


Then I remembered that in old-old MacOS versions, there was sometimes a need to rebuild the desktop. In Ventura it should be equivalent to "Rebuilding the Launch Services Database." I have not tried that yet.


But being lazy, I just moved the whole folder with documents to my user folder on the computer and back again (out/in of the iCloud domain). That worked!!! Now clicking works. I guess the movement makes the computer refresh the location information.


From anywhere to like this location: Macintosh/Users/JohnDoe/Any folder - and then back again.


Ive just tried the following on request of apple support and I cannot now recreate the problem.


Rebuild the Spotlight index on your Mac - Apple Support


I did this with the download folder which is where I originally saw the problem.


Does this fix it for anyone else?

Yeah. It was just a sighs. I know how this works @ Apple side (I'm doing something similar for 20+ years). :D


IMHO it's xattr / Gatekeeper issue. Maybe that part storing 'source' of the file because I'm 'seeing' it only on files downloaded via FTP (python script, lftp) and here is 'the source' unknown. It looks like Finder's trying to open locked/not-updated/not-assigned-yet inode...

As far as I remember when I moved them onto network drive (not afp but something without xattr support) and then moved them back - the problem disappear.


Conclusion:

It's deeper than we expected, I hope not inside AFPS core, and someone with real experience will have to fix it. I'm just wondering how long is this issue there as I've noticed it in Mojave but without alert window (1st double-click failed). It should be hi-prio tho...

MBP13M1 - v13.2 resolved this issue.

About Monterey... Now it make sense as I was always like 'did i double-clicked or not'... Seems the bug was also there but alert message was added later... :D


Just for the record... Today I've updated to 13.2.1 and it's gone (so far).

So with me this did not go away, certainly with the already double clicked files then it did. But as soon as they are moved again or renamed it came back.


Even on a new vanilla system, or save boot with no extra stuff installed: it will happen.


I have reproduced it with a support staff long and detailed. it occurs 100% always if you try this example:

  1. create three screenshots.
  2. mark these 3 pictures, right mouse button, new folder with selection
  3. then rename the newly created folder, to "project X" or "images" or what ever
  4. Go into the folder on your desktop and try to open the files.

You will get this pop up with can't be found for every single file at the first time I you double click.


I have recorded this with support and Apple Capture Data app now and hopefully will get information soon what the problem is.

Anyway, I also went to an Apple Store and was able to reproduce it there on every computer with 13.2.1 that I could use (Macbook pro, iMac, Mac Studio). Even the employee looks surprised.


It seems to be somehow only people who need the Macs for surfing or watching videos and no longer for real work with a lot of files and data organization :-P

Anyway, the popup annoys me dozens of times a day and I seriously wonder why no one internally at Apple notices.


Do they not work with files and Folders and move them sometimes, or rename them sometimes?


Anyway, I'm glad that it also affects all M1/M2 machines I could test and not just Intel old-timers like me. Hope this gets fixed soon. Last time I found a Bug in Quicklook with the huge red areas poping up, if you use an AMD card, and it took apple 1,5 years to correct it(Big Sur and Monterey affected, and often to see if you turn off transparency in accessibility settings). really hoping this is not taking so long.

I've noticed this happening consistently when connecting to SMB shares (many different server platforms including Windows Server, Linux, macOS, assorted NAS hardware). Doesn't happen when connecting via AFP - only SMB.


Further, it's not restricted to one computer. I'm an ACN and this I can replicate the issue on literally hundred of Macs of assorted types across a couple dozen client sites, including on brand new machines right out of the box with just the stock applications on them. No additional applications, no weird kexts, no third party utilities, no migrated data. Take the iMac out of the packaging, plug it in, make a user, connect to an SMB server, open a file, move that file, try to open the file again. Boom. The error appears.


The only thing that I've found effective (other than quitting the Finder/changing a file tag/dragging the file over the application icon in the dock/a bunch of other ugly workarounds) is to disable SIP on the client machine. That seems to improve matters some. It doesn't completely fix the issue, but it often reduces the incidence of the error.

This has been here since Mojave release. It's an APFS issue that apple has been aware of. in Mojave you do not get an error message when this happens, you simply re-double-click the file and it opens. Since newer os releases we now have an error message displayed (since apple became aware in Mojave). This is most likely not fixable in the immediate future as I'm sure that mach kernel is also part of the issue and will need reworking once the file system is updated/fixed, they would have already if this was an easy fix. After I spoke with a system admin at apple support they basically said its something that shouldn't be happening and that it must be MY machine with something wrong with it. Obviously this isn't the case. Try changing file attributes also, if you open a jpeg or similar image in text edit, then change back to preview, it will open all images in text edit, even after resetting the file attribute. This means it's the filesystem, plain and simple. APFS has always been problematic. I also think it's worth mentioning it has nothing to do with sharing, network drives, or anything disk/network related, although it will be more prevalent with the amount of caching going on. Also, when using terminal to reload finder, the problem looks like it may be resolved, but it isn't. All this does is start the finder's caching process over from where it left off, which recreates the problem shortly after. At first I thought it was iCloud trying to sync and cache on both ends while working with the file live, this isn't the case since turning all of iCloud off, starting with a fresh system install with nothing linked to accounts the problem happens almost immediately while working with graphic files of any kind.

Happens to me also. I think it might be Google Drive related. It also seems to align with issues I'm having deleting files from the TRASH where the delete will take a VERY VERY long time. If I "quit" the Google Drive app, the delete issue goes away, and I'm guessing the "Can't be Found" error might as well.

13.4 did fix this bug for me !!!! YEAHH! :-)

yes, but i did a clean install of monterey (boot from a usb drive, need to set recovery security to allow external drives) and had to reinstall all software. My Data was on a external backup. So make sure you don't lose anything. No Problems so far on my Mac Pro. But it was just so annoying that I decided to go this way. Now I look first that I get my work done before I update anything again.

Have been using Ventura 13.2 for three days, and tried to replicate the error, but no problem at all. All working fine. 👍


FYI, this is on a MacBook Pro 2018 with Intel i5. I was only getting the error message on Dropbox folders fully synced locally (i.e. available offline on Finder), when trying to open files that had been moved/changed/renamed. Opening the same file a second time didn't give the error message.


Before the upgrade to Ventura 13.2 I also reindexed the entire SSD on Spotlight (I was also having problems searching within a folder in Finder). That and a restart might help. And maybe a pass with Onyx to check for disk/indexation errors wouldn't hurt.


My two cents.

opt+cmd+esc to bring up 'Force Quit Applications', select 'Finder' and click on 'Relaunch'. So that's three keystrokes compared with typing 'kill Finder' and the Return key, which is 11. Alternatively, wait until Apple fix the bug. 😏

For what it's worth... simply duplicating the file and opening the duplicate solves the problem for me. PITA mind you, but i dupicate the file, delete the original, remove "copy" from the duped file and away I go.

I also got my feedback from Apple support a week ago about the Problem and the problem probably didn't have enough people for it to be high priority and the support ticket was just closed without solution/resolution.


So, take your time and make an Apple support request, there please show that moving folders or renaming them often creates this error and file won't open at the first try. Also a screen video as proof, so that the Apple people see it every time. Maybe then enough support requests come together, so that they fix it. In 13.3 they did not fixed it.


super annoying error and mega embarrassing that the bug is also not taken seriously and that of Apple itself probably no one perceives. Pretty frustrating this iPhone company that leaves mac users in the rain.


i have made some short videos of them and share them here if not blocked (apple also has this stuff):


https://youtu.be/G6FDluPzHts

https://youtu.be/Scg9UvwgAzM

https://youtu.be/OdTw66aNA1o

https://youtu.be/64LUBUuSEjY

https://youtu.be/tOAowsLw1bI

I have Dropbox as well and wondered if it was the issue. However, the issue occurs inside of Dropbox nested folders, and on my desktop. The wrench here is that dropbox is backing up my Desktop. Perhaps I need to turn that off to try to isolate the problem further.

Hi

Seems that unmounting SMB, and disabling (re-enabling) file sharing fixes the trouble

Easier than that. Option-right click on Finder and select Relaunch.

It's clearly in the Finder, since restarting the Finder fixes it (for me and many other people here).

I can report back that on updating to 13.3 this problem MIGHT have gone away.

I tried opening a number of files that would normally give me that error and I had no problem.

Maybe it's fixed?


Hey guys,


I haven't noticed this issue again in the last 1 or 2 months. Very glad it's fixed.


I'm on Ventura 13.4.1.


Is it gone for everyone?



Same here. Hasn’t happened since updating to 13.4.1.

Thanks for your post, troyjack. The exact same thing is going on here, Mac Studio, Ventura 13.1.

It is becoming increasingly annoying. One thing I also noticed was that right-clicking and selecting "Open" consistently worked on the first try (I tested this with numerous files, but maybe not enough?). Nevertheless, this is something I wish Apple would address sooner than later. It is unfortunate that double-clicking is not a reliable way to open files; quite annoying. I much prefer to double-click instead of the right-click method. I think most, if not all, Ventura users would agree. Anyway, has anybody heard anything from Apple about this issue?

Thanks.

I have the problem, too. If I rename the file, I can open it. Clearly some sort of caching issue in macOS.


I saw the problem first in Monterey, but there was no error message from Finder. There, it would just silently ignore the file. The renaming trick worked fine there, too.


Btw, I'm on 13.2.

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.

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.

For me this is happening on a new Mac that came with Ventura 13.2.1. If I move a folder to another location, none of the moved files within that folder can be opened. I have to cmd+z, make a new folder with the same name in the target location, and then move the files. After that they can be opened. The "file not found" error also occurs at random times when opening a file in the finder. In that case, double clicking the same file a second time will open it. This all occurs on the local disk. I wonder if this is a Finder bug or an APFS bug. I also wonder if file corruption is a possibility. I'll reiterate that this is a brand new Mac.


MBP 16.2 SG/12C CPU/38C GPU/64GB/4TB/KB-US

MacOS 13.2.1




Hi


So what's going on here? Stuff like iCloud cache the file off somewhere. File shares take a while to respond. The Finder has a timeout somewhere in it that simply isn't right when running on an M1 or M2 based Mac.


What should happen:


I ask for a file

Finder goes to look for it

iCloud or whatever heads off to say "got it"

Finder comes back after that reply and says "here it is"


What does happen:


I ask for a file

Finder goes to look for it (the first time)

iCloud or whatever goes off ...

Finder decides to kill the process ( = Timeout ) and reports "nope, not there"


In some cases the iCloud process. isn't fully killed and the next time you click, it's there.

In other (= most) cases the process is killed fast enough that it's not going to get there


Is that the full story? Of course not. It's about 95% of the story. You can copy / move the files just fine. They *are* in existence. Finder can get at them. It simply is a bug in the "let's open a file" code. It quits too soon.


Does any of that help anybody? Nope, not in any way at all. The *only* thing that will help is an Apple dev guy actually diving into this. The previous comment about opening a case with Apple *is* the only way to stop seeing this "fine stuff" ( I could use a different term ...... ).


Bob


Or just relaunch Finder, which requires fewer keystrokes.

I have found that if you click on the file name, these files open. If you click on the icon, they don't. Anyone know of a fix? This all started when I upgraded to Ventura.

I've just done that. A very helpful agent reported that the problem is currently under investigation by the Apple Engineering team and they hope to have fix in the next release or two of Ventura.

I'm seeing similar behavior with Ventura 13.1 when opening files on an SMB server. A file can be opened, but if you close that file and move it to a different directory/subdirectory then the "(Filename) can't be found" message appears.

Hmm interesting, good work on the solid recreation instructions.


Yes it did come back on number 3 of the 3 files I put in a new folder then renamed.


I hadn't had this problem since I originally posted but it looks like it still there.


However soon after it goes away, I really do wonder if its related to background indexing and when its caught up the problem is gone.


This is a new M2 Pro Mac mini by the way. Doesn't happen on my i7 iMac but that is stuck on Catalina hence the upgrade.

As I have said before, for me, simply duplicating the file, delete the original, rename the copy if you need to, and that fixes the file for me. Of course, next time I try to open it, I *MIGHT* get the same error, but it does work over and over to do that. It's just a PITA.


Don't ya'll remember the one version Apple put out where you couldn't simply change a capital letter in a file name to a lowercase one?? That drove me nuts, but Apple fixed that one quickly. It's too bad this isn't fixed.


There's also another possible finder error that I see, specifically when using InDesign. When I go to save my files, one of the two, (APPLE or ADOBE) leaves a space between the file name and the extension, so I get file names like MyFile .eps instead of MyFile.eps


Weirdness.


Quite honestly, I'm not seeing a sigificant improvement in my network access times when saving files.


I still think that Apple is catering to Mom and Dad and not production minded people like me.

FWIT


David

Any above solution is not acceptable for me. Reopening Finder disconnects me from afp/smb shares, rebuilding cache, OnyX, First Aid over whole drive/AFPS container, etc... None of them works. It's back couple of minutes after.

The funny part is that this bug is in macOS since Monterey, Big Sur or even Catalina (2nd double click works). They just added alert window now.

I'm now downloading Ventura 13.3... Crossing fingers...

I also am seeing the issue on Apple Silicon and have not seen it on Intel based Mac's. My *guess* (and it's only a guess) is that this is M1 / M2 chip related. Is it in the code conversion from Intel to Arm code? Is it in the threading on the chip? There's no way to know from this side of things.


It is related to "lag" in file sharing to some degree. It applies to iCloud just as much as any of the rest. It is not 100% clear that sharing *must* be involved. Pretty much everybody turns on iCloud for their files these days ...

Definitely not M2 related. Happens consistently on my intel iMac. Also, no iCloud usage here, as my agency does not allow us to store files on clouds.


What's also strange, is that I've noticed that some posters here have the issue with files on their SMB servers. Here, we work on files locally, and back up to SMB, but the issue only happens when trying to open a local file. Never had any issue opening files on our SMB.

What also works as a fix: Just leave the computer for a couple minutes / hours / overnight and come back. The problem is gone on that specific file.


Does that work every single time? Nope. It does work pretty often. Best guess is 4 out of 5 times. Thats enough to make this tough to confirm any fix.



It's a Kernel problem on all Macs with any version of Ventura, like the above said, this has been there since Mojave but did not throw Kernel exceptions or an error window, and yes it should have been addressed back then, it's been a known problem. The update does not fix this and I can see bad addresses and kernel errors in console when this happens. Wonder what's taking them so long to fix it. I mean... it's kind of a huge issue for any OS to have.


Aso, turning off SIP won't help, it still happens. Doesn't matter where the file came from in my case, happens to anything I open other than an App, even unsigned apps don't have this issue. I believe this problem is also related to the preview app crashing when saving.

I updated to 13.3.1 this morning and the problem is still there.

I use InDesign files that have this problem. If I drag the file to the APP in the dock, it opens it up correctly.

Also if I duplicate the file the duplicate works.


also in 13.3.1 a new feature has been added... my icon for shortcuts to server connection are blank icons. They don't look like a folder anymore.

Could be. I have also installed Google Drive, but I haven't tried to stop it.

After changing the unicode characters in files and folders, the problem disappeared, but sometimes it shows me the "file can't be found" error (and if I click twice it opens the file though).

I just updated to 13.2. Going to give it a few days and see if it made a difference on the Intel iMac.

It comes back every time a file is moved. The Finder is clearly caching something that isn't invalidated when the move happens. This is probably a 1-line fix, but Apple does not give af.

I agree... it happens less... but still happens.

Duplicating the file and deleting the original makes it better.. but what a PITA

Nope. It's not about the M1/M2 chips. I am on an Intel-based MacBook Pro (2018) and this also happens.

Definitely not M2 related. Happens consistently on my intel iMac. Ventura is the first time I've ever experienced this in over 25 years of using a Mac.

I have the exact same problem. But this was after I did boot in safe mode for another issue.


I've had this new MacBook Pro for 4 days.


Just upgraded to Ventura 13.1 yesterday.


I did a repair disk, and restart. It seemed to go away after that, but of course it came back. This is ridiculous.

Yup. Must be an OS issue. Unfortunately, I'm not sure the solution will be coming quickly. Possibly with the next OS update? I hope Apple is listening. I did find similar posts as far back as Big Sur. Please Apple.

I'm glad that seemed to work, but it's crazy that one should have to go through that. If mine keeps doing this I guess I'll have to call again or do what you did but I wish they would just resolve this.

Have any of you lost any file with this Mac OS bug? I have updated my Mac to Ventura 13.2 and I have noticed some pdfs were totally corrupted. Fortunately I had a copy of them. But it seems to me this bug is actually damaging files too. Its a nightmare to think Mac Os could randomly damage 180 thousand files and you will find out in what, years to come?

Hi


In Mac OS Ventura 13.1 we all also facing the same issue, file are not shown properly in SMB server. I attached video file for your reference.


I hope Apple will look this issue immediately.


Video link

https://we.tl/t-f9MzPWTZCa


UPDATE: Nope, it's still there. I also noticed something else, when I try to ⌘ + ⇧ + 4 (screenshot) and drop PNG file into webmail (OWA) - the file is suddenly without extension (so it is 'Screenshot 2023-02-14 at 14.18.43' instead of 'Screenshot 2023-02-14 at 14.18.43.png'). That's another weird finder's behavior and maybe it's linked with issue described in this thread...

Oh dear this has just started happening for me on a 1 week old Mac mini just after moving some files to a subfolder. Now every first attempt to open a file gets the not found message and then the second attempt works. Very annoying was hoping there would be a simple fix but it looks like I'm not alone.

yeah it was the first time I saw it today after moving a large number of files to a sub folder.


I guessed it was some sort of caching issue but couldn't fix it. Rebooted to be sure. Still there, not a great introduction to Ventura...

Still happening on 13.2.1 😡


< 00004000 p>I have noticed it tends to happen on files stored on external disks, so it might be a Finder issue, e.g. not updating the local directory cache after files are moved or renamed.

its always in the local downloads folder for me and has come back after 2 different reboots for other reasons, very annoying bug hope it gets fixed soon.


I find that trying again immediately finds the file (CMD+Down shortcut to open file twice)

Thank you. Unfortunately it persists after a safe boot. I should have mentioned I've tried the following: safe boot, disk first aid and SMC reset. I plan to zap the NVRAM shortly.

I occasionally have the same error in cleanly installed 13.1 AFAIK with no suspicious 3rd party add-ons and PRAM, SMC, safe-boot and Disk First Aid done.

Same problem here. My solution is to unmount the SMB share and mount it again. But this problem should be solved by apple. Actually strange that Apple always struggles with SMB mounts.

I have the same problem, apparently only on the local Dropbox folder.

Agreed. It only happens for me with local files on my intel iMac. I haven't noticed the issue with any files stored on the company's SMB server.

That worked great GJNA - thanks! :)

I definitely agree... Glad to know I'm not the only one with the issue. Hopefully Apple will take notice and correct the issue.

Agree. Thanks!

Did downgrading to Monterey solve the issue for you?

Yep, same for me! Seems to be all sorted out!

I've updated to Ventura 13.2 and it still happens.

Sorry mate. I thought it disappeared but after a while it's still there... So not fixed yet...

Nope... Still happening on Intel iMac.

Same here, it still happens. Reboots don't help. Clearing out caches doesn't help.

I have the same issue in Ventura 13.2 on MacBook Air, it is very annoying though

Me too but then when I click again it opens the files. Very annoying


Yup mine is the same, opens on the second try fine, indeed its very annoying

Oh, well. The error message is back for me... 😵‍💫

Same issue here. Happened as soon as I updated to Ventura on an M1 MBP. Very annoying. Hopefully Apple fixes this.

Same problem here.

Ventura 13.2

MacBook Pro

Apple M1 Pro

Same here.

MBA M1 on Ventura 13.2

I didn't have the problem until I upgraded to 13.2.1.

Now I frequently have the problem double clicking a file in finder on the internal SSD.

For (1) I had two items and neither were old. Both current programs. Did (2). Problem remains.

You are right. Came back for me too

nice I'm sure my problem survived a reboot or came back pretty soon after.

Absolutely, what I meant was I've even rebooted and it came back.

Same here. MacBook Pro M1 Max with MacOS 13.2.1

Very annoying but at least the files open on the second try.

On the Finder icon in the Dock. Thanks!

I have the same issue. It started after upgrading my M1 iMac to Venture. Sad times :-(

I think its gone away for me, I wonder if its to do with the spotlight indexing and when that was finished it cleared up.


Anyone else had it just go away?

Does this bug damage the files though?

I have tried, as many others I presume, to rebuild launch services with Onyx, and the bug returns after a few minutes/hours

I tried rebuilding my Launch Services database using OnyX, but the bug was still present right after the reboot.

Seems so... :) Thank you for your confirmation. I tried to create new files, move them back and forth and no error alert so far.

it is NOT fixed....

I just ran into a file that doesn't open.


Yeah, it's back (files downloaded via FTP). Fukitol™ ...

Just updated to Ventura 13.3 (MacBook Pro M1 Pro)

Still happens at random times.

edit: didn't notice someone already gave this hint

The problem appeared for me on a new Mac mini and I don't use Dropbox.

I've noticed that this is the Toad's answer to almost everything I've come here for, without even investigating the issue.

how is it that apple does not see this in testing. do they only test there computers for surfing the web? and garage band

Yes, rebuilding the Spotlight index has been suggested and it’s been tried. The issue comes back after a while.

Have you tried moving files around afterwards? I suspect the problem will come back if it's a Finder bug.

Still happens on my iMac with macOS 13.3. But if I just re-try to open the file, it will open.

Just tried reindexing Spotlight (in case it was the missing action after Ventura 13.3), but the issue is still there.

Update to 13.3.1 finally arrived but fixing only important stuff like this:

  • Pushing hands emoji does not show skin tone variations

... so we have to wait ...

I am also still having this exact same problem, and getting really frustrating, has a fix still not been released?

Still getting this error - hoping Apple can fix it soon!

NO, IT DID NOT


It still happens under 13.2.1 😡

I wonder whether Apple will ignore this problem and hope that it will magically go away in MacOS 14?

I'm able to reproduce this problem after 13.3.1 update on a MacBook M1. Have been seeing it for some time previous.

Sorry Nitaka I got frustrated- It’s been going on for awhile & w no improvement

For me too!!!

It happends on macOS Sonoma 14.1 again!!! OMG it's anoyyning.