Searching for “DGX Spark Windows” can mean several different things: connecting from a Windows laptop, replacing the Spark host operating system, or running Windows as a guest. This guide covers guest virtual machines in Team AI Box. The Spark retains its supported host system.
Team AI Box provides a virtual-computer interface for mounting installation media and using a virtual display in the browser. It does not distribute a preinstalled licensed copy of Windows, and it does not promise compatibility with every guest application.
Choose ARM64 installation media
DGX Spark uses an Arm CPU. For this workflow, choose compatible ARM64 installation media—not an ordinary x86-64 or AMD64 PC ISO. Use an official publisher source and verify the file against publisher information where available.
For Windows, use a suitable Windows 11 ARM64 ISO and review the applicable Microsoft license and installation requirements. For Ubuntu, select an ARM64 release and installer supported by the virtual hardware and your intended workflow. A distribution offering an Arm build does not mean every image format is a bootable ISO for this virtual computer.
The project’s MIT license applies to its own code and documentation. It does not grant a Windows license or change the terms of a Linux distribution, bundled software or firmware. See the project’s license scope.
Install through the virtual display
After installing Team AI Box, open Virtual Computers in the workspace and create a new computer for the guest you intend to install. Choose resources appropriate to the workload; do not modify an existing computer’s disk simply to try a new OS.
- Upload the authorized ARM64 ISO, or select the ISO from team drive.
- Mount it in the virtual optical drive using the installation/media controls.
- Start the new virtual computer and open its virtual display.
- Follow the operating system’s installer, choose its display language and create its guest account.
- When installation finishes, eject the installer when appropriate and boot from the guest’s system disk.
Before formatting, confirm that you selected the new virtual computer’s virtual disk.
Virtual display is not remote desktop
The virtual display acts like a monitor attached to the VM. It can show boot, restart and installation screens without first signing in to a remote desktop service inside the guest.
That does not remove the guest operating system’s own login screen. If Windows or Ubuntu asks for the account password created during installation, sign in to that guest account. Team AI Box’s workspace account and the guest account serve different purposes.
Remote desktop is an additional connection mode rather than a prerequisite for viewing the console. Audio is supported by the display workflow, but browser playback permission, the guest’s audio device and the selected output still matter. Install the drivers and applications required by your chosen operating system.
Share a demonstration deliberately
An owner can invite others to view or control a virtual computer. Prefer view-only access when presenting; hand off control when collaboration requires it. Shared control is a separate choice, and the owner can reclaim control. Do not expose an installation screen containing credentials in public screenshots.
For a shared appliance, read the team rollout guide before inviting everyone to use the same guest.
Set realistic expectations
ARM guest software and drivers need compatibility checks. A Windows ARM guest is not a guarantee that every legacy Windows program or peripheral works. Likewise, creating a VM does not establish GPU passthrough or native-speed GPU compute inside that guest.
VMs share the Spark’s finite resources with AI applications. Start with a useful workload, observe its behavior and adjust deliberately. Consult the public source and installation documentation for the current supported setup rather than bypassing firmware, TPM or image-integrity checks to force an unsupported combination.