BusyBox w32

BusyBox w32 is a "digital Swiss Army knife" for Windows.

  • Development
  • Tools & Utilities
BusyBox w32 is a "digital Swiss Army knife" for Windows. It packs dozens of small, useful computer tools into one tiny file. It allows you to perform various tasks—like searching, sorting, or moving files—using simple commands, making your computer more versatile without installing multiple heavy programmes.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

61/100 Good

Maintained
100last commit 18 days ago
Popular
59899 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
201 serious finding, tests

Based on 4 of 5 factors.

GitHub stars
899
Open issues
108
Last commit
2026-11-03
Activity
declining

Checked 18 days ago - source: GitHub (rmyorston/busybox-w32)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Create /dev with mdev first If you're installing BusyBox on a minimal Linux box, run the basic mdev init steps to mount proc/sysfs and seed /dev with device files. Without this, many programs can't find hardware like disks or serial ports. source
  • Use a writable /dev on flash systems On systems that boot from flash and need device files created at startup, make /dev a tmpfs (a tiny RAM-backed file system) and mount devpts under /dev/pts before mdev runs. This gives device files a place to appear and helps terminal-related apps work. source
  • Set device permissions in mdev.conf Lines in /etc/mdev.conf, such as hd[a-z][0-9]* 0:3 660, decide which users and groups can access detected devices. Wrong permissions can stop apps from using hardware or make disk devices too easy for unauthorized users to access. source
  • Precompiled binaries available Precompiled binaries for i686, x86_64, and aarch64 are available for download from the project page. No build step is required — run the single executable directly. source

Fetched 42 days ago - each note links to its source

Alternatives (3)

  • Cygwin - Cygwin is a Unix-like environment and command-line interface for Microsoft Windows.
  • MSYS2
  • busybox - BusyBox is a single compact executable that bundles many common UNIX command-line utilities into one tiny binary.

Checked 39 days ago - source: AlternativeTo

Common questions

Can BusyBox w32 be used as part of a portable Windows toolchain?

A Reddit thread discusses compact portable Windows toolchains that combine busybox-w32 with tools such as TCC, GCC, make, gdb, and vim.

How well does BusyBox w32 handle POSIX shell scripts?

A user reports that busybox-w32 works well with POSIX-compliant shell scripts, though the ln -s command had some issues.

Where can users report problems with the Windows port?

The GitHub repository has an Issues page for the WIN32 native port of BusyBox.

Answers sourced from github.com, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads