#1130·pinokio

[Bug] Pinokio setup stuck on bun update (EBUSY) on Windows 10/11 even after clean reinstall

Author: EffeDEffeCreated Sep 17, 2026Updated Sep 17, 2026

Describe the bug

After downloading and installing the latest version of Pinokio (version [8.2.0]), on first launch the program asks to update some components, including bun. The bun update consistently fails with an EBUSY error, preventing Pinokio from starting correctly.

To Reproduce

Download the latest version of Pinokio for Windows from the official website or GitHub releases.

Install Pinokio.

Launch Pinokio for the first time.

The program starts and attempts to update its internal components.

The bun module update fails with the EBUSY error.

Expected behavior

Pinokio should complete updating its components and start correctly.

Actual behavior

The bun update stops with a "resource busy or locked" error. As a result, Pinokio cannot finish updating.

Error message (full traceback)

bash
npm warn cleanup Failed to remove some directories [
npm warn cleanup   [
npm warn cleanup     '\\\\?\\J:\\pinokio\\bin\\npm\\node_modules\\bun\\node_modules\\@oven\\bun-windows-x64',
npm warn cleanup     [Error: EBUSY: resource busy or locked, unlink 'J:\pinokio\bin\npm\node_modules\bun\node_modules\@oven\bun-windows-x64\bin\bun.exe'] {
npm warn cleanup       errno: -4082,
npm warn cleanup       code: 'EBUSY',
npm warn cleanup       syscall: 'unlink',
npm warn cleanup       path: 'J:\\pinokio\\bin\\npm\\node_modules\\bun\\node_modules\\@oven\\bun-windows-x64\\bin\\bun.exe'
npm warn cleanup     }
npm warn cleanup   ]
npm warn cleanup ]

System Information

OS: [Windows 11 Pro 25H2 and Windows 10 Pro 22H2]

Pinokio version: [8.2.0]

Node.js version: [v24.18.0]

npm version: [e.g. 11.16.0]

bun version: [1.3.11.0]

Hardware (Windows 11): [AMD Ryzen 7 7800X3D 8-Core Processor (4.20 GHz), 64GB RAM, SSD]

Hardware (Windows 10): [Intel I7 4790K, 32GB RAM, SSD]

Troubleshooting already attempted (without success)

Completely uninstalled Pinokio and reinstalled from scratch.

Restarted the PC after uninstallation.

Tried installing on a second PC with Windows 10.

Closed all bun.exe, node.exe, and npm.exe processes in Task Manager before attempting the update.

Ran Pinokio as administrator.

Ran npm cache clean --force before launching Pinokio.

Temporarily disabled Windows Defender real-time protection.

Additional context

The issue occurs identically on two different machines (Windows 11 and Windows 10), which suggests it is not specific to a single installation but a reproducible bug related to the Windows environment and how bun or its installer handles file locking.