Installation

June 8, 2026 ยท View on GitHub

AudioPlaybackConnector2 supports two installation paths:

  • Build from source (developer workflow)
  • Install the published MSIX release (end-user workflow)

For local development, see Developer setup and build.

Install Released MSIX

Each GitHub release provides:

  • .appinstaller
  • .msix
  • .cer certificate

1) Trust the release certificate

Right-click the .cer file and choose Install Certificate, or use PowerShell:

Import-Certificate -FilePath ".\AudioPlaybackConnector2.cer" -CertStoreLocation "Cert:\LocalMachine\Root"

If you only want per-user trust, use:

Import-Certificate -FilePath ".\AudioPlaybackConnector2.cer" -CertStoreLocation "Cert:\CurrentUser\TrustedPeople"

2) Install via App Installer

Download the App Installer feed and open the local .appinstaller file:

$installer = Join-Path $env:TEMP "AudioPlaybackConnector2.appinstaller"
Invoke-WebRequest -Uri "https://n0ahtm.github.io/AudioPlaybackConnector2/AudioPlaybackConnector2.appinstaller" -OutFile $installer
Start-Process $installer

Opening a downloaded .appinstaller avoids the ms-appinstaller: web protocol, which Microsoft has disabled by default on consumer devices since December 2023. The protocol can be re-enabled by enterprise policy, but the local .appinstaller flow is the supported path for general GitHub release distribution.

The .appinstaller automatically pulls in required framework dependencies (VCLibs and Windows App SDK runtime). Because these are system framework packages, Windows may prompt for administrator approval during installation.

See:

Optional fallback: direct MSIX install

Add-AppxPackage works as a fallback, but it does not preserve update-feed behavior from .appinstaller. If you install the .msix directly, any missing framework dependencies will be reported and must be resolved manually.

Build and run locally

Open AudioPlaybackConnector2.slnx, choose Release | x64, build, then run/install the generated package.

Local builds use a temporary developer certificate, so manual certificate installation is usually not needed.

Notes on signing

Releases are currently signed with a self-signed certificate. Installing the .cer is required before the .msix can be trusted by Windows.