AppUpdater
packaging console

Good afternoon.

Loading fleet…

Checking worker…
Build app package
Drop an installer, pick a profile, ship it.
›
fleet
Tracked in local manifest
01 · source
Installer
Drop installer here or click to browse · exe, msi
identity
How Intune sees it
Registry name must match Add/Remove Programs exactly — used for detection.
package type
Wrap & behaviour
Installs auto-update task, scripts and desktop shortcut on every device.
Package for Intune Win32 app upload.
A profile overrides organisation/branding for this build. Manage profiles from the nav rail.
behaviour
On the endpoint
Close blocking appsDetected process to close on install
Allow deferralUsers may postpone 3 times
building

Package

Package ready

 

App fleet

Worker & settings

Cloudflare worker
Loading…

"More worker options" covers re-deploy, custom domain, password reset, MFA and token rotation - still the existing dialog for now while those get ported into the shell individually.

Preferences
Saved
Client profiles can override this per build.
Reduce motionDisables window animations. Also respects sessions over RDP.
Check GitHub for new releasesOff = no outbound call is ever made. Recommended off for air-gapped machines.
 
recovery

A passphrase-protected backup of your config, token, client profiles and manifest. Restores only on THIS machine - for a new machine, reconnect to the Worker and re-run setup.

 

Client profiles

Real, existing feature (profiles.json) - branding + defaults applied to every build for a client.

reference

How AppUpdater works

A quick walkthrough of every screen, plus where to find the source and file issues.

Source & issues
github.com/Lyvvy-xyz/Appupdater
screen by screen
Home

Your fleet at a glance, and whether the Cloudflare worker is connected. "Build app package" starts a new package; the table below shows the last few tracked apps.

Build
01Drop or browse to an installer (.exe/.msi) - version, publisher and silent args are detected automatically.
02Confirm identity fields - registry name must match Add/Remove Programs exactly for detection to work.
03Choose Runtime (auto-updates itself) or Simple, and an output target - .intunewin, or PSADT v3/v4/both.
04Review behaviour toggles, then Build.
App fleet

Every app tracked in your local manifest. "Rebuild" re-opens the builder pre-filled for that app; "Mark deployed" records that you've pushed it live (tracked locally by the shell, separate from the manifest itself).

Client profiles

A profile bundles a client's organisation name, logo/banner, and default output target so every build for that client is branded consistently. Pick one on the Build screen before building.

Worker & settings

Connect to Cloudflare for auto-updates and a live status dashboard, or stay fully offline - packaging always works standalone. Recovery bundles back up your config/profiles/manifest with a passphrase; they restore only on the machine that made them.