VPadConnect 0.2.1 Beta 2

This release adds a self-contained Windows installer. Download
VPadConnect-Setup.exe; Python and a separate ViGEmBus download are not
required.

What's new

Inno Setup requests administrator approval, lets you choose the installation
folder, creates a Start Menu shortcut, and offers a Desktop shortcut and a
launch option.
The installer detects a working ViGEmBus installation and installs the
bundled official ViGEmBus 1.22.0 setup when the driver is missing.
Setup waits for the driver installer, checks service and Plug and Play state,
and reports failure or a possible restart requirement. Windows is never
restarted automatically.
Upgrades reuse the prior install folder and close VPadConnect before replacing
its executable. Uninstall removes the application but preserves user data and
never removes ViGEmBus.
Installed builds store settings, profiles, logs, and Web Companion keys in
%LOCALAPPDATA%\VPadConnect. Existing legacy data is copied without replacing
conflicts or deleting the original files.
The installer includes the ViGEmBus BSD 3-Clause license notice.

Windows 10 or later, 64-bit x64.
Administrator approval is needed for setup and driver installation.
ViGEmBus was retired on November 2, 2023; version 1.22.0 is its final release
and will not receive upstream updates. Compatibility with future Windows
releases is not guaranteed.
If driver setup fails, virtual Xbox/XInput output is unavailable until the
driver is installed or repaired. Mouse controls, hotkeys, and Web Companion
remain available. A restart may be required after driver installation.
VPadConnect is not affiliated with or endorsed by Nefarius Software Solutions
e.U. Uninstalling VPadConnect does not remove the shared ViGEmBus driver.

python -m compileall -q core ui tests main.py — passed.
python -m pytest -q — 100 passed.
node --check ui/web/static/app.js — passed.
node --test tests/test_web_frontend.cjs — 32 passed.
The PyInstaller executable and Inno Setup installer compiled successfully.
The installer embeds the official ViGEmBus binary whose SHA-256 and
Authenticode signature were verified.
Mocked Windows orchestration tests passed for existing driver, install
success, install failure, and restart-needed paths.
Windows Sandbox was disabled in the build environment. The installer was not
installed or uninstalled on the host because doing so could invoke the
kernel-driver installer; interactive destination-page, shortcut, upgrade,
uninstall, and real-driver scenarios therefore remain unverified.
The driver command-line switches match the Microsoft WinGet manifest, but the
official ViGEmBus installer was not executed in this environment.