Bun 1.4.4 Directory Open Requests Fail with EPERM Inside Windows Containers
Is it fixed? Not yet.
Ongoing since Nov 11, 12:43 UTC. First reported Nov 11, 12:43 UTC.
What happened
Bun 1.4.4 fails to perform directory operations and module resolution inside Windows process containers (MXC/PSEC) because directory opens request FILE_READ_EA and FILE_TRAVERSE permissions, resulting in EPERM errors under read-only grants.
What caused it?
Directory opens request FILE_READ_EA | FILE_TRAVERSE which causes STATUS_ACCESS_DENIED under read-only grants in Windows process containers (MXC/PSEC).
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on GitHub issue
Windows: directory opens request FILE_READ_EA | FILE_TRAVERSE, so readdir and module resolution fail with EPERM inside Windows process containers (MXC/PSEC)
Source
Evidence
1 report · 1 GitHubShow
- [1]GitHub First reportWindows: directory opens request FILE_READ_EA | FILE_TRAVERSE, so readdir and module resolution fail with EPERM inside Windows process containers (MXC/PSEC)(opens GitHub issue in a new tab)
What version of Bun is running? 1.4.4 (38afee6c84fcf48c0edb2466aa4b27d287a59c30), Windows 11 26100 x64 What is happening? Inside a Windows process container (Microsoft MXC processcontainer / BaseContainer, PSEC), every directory Bun opens under a read-only grant fails with STATUS_ACCESS_DENIED: fs.readdirSync / fs.promises.readdir / fs.opendirSync → EPERM: operation not permitted, scandir '<dir>' module resolution → error: Module not found '...\cli.ts' with note: Cannot read directory…
by apoc 0upvotes 0comments
FAQ
What happened in the Bun issue?
Bun 1.4.4 fails to perform directory operations and module resolution inside Windows process containers (MXC/PSEC) because directory opens request FILE_READ_EA and FILE_TRAVERSE permissions, resulting in EPERM errors under read-only grants.
What is affected by the Bun issue?
Bun (versions: 1.4.4). Also affected at the same time: Windows.
When did the Bun issue start and end?
It started Nov 11, 12:43 UTC and is still ongoing (7 d 16 h so far). This page updates as it develops.
How do I get alerts for Bun?
Subscribe to the Bun RSS feed for every new Bun incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Bun is down. Bun feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.