Getting started
Setup diagnostics and startup verification
1.0.2
Novaber · Content reviewed
On this page
When installation fails or an apparently installed program will not start, identify the blocked layer: desktop files, the current launch, WSL / Docker, local GPU access, or the app and models. Reinstallation does not replace this diagnosis.
Download and verify the read-only probe
The official diagnostic script reads system and installation evidence. It does not install software, launch Novaber or upload reports automatically. Verify its SHA-256 against the setup package manifest, then review the file. Never pipe a network response into Invoke-Expression.
In an ordinary 64-bit Windows terminal on the intended PC, open the download directory and choose an installed PowerShell:
powershell.exe -NoLogo -NoProfile -File ./Test-NovaberSetup.ps1
For PowerShell 7, use pwsh.exe -NoLogo -NoProfile -File ./Test-NovaberSetup.ps1. Do not elevate automatically for diagnosis; inaccessible checks are reported as restricted or unknown.
Use a custom installation directory
powershell.exe -NoLogo -NoProfile -File ./Test-NovaberSetup.ps1 -InstallPath 'D:/Apps/Novaber/Novaber.exe'
Replace the example with your known EXE path. The option reads file version resources and installation-drive free space without launching the file. Default discovery checks uninstall records and standard paths; no discovery does not prove absence.
-CommandTimeoutSeconds accepts 1–30 seconds, defaulting to 8. A timeout remains insufficient evidence rather than proof of a broken component.
Interpret the report
Normal output is one JSON object with schemaVersion: 1, the tool version, UTC check time and checks. Each check contains a status, reason classification and evidence. Exit code 0 means a report was generated, not that setup passed. Also read permission and tool restrictions reported by the terminal.
| Status | Meaning and next step |
|---|---|
pass | This observation succeeded; other layers and overall readiness still need checks. |
missing | Evidence of absence; confirm the component is needed before installing. |
incompatible | The target is outside this check’s scope, such as remote Docker or a mismatched architecture. |
restart-required | A pending restart was observed; recheck after handling it. |
permission-denied | Access or tool restrictions prevented evidence collection; this does not mean absent. |
unknown | Timeout, failure or insufficient evidence; obtain further observations. |
Recognize the limits of a pass
- Windows: an x64 workstation check does not establish current Microsoft or Docker support.
- Memory and disks: measured capacity is not an app-specific sufficiency result. Docker data, models and outputs may use other drives.
- Virtualization and restarts: missing firmware fields do not prove disabled BIOS virtualization. No known restart signal does not guarantee that no restart is needed.
- WSL: enabled features do not establish a sufficient WSL version. Older inbox WSL may lack a version command; interpret other evidence too.
- GPU: host
nvidia-smisuccess is a host observation. Verify container GPU access separately. - Docker: inspect a confirmed local engine. A remote context does not establish this PC’s readiness, and a responding Linux engine still requires a WSL2 backend check.
Handle restricted and unknown checks
If script execution is blocked, inspect Get-ExecutionPolicy -List in your own terminal to distinguish personal defaults, organization policies and AI-tool restrictions. Ask an administrator to handle managed policy. Use an approved execution route without globally relaxing policy. See Microsoft’s execution policy documentation.
After a tool explicitly blocks wsl.exe, do not rerun a full probe that still calls WSL. If permitted, use -SkipWsl for other checks; WSL remains restricted rather than passing. Run wsl --status and wsl --version in your own Windows terminal, or deliberately handle permissions in the tool’s official settings before rechecking.
Verify installed files and the current launch
Wait for explicit wizard completion, then inspect the installed Novaber.exe version and resources/app.asar, resources/app-update.yml, resources.pak and icudtl.dat. A trailing zero fourth version component may be compared with the corresponding three-part release, while retaining the observed value. Do not execute an uninstall command during diagnosis.
Open the actual EXE’s parent directory and confirm this installation’s path. Shortcuts, uninstall records and historical logs are supplementary evidence. A missing shortcut does not by itself justify reinstalling, particularly at a custom location.
Start the installed program and observe current environment checks finishing, the workbench and the displayed version. A process, update-check success or development-mode screenshot alone is not startup acceptance. Record a missing or disappearing window and investigate its cause.
Then check Docker / WSL, the selected app and models, and perform a small task and export. Historical read-only extraction of an installer did not validate silent flags or actual wizard cancellation and failure paths, and does not establish this PC’s installation.
Share evidence and continue
Review custom paths, errors and log excerpts before sharing, removing passwords, tokens, private addresses and unrelated personal details. The probe minimizes exported evidence, but custom paths can still expose private information.
Prepare a feedback report. Before a restart or handoff, retain the necessary resume checkpoint.