In this guide1 / 5
Install the current Windows release once if version 2.2.13 or 2.2.14 shows a missing-feed update error. Pair this Companion with Studio and keep at least one browser approval active. Then open Updates in Companion and choose Check for updates; the website tab can be closed.
Review the available version and release notes, then choose Install and restart.
Watch download and validation progress in the app. You can cancel before activation or retry a failed operation.
After Companion restarts, confirm the new version in About and check your connection. Optional automatic checks do not install updates without your action.
The app authenticates with its protected device identity and downloads through the fixed Nexlock release service over HTTPS. An active browser approval grants update access; anonymous devices cannot download packages. Complete versioned packages must pass identity, version, runtime, size, required-file, archive-path and SHA-256 checks before activation. An approval error remains in the app with instructions to pair or restore access; checking or installing an update does not open a website.
Pairing records, slicer/profile paths, output location and exported models live outside versioned application folders. The prior payload remains available for startup rollback if an update cannot complete initialization.
A runtime-changing release can require the full Windows installer. Ordinary compatible app updates retain the installed launcher, runtime and shortcuts. Installer and app builds are separate: when the software hub says an app update is needed after installation, pair once and use Updates → Check for updates → Install and restart to receive the current features.
Run the current Windows installer once if your older app sends you to a browser for updates or version 2.2.13/2.2.14 reports the old missing-feed error. Exit the old instance from its tray menu before setup. The current installer also registers the Open Companion link and keeps your local settings and exports.
Internet relay becomes the normal connection. Saved local folder and legacy port/code values remain under Advanced compatibility; browser approvals for the new relay must be created once.
An existing compatibility session at /connector-update distinguishes connection problems, package delivery and returning to Companion. Keep the tab open during transfer, use Retry connection when offered, and follow any approved-folder reconnection prompt.
Package handoff is not confirmation of activation. Check the result and version in Companion after restart. If the browser link was opened directly or expired, start a fresh update check in the app. Current Companion releases keep the normal update workflow inside the app.
- Check the internet connection and the saved browser approval. Pair once if approval is missing or revoked, then use Retry. Updates do not require an open website tab after pairing.
- A checksum or package-validation error must be resolved by a fresh verified download. Do not edit manifests or staged files.
- Cancel leaves the active application in place. After a successful restart, verify the version in About.
- If startup recovery cannot restore a working version, run the latest verified Windows installer and keep the existing user-data folder.