15 guides
Updates, builds and bug reports
Keeping the app current, and telling us when it breaks.
Updating the app
Check for an update, the Updating screen at launch, and when one does not apply or fails.
- Check for updates and install oneIn NeuralVault 2.0 the app checks for an update when it starts and from Settings, Account, About; it downloads in the background but only installs when you press "Restart to install". *
- NeuralVault shows "Updating NeuralVault" when it startsIn the Beta build, NeuralVault checks for updates and installs them. When one is ready the "Updating NeuralVault" window appears as the app opens; you can also download the newest installer and run it over your copy.
- An update failed: what each NV-UPD code meansIn the Beta build, a failed update shows a code starting NV-UPD; your installed version keeps working and your files are safe. "No update information was found" (NV-UPD-001) means the update location did not have the file that lists the latest version; try again later, or download the newest installer.
- Update the Beta: download the new installerNeuralVault checks for updates and installs them. If an update does not arrive, or "No update information was found" (NV-UPD-001) shows, you can download the newest installer from the download page and run it over your copy; your vault is kept.
Builds and update channels
What Stable, Beta, Test and Dev are, the pink Beta bar, the locked screens, and how to read the About screen and build code.
- Update channels: Stable, Beta, Test and DevStable and Beta are the two public channels; Test and Dev are reserved for people Perpetual Technologies picks, and a Test or Dev build locks unless the signed-in account has been granted it.
- Read the About screen and the build codeSettings, Account, About names your version and build, the engine, shell and renderer versions and where the settings file lives, which is what a support reply asks you for.
- The pink Beta bar: what to expect from a Beta buildIn the Beta build, a pink bar across the top of the window reads "BETA BUILD" with your build code and version, then the warning "Expect bugs. Keep a backup of your vault."
- The screen says "The Beta is not released yet"In the Beta build, a screen reading "The Beta is not released yet" replaces the app when the Beta has not been opened to your account yet; nothing is wrong with your account or your notes.
- The app shows a locked screen: what each message meansIn the Beta build, a locked screen replaces the app when it cannot confirm that your account may run it; the title says why, and most causes clear by themselves.
When something breaks
The engine banner, a window that will not open, error codes, network errors, and how to report a bug so it reaches us.
- The engine is not running, or is restartingThe desktop app is a window over a separate engine process; a banner tells you when the engine stops, restarts or fails, and offers "Restart the engine" and "Open log folder".
- What a bug report sends, and what it hidesIn the Beta build, a bug report always carries your build code and nothing else unless you switch an extra on, and a live preview shows the exact text that will be sent with secrets and file paths already hidden.
- The bug report did not sendIn the Beta build, a failed send says "Nothing was filed. Your words are still here.", names the reason, and offers the private inbox; the usual causes are the network, an hourly limit on reports, or a missing build code.
- NeuralVault will not open, or the window is blank or stops workingIn the Beta build, work through this list when the app does not open or the window goes blank: it may already be running, a Reload may fix a crashed window, and the log file is at %APPDATA%\NeuralVault\logs.
- What an NV code means, and how to copy the detailsIn the Beta build, a failure shows a code like NV-ROUTE-002 with a plain sentence and a "Copy error details" button; the code always means one thing, so quote it when you write to us.
- Network errors and working offlineIn the Beta build, a network error means NeuralVault could not reach a service; your notes and a local model keep working offline, but signing in, plan checks, cloud models and updates need the internet.