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 some random Unix utility on Windows 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. Adding the option
creates symbolic links, but this may not work if you don't have the
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.
busybox.exeprocesses from monitoring by Windows Defender and, if possible, disable Program Compatibility Assistant.
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-4487-gd239d2d52.exe). Release notes for this version are available.
The latest executable is 600,078 bytes in size. A checksum for this binary (and all others) is in the SHA256SUM file. This key has been used to generate the GPG signature file busybox.exe.sig. The same key is used to sign release tags in the Git source repository.
The 32-bit binary above will work on 64-bit systems but if you have a 64-bit version of Windows there's some advantage in using the 64-bit executable busybox64.exe. It's 642,560 bytes in size.
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.