Installing the server

One Windows PC at your church runs the server. It talks to the X32, serves the app to everyone's phones, and stays running in the background. This is a once-per-church job.

What you need

Requirements
A Windows PC	Windows 10 or 11. The sound-booth machine is the obvious choice — it needs to be on whenever the team is using the app, so a laptop somebody takes home is not.
Administrator access	The installer asks for it once, to write to Program Files and register itself with Windows.
A Behringer X32 or Midas M32	On the same network as that PC. A wired connection between the two is strongly preferred.
Internet access on that PC	Needed so musicians can reach the app from anywhere. Without it, only devices on the church's own network can connect.
A church account	Created on this website. Sign up first — the server attaches itself to your church the first time an admin signs in on it.

Running the installer

The whole thing is one file, WDM-Setup.exe. There is nothing else to download and no separate runtime to install.

Copy WDM-Setup.exe to the church PC and double-click it.
Windows will ask for permission to make changes. Say yes — the installer can't do its job without it.
Check the options (below) and press Install.
When it finishes, choose Launch it now. A small icon appears in the system tray, next to the clock.

The three options

Installer options
Create Desktop Shortcut	A shortcut on the desktop, for every user of the PC.
Create Start Menu Shortcut	Puts it in the Start menu.
Add to Startup	Launches the app automatically when anyone signs in to the PC. Leave this on — it's what stops somebody having to remember on a Sunday morning.

It installs to C:\Program Files\Worship Device Manager — the folder keeps the product's former name — and registers itself in Windows' Apps list like any other program.

Where to get the installer

WDM-Setup.exe comes with your subscription. If you don't have it to hand, email support@worshipdevicemanager.com and say which church you're from.

Running the app

The server has no window. It lives in the system tray, and everything you actually do happens in a browser.

Open a browser on that PC and go to http://localhost to reach the app.
Right-click the tray icon for Restart and Exit. Restart is the first thing to try if the app is behaving oddly; it takes a few seconds.
Closing the browser doesn't stop the server. Only Exit does.

Next: connect it to your church and run the setup wizard.

It uses port 80

The standard web port, so that a phone only needs the PC's address with nothing after it. If something else on that PC is already serving web pages — IIS, an older Skype, another control app — one of the two has to move. That's the usual reason the app appears to start and then isn't reachable.

Updating

Updating is the same file again: download the newer WDM-Setup.exe, run it, and it recognises the existing installation and offers Update instead of Install. It shows you both version numbers before you commit.

Your settings, musicians and saved mixes are left alone. Only the program files are replaced.
The running app is stopped and restarted for you.
Check the version afterwards under ⋮→Settings→About.

Tip

Update on a weekday, not ten minutes before a service.

Uninstalling

Use Settings → Apps → Installed apps in Windows and remove Audio Passport, or run the installer with the uninstall switch:

WDM-Setup.exe /uninstall

Either way it removes the program, its shortcuts and its startup entry. Your church account, musicians and subscription are on this website and are not affected — reinstalling and signing in gets you back exactly where you were.

Where things live

File locations
`C:\Program Files\Worship Device Manager`	The program itself. Replaced on every update.
`C:\ProgramData\Worship Device Manager`	Your configuration: available microphones, monitors and sends, the roster, and saved mixes. This is the directory to copy if you ever move to a different PC.
`%APPDATA%\worship-device-manager\`	The log files — the last ten runs. This is what support will ask for.

Audio Passport used to be called Worship Device Manager, and these folders still carry the old name. That is deliberate — renaming them on an existing install would leave your settings behind. Nothing is wrong if you see the old name here.