AppWrapperfor Windows
macOSWindows
PLENDE
Request access

Enterprise Windows application authoring, packaging and runtime platform

From Windows application source to managed deployment — in one controlled workflow.

AppWrapper guides source analysis, project configuration, detection, install, uninstall, packaging, publishing and diagnostics. The same project can support Microsoft Intune, Microsoft Configuration Manager and a consistent endpoint runtime.

Replace one-off scripts, package notes and disconnected checklists with one project contract: _config.ini, controlled action order, repeatable detection and reviewable deployment artifacts.

Request accessVideos
MSIEXEPS1 / CMD / BAT / VBSAPPX / MSIXMSU / KBStoreCapabilityOffice ODT
PowerShell — AppWrapper Package Wizard
PS C:\Packages\GCTrace> .\wrapper.exe -Run

AppWrapper for Windows
Package Wizard [new package]
Mode: Authoring | Stage: Source selection
====================================================================

Select a source or helper
[1] Local MSI / EXE / script
[2] Microsoft Store application
[3] Windows Capability
[4] Microsoft Update Catalog KB
[5] Office Deployment Tool
[6] Open existing package

>
9 runtime action familiesRuntime
One _config.ini contractProject
Intune and Configuration ManagerPackaging
Logs, summaries and DiagBundleSupport

Why Windows packaging keeps consuming specialist time

Every application can become a separate engineering project.

Installer behavior, silent arguments, user requirements, detection, cleanup, reboots and publishing often remain scattered across scripts, tickets and individual knowledge.

For administrators
  • Inspect installer behavior and reliable silent arguments
  • Order MSI, EXE, scripts, APPX, updates and additional actions
  • Prepare detection, uninstall, reboot handling and tests
  • Troubleshoot exit codes, retries and resumed execution
For the organization
  • Inconsistent standards between teams and delivery channels
  • Operational knowledge concentrated in individual specialists
  • Harder audits, handovers and maintenance of older packages
  • More unplanned support effort after release

Complete Windows scope

More than MSI and EXE. One wizard covers the real Windows packaging toolbox.

MSI, EXE and scripts

Support .msi, .exe, .ps1, .cmd, .bat and .vbs with controlled arguments, exit codes, install and uninstall.

APPX, MSIX and Microsoft Store

Discover local APPX/MSIX/MSIXBUNDLE, download Store apps, select architecture and handle provisioned packages.

Windows Update and KB

Search Microsoft Update Catalog, download MSU/CAB, install or remove updates and handle reboot outcomes.

Windows Capabilities

Search capability names, add multiple components and use online or local sources.

Office Deployment Tool

Download ODT, select XML, prepare offline sources and normalize Office content into the package.

ADD and DEL

Registry import, file/folder copy, path cleanup and registry cleanup as controlled project actions.

CALL and run order

Combine custom commands with MSI, INST, UNINST, ADD, DEL, WU, APPX and CAP in an explicit execution order.

Existing package mode

Reopen _config.ini, change sources and identity, retest, regenerate detection, package and publish.

Branding and interaction

Configure titles, icons, progress, running-process prompts, completion and reboot through UiSessionBridge.

SecondRun and resume

Continue after reboot or logon, retry, postpone and persist runtime state under GlobalClient.

Multi-source detection

REG, FILE, MSI, WU, APPX, CAP and MARKER with groups synchronized to source indexes.

Package stamp and trust

Validate licensing, configuration integrity, payload signatures and trusted certificate expectations.

One controlled workflow

From source to authoring, packaging, publishing and runtime.

Every stage uses the same configuration. Reopen, modify, test, repackage and publish without reconstructing the project context.

01Select sourceLocal payload or a Store, KB, Capability or Office helper.
02Generate project_config.ini with identity, run order, interaction and execution settings.
03DetectionGenerate _detection.ps1 and run an administrator-readable test.
04ValidationCheck sources, prerequisites, detection and configuration integrity.
05Local testsInstall and uninstall with logging, UI and exit-code handling.
06PackageSCCM content or .intunewin through IntuneWinAppUtil.
07PublishHand off to publisher.exe and the target channel.
08RuntimeSYSTEM context, retry, reboot, SecondRun, final detection and summary.

