Audience: Customers and company administrators using Jakten Platform on Windows
Last updated: 2026-08-12
Applies to: Jakten Platform 2.0
Related: Single-User Quick Start, Troubleshooting
This guide explains how Jakten checks for suite updates, what the update stages mean, and how to apply an update safely from About & Deployment.
1. How Jakten checks for updates
Jakten Platform is a suite (Platform + bundled modules such as Risk and Estimate). Updates are published as a new suite installer, not as separate module downloads.
While the app is running, Jakten:
- Soft-checks the commercial release feed shortly after startup (~5 seconds)
- Soft-checks again about every 24 hours
- Updates banners and Deployment Health on the About page
Checks are non-blocking. A failed or offline check does not invent a “blocked” state by itself.
Jakten never downloads or installs an update automatically. You always choose Download & apply on About & Deployment.
2. Update stages (optional → warning → grace → blocked)
When a newer suite version is available, Jakten may show progressive notices based on how long the update has been available on your workstation:
| Stage | What you see | Can you keep working? |
|---|---|---|
| optional | Informational banner | Yes — fully usable |
| warning | Stronger notice | Yes — fully usable |
| grace | Countdown toward a deadline | Yes — until grace ends |
| blocked | Primary workflows gated until you update | About, Help, Connection, and Licensing remain reachable |
Timing comes from the published suite release (defaults are typically about 7 / 7 / 14 days for optional / warning / grace). Your company may see different timing if Northland publishes different policy values for that release.
3. How to check and update manually
- Open Jakten Platform and sign in.
- Go to About & Deployment (Shell route
/about, also linked from Help). - Review Deployment Health (license, validation, legal, update, migration, compatibility).
- Click Check for updates.
- If an update is available, read the release notes on the page.
- When ready, click Download & apply and confirm.
- Jakten downloads the installer, verifies its SHA-256 checksum, then launches the installer and exits cleanly.
- Complete the Windows installer prompts.
- Relaunch Jakten Platform from the Start Menu / desktop shortcut.
You do not need to re-enter your activation key after a normal suite update.
4. What happens during install
When you apply a suite update:
- The installer is staged under your Windows user data folder (not inside the install directory)
- Integrity is verified (SHA-256 must match the published release)
- The installer runs and replaces the application files
- On next launch, Jakten runs database migrations and compatibility checks before normal use
- Your projects, settings, and activation remain in user data (
%APPDATA%\Jakten Risk\)
If a required migration fails, Jakten fails closed (shows an error and does not open a half-migrated app). Contact support with the error text and your suite version from About.
5. No reactivation required
Suite updates do not require reactivation.
- Your company activation and deployment registration survive the installer replace
- Legal documents are only re-prompted when the published legal document version changes — not on every suite apply
- Seat assignments and project data remain in place
If About shows a licensing problem after an update, treat it as a support case — not as a normal update step.
6. Offline behavior
| Situation | Expected behavior |
|---|---|
| No internet when checking for updates | Check soft-fails; About shows an offline / check-failed note |
| Offline during optional / warning / grace | Cached policy may continue; Jakten does not invent blocked from a failed check alone |
| Offline when you try Download & apply | Download cannot complete until Authority is reachable |
| Working offline after a successful update | Normal local use continues; release checks resume when online |
Outbound HTTPS to Jakten commercial hosts is required for release checks and authorized downloads. See Network and Firewall Requirements.
7. Troubleshooting
| Symptom | What to try |
|---|---|
| “Check for updates” fails | Confirm internet access; retry later; note the error on About |
| Banner says update available but Download is disabled | Sign in; refresh status; confirm you are on the packaged desktop app (not a browser-only session) |
| Download fails mid-way | Retry Download & apply; confirm disk space and antivirus exclusions for Jakten |
| Installer refused (hash mismatch) | Do not bypass; contact support — the staged file did not match the published checksum |
| App will not start after update (migration error) | Capture the error dialog text; contact support. Do not delete %APPDATA%\Jakten Risk |
| Asked to activate again after update | Unexpected — contact support with company name and suite version |
| Primary workflows blocked | Open About & Deployment and apply the available suite update |
| Health shows migration / compatibility issues | Capture About → Deployment Health details for support |
When contacting [email protected], include:
- Company name
- Suite version, channel, and build ID from About & Deployment
- Deployment Health rollup and any failed dimension details
- Whether the issue happened during check, download, install, or relaunch
8. What support can see (Deployment Health)
About & Deployment shows a workstation fitness snapshot, including:
- License / validation / legal status
- Update policy stage
- Per-store migration status (Platform, Estimate, Risk)
- Suite/module compatibility
This is the first place to look before opening a support ticket about updates.