Docs

Install guide

Requirements, installer options and updating.

Most people only need Option 1. Options 2 and 3 are for building Ember yourself.

Requirements

Which release?

You can also switch from inside Ember: Settings, Updates, Release channel moves the installation to the newest Stable or Beta version after you confirm.

Option 1: the installer (easiest)

Download Ember-Setup-<version>.exe from the releases page, run it, read and accept the Terms of Use, and follow the pages. It installs the .NET 8 and Visual C++ runtimes if your PC lacks them, adds the services, and downloads the PawnIO driver (checked before it runs). Ember appears in the Start menu and under Installed apps in Windows Settings, where you can also remove it.

Windows will show an "unknown publisher" warning because the installer is not code-signed yet (see signing.md). You can check the file against the .sha256 next to it on the releases page first: Get-FileHash Ember-Setup-<version>.exe.

Silent install: Ember-Setup-<version>.exe /S /ACCEPT. Add /D=C:\Path\Ember for another folder, /NODESKTOP for no desktop shortcut, /NOPAWNIO to skip the driver. /ACCEPT says you have read TERMS.md. The installer writes a log to %TEMP%\EmberSetup.log.

Option 2: from source, with one script

Build the release folder once. In PowerShell, from the repository folder:

scripts\build-release.ps1          # fetches OpenRGB and the Microsoft runtimes, publishes everything, writes dist\Ember-<version>.zip and dist\Ember-Setup-<version>.exe

Then, in an elevated PowerShell, from the unzipped dist\Ember-<version> folder:

scripts\install-ember.ps1          # installs to C:\Program Files\Ember, adds both services and a Start Menu shortcut

Run the same script again to upgrade; your settings are kept. An installed Ember can also update itself: Settings, Updates, Check now, then Update now. scripts\uninstall-ember.ps1 removes it (add -RemoveFiles to delete the program files too).

Option 3: by hand

The steps the script follows:

  1. Fetch the bundled OpenRGB (checks a pinned SHA-256) and publish:

``powershell scripts\fetch-openrgb.ps1 dotnet publish src/Ember.Service -c Release -r win-x64 --self-contained false -o publish\service dotnet publish src/Ember.Watchdog -c Release -r win-x64 --self-contained false -o publish\watchdog dotnet publish src/Ember.App -c Release -r win-x64 --self-contained false -o publish\app ``

  1. In an elevated PowerShell, install PawnIO (downloads the official release and checks its SHA-256 and signature):

``powershell scripts\install-pawnio.ps1 ``

  1. Copy publish\service\* to a folder only administrators can write, such as C:\Program Files\Ember\, then, elevated:

``powershell scripts\install-service.ps1 -ExePath "C:\Program Files\Ember\Ember.Service.exe" ``

The service runs as LocalSystem, so the script refuses folders that normal users can write.

  1. Copy publish\watchdog\* to C:\Program Files\Ember\Watchdog\, then, elevated:

``powershell scripts\install-watchdog.ps1 -ExePath "C:\Program Files\Ember\Watchdog\Ember.Watchdog.exe" ``

  1. Run publish\app\Ember.App.exe as your normal user. Open the Fans page, test one System Fan header, then enable it. Close any other fan-control program first.

If you install PawnIO after the service, run Restart-Service EmberService (or press Restart services on the Devices page). To remove the service, run scripts\uninstall-service.ps1 (elevated).

Updating

Ember checks for updates when it starts and every few hours, and asks before it does anything: Update now, Remind me later or Skip this version. Settings, Updates has Check now and the Release channel. The installer is checked against the checksum published with the release before it runs.