Bun install doesn't work in shared folder

[lumik0]

What version of Bun is running?

1.3.8+b64edcb49

What platform is your computer?

parallels desktop: Microsoft Windows NT 10.0.26100.0 x64 \ macOS Monterey

What steps can reproduce the bug?

1. Open the shared folder (network folder or location) where the project is located (there's package.json)
2. Open cmd and type bun i
3. It will say ENOENT: Bun could not find a file and the code that produces this error is missing a better error

What is the expected behavior?

It will create node_modules

What do you see instead?

ENOENT: Bun could not find a file and the code that produces this error is missing a better error

Additional information

im using parallels desktop to use bun because my proccessor doesnt support AVX2 on my mac

If i enter bun i in a regular folder (the same project) C:\ it will work

P.S. the shared folder does have read & write permissions

[github-actions]

Found 3 possible duplicate issues:

1. Bun fails to install/add packages to any project that is not on the C: drive #10169
2. Windows: not handling many UNC path cases #9071
3. Windows: bun link fails on mapped drives #19575

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[robobun]

This is the same bug tracked in #26192: on Windows, bun install in a project that lives on a volume where Bun cannot resolve the opened package.json back to a DOS path (an imdisk RAM disk there, a Parallels shared folder here) aborts with the same unhandled "ENOENT: Bun could not find a file, and the code that produces this error is missing a better error", while the identical project installs fine from a regular local drive. The failing realpath of the root package.json during install startup is common to both reports, so one fix closes both; it will be tracked in #26192.

Duplicate of #26192

Please add a 👍 or any extra details over there so it all stays in one place. If this is actually a different problem, say so here and we'll reopen.