Windows installation, updates and removal

Use the official release's Windows x86-64 setup EXE for installation and upgrades. It contains the exact raw MSI and coordinates local recovery. The MSI offers Desktop application, CLI or both; both are selected by default. The ZIP packages remain available for portable copying. amd64 means x86-64, including compatible Intel and AMD processors. The version index states whether official downloads are available.

The Windows setup EXE, raw MSI and application are initially unsigned, with no verified publisher signature. A checksum identifies matching bytes; it does not add a signature or establish Windows reputation. Download, application reputation, permission approval, license acceptance and missing dependencies are separate checks.

Install normally

1. Open the official releases, choose the exact version and download its recommended insonic_VERSION_windows_amd64_setup.exe. Replace VERSION with that release's version. Keep its SHA256SUMS and release-manifest.json links for identity checks. If a warning appears, follow the matching branch below.
2. Install the applicable prerequisites, then open the downloaded setup EXE. Its native MSI pages install for the current user; it does not install for all accounts, acquire prerequisites over the network or add directories to PATH.
3. Read the actual Apache License 2.0 and select I accept the Apache License 2.0, which starts unchecked. Acceptance is required to continue.
4. Choose Desktop application, CLI or both. Desktop-only retains the shared runtime and command executable required by the application, while omitting exposed CLI launch integrations. CLI-only omits the desktop application and its WebView2 requirement. At least one client is required.
5. Keep the per-user program location under %LOCALAPPDATA%\Programs\insonic, or browse to a suitable writable program directory. Keep libraries, recordings, models and settings outside it. Spaces and non-ASCII names are supported. No user data is stored in installer-owned program files. An explicitly chosen directory is retained when saved installation metadata is read back.
6. Choose the optional desktop icon and Start menu integrations. The Start menu folder is insonic; the application shortcut is insonic and the command shortcut is insonic CLI. The desktop shortcut is insonic. Integrations follow the selected clients. If an existing shortcut with the exact optional name belongs to another installation or to you, the MSI refuses to overwrite it. Deselect that integration or move your existing shortcut, then retry.
7. Choose Install to commit the fresh installation. The execution page shows Windows Installer progress and the current phase. Cancel asks for confirmation while cancellation remains available; allow rollback to finish before closing the result. The final page distinguishes success, cancellation and failure.
8. After successful fresh installation, keep the checked Launch insonic option to open the desktop when selected. For CLI-only, Open insonic CLI opens a persistent command session with useful help/setup guidance. Open documentation is a separate, initially unchecked option. Choose either, both or neither, then select Finish. Documentation opens the installed version’s local HTML in the configured Windows HTML/browser association. If it cannot open, the correction explains how to open help/index.html, configure an HTML browser or use installer Repair; the committed installation remains available.
9. Neither completion action runs after unattended installation, upgrade, change, repair, removal, cancellation or failure. Those operations have their own result heading and one Finish or Close action.
10. Use optional first-run setup, open an existing library or choose Set up later. Local filesystem/SQLite/LadybugDB defaults need no service account or API key. Installing insonic does not download inference models or elect connected routes.

Optional checksum comparison

1. Save SHA256SUMS beside the downloaded setup EXE.

2. Open PowerShell in that download folder and replace VERSION below:

   Get-FileHash -Algorithm SHA256 ".\insonic_VERSION_windows_amd64_setup.exe"
   

3. Compare the complete hexadecimal hash with the line for that exact filename in SHA256SUMS. Matching letters can differ in case. If bytes do not match, discard that download and retrieve the official asset again; do not install it.

Prerequisites

Both clients require the Microsoft Visual C++ v14 x64 runtime. Use Microsoft's runtime guidance and official x64 installer. Download the complete installer while online for transfer to an offline computer.

Desktop application additionally requires the WebView2 Runtime. Microsoft's download page and distribution guidance distinguish the online Evergreen Bootstrapper from the x64 Evergreen Standalone Installer for offline installation. Microsoft Edge itself does not replace WebView2. CLI-only does not require it.

