Can I work on multiple packages at the same time?

Yes. Create as many packages as you need from the dashboard (free edition limit: 10). Switch between them by clicking a card or using the package picker. Each package has its own files, configuration, phases, and test-run settings.

Do I need an internet connection?

Only for:

• Downloading .NET 9 runtimes (first install only, if not already installed)
• Downloading the latest PSADT from GitHub (optional)
• Checking for toolkit updates (optional; toggle in Settings)

All other functionality works completely offline.

Where are my packages saved?

Package definitions (configuration, phase code, parameters) are saved in %AppData%\XOAP\PackageWizard\packages.json. Uploaded files are in %AppData%\XOAP\PackageWizard\workspace\Files\{packageId}\.

Can I back up my work?

Yes. Copy the entire %AppData%\XOAP\PackageWizard\ folder. It contains all your packages, preferences, uploaded files, and downloaded toolkits.

How do I use the exported package?

The exported .zip is a standard PSADT v4 package. Extract it and run:

# Interactive install
.\Invoke-AppDeployToolkit.ps1 -DeploymentType Install

# Silent install
.\Invoke-AppDeployToolkit.ps1 -DeploymentType Install -DeployMode Silent

# Uninstall
.\Invoke-AppDeployToolkit.ps1 -DeploymentType Uninstall

# Repair
.\Invoke-AppDeployToolkit.ps1 -DeploymentType Repair

Or deploy it via SCCM/MECM, Intune, or any tool that executes PowerShell scripts.

Can I import my old PSADT v3 packages?

Yes. Use Import Local on the dashboard. The wizard detects v3 packages (Deploy-Application.ps1) and translates commands, variables, and parameters to v4 syntax automatically. Commands that map to multiple v4 functions are annotated with # TODO comments for you to resolve.

The application won’t start — what do I check?

1. Check the logs at %AppData%\XOAP\PackageWizard\logs\
   • desktop-{date}.log — Shows startup errors, API health check results
   • api-{session}.log — Shows API server errors
2. Verify .NET 9 is installed: Open a command prompt and run dotnet --list-runtimes. Look for Microsoft.WindowsDesktop.App 9.0.x and Microsoft.AspNetCore.App 9.0.x.
3. Reinstall if the issue persists — uninstall first, delete the install folder, then reinstall.

How do I update XOAP PSADT Package Wizard?

Run the new installer. It will upgrade the existing installation in place. Your packages and settings are stored in %AppData% and are not affected by upgrades.

Can I change the install location?

Yes, during installation you can choose any folder. The default (C:\Program Files\XOAP PSADT Package Wizard) is recommended because the [InstallDelete] step in Inno Setup’s upgrade handling looks for that location.

Is my data sent anywhere?

No. XOAP PSADT Package Wizard runs entirely on your local machine. The only outbound network requests are:

• Checking GitHub for the latest PSADT version (optional, can be disabled in Settings)
• Downloading PSADT from GitHub (only when you click Download Latest)
• Downloading .NET runtimes from Microsoft (only during first install if needed)

No telemetry, no cloud services, no data leaves your machine.

What do the “Not available in Free version” lock badges mean?

They mark features that are visible in the UI so you can see the full feature surface, but are not active in the free edition. See EDITIONS.md for the full comparison.

How do I test my script without exporting?

Go to the Preview step (step 7), pick a DeploymentType and DeployMode, optionally toggle Run as Admin, and click Test Run. The script executes on your local machine and streams output into the embedded terminal. Test Run has a 120-second timeout.

The post FAQ appeared first on XOAP.

To open %AppData%\XOAP\PackageWizard\ directly: press Win+R, type %AppData%\XOAP\PackageWizard, press Enter.

The post File locations appeared first on XOAP.

• Auto-save runs every 2 seconds while you work, and runs once more when you click Save in the wizard header strip or navigate away.
• Browser refresh warning — if you reload the page with unsaved changes, the browser will prompt you to confirm.
• Skip to main content — press Tab from the document root to reach a hidden skip link for keyboard navigation.
• Mobile-friendly — the sidebar can be collapsed with the hamburger toggle on narrow viewports.
• Maximize editor — every code editor has a button (arrows-diagonal icon) to expand to full-screen, useful for long phase bodies.
• Esc to close drawers/modals — the Function Builder, tag drawer, import drawer, and confirm modal all support overlay click / Esc to close.

The post Keyboard & UX tips appeared first on XOAP.

The code editors in the Install / Uninstall / Repair phases include two productivity tools:

Cmdlet autocomplete

Built into every PowerShell code editor. No setup required.

• Cmdlet suggestion — type any prefix (e.g. Start-ADT) and the editor proposes matching cmdlets from the PSADT v4 library. Accepting a suggestion inserts the cmdlet with a snippet for each required parameter.
• Parameter suggestion — after a cmdlet name, type a space and - to see all parameters with type, required flag, description, and valid values (if any).
• Works across every phase editor and the Function Builder modal’s code preview.

Function builder modal

Click the Function Builder icon in any phase editor toolbar. A modal opens showing a category sidebar and a function list.

Categories:

Locked cmdlet cards still display (with the lock badge) so you can see what exists, but selecting them does nothing. Cmdlet autocomplete in the editor includes all cmdlets regardless of category, so typing them directly works even in the free edition — only the visual builder is gated.

For each function card:

• Name and short description
• A visual parameter editor (text inputs, dropdowns for validate sets, switches for SwitchParameter)
• A file-path picker for parameters named FilePath, Path, Destination, StubExePath, TargetPath, IconLocation, WorkingDirectory — populated from your uploaded package files
• Live code preview of the generated snippet
• Insert — drops the snippet at the cursor in the current code editor

The post Function builder & cmdlet autocomplete appeared first on XOAP.