Product walkthrough

From source to authoring, packaging, publishing and runtime.

Every stage uses the same configuration. Reopen, modify, test, repackage and publish without reconstructing the project context.

01 / 6

Source selection

Start the complete wizard and select a local source or helper.

PowerShell — AppWrapper Package Wizard
PS C:\Packages\GCTrace> .\wrapper.exe -Run

AppWrapper for Windows
Package Wizard [new package]
Mode: Authoring | Stage: Source selection
====================================================================

Select a source or helper
[1] Local MSI / EXE / script
[2] Microsoft Store application
[3] Windows Capability
[4] Microsoft Update Catalog KB
[5] Office Deployment Tool
[6] Open existing package

>
1 / 6

One project contract

_config.ini preserves the decisions required to execute the package.

Configuration brings together application identity, source preparation, run order, detection, downloads, cleanup, user interaction, branding, security, logging and SecondRun.

[Inventory]

Application identity, publisher, version, owner and organizational inventory context.

[PrepareSetup] + [APPInstall]

Source preparation and primary install or uninstall behavior.

[RunOrder] + [Additional]

Explicit sequencing of primary and additional action families.

[Detection]

Detection groups, comparison rules and source-index synchronization.

[UserInteraction] + [Branding]

Progress, process prompts, completion, restart, icon and title.

[Security] + [Logging] + [SecondRun]

Integrity, trust, diagnostics and controlled continuation after reboot.

Outputs for the target delivery channel

Intune, Configuration Manager and Publisher use the same project.

AppWrapper validates prerequisites, prepares content and hands it to the right channel without creating a separate runtime model for every platform.

Intune

.intunewin and publishing handoff

  • Content validation before packaging
  • IntuneWinAppUtil discovery or explicit path
  • Detection prerequisite validation
  • Publisher handoff from the wizard
wrapper.exe -PackIntune -SourcePath . -SetupFile .\setup.exe
Configuration Manager

Prepared SCCM application content

  • Same runtime and project configuration
  • Install and uninstall commands
  • Detection script and package content
  • Publisher handoff for the target channel
wrapper.exe -PackSccm -SourcePath .

Enterprise runtime

Install and uninstall execute through a controlled plan.

The runtime handles action order, retry, exit codes, reboot, SecondRun resume, user interaction, final detection and operation summaries.

INSTALL

Controlled execution

  • MSI, INST, ADD, WU, APPX, CAP and CALL
  • Accepted exit codes, retries and state tracking
  • End-of-run detection and registry footprint
  • SecondRun continuation after reboot
↔
UNINSTALL

Designed removal path

  • UNINST, DEL, MSI, APPX, WU and CAP removal
  • Cleanup of paths and registry state
  • Running-process protection and postpone
  • Uninstall detection, history and final summary

End-user interaction

Visible communication without stray console windows.

The current UiSessionBridge transport delivers progress, running-process prompts, completion messages and reboot dialogs into the active user session.

AppWrapper

Installing GCTrace

Please keep your device powered on. AppWrapper will close this window when the operation is complete.

Current UI transport

GlobalClient.UiSessionBridge.exe delivers user-visible windows from managed SYSTEM deployments into the active session.

  • Progress windows
  • Running-process prompts
  • Completion dialogs
  • Reboot and resume communication
  • Default, delivery-channel or custom branding

Cases that normally need separate scripts

Windows updates, Store, Office, capabilities and resume flows live in the same model.

Download workflows

Microsoft Store, Update Catalog KB, Office ODT and package-local source preparation.

Architecture-aware APPX

Prefer the correct package for the current OS and skip duplicate identities after successful installation.

Capability source control

Online or local sources, source health checks, fallback policy and pending reboot handling.

SecondRun

Persist state and continue controlled work after restart or logon without starting from the beginning.

Postpone and resume

Protect user work, schedule a later attempt and preserve the operational state.

What-if and diagnostics

Use structured logs, human-readable test output and bundles to reduce troubleshooting time.

Support without guesswork

Logs, JSON summaries and DiagBundle are created with the operation.

Administrators and support start with structured evidence: current logs, outcome summaries, history and a diagnostic bundle carrying the relevant package context.

