NOVABERDocs

Loading search index…

    Documentation menu

    Getting started

    Install Novaber with AI assistance

    1.0.2

    Novaber · Content reviewed

    On this page

    AI-assisted setup is for users who want an assistant to inspect Windows, prepare missing components and verify startup. The tool needs access to the intended computer; instructions in a chat or a claim of success do not establish what happened on that machine. For manual setup, follow installation and environment preparation.

    Confirm the target and scope

    Confirm the intended Windows x64 PC, any existing Novaber installation or custom directory, and running Docker workloads. Inspect first and retain compatible drivers, WSL and Docker. Failure to find Novaber in a default location does not justify reinstalling it.

    Installing the desktop, starting it, preparing the runtime and making a particular app usable are separate outcomes. If the desktop is installed but Docker has not started, report what remains incomplete.

    Read this version’s setup instructions

    Give the setup entry URL to an assistant that can operate the target PC. Ask it to use skill 1.0.2, read its matching references, inspect the environment and verify the outcome.

    Have the assistant read the versioned entry, the full skill, and the references needed for the current step. Use the version linked from this page for execution. This article explains the workflow; it does not replace the skill, release data or local evidence. Resolve inaccessible instructions before continuing.

    Continue from read-only checks

    Inspect Windows, an existing desktop installation, virtualization, drivers, WSL and Docker. Evaluate VRAM, memory and storage against the selected app. Inaccessible checks remain unknown or restricted rather than missing or passed.

    See setup diagnostics and startup verification for report fields and manual observations. Prepare missing components with the installation guide, and pin one official release using download verification.

    Complete steps that need your input

    You handle the installer’s license, location and scope choices, Windows elevation, account sign-in and necessary restarts using the actual interface. A managed device may require an administrator. The assistant should provide the verified local package path, the current step and what to check after completion.

    A program blocked by the AI tool is different from a Windows failure. Do not ask the assistant to bypass the restriction through another script. Use permitted checks in your own Windows terminal and return to the same workflow. See restricted and unknown checks.

    Verify the handoff

    Ask for separate results covering:

    • The actual installation directory, version and required runtime files.
    • Whether this attempt opened the installed Novaber and reached the workbench after environment checks.
    • WSL, the local Docker engine and any required GPU checks.
    • Whether Docker’s sign-in startup preference was saved, and whether the next sign-in was actually tested.
    • Unverified apps, models, tasks or exports, with the next step.

    Open the actual installation folder so you can locate the program. Opening a folder and verifying application startup are separate observations. Finish with the selected app’s small task and export checks.

    Resume after an interruption

    Before restarting, resolving permissions or changing assistants, retain the checkpoint below. Record completed and unfinished steps without exporting directory inventories or account data.

    Novaber setup checkpoint
    Recorded at:
    Confirmed target computer:
    Pinned release version and concrete official release URL:
    Downloaded filename and verification result:
    Actual installation directory and version:
    Last attempted step and actual result:
    Current startup observation, or unverified:
    Docker / WSL state and sign-in startup preference:
    Pending permission, license, restart or sign-in action:
    Next: reconfirm target, rerun read-only checks, revalidate release
    Unverified items:
    

    On resuming, read the same versioned entry, reconfirm the target and recheck components, the installation directory and the pinned release. Historical reports describe previous observations; Docker state after a restart and the current launch need fresh checks. Skip satisfactory components and do not create a separate background resume service.

    Remove passwords, tokens, full private paths and unrelated logs before sharing. Use the feedback guide when reporting a problem.

    Sources