Open Settings from the sidebar footer. It is organized into three side-tabs.

General tab

Default package values

Documentation options — locked in free edition

Package storage — locked in free edition

The Save Settings button at the top of the page saves General tab values and any pending Package Configuration edits in one action.

PSADT toolkit tab

Active toolkit for export

Shows which toolkit will be used for script generation and export:

• Source label — Custom, Bundled, or No Toolkit Available
• Module Version — detected from PSAppDeployToolkit/PSAppDeployToolkit.psd1
• Custom Extensions included — badge shown if PSAppDeployToolkit.Extensions is present
• Refresh — re-queries the server

Below the status card:

• Auto-check for toolkit updates on startup — toggles GitHub version check at startup

Resolution order (top wins):

1. Custom toolkit path (if set and valid) — paid feature (see below)
2. Downloaded toolkit in %AppData%\XOAP\PackageWizard\Toolkit\{tag}\
3. Bundled template shipped with the installer

Download latest from GitHub

• Large Download Latest PSADT button — fetches the latest release from github.com/PSAppDeployToolkit/PSAppDeployToolkit, extracts it (zip-slip protected), and sets it as the active toolkit
• Displays the latest release tag and an “Update available” badge when applicable

Use custom toolkit — locked in free edition

Locked in free edition. Both the text input and the button are displayed but disabled.

Package configuration tab

Reads Config/config.psd1 from the active toolkit and renders each section as a card.

For each field the UI shows:

• The field key (e.g. MSI_LogPath)
• Any comment/description parsed out of the .psd1
• A form control appropriate for the type (text input, number input, or True/False toggle)

Editing a field and clicking Save Settings (top of page) writes the changes back to config.psd1 (with zipslip / path-traversal protection). The signature block, if present, is stripped on save.

The post Settings appeared first on XOAP.

Tags help you organize packages in the dashboard. Open Tags from the sidebar footer.

Managing Tags

• Create a tag with a name (max 40 characters), description (max 160), and color
• Available colors: cyan, pink, orange, green, purple, indigo
• Edit or Delete tags at any time. Deleting a tag removes it from all packages automatically.

Assigning Tags

• From the dashboard, click the tag icon on a package card, or
• Select multiple packages and click Assign Tags on the toolbar

Each package can have up to 5 tags in the free edition. Tags appear as colored badges on package cards and in the tag filter dropdown.

The post Tags appeared first on XOAP.

The Logs page (/logs) shows the API server’s log files.

• Session selector — each time the API starts it opens a new log file named api-{yyyy-MM-dd-HHmmss}.log. The dropdown lists all sessions still on disk (14-day retention).
• Monaco viewer — the selected log is rendered read-only in a code editor
• Search — filter lines in the current log
• Auto-refresh — the current session log refreshes every 5 seconds so you can watch requests stream in live

Files are stored in %AppData%\XOAP\PackageWizard\logs\. Each session’s log has a 10 MB size cap; files older than 14 days are cleaned up on startup. A parallel log for the desktop shell (desktop-{yyyy-MM-dd}.log) exists in the same folder but is not shown in this viewer.

The post Logs appeared first on XOAP.

Installed apps

The Installed Apps page (/installed-apps) lets you browse applications installed on your Windows machine.

Controls

The registry is queried from:

• HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\ (64-bit)
• HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ (32-bit)
• HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall\ (per-user)

Snapshot workflow

1. Click Take Snapshot before running your deployment
2. Run your PSADT package (via Test Run or a real deploy)
3. Click Compare to see which applications were installed, removed, or modified
4. Results show status for each app and can help you verify that your uninstall phase cleans up everything your install phase added

The post Installed apps appeared first on XOAP.

You can import existing PSADT packages (v3 or v4) from .zip files.

1. From the dashboard, click Import Local
2. A drawer opens; drop one or more .zip files (or click to browse)
3. The wizard processes each zip and reports status

For each zip, the wizard will:

• Detect whether it’s a v3 (Deploy-Application.ps1) or v4 (Invoke-AppDeployToolkit.ps1) package
• Parse the script to extract session configuration values
• Extract phase content (pre/main/post for each deployment type)
• Extract any custom parameters
• Copy Files/* into the package’s workspace directory
• Add a new package to your workspace (respecting the 10-package cap)

For v3 packages, command names and variables are automatically translated to v4 syntax using the same translation service used by the /api/translate endpoint.

After import, you can review and edit each package through the normal wizard steps.

The post Importing existing packages appeared first on XOAP.

There are three ways to export:

1. Per-package export — from the dashboard, click Export on a package card
2. Batch export — select multiple packages and click the Export toolbar icon
3. HTTP download — when running in a browser (not the desktop app), exports download as {AppVendor}_{AppName}_{Version}_{Arch}.zip through the browser

In the desktop app, exports are written directly to the Default Output Folder set in Settings. If that path is empty or invalid, the app falls back to your Downloads folder.

The exported .zip contains everything needed to deploy:

Contoso_MyApp_1.0.0_x64.zip
  Invoke-AppDeployToolkit.ps1     <- Your generated script
  Invoke-AppDeployToolkit.exe     <- PSADT executable stub
  PSAppDeployToolkit/             <- PSADT module
  PSAppDeployToolkit.Extensions/  <- Extensions (if present in toolkit)
  Config/                         <- Configuration
  Strings/                        <- Localization
  SupportFiles/                   <- Support files
  Assets/                         <- Icons
  Files/                          <- Your uploaded files
    MyApp.msi
    config.xml

Free vs Paid: In the paid edition, enabling Include README.md on the Settings → General tab causes a README.md with package metadata, parameters, and phase documentation to be generated and added to the exported zip. The toggle is visible but locked in the free edition.

The post Exporting packages appeared first on XOAP.