The MSI explains missing prerequisites. Install the relevant official runtime, honor its restart instructions, then retry the MSI. Prerequisite installers may request administrative approval depending on their chosen mode; the insonic per-user MSI does not request an all-users installation. Removing insonic does not remove shared Microsoft runtimes. Loader errors and unavailable dependencies are not a license or reputation confirmation.

Download and Windows warnings

Edge says the download is not commonly downloaded

1. Confirm the download's filename, version and official release address. An unknown/not-common reputation warning differs from a file reported as malicious.
2. For the unknown-file branch in Microsoft Edge, open the download item's ... menu, then choose Keep, Show More and Keep anyway when offered. This retains the selected download.
3. If the warning reports malware, or device policy removes continuation, record the exact warning and use the support checklist. Do not apply unknown-file instructions to a reported-malicious detection.

Microsoft documents these controls and managed-policy differences in Edge SmartScreen guidance. Other browsers have different controls; use their matching guidance.

Windows protected your PC

1. If this application-reputation dialog appears, select More info.
2. Check the displayed file matches your selected official download. This unsigned release does not have a verified publisher signature.
3. Select Run anyway if that control is available and you intend to run the selected file. If it is absent, use the support checklist; organization policy can prevent continuation.

Microsoft's first-app guide documents those controls, and SmartScreen reputation guidance explains unsigned-file reputation and enterprise blocks. The dialog is conditional; every MSI or extracted application need not show it.

Permission to change the device

A User Account Control prompt concerns elevation. It is separate from SmartScreen and Apache license acceptance. A prerequisite installer or an administrator-directed change can need permission even though insonic installs per user.

1. Identify the program and requested change. An unsigned program has no verified publisher identity.
2. Choose Yes only for the identified change you intend to allow, or No to decline it.
3. A standard account may instead need administrator credentials. Ask your administrator rather than entering credentials into the insonic setup guide or an unrelated window.

Microsoft's UAC documentation distinguishes administrator consent from standard-user credential prompts and explains secure-desktop behavior.

Smart App Control, S mode or organization policy blocks execution

Smart App Control can reject an unsigned/untrusted file and currently offers no individual-app override. More info / Run anyway does not bypass it. Contact the developer or device administrator with the support checklist. Microsoft's current FAQ also explains that recent Windows updates can permit re-enabling Smart App Control without a clean installation; older universal reset claims are not applicable to every device.

Windows S mode permits Microsoft Store applications. Leaving S mode is a one-way device choice, not a normal warning acknowledgment. Read Microsoft's S mode FAQ and consult the device owner or administrator before deciding.

App-source recommendations are another setting. On Windows 11 they appear under Settings > Apps > Advanced app settings > Choose where to get apps, with options depending on the device. Microsoft's app recommendation guidance explains those choices. Organization controls may be locked and can prohibit unsigned or outside-store installation. Global antivirus, Defender, SmartScreen and organization-policy disabling are not steps in the normal installation procedure.

Change, repair, upgrade or remove

1. Finish or explicitly cancel selected work in Jobs or CLI work commands, then close clients from the installation being changed. Closing the desktop does not cancel durable work. Allow the hidden runtime at least 31 seconds of inactivity to exit; new requests reset activity. Desktop maintenance guidance explains how to identify remaining processes.
2. Open Settings > Apps > Installed apps, find insonic, and use its offered maintenance/removal action. The installer supports feature changes, repair and removal. If active work prevents replacement, close that work and retry; maintenance does not silently terminate it.
3. For an upgrade, download and open the newer matching setup EXE. Before removing the working version, setup validates a retained full MSI source and snapshots the previous program path, clients and shortcuts. Failed or cancelled replacement restores the prior installed registration and owned program bytes before setup returns, retaining the original failure or cancellation result. When moving an upgrade to a different program directory, active work under the registered old directory must also be closed before replacement. Older-version installation is rejected. Retain a library backup because program rollback does not reverse independently accepted library changes.
4. For removal, select Uninstall and complete the MSI removal. It removes only owned program files and integrations. Libraries, media, settings, models, credentials, shared Microsoft runtimes and unrelated portable ZIP installations remain.

