Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Smellmet

macrumors 6502
Original poster
Dec 15, 2012
374
137
Goole, UK
I've had this issue for a while now but it seems to have suddenly got worse with the latest update - if I rename a folder, the enclosing files, wether they are Indesign, pdfs, whatever won't open via double clicking. I have to either open via Finder and file > open or by dragging the file on to the respective app in the dock. Has anyone else experienced this issue?
 
  • Like
Reactions: Long Tran
How old is your mouse? My parents both need new mice as thiers refuse to double click.

It's 100% to do with the system, not the mouse. It only happens when I change the enclosing folder's name. Double clicking works absolutely fine in every other setting.
 
Double click won't open a folder or a file while the name is being edited. It will select words. It will always open the folder or file when the name is not being edited.
 
Double click won't open a folder or a file while the name is being edited. It will select words. It will always open the folder or file when the name is not being edited.
The OP (and others having the issue) aren't editing the file name at the time they have the issue.

With Monterey, some documents will inexplicably not open no matter how many times you double click the icon, hit File>Open, use Command+O, or right-click to open. The only way to open them is to drag them to the app icon on the Dock from where they are, or move the document to a completely different location before trying to open them.

I've run into this issue as well. Unlike Smellmet's statements above, I don't even change the enclosing folder's name. Files on the desktop that previously opened with a double click just minutes ago mysteriously and suddenly will not open unless I drag the document to the app icon in the Dock (or re-launching the Finder).
 
  • Like
Reactions: katbel and Smellmet
The OP (and others having the issue) aren't editing the file name at the time they have the issue.

With Monterey, some documents will inexplicably not open no matter how many times you double click the icon, hit File>Open, use Command+O, or right-click to open. The only way to open them is to drag them to the app icon on the Dock from where they are, or move the document to a completely different location before trying to open them.

I've run into this issue as well. Unlike Smellmet's statements above, I don't even change the enclosing folder's name. Files on the desktop that previously opened with a double click just minutes ago mysteriously and suddenly will not open unless I drag the document to the app icon in the Dock (or re-launching the Finder).

At last! Someone knows what I'm taking about!
 
  • Like
Reactions: Long Tran
Have you tried to reset the launch services database?

It used to be something like

lsregister -kill -r -domain local -domain system -domain user
 
and lsregister is actually

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister
 
I should mention that quitting the app of the document in question also fixes the problem... but that gets old real quick.

As a side note, the problem still exists (though not as frequently) in the latest version of Ventura (13.2.1) — and yes, it happens with a new Apple mouse as well as 3rd-party products.
 
  • Sad
Reactions: MrScratchHook
Ridiculous that this has even got through their 'quality control' let alone subsequent updates and now Ventura (and several updates to that) too?
 
  • Like
Reactions: Long Tran
I should mention that quitting the app of the document in question also fixes the problem... but that gets old real quick.

I've also just encountered this today when I renamed a folder of photoshop files - quitting photoshop didn't resolve it.
 
No it doesn't. Only way is file>open from within the app or drop the file onto the app's icon in the dock.
Are the folders and files with the problem sync'd to iCloud Drive or some other cloud storage?
 
As a side note, the problem still exists (though not as frequently) in the latest version of Ventura (13.2.1)

I've also just encountered this today when I renamed a folder of photoshop files

Hey. I created an account just to be able to respond. I have exactly the same problem and wanted to share my experiences. Not a solution, though. Unfortunately.

For me it began when I was still using Monterey. I even opened an issue with Apple support back then and got to a point where they logged on to my Mac and I demonstrated the issue. Some time later the lady got back to me and told me it was a known issue and Apple are already working on it. That was in April 2022.

I first noticed it when working with network shares. It really does not matter which protocol is used: SMB, AFP or even another Mac with file sharing activated both pose the same problem. I did some extensive testing back then because this issue was quickly getting annoying. It is not an issue of the type of mouse used. It is (or very much seems to be) a bug in finder. I know this because a restart of finder (option key + keeping finder icon clicked + choosing restart) resolves the issue. Until the next time a folder is renamed.

My test course is this:

1. Copy (Apple + C) a random file. Let's say a random jpeg.
2. Create an empty folder. Let's say "Test".
3. Paste the file into the folder.
4. Rename the folder. Let's say to "Test2".
5. Double click the file. Under Monterey, nothing would happen. The double click would just be ignored. Under Ventura I am getting the message "XYZ could not be found." I am translating this as my Mac is not set to English. The wording of the message may differ slightly.

By performing these steps I can reproduce the problem 100%.

I never even noticed this on my local SSD, presumably because I keep all my files on a NAS and rarely work with local files. Or maybe this problem was introduced to the local file system since Ventura. To which I only updated last week. In a recent forum post in a German forum (from January 2023) the OP there mentioned that this happened to him under Ventura on the local file system (SSD). So I got curious and did some testing. And I can reproduce the problem there as well.

However, compared to network shares I have noticed that the error message doesn't happen when I double click the file between steps 3 and 4. Then, after performing step 4, the file can still be opened. Again, that doesn't help on network shares. The files in the folder can no longer be double clicked after renaming the folder. No matter what.

It is worth mentioning that the files remain accessible all the time. So it is always possible to e.g. drag & drop the files to preview and they will open just fine. Same with copying the files. It is just the double click that is broken.
 
Last edited:
Hey. I created an account just to be able to respond. I have exactly the same problem and wanted to share my experiences. Not a solution, though. Unfortunately.

For me it began when I was still using Monterey. I even opened an issue with Apple support back then and got to a point where they logged on to my Mac and I demonstrated the issue. Some time later the lady got back to me and told me it was a known issue and Apple are already working on it. That was in April 2022.

I first noticed it when working with network shares. It really does not matter which protocol is used: SMB, AFP or even another Mac with file sharing activated both pose the same problem. I did some extensive testing back then because this issue was quickly getting annoying. It is not an issue of the type of mouse used. It is (or very much seems to be) a bug in finder. I know this because a restart of finder (option key + keeping finder icon clicked + choosing restart) resolves the issue. Until the next time a folder is renamed.

My test course is this:

1. Copy (Apple + C) a random file. Let's say a random jpeg.
2. Create an empty folder. Let's say "Test".
3. Paste the file into the folder.
4. Rename the folder. Let's say to "Test2".
5. Double click the file. Under Monterey, nothing would happen. The double click would just be ignored. Under Ventura I am getting the message "XYZ could not be found." I am translating this as my Mac is not set to English. The wording of the message may differ slightly.

By performing these steps I can reproduce the problem 100%.

I never even noticed this on my local SSD, presumably because I keep all my files on a NAS and rarely work with local files. Or maybe this problem was introduced to the local file system since Ventura. To which I only updated last week. In a recent forum post in a German forum (from January 2023) the OP there mentioned that this happened to him under Ventura on the local file system (SSD). So I got curious and did some testing. And I can reproduce the problem there as well.

However, compared to network shares I have noticed that the error message doesn't happen when I double click the file between steps 3 and 4. Then, after performing step 4, the file can still be opened. Again, that doesn't help on network shares. The files in the folder can no longer be double clicked after renaming the folder. No matter what.

It is worth mentioning that the files remain accessible all the time. So it is always possible to e.g. drag & drop the files to preview and they will open just fine. Same with copying the files. It is just the double click that is broken.

Excellent post. I duplicated your steps on my main SSD and get the "XYZ could not be found error" every time. For me, double clicking a second time fixes it and the file opens.
 
Why does that not make sense to you?
Sorry you can't understand or figure it out.

They are very old white mice. they tapped them so hard for years that they refused to work.
Well, if someone had not read your previous posts in this thread…
However, an apostrophe indicating a possessive would have helped.
Without that, your statement implies that you are the child of two old white mice. ;)
 
  • Like
Reactions: MacGizmo
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.