C:\ProgramData\GlobalClient\
  • Logs\*.latest.log
  • Logs\summary\*.latest.json
  • OLD_Logs\
  • Diagnostics\*_DiagBundle.zip
  • Registry history and markers under HKLM
PowerShell — AppWrapper diagnostics
PS C:\Packages\GCTrace> .\wrapper.exe -DiagBundle

Collecting current logs...
Collecting package configuration...
Collecting operation summaries...
DiagBundle ready: GCTrace_DiagBundle.zip

Who it is for

For teams responsible for the complete Windows application lifecycle.

Microsoft Intune

Win32 packaging, detection, user interaction and publisher handoff.

Configuration Manager

Prepared application content with the same runtime contract.

Application packaging teams

Repeatable authoring across payload types and administrator handovers.

Endpoint operations

Consistent runtime, logs, summaries and escalation evidence.

Consultants

Deliver reviewable projects instead of undocumented one-off scripts.

MSP / partners

Multi-customer use requires a dedicated partner agreement and licensing model.

Simple licensing

One platform. Two levels of partnership.

Every plan includes the complete Windows feature set. Plans differ by Author Seats, support, onboarding and SLA.

Professional

Professional

From€2,990/ year
  • Complete feature set
  • 1 organization
  • 3 Author Seats
  • Publisher included
  • Updates and email support
Book a demo

Enterprise

From€8,990/ year
  • Complete feature set
  • 1 organization
  • 10 Author Seats
  • Priority support and SLA
  • Onboarding, workshops and roadmap influence
Contact sales

Product resources

Documentation, requirements, security and release history in the same standard as the macOS edition.

Documentation

Authoring, detection, packaging, runtime and diagnostics guidance.

→

Release notes

Changes across AppWrapper, Publisher and Windows helpers.

→

Security

Licensing, package stamp, signatures and organization trust.

→

System requirements

System, PowerShell, permissions, IntuneWinAppUtil and servicing tools.

→

Windows packaging maturity assessment

See where the process loses consistency and operational knowledge.

Eight questions assess source preparation, detection, uninstall, validation, documentation and project handover.

Packaging maturity74 / 100
  • Detection model consistency
  • Install and uninstall parity
  • Validation before release
  • Documentation and handover
Start assessment

Interactive walkthroughs

Explore the most important Windows workflows without leaving the page.

Open walkthrough →
01

Authoring and existing-package mode

Source selection, configuration, detection and reopen flow.

02

Intune and SCCM packaging

Validation, content preparation and channel handoff.

03

Runtime and diagnostics

Install, user interaction, SecondRun and DiagBundle.

Frequently asked questions

Clear answers about sources, runtime, Intune, Configuration Manager and licensing.

Does AppWrapper support only MSI?

No. The Windows edition supports MSI, EXE, scripts, APPX/MSIX, MSU, Windows Capabilities, Microsoft Store, Office ODT, additional actions and cleanup.

Is Publisher part of the product?

Yes. The wizard can hand a prepared project to the companion Publisher. Publishing remains a separate subsystem but uses the same project context.

Does AppWrapper generate detection?

Yes. It can generate _detection.ps1 for REG, FILE, MSI, WU, APPX, CAP and MARKER and run an administrator-readable detection test.

Can an existing package be reopened?

Yes. When _config.ini exists, the wizard exposes source, identity, inventory, detection and UI editing, tests, packaging and publishing.

How is end-user interaction delivered?

UiSessionBridge delivers progress, running-process prompts, completion and reboot into the active session without relying on the retired legacy VBS transport.

Can AppWrapper work offline?

Core authoring and runtime can work locally. Download, Microsoft Catalog, Store and publishing functions require access to the relevant services.

Does AppWrapper replace application testing?

No. It standardizes authoring, validation and execution, but production deployment should still follow your testing and change-management process.

Can one standard license serve multiple MSP customers?

No. A single-organization plan does not cover independent customers; a separate partner agreement is required.

Early access

Standardize Windows application delivery without rebuilding every package from scratch.

Tell us about your environment, delivery channels and packaging challenges. We will help define the right AppWrapper pilot.

Contacthello@app-wrapper.com