diff --git a/launcher/windows/build.sh b/launcher/windows/build.sh
index aa150e0..0bf4bbc 100644
--- a/launcher/windows/build.sh
+++ b/launcher/windows/build.sh
@@ -1,7 +1,8 @@
 #!/bin/zsh
 # Build the Windows bundle — ProdDash-<version>-win-x64.zip: the dashboard,
 # its own Node runtime and a start script, so nothing has to be installed on
-# the Windows machine. Unzip, double-click ProdDash.bat, done.
+# the Windows machine. Unzip, double-click ProdDash.bat, done. It carries no
+# modules: those come from the admin page's catalog into %APPDATA%\ProdDash.
 #
 #   ./build.sh                 build/ProdDash-<version>-win-x64.zip
 #
@@ -55,9 +56,9 @@ echo "  embedding Node $NODE_VERSION (node.exe and its licence)"
 unzip -q -j "$CACHE_DIR/$ZIPFILE" "$NODE_DIST/node.exe" "$NODE_DIST/LICENSE" -d "$STAGE/node"
 
 # ── ProdDash ─────────────────────────────────────────────────────────────
-echo "  embedding ProdDash $VERSION"
+echo "  embedding ProdDash $VERSION (no modules — the catalog installs them)"
 cp "$REPO_ROOT/server.js" "$REPO_ROOT/package.json" "$STAGE/"
-cp -R "$REPO_ROOT/public" "$REPO_ROOT/modules" "$STAGE/"
+cp -R "$REPO_ROOT/public" "$STAGE/"
 # Only the checked-in defaults: config/ also holds this machine's own
 # modules.json and layouts when ProdDash has ever run from the checkout.
 cp "$REPO_ROOT/config/proddash.json" "$STAGE/config/"
@@ -98,6 +99,9 @@ Nothing to install. This folder holds the dashboard and its own copy of Node.
 3. Open http://localhost:24500 on this PC. Other devices on the network use
    http://<this PC's IP address>:24500. Settings are on the admin page,
    http://localhost:24500/admin.
+4. The bundle ships without modules. On the admin page, tick the ones this
+   PC needs under Available modules and press Install selected; each one
+   updates on its own from then on.
 
 Your settings and layouts live in %APPDATA%\ProdDash, not in this folder,
 so unzipping a new version or updating never loses them.