# Build an offline software bundle for air-gapped PCs

> Pack Chocolatey apps into a portable folder on a connected PC, then install them on a PC with no internet using Offline Deploy in S.A.K. Utility.

Source: https://sakutility.com/wiki/offline-software-bundle
Applies to: S.A.K. Utility (SAK), a free portable Windows toolkit
Updated: 2026-11-15

To install software on a PC with no internet, build a bundle with Offline Deploy in S.A.K. Utility: go to the **Application Management** tab, choose **App Installation**, then **Offline Deploy**. Add your apps, press **Build Offline Bundle** on a connected PC, copy the folder across, and press **Install from Bundle** on the other PC. This needs two PCs or one PC at two times, and administrator rights to install.

## When to use this

Use it for air-gapped PCs (ones deliberately kept off any network), for sites with slow connections, or to install the same set of apps on many PCs without downloading them each time.

## What you need

- A PC with internet to build on, with enough free disk space for all the installers. Building does not need administrator rights.
- For a Full Bundle or **Direct Download**: at least 1 GB free on the drive S.A.K. Utility runs from. It keeps its work files in its own folder there while it works, whichever folder the result goes to.
- On the target PC: a copy of S.A.K. Utility, the bundle folder, and administrator rights. Chocolatey does not need to be installed there, because S.A.K. Utility brings its own copy.

## Choose what to build

Set **Payload type:** before you build:

- **Full Bundle (installers packed in)** downloads every installer now and packs it in. Use this for a PC with no internet.
- **Thin Bundle (names only; downloaded at install)** records only the names and versions. It builds in moments, but the target PC needs internet to install. Use it to repeat the same setup on connected PCs.

**Direct Download** is different. It saves the plain `.exe` and `.msi` installers into a folder for you to run by hand. The result is not a bundle and **Install from Bundle** cannot use it.

## Build a bundle

1. Go to the **Application Management** tab and choose the **App Installation** sub-tab, then **Offline Deploy**.
2. Choose a list from **Preset:**, or type a name, press **Search**, click a result, and press **Add Selected**. Apps appear in **Packages to Deploy**.
3. Set **Payload type:**.
4. Press **Build Offline Bundle** and choose an empty folder.
5. Wait for the status bar to show the button's name and the counts, such as **Build Offline Bundle: 10 succeeded, 0 failed**. The line under the buttons, which you may need to scroll down to, reads `Complete` or `Incomplete` with the same counts. If a package failed, the run is `Incomplete`, and a warning box titled **Build Offline Bundle** names each failed package with the reason. **Cancel** stops the run. Turn on **Log** to see each package.

![The Offline Deploy sub-tab with the Kiosk / POS preset listed in Packages to Deploy, and the Payload type list, Air-gap install box, and Build Offline Bundle, Direct Download, and Install from Bundle buttons below](https://sakutility.com/screenshots/wiki/app_mgmt_offline_list.webp?v=c5f580c1c1)

*Packages ready to bundle*

![The Offline Deploy sub-tab after a build of the Kiosk / POS list, with the status bar reading Build Offline Bundle: 10 succeeded, 0 failed beside a full progress bar](https://sakutility.com/screenshots/wiki/app_mgmt_offline_built.webp?v=b3349e8199)

*A finished build: the counts are in the status bar*

The folder now holds `manifest.json` (the list of packages), `README.txt`, and, for a Full Bundle, a `packages` folder.

### If a build is refused or fails

If **Build Offline Bundle**, **Direct Download**, or **Install from Bundle** is refused or fails, a warning box titled with that button's name says why. The status bar says it too, after the button's name, often in a shorter form, and keeps it for a few seconds after you close the box. The progress bar goes away. A run you cancel opens no box.

If the drive S.A.K. Utility runs from is short of space, the box names that drive, and says how much is free and how much is needed, such as **Not enough free space for the work files: S.A.K.'s work folder is on V:, which has 304.0 MB free; at least 1.00 GB is needed. Free some space on V:, or run S.A.K. from a larger drive.** The status bar then reads **Build Offline Bundle: not enough free space on V:**.

![A warning box titled Build Offline Bundle saying there is not enough free space for the work files, naming drive V: with 304.0 MB free and at least 1.00 GB needed](https://sakutility.com/screenshots/wiki/app_mgmt_offline_space_refusal.webp?v=91195cd3da)

*The refusal names the drive*

![The Offline Deploy sub-tab after the refusal, with the status bar reading Build Offline Bundle: not enough free space on V: and no progress bar](https://sakutility.com/screenshots/wiki/app_mgmt_offline_space_refusal_status.webp?v=e20ffc8498)

*After the box closes, the status bar says it in short*

## Install on the target PC

1. Copy the whole bundle folder to the target PC, along with S.A.K. Utility.
2. Start S.A.K. Utility and press **Run as Admin** in the status bar. If you skip this, the app offers to restart as administrator part way through, and you then start these steps again.
3. Go to **Application Management**, **App Installation**, **Offline Deploy**.
4. If the PC has no internet, tick **Air-gap install (packed only)**.
5. Press **Install from Bundle** and choose `manifest.json` in the bundle folder.
6. Check the list in **Confirm Bundle Installation** and press **Yes**.

![The Confirm Bundle Installation dialog listing the packages in a bundle with their versions, with Yes and No buttons](https://sakutility.com/screenshots/wiki/app_mgmt_offline_confirm.webp?v=54d2bf6bcf)

*Checking the packages before they install*

A Thin Bundle has no `packages` folder and does not need one. A Full Bundle does: if its `packages` folder is not beside `manifest.json`, **Install from Bundle** says so and stops.

## How it works

For a Full Bundle, S.A.K. Utility downloads each package from the Chocolatey community repository, along with the packages it depends on, then fetches the real installer and packs it inside. On the target PC, its own copy of Chocolatey installs from the local `packages` folder, checking each package file first and installing dependencies first.

## Good to know

- Some apps cannot be fully packed. The log's last line says how many are fully offline-capable and how many still require internet at install. **Air-gap install (packed only)** skips those rather than letting them fail, and the result then reads `Incomplete` with a skipped count.
- The air-gap box only matters when installing a Full Bundle.
- A build can hold up to 200 packages.
- A bundle holds the versions current when it was built. Build a new one to get newer versions.
- If **Direct Download** finds no installer for a package, the log shows `No installers found` for it.
- **Save List** and **Load List** keep your package list as a JSON file. A list from **Offline Deploy** cannot be loaded on **Online Install**, or the other way round.

## Related guides

- [Bulk install Windows apps with Chocolatey](https://sakutility.com/wiki/bulk-install-apps)
- [Check installed software for known vulnerabilities](https://sakutility.com/wiki/scan-software-for-vulnerabilities)
- [When S.A.K. Utility needs administrator rights](https://sakutility.com/wiki/administrator-rights)
