W i was born as an independent project and as such versions 7.04 and 7.10 were unofficial releases. Since 8.04 the code has been merged within untu and since 8.04 alpha 5, W i can also be found in the untu Live CD.
The goal of the project is to assist a Windows user unacquainted with Linux in trying untu without risking any loss of information due to disk formatting or partitioning. W i can also uninstall untu from within Windows.
It is not a virtual machine, but rather, it creates a stand-alone installation within a loopmounted device, also known as a disk image, like Topologilinux does. It is not a Linux distribution of its own, but rather an installer for untu.
While W i does not install untu directly to its own partition (which the developers consider a feature) this can also be accomplished by using LVPM, the Loopmounted Virtual Partition Manager, to transfer the W i-generated untu installation to a dedicated real partition, including a bootable USB keydrive. The advantage of this setup is that users can test the operating system and install the drivers before they install it to a dedicated partition (and avoid booting and functioning risks).
W i adds an entry to the Windows boot menu which allows the user to run Linux. untu is installed within a file in the Windows file system (c:\ untu\disks\root.disk), as opposed to being installed within its own partition. This file is seen by Linux as a real hard disk.  W i also creates a swap file in the Windows file system (c:\ untu\disks\swap.disk), in addition to the memory of the host machine. This file is seen by untu as additional RAM.
Users can select the desktop environment within W i. But, because each desktop environment is also available as an application package, it is recommended that users install untu (default option) and from there install the other desktop environments. When users log in, they can choose the desktop environment to use.
The lead developers are Agostino Russo, Geza Kovacs, Oliver Mattos and Ecology2007. The main development occurs at Launchpad and is led by the Lupin Team (Lupin is the loop-installer, handles everything that happens after reboot)  through the original untu blueprint page  and the new W i, L i, Lupin, and LVPM project pages.
The idea for W i was drafted by Agostino Russo taking inspiration from Topologilinux, which provided a loopmounted installation, and Instlux, that provided a simple Windows frontend. The idea was to merge the two concepts having a windows installer that would loopmount an image of untu. Geza Kovacs later refined the spec and provided the first prototypes to show that the concept was sound. Oliver Mattos wrote the original user interface in NSIS.
Agostino Russo then refined the loop-installation concept, moving from a simple loopmounted pre-made image file, to an image created on the fly using a dynamically patched version of the Debian installer, thus providing an experience which was closer to a real installation while addressing several other issues of the early prototypes. Lupin project was thus born and Agostino Russo wrote and implemented most of its code with some contributions from Geza Kovacs.
Later on Agostino Russo and Ecology2007 redesigned and rewrote the Windows front-end, which is what people see today. Hampus Wessman contributed the new downloader and the translation scripts. Bean123 and Tinybit also helped to debug and fix bootloader issues. L i and LVPM were s sequently created by Geza Kovacs.
The project has inspired the creation of other Windows-based Linux installers, such as Win32-loader.