Updates (Windows)

See how updates are downloaded, verified and installed, and what happens when an update fails.

NeuralScio checks for new releases and can install them for you. This page describes the behavior verified on Windows with real installers in a test virtual machine; it makes no promise about release dates or channels.

What happens during an update

  1. The app finds a newer release and shows an Update dialog with the version and release notes.
  2. When you choose Update now, the installer is downloaded to a temporary folder. Before it runs, the app checks its size, its SHA-256 hash and its Ed25519 signature against keys built into the app. A package that fails any check is discarded and nothing is installed.
  3. If a Writer document has unsaved changes, NeuralScio asks Save, Discard or Cancel before it closes. Cancel stops the update and keeps your work open.
  4. The app closes, the installer waits (up to 60 seconds) for the old files to be released, installs the new version in the same folder and scope, and starts NeuralScio again.

Install scope

  • New installs are per-user by default (no administrator prompt; files in %LOCALAPPDATA%\Programs\NeuralScio).
  • An existing all-users installation keeps its scope and updates in place; Windows shows one administrator (UAC) prompt.
  • The updater never moves an installation between scopes. If both scopes are registered, it refuses before closing the app and tells you why.

When something goes wrong

| Situation | What you see | Your data and the installed version | |---|---|---| | You decline the administrator prompt | An error in the update dialog; NeuralScio keeps running | unchanged | | The download is interrupted | The update does not start; you can try again | unchanged | | The signature or hash does not match | The update is refused | unchanged | | Files stay in use for more than 60 seconds (for example another Windows session) | The installer reports that files are busy and changes nothing; NeuralScio is started again and tells you the update was not applied | unchanged | | The result of an installer failure cannot be confirmed | NeuralScio is not restarted automatically; start it from the Start menu or run the installer again | check the version in Help |

There is no in-app rollback, and installing an older version over a newer one is not a supported or tested path: the installer does not block it, but nobody has verified that your profile and local databases stay readable by an older build. Do not downgrade to fix a problem. Make a copy of your data first (see Backup, Restore & Data Locations) and contact Support; a fix is delivered as a newer release or a published rollback release.

Reporting an updater problem

Include: the version before and after, per-user or all-users install, the dialog text, and the installer log. The installer log is written next to the downloaded package as <package name>.install.log inside `%TEMP%\NeuralScio\updates`. Remove personal paths and account details before sharing it (see Support).