Per-user configuration uses %APPDATA%\insonic; local data/cache/runtime coordination uses %LOCALAPPDATA%\insonic. Library data follows the actual elected profiles. Native protected credentials remain in Windows Credential Manager; vault/credential configuration uses the library's private secret area. Preserve these locations during ordinary program removal. See storage, credentials and models.

Recovery sources and raw MSI

Setup retains the complete current MSI privately under %LOCALAPPDATA%\insonic-setup. During upgrade it needs space for the old and new full MSI sources, in addition to installed program files. Legacy-source validation can also require a temporary private cabinet copy. Recovery uses the retained package even when the downloaded MSI or setup EXE is gone. Successful upgrade removes the obsolete old source; successful removal cleans its source. Libraries, media, settings, models and credentials remain outside this cache.

A legacy installation may have no retained source. Missing or corrupt required recovery data stops the coordinated upgrade before old removal. Obtain the exact previous release's MSI and its SHA256SUMS digest, then supply both explicitly:

& ".\insonic_NEW_VERSION_windows_amd64_setup.exe" --previous-msi "C:\Downloads\insonic_OLD_VERSION_windows_amd64_installer.msi" --previous-sha256 "PREVIOUS_MSI_SHA256"

Replace both versions, the local path and the complete digest. Source identity, digest and embedded inventory must match the previous installed release. Supplying the valid original package also repairs corrupt application-owned source bytes before upgrade starts. Setup does not fetch recovery packages over the network or request administrator privileges. If Windows started it elevated, it hands execution to the same account's limited token and waits for the result; an unavailable limited token produces a correction to reopen normally.

The raw insonic_VERSION_windows_amd64_installer.msi remains available for direct Windows Installer use and advanced deployment tooling. It bypasses coordinated source retention and recovery. On the reproduced Windows Installer failure, old files return while old registration is only advertised, so raw-MSI file rollback cannot establish a usable registered installation. Use setup for the coordinated guarantee. Installed Apps still uses native MSI maintenance and removal.

If recovery cannot finish, setup retains its local source and pending.json record, reports incomplete recovery and returns failure. Correct the reported local-source or active-work problem, then retry the same setup with --resume-recovery (add --quiet for unattended recovery). Private last-result.json, setup.log and recovery logs distinguish the original native result from recovery. A preflight refusal has no native result because the MSI did not run. Omit private paths and account details when sharing diagnostics.

Unattended setup

Read the Apache License 2.0 before electing unattended acceptance. From an existing PowerShell session, choose the exact release and client selection:

$arguments = "--quiet --accept-license --clients cli --start-menu 0 --desktop-shortcut 0"
$setup = Start-Process -FilePath ".\insonic_VERSION_windows_amd64_setup.exe" -ArgumentList $arguments -WindowStyle Hidden -Wait -PassThru
$setup.ExitCode

This PowerShell process invocation waits for setup and reads its actual process exit code. Use both, desktop or cli; new installations default to both. --install-dir PATH selects a program location. Unattended upgrades retain prior choices unless explicitly overridden. Use setup for the installed version with --quiet --repair or --quiet --remove for maintenance. No completion launch or documentation action runs in quiet mode.

A result of 0 means the selected operation succeeded. Windows Installer can also return successful restart codes 3010 (restart required) or 1641 (restart initiated); setup preserves these native results and suppresses automatic restart requests. Native 1602 means cancellation; 1603 means failure. Recovery preserves those original codes even when it restores the previous version successfully. Preflight failures return 1603 before starting MSI work. Recovery runs synchronously under the ordinary invoking account.

Portable ZIP alternative

1. Choose the exact Windows Desktop + CLI or CLI-only ZIP and install its applicable prerequisites.
2. Extract the complete tree. Keep companions, native libraries, notices, corresponding sources and offline help together.
3. Follow Windows ZIP installation to copy into a stable program directory and choose a separate library.
4. Open insonic-desktop.exe when included, or use insonic.exe from an already open terminal. ZIP copying creates no MSI registration, Installed Apps entry, shortcut, PATH integration or supplied uninstaller.

