Installing and Updating

Installing and updating

Beta test builds are available from the Releases page. The beta exe is unsigned and has no self-update. A public beta will start in Phase 13, and the first signed release with auto-update ships as version 1.0.0 in Phase 14.

Running the beta

The beta exe (OpenNote_Windows64.exe) is unsigned because code signing costs money and is reserved for the official releases. Windows will show a SmartScreen warning about an unknown publisher. To run it, click More info, then Run anyway.

There is no installer and no self-update in the beta. To keep your beta build up to date, download the latest release from Releases and replace your current exe. To run it at the same location (for example, %LOCALAPPDATA%\Programs\OpenNote\), you can quit the app and move the new exe there.

Your notes and settings are kept elsewhere and never affected by replacing the exe. See Privacy and your data for the folders.

When updates arrive (Phase 14)

In the final release, OpenNote will check for a newer version at start-up and every six hours. If there is a newer version, the app downloads it quietly in the background. A "Update ready" notice appears. Choose "Restart to update", or just close the app.

In Settings, you will choose how updates behave:

• Install updates automatically (the default).
• Ask first.
• Check by hand.

You can also skip a version, or join the beta channel.

Going back a version

In the final release, Settings will offer "Go back to the previous version" in one click. An older version opens newer files read-only instead of changing them, so going back is always safe.

Why updates never touch your notes

The exe holds no personal data, so replacing it can't delete anyone's work. Your notes, settings, and search index all live in standard Windows folders outside the exe. Updates never apply while you have unsaved changes or an active recording.

Who can publish an update

Each signed release is signed with a private key that only the release workflow can use. The matching public key is built into the app. Without the private key, nobody can push an update to OpenNote, even from a fake server.

For more details, see Releasing and section 14 of the development plan.