Skip to main content
skill CX Codex

windows-sandbox-installer-test — Claude Code skill: installer tests

The windows-sandbox-installer-test Claude Code skill tests Windows installers and uninstallers in a clean Windows Sandbox. It runs when asked whether an .exe or .msi installs silently, hangs, or leaves files behind.

MIT ★ 494 updated 2026-11-15

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add shanselman/sandbox-mcp --skill windows-sandbox-installer-test -a claude-code
Open on GitHub

What windows-sandbox-installer-test does

The skill runs an installer in a fresh Windows Sandbox, records system changes, then uninstalls the program and captures what remains. Start the test with the sbx CLI or the optional MCP adapter; both use the same workflow. Windows Sandbox must be ready.

The host receives a report.md with a PASS or FAIL result and diffs from before and after installation and removal. A screenshot accompanies a hung install, while MSI errors are collected from msi-install.log. Leftover files and registry keys do not cause FAIL by themselves; set failOnLeftovers: true to make them fail the run.

MSI installers get /qn /norestart automatically. For an .exe, pass its silent switch through args; without one, it can wait for a dialog until timeoutSec. If Windows Sandbox is not ready, the windows-sandbox-setup skill is needed.

What it helps with

  • check whether an .exe or .msi installs without dialogs
  • identify a stuck installer and see which window is waiting
  • compare system changes before and after installation
  • find files and registry keys left after uninstalling
  • test whether an installer needs network access

Example prompts for the agent

  • Check whether setup.exe installs silently and list what it adds to Windows.
  • Run installer.msi, uninstall it, and report any files or registry keys left behind.
  • Test this installer with network access disabled and show any stuck dialog.

How to install windows-sandbox-installer-test

1Skills CLI (Vercel)

npx skills add shanselman/sandbox-mcp --skill windows-sandbox-installer-test -a claude-code

2Manually: put the files in place

~/.claude/skills/windows-sandbox-installer-test/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/windows-sandbox-installer-test/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about windows-sandbox-installer-test

How do I install windows-sandbox-installer-test in Claude Code?

Run npx skills add shanselman/sandbox-mcp --skill windows-sandbox-installer-test -a claude-code. The skill file is placed at ~/.claude/skills/windows-sandbox-installer-test/SKILL.md.

What does windows-sandbox-installer-test do?

It runs a Windows installer in a clean sandbox, records system changes, uninstalls the program, and reports what remains.

What does windows-sandbox-installer-test need to run?

Windows Sandbox must be ready. Tests can run through the sbx CLI or the optional MCP adapter.

Source text

SKILL.md · MIT
---
name: windows-sandbox-installer-test
description: Test a Windows installer and uninstaller on a clean machine with Windows Sandbox using sbx or the optional MCP adapter. Use when asked whether a setup.exe or .msi installs silently, what it adds to the system, whether its uninstaller cleans up, why an install hangs, or what an installer leaves behind.
---

# Test an installer

If shell access is available, use the `sbx` CLI; the optional MCP adapter uses the same engine and is not required.

If a tool says the sandbox isn't ready, follow the windows-sandbox-setup skill.

Run `sbx install-test <installer>` or call `sandbox_install_test` with `installer` set to a host path to a `.msi`, `.exe`, `.ps1`, `.cmd` or `.bat`. Both use the same workflow: boot a fresh sandbox and then snapshot, install, snapshot, optionally run a test, uninstall, snapshot again and destroy the sandbox. Allow about two minutes plus the installer's own time.

## Make it silent

An `.msi` gets `/qn /norestart` automatically. An `.exe` needs its silent switch in `args`:

| Installer type | `args` |
|---|---|
| NSIS | `/S` |
| Inno Setup | `/VERYSILENT` |
| Squirrel | `--silent` |
| Burn, InstallShield and others | Often `/quiet`; check the vendor's docs |

Without a silent switch, the installer waits on a dialog until `timeoutSec` (default 600). Set a shorter timeout when probing an unknown installer.

## Uninstalling

`uninstall` defaults to `"auto"`, which uses what the installer registered in Add/Remove Programs: `msiexec /x {ProductCode}`, else `QuietUninstallString`, else `UninstallString` plus `uninstallArgs`. Use `uninstallArgs` for the silent switch when only an `UninstallString` is registered, such as `/S` for NSIS. Set `uninstall` to `"none"` to skip it, or to a command line to run your own.

If the installer registers nothing in Add/Remove Programs, nothing is uninstalled automatically, and the report says so.

## Add a test

`test` is a host `.ps1` that runs inside the sandbox after the install. It gets `$env:SBX_INSTALL_DIR`, `$env:SBX_PROGRAM` and `$env:SBX_OUT`, plus `Get-SbxUiTree`, `Invoke-SbxUi` and `Wait-SbxUi`. Throw or exit non-zero to fail. `SBX_INSTALL_DIR` is empty when the installer doesn't register an install location, so check it before using it.

## Read the result

The result is PASS or FAIL, a diff of what the install changed, a diff of what's left behind after uninstall, and a `report.md` on the host.

**It fails when:**
- the installer or uninstaller exits with an error or hangs (exit codes 0, 1641 and 3010 all count as success; the last two mean a reboot is needed)
- the test script fails
- the program is still listed in Add/Remove Programs after uninstalling

**Leftover files and registry keys do not fail the run** unless you pass `failOnLeftovers: true`. Always read the "Left behind" section and report it, even on PASS.

- **A hung install** comes back with a screenshot of the stuck window and its controls. That's usually a "silent" install waiting for a click, so report which dialog it was.
- **Processes left running** after install (tray apps, updaters) are listed and stopped before the uninstall. Mention them, because they often explain leftovers.
- **Noisy paths** can be ignored with `exclude`. A trailing `*` makes the path a prefix match. Known Windows background noise is already filtered.
- **MSI failures** have a log in the run's `out` folder (`msi-install.log`), and its errors are extracted into the report.

Pass `network: "off"` to prove an installer doesn't need to download anything. Offline runs are a good way to find web-bootstrapper dependencies.

© Scott Hanselman · MIT · shanselman/sandbox-mcp

Similar skills

All skills for Testing and QA →

From the same set6

Project sponsors

Companies that keep this analytics open