Installer page walkthrough

These are actual authored MSI pages rendered by native Windows Installer on a disposable Windows Server 2022 runner, build 20348, in English (United States). A restricted installer session elected the illustrated clients, integrations, program path and Launch option, then read back their actual native control values before capture. The images show those fixture choices; they do not prove fresh-install defaults or a completed installation transaction. The normal steps above describe default behavior. No browser reputation, SmartScreen, UAC or other Windows policy prompt was captured.

Figure 1. Welcome to per-user installation. Select Next to read the license before choosing clients and integrations.

Figure 2. Read the Apache License 2.0. Select I accept the Apache License 2.0 to enable Next.

Figure 3. The fixture elects both clients and optional integrations. Choose the clients you want; Desktop-only retains shared runtime bytes, while CLI-only omits the GUI.

Figure 4. The fixture shows a generic per-user program directory. Keep the default or enter your selected writable program directory; Browse opens directory selection. Keep library data outside this directory.

Figure 5. Check your choices, install missing official prerequisites if requested, then select Install.

Figure 6. Close affected clients and finish/cancel work before changing features, repairing or removing this installation.

Figure 7. The refreshed native completion fixture shows checked client launch and unchecked Open documentation as independent choices. Select either, both or neither, then Finish. Maintenance and terminal failure/cancellation results suppress these choices.

Actual transaction outcomes

These captures come from completed full-UI Windows Installer journeys in a separate ordinary account on a disposable Windows CI runner. Progress follows native engine events. The installation image uses the exact packaged payload; maintenance, upgrade and rollback images use owned package fixtures with the production installer authoring. Native client reporters verify independent completion actions and user identity. These fixtures do not represent an additional published release or an attended installation on the operator's computer.

Figure 8. Installation displays actual engine progress and phase text. Cancel requests cancellation while the operation remains cancellable; rollback can take time before setup closes.

Figure 9. Successful repair restores the owned program bytes and ends with insonic repaired. Fresh-install client and documentation choices are absent.

Figure 10. Successful removal ends with insonic removed. Libraries, media, settings, models and credentials remain outside program removal.

Figure 11. Cancellation during execution returns native code 1602 and shows Setup cancelled after rollback. This cancellation fixture verifies the prior registration and owned bytes; coordinated upgrade recovery uses the setup EXE.

Figure 12. The controlled failed upgrade returns native code 1603, shows the failure result and restores prior owned files. Raw MSI registration can remain advertised after this failure; use the setup EXE for coordinated restoration before return. A failed operation does not offer fresh-install completion actions.

Figure 13. A successful feature change ends with its own heading and one Finish action.

Figure 14. A successful upgrade ends with insonic updated. Client launch and documentation choices belong to successful fresh interactive installation.

Application walkthrough

These application images are real rendered controls from the compiled frontend using an isolated library and current shared CLI contracts. Their renderer is headless Chromium rather than native WebView2. Browser/viewport/source and image identities are recorded beside the captures. They contain fixture data, not a user's library. Policy-dependent Edge, SmartScreen and UAC prompts are described above; no unobserved OS dialog is presented as a screenshot.

Figure 15. Optional setup previews an editable library location outside program files. Keep the default or enter your chosen separate library directory, preview capacity, then save the location and continue.

Figure 16. Keep local backend defaults or explicitly choose the three storage roles before creating a library. Choose local defaults or complete the elected backend fields. Preflight before provisioning; service credentials remain transient protected inputs.

Figure 17. Optional processing follows successful library creation; import and supplied subtitles need no model download. Elect processing when wanted, or skip it and continue. Application installation alone does not prepare model inference.

Figure 18. Deferring setup leaves the ordinary Library controls available. Use ordinary Import controls without completing optional stages.

Support checklist

Record Windows edition/build, browser/version, selected package/version, exact warning or error text and available controls. Include whether the failure occurred during download, setup/MSI launch, prerequisite installation, maintenance or application first use. Omit private paths, account identifiers, keys and secrets. Open a GitHub issue with those details and the relevant package identity.