The pinned repository includes Windows help pages and screenshots. They are historical documentation, not evidence of a current supported installer. One screenshot explicitly displays a 2.0 alpha-era title. Its menus and platform assumptions must not be presented as a verified modern KH interface.
Identify the executable first
Record where a binary came from, its version, architecture, linked libraries and relation to a source commit. A GUI window labelled “Icecast” does not establish that it is KH, that it includes the pinned changes, or that TLS and authentication features are enabled. Use the official project source and release information to establish provenance.
The ordinary and Windows indexes repeat much of the same documentation. The first Windows section discusses GUI operation; the second repeats the configuration reference. The third section is an unfinished documentation stub. This handbook maps those materials to tasks instead of turning each duplicate or stub into an authoritative instruction.
Translate GUI actions into operational checks
| Historical activity | Required check on the actual installation |
|---|---|
| Select a configuration file | Full path, file permissions and active file identity |
| Start the server | Startup log, port binding and correct service account |
| Inspect a statistics tab | Current XML fields and authentication scope |
| Manage mount users | Active source, supported backend and private user file |
| Stop or restart | Source recovery, listener interruption and log closure |
Do not run with administrator privileges merely to make an incorrect path work. Place writable runtime data in suitable locations, protect secrets and configure the Windows firewall deliberately. A foreground GUI session is not automatically a supervised service.
Test the installed combination
On an isolated Windows host, verify startup, one source, one listener, failed admission, restart and certificate handling if supported. Compare logs against the exact configuration. Historical screenshots are reviewed evidence about the old documentation only; they are not reused as screenshots of a tested current installation. This implementation did not execute a Windows KH binary.