"Could not open page.js in the editor" error on VSCode Windows

Link to the code that reproduces this issue

https://github.com/YerayAlonso/nextjs-group-route-debug

To Reproduce

1. Open the workspace in VSCode, in Windows
2. Start the application in dev mode (pnpm dev)
3. Navigate to the /broken route. An error is thrown, as expected, but you can't navigate to the file in VSCode from the browser. And the terminal in VSCode says:

Could not open page.tsx in the editor.

When running on Windows, file names are checked against an access list to protect against remote code execution attacks. File names may consist only of alphanumeric characters (all languages), periods, dashes, slashes, and underscores.

Current vs. Expected behavior

I'd expect to be sent to VSCode with the file where the exception happened.
This is how it works if you try the /working route in the same test project.
The only difference is in the (group) route.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro     
  Available memory (MB): 16274
  Available CPU cores: 12     
Binaries:
  Node: 20.10.0
  npm: N/A
  Yarn: N/A
  pnpm: 8.15.3
Relevant Packages:
  next: 14.3.0-canary.54 // Latest available version is detected (14.3.0-canary.54).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.1.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Developer Experience

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response