Overview
This is a launcher rather than a full image, which is the reason it downloads in seconds and still installs a complete suite. It fetches the application payload directly from the official distribution and configures the install locally, so the files that land on the machine are the same ones a normal install would produce, without a multi-gigabyte archive sitting on the disk first.
The selection panel is where the work happens. Choose the release you want, pick 32-bit or 64-bit, select exactly which applications get installed, choose the interface and proofing languages, and set the update channel. Excluding the applications nobody uses turns a bloated suite into a lean one, and the choices are written into a configuration file that can be reused on the next machine.
It also handles the cleanup step that trips most people up. A removal routine clears leftover click to run components, store installs and half removed suites before the new install starts, which is the single most common cause of a setup that fails at the end and rolls itself back.
What it does well
Pick the applications
Install only Word, Excel and Outlook if that is all you need, and leave the rest of the suite off the machine entirely.
Release and channel choice
Choose the release line and the update channel at install time rather than accepting whatever the default happens to be.
Language selection
Interface and proofing languages selected up front, with additional packs addable from the same panel afterwards.
Cleanup routine
Removes leftover components, store versions and partial installs so setup does not fail on a dirty machine.
Reusable configuration
Every choice is written to a configuration file that can be carried to the next machine for an identical silent install.
Changes in this build
- Application selection list reorganised with search and per-application size figures.
- Cleanup routine extended to catch store based installs left by a system refresh.
- Added resume support so an interrupted download continues instead of restarting.
- Configuration export now includes the channel and language choices.
- Fixed a stall on connections that throttle long transfers.
What is in the package
- Online installer launcher, 32-bit and 64-bit
- Application and language selection panel
- Cleanup and removal routine
- Configuration export for silent reuse
- Readme covering the channel options
System requirements
| Processor | 1.6 GHz dual core or faster |
| Memory | 4 GB for 64-bit, 2 GB for 32-bit |
| Graphics | DirectX 9 capable with WDDM 2.0 driver |
| Storage | 12 GB free during install |
| Display | 1280 x 768 minimum |
| Network | A working connection, the payload is fetched at install time |
Installation
- Extract the launcher to a local folder.
- Run the cleanup routine first if any Office remains on the machine.
- Pick the release, architecture, applications and languages in the panel.
- Start the install and leave the machine connected until it completes.
- Open Word once and check the account panel before turning updates off.
Before you start
This one needs a connection, it is a launcher and not an offline image.
Mixing architectures across applications is not supported, choose one for the whole set.
Export the configuration before you close the panel if more than one machine is being set up.
Questions about this title
Why is the download so small?
It is a launcher. The application payload is fetched from source during install.
Can I install only some applications?
Yes, the selection panel controls exactly what lands on the machine.
Does it remove an older Office?
The cleanup routine handles that, and should be run before the install starts.
Can I reuse the same settings elsewhere?
Yes, export the configuration file and run it on the next machine.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (32-bit and 64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.