BUN got stuck in Windows when there's a mapped drive B: (and is inactive)

[robbyjo]

Description

I installed OpenCode Desktop for Windows v1.2.15. The GUI will get stuck at the initialization. It was not obvious until I invoked the opencode-cli.exe and revealed BUN was invoked from drive B. I had drive B mapped and it is disconnected. Once I unmapped drive B, the GUI works.

Plugins

N/A

OpenCode version

OpenCode Desktop for Windows v1.2.15

Steps to reproduce

1. Have a drive B mapped to a network drive that is currently inactive
2. Start OpenCode Desktop for Windows
3. Get stuck
   Work around: Unmap drive B so that BUN could work

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

cmd (actually it's the GUI)

[github-actions]

This issue might be a duplicate of an existing issue. Please check:

• EPERM: operation not permitted, open 'B:\~BUN\locales\en_US.json' #8441: Same root cause — Bun hardcodes or resolves paths to drive B: on Windows, causing EPERM errors when B: is a disconnected mapped network drive. Your issue describes the same underlying problem (Bun referencing B:\~BUN paths), just manifesting as a hang rather than an explicit error message.

[robbyjo]

Yes I think this is a duplicate of that issue. Apologies.