Double-clicking documents in Finder sometimes fails to open them

etresoft wrote:

That's the big difference between macOS 27 and previous versions. Just because something works fine for you doesn't mean it works for anyone else.

Oh, I get that. This was one of my favorite Spotlight issues, though it was on Tahoe so Spotlight going wonky is not a distinguishing feature of Golden Gate.

Bugs happen, a small number of them affect me personally and that's annoying but I tend to find and use workarounds, if available. Most of the issues I see here that are bona fide bugs (which is the minority of them) don't affect me. macOS is complex and getting more so, and less spent on software testing in development means more profit. Apple is good at profit.

neuroanatomist wrote:

So when you double-tap on a file, sometimes that file fails to open? Or with one file selected, when you double-tap on a different file does the original/selected file open? Those are the topics in this thread, not filenames. Neither of them happen to me. Double-tapping a file opens it, as it always has.

I suppose you've got a good point there. As the OP said when they started this question, "Double-clicking documents in Finder always fails to open them".

Silly me, I read that "always" as "sometimes" for some reason. I must be getting old and seeing things, eh?

So that's why I speculated that "perhaps this change affects other functionality as well. Perhaps that second click (or first?) isn't really treated as a click." I assumed that if Apple is hacking around on low-level gestures to the point where a tap doesn't get registered as a click, but on only the second tap, and only on certain views, then that might explain why both the OP and I have noticed some strange, difficult-to-reproduce anomalies.

As with many thing in life, you have choices.

I do not. I'm a developer, so I must test my software on whatever buggy junk OS Apple throws at its users. And come April, I'll be required to use either 26 or 27 to submit apps. No choices there. But when it comes to my personal devices, not for writing apps for the Apple platform that I'm welded to for the duration, I am, indeed, looking at other choices.

Works fine for me.

That's the big difference between macOS 27 and previous versions. Just because something works fine for you doesn't mean it works for anyone else.

It probably wasn't your intent, but 39 years ago is when I bought my first Mac, a Macintosh SE/20.

That was when I first used a Mac, owned by the US government. It would be another 8 years before I could afford to buy one of my own. And I needed government help with that, too.

etresoft wrote:

Have you tested it?

Well I did say, "I can easily see this when".

So when you double-tap on a file, sometimes that file fails to open? Or with one file selected, when you double-tap on a different file does the original/selected file open? Those are the topics in this thread, not filenames. Neither of them happen to me. Double-tapping a file opens it, as it always has.

So using tap to click works fine in configurations other than those where it doesn't? Maybe it also works in List view when the current folder begins with a vowel? I don't know what "fully automatic" means. It's broken.

'Fully automatic' was in reference to my use of tap-to-click. I pretty much never click my trackpad, unless I am using a force click (or waking up my sleeping MBP in clamshell mode using the external trackpad).

So it's my fault for getting used to behaviours that have worked the same way for almost 40 years? I'm the one that needs to adapt? How about Apple stops with this AI nonsense and hires some competent software engineers and actual testers. Relying exclusively on users to do product testing after release is clearly not working.

Not suggesting that at all. It's a bug. Since it's a bug in macOS, only Apple can fix it. As with many thing in life, you have choices. You can choose to live with this bug, find a workaround (which is why I suggested one; Force Clicking on the filename is another), report it to Apple or not, or switch to Windows, Linux or ChromeOS.

PS: Normally I would just tap on Spotlight and enter 2026-1987, but that doesn't work anymore either, does it?

Works fine for me. I tapped on the Spotlight icon in the Menu Bar:

...and typed into the Spotlight search bar:

It probably wasn't your intent, but 39 years ago is when I bought my first Mac, a Macintosh SE/20.

neuroanatomist wrote:

Have you tested it?

Well I did say, "I can easily see this when".

Other than the second tap failing to trigger filename editing in List and Column view (it works in Icon view), I have not noticed any differences in double-tapping to open a file. I haven't had a desktop Mac in close to three decades (my last one was a Power Mac 6500), and I've been using tap-to-click since my first PowerBook so it's fully automatic.

So using tap to click works fine in configurations other than those where it doesn't? Maybe it also works in List view when the current folder begins with a vowel? I don't know what "fully automatic" means. It's broken.

I noticed the bug/failure of the second tap straight off, though. There's a quick workaround for that. Select the file with the first tap, then press the return key and type the new filename.

So it's my fault for getting used to behaviours that have worked the same way for almost 40 years? I'm the one that needs to adapt? How about Apple stops with this AI nonsense and hires some competent software engineers and actual testers. Relying exclusively on users to do product testing after release is clearly not working.

PS: Normally I would just tap on Spotlight and enter 2026-1987, but that doesn't work anymore either, does it?

etresoft wrote:

I can easily see this when renaming files in the Finder. The first tap is sufficient to select a file. But the second tap is not enough to trigger a rename. For that, I must click.

Have you tested it? Other than the second tap failing to trigger filename editing in List and Column view (it works in Icon view), I have not noticed any differences in double-tapping to open a file. I haven't had a desktop Mac in close to three decades (my last one was a Power Mac 6500), and I've been using tap-to-click since my first PowerBook so it's fully automatic.

I noticed the bug/failure of the second tap straight off, though. There's a quick workaround for that. Select the file with the first tap, then press the return key and type the new filename.

hwlngfntds wrote:

Same problem here as op, kros, brad. This new behavior came along with Golden Gate 27.2 update.

Are people really talking about "clicking" or "tapping"? One change I noticed in macOS 27.2 is that trackpad taps are not the same as clicks (i.e. pushing down on the track with with haptic feedback.)

I have System Settings > Trackpad > "Tap to click" enabled, but taps are no longer the same as clicks.

I can easily see this when renaming files in the Finder. The first tap is sufficient to select a file. But the second tap is not enough to trigger a rename. For that, I must click.

So perhaps this change affects other functionality as well. Perhaps that second click (or first?) isn't really treated as a click.

PS: I'm now refusing to use the "Golden Gate" marketing names. It's clear that the differences between OS versions can be so great that using the "Golden Gate" term alone can be confusing. Are they talking about 27.0.1, 27.2, or 27.3? They are all essentially distinct OS versions with distinct behaviours.

I'm new here, but why is neuroanatomist's reply pinned as helpful? It is in no way relevant to the bug.

The same reason clicks aren't working - AI. A long post, multiple links to Apple support articles, screenshots. neuroanatomist knows how to work the AI.

The troubleshooting steps are generic.

hwlngfntds wrote:

Same problem here as op, kros, brad.

OP: if it's not selected, then sometimes double-clicking opens it, but quite often it doesn't – especially if it's a document I haven't touched for a while

kros55: When I open the first file and then close it, the first file is still highlighted in the grey color. I click on second file to open it but the first file that remained highlighted in grey opens.

bradfrombracknell: If another file is already highlighted, double-clicking a different file opens the one that's already highlighted rather than the new one that's been double-clicked.

The OP is describing something different than the other two. Regardless, I cannot replicate either of them. I suggest starting with the suggestion by @tbirdvet and adjusting the double-click speed (System Settings > Accessibility > Pointer Control.

Same problem here as op, kros, brad. This new behavior came along with Golden Gate 27.2 update. I'm new here, but why is neuroanatomist's reply pinned as helpful? It is in no way relevant to the bug.

I find this interesting. Since I updated to 27.2 when I double click on a template in MS Office Word or Excel it will not open. Then after seeing the comment by Neuroanatomist on adjusting the double click speed under the accessibility menu it all now works. Not sure what this did as I have never touched that setting. It is odd that double clicking on anything else worked without issue so not sure why Word or Excel templates were the exception.

I have the same issue similar as Mr. bradfrombracknell described.

When I open the first file and then close it, the first file is still highlighted in the grey color. I click on second file to open it but the first file that remained highlighted in grey opens. If I click on the first file to change the selection color to blue, I then can click on the second file to open it. Yes, this problem is on Golden Gate V. 27.2.; appears to be a bug affecting window focus. I have this problem on my Mac mini M6 and on my MacbookPro M1. I tried everything suggested, cannot resolve the issue.

I'm having the same sort of issue. If another file is already highlighted, double-clicking a different file opens the one that's already highlighted rather than the new one that's been double-clicked. This didn't use to be a problem before the most recent update to Golden Gate. Hopefully, a version update will fix this glitch. It's happening both on my Mac Mini and MacBook Air. The only way around it seems to be to click the new file you want to open, wait a second or two, and then click it again. It's even harder to rename files on the desktop. Again, this never used to be a problem.

I am having the same problem. When I unzip something from a ZIP file, for example, then double click the unzipped file/folder, the first double click fails. I have to wait a sec, then the next double click attempt succeeds.

What you are describing is not normal behavior for macOS. Double-clicking on a file will open that file, regardless of how recently the enclosing folder was opened.

Have you rebooted your Mac? If not, that's the first step. If that does not help, then see if the problem is present when you boot in safe mode. That process performs some system cleanup and clears caches, and also disables 3rd party extensions that may cause problems.

Start up your Mac in safe mode - Apple Support

If that does not correct the issue, test in a new user account. A newly-created user account will have all settings at default, and if the issue does not occur in that new account then it provides guidance on what may need to be changed to correct the issue.

Add a user or group on Mac - Apple Support

Once the testing is complete, the new account can easily be deleted.

Delete a user or group on Mac – Apple Support

Those steps will help to isolate the problem.

It might help to download and run EtreCheck, written by a long-time forum member. The free version is fine. Post the full report using the Additional Text button. No personal information is revealed. 

I cannot replicate the behavior you describe. For example, here is a folder of RAW images from a trip in February 2025. I have not accessed that folder or any files in that folder since that time (I convert the RAW images to JPGs that go in the Photos app, then archive the RAW images).

When I open the folder and double-click on a file, the file opens in the designated app (in this case, DxO PhotoLab):

Given that I cannot replicate the issue you describe on macOS 27.0.1, it does not appear to be a bug in macOS. You can certainly still report it to Apple. Bugs can be reported to Apple here:

Feedback - macOS - Apple