Windows desktop runtime¶
Build natively on Windows x64 with Python 3.13+ and Node.js 24 LTS. Git Bash runs
cd electron && ./build-desktop.sh --win; builds remain local and use
--publish never. The installer includes its own pinned Python interpreter and
binary wheels. End users do not need a Python or Node.js installation.
The Windows runtime lock records every upstream URL and SHA-256 checksum. Downloads are verified on reuse, packages are installed offline, and build tools, bytecode and absolute installation records are removed from the payload. The same dependency and architecture checks run against the final packaged resources. The runtime is isolated from user Python settings and fails closed instead of falling back to a system interpreter.
Windows qualification must cover a clean installation, first launch, basic file opening, uninstall and reinstall. An installer build alone does not establish GUI or graphics support for every Windows device. Existing macOS and Linux runtime locks and installation paths are unchanged.
VTK is loaded through its explicit vtkmodules interfaces. The aggregate
import vtk also loads optional testing and VR plugins and can stall on Windows.
Startup verifies core VTK, PyVista geometry and the server dependencies; optional
OSPRay capability checks import only the ray-tracing module. This follows
Kitware’s import guidance.
Website installer and updates¶
The Windows x64 website download is an unsigned NSIS installer, qualified on Windows 11. It is separate from any future Microsoft Store/MSIX package. Download it from Vibyverse and compare its SHA-256 with the published checksum. Windows updates currently use a fresh installer downloaded from that page; the automatic desktop updater does not install Windows releases. Existing documents and settings are retained.
Graphics requirements¶
The bundled Python, PyVista and VTK libraries still need a suitable Windows graphics backend. The native qualification used software OpenGL in a virtual machine; it does not establish compatibility with every GPU or driver. Mesa is not bundled in the installer. A virtual machine without a suitable graphics driver needs its own software graphics setup. The tested software-rendering path does not establish large-volume or ray-tracing performance.