BusyBox is a single binary that contains many common Unix tools. It's often found in embedded Linux systems like routers, in Android smartphones, in Linux containers and anywhere else it would be handy to have a compact set of Unix command line tools.
busybox-w32 is a port of BusyBox to the Microsoft Windows WIN32 API. It brings a subset of the functionality of BusyBox to Windows in a single self-contained native executable.
This version of BusyBox implements well over a hundred Unix-style commands. Some of the more significant are:
Other staples of Unix shell programming, such as
grep are also
available. Most of the commands have a
that displays a brief description and documents the available options.
If you need the full power of bash or the other GNU utilities busybox-w32 may not be what you want: Cygwin , Gow or UnxUtils may be more suitable. However, if you need to ship some shell scripts with your software or if you need to run a Unix build script busybox-w32 may be a compact alternative. The full executable is less than half the size of the Cygwin setup program!
You can run individual BusyBox commands from a Command Prompt window:
C:\Users\rmy>busybox uname -a Window_NT win81 6.2 9200 i686 MS/WindowsHowever, for the best experience I recommend using the BusyBox shell. This is configured to run BusyBox commands without having to link each of them into your path. Set up a shortcut on your desktop to run the shell using a command like this:
C:\path\to\busybox.exe sh -l
The last character there is a lowercase 'L' (for login).
Though I don't recommend it, it's possible to create links to each of the BusyBox applets using the command:
busybox --install C:\path\to\directory
Omitting the directory will result in the links being made in the same
directory as the busybox.exe executable you're running. The
--install option creates 'hard' links which are
available on NTFS filesystems but not FAT.
It's possible to remove the hard links to busybox.exe (including busybox.exe itself) by running:
busybox --uninstall C:\path\to\busybox
Since Microsoft Windows can't delete a running executable this only works if the 'busybox' in the command above is different from the binary you're trying to delete. The command:
busybox --uninstall -n C:\path\to\busybox
displays the links to the binary without deleting them.
If you plan on using BusyBox from the Windows command prompt you should note that the binaries provided here are configured with wildcard expansion disabled. This is the preferred option when the BusyBox shell is being used. There is a build-time setting to enable wildcard expansion but it isn't the default. More...
If you want to install a 32-bit build of BusyBox in a system
directory on a 64-bit Windows system you should put it in
C:\Windows\SysWOW64, which is the correct location for
32-bit binaries on 64-bit Windows.
Putting it in
C:\Windows\System32 will result in mysterious
From time to time binary builds and source tarballs will be made available. The latest version is always busybox.exe (currently this is an alias for busybox-w32-FRP-3025-gc01300361.exe). Release notes for this version are available.
The latest executable is 523,776 bytes in size. Its sha256sum is:
0ed3b19d57b3fc556e5879072be6b978cac04c56119d013223318537a0211f23This key has been used to generate the PGP signature file busybox.exe.sig.
A 64-bit binary, busybox64.exe, is also available. It's 599,040 bytes and its sha256sum is:
busybox-w32 includes the
man applet. A
ready-formatted man page for the current version can be downloaded
here. It's only provided
as an example: it just contains the help text for all the applets in
an inconvenient format.
It'll be picked up automatically if you position it relative to the
executable like so:
Recent and notable changes include:
suapplet is available. It runs a shell with elevated privileges ('as Administrator').
dpkgapplets are enabled by default.
iconv(which is not present in upstream BusyBox) has been added.
psapplet has been improved. It now displays the full command line of other running instances of BusyBox.
.share treated as executable scripts. If they don't start with a
#!line to specify an interpreter they're assumed to be shell scripts. As before, text files starting with a
#!line are considered to be executable scripts, even if they don't have an extension.
realpathapplet is enabled by default.
ttysizeapplet is enabled by default. It reports the size of the console window.
manapplet searches for man pages relative to the location of the BusyBox executable as well as on
timeoutapplet supports the same exit status as the coreutils version
wgetsupports the use of https URLs
.cmdare treated the same as other executables: they're highlighted in file listings, they're searched for on the path, and tab-completion in the shell works
/dev/zeroas input files
lnapplet is enabled by default, though it only supports hard links
The binaries are built using the MinGW-w64 toolchain on Fedora and are tested on Microsoft Windows 8.1 and 10. busybox-w32 also works on Windows XP and on ReactOS, though with reduced functionality.
Source is available in a Git repository which is mirrored on GitHub and Gitlab. It can also be obtained using (IPv6 only):
git clone git://git.frippery.org/busybox-w32
Bug reports can be submitted via GitHub, GitLab or by email to the address below.