TL;DR: no code skills needed — run one PowerShell script on a Windows 11 gaming PC with an NVIDIA card and tell us what happened.
Since 0.4.3, TranscrIA ships a guided Windows 11 install: scripts/windows/Install-TranscrIA.ps1 checks your machine (Windows version, NVIDIA GPU, RAM, disk space per drive), asks two questions (target drive C:/D:/E:, bundled or slim image), then drives WSL2 + Docker Desktop + the Docker quickstart end to end. It is re-runnable after every reboot and each step was verified against official Microsoft/Docker/NVIDIA documentation.
What has NOT happened yet: nobody has watched it run on a real Windows machine. The honest status in our docs is "real-machine validation in progress" — this issue is that validation.
What a report looks like
- Windows 11 (or Windows Server 2022+), an NVIDIA GPU (8 GB VRAM or more), ~130 GB free (bundled) or ~60 GB (slim).
- Follow the two-command path at the top of docs/QUICKSTART_WINDOWS.en.md.
- Paste here: where it succeeded, where it stalled or asked something unexpected, and the final outcome (portal reachable at http://localhost:7870 or not). Screenshots welcome.
The most likely rough edges (flagged in the script's comments): the first Docker Desktop launch, the Ubuntu first-boot step, and winget behavior on a fresh machine. If it breaks there, that is exactly what we want to hear about — the last two external reports each produced a same-week fix.
TL;DR: no code skills needed — run one PowerShell script on a Windows 11 gaming PC with an NVIDIA card and tell us what happened.
Since 0.4.3, TranscrIA ships a guided Windows 11 install:
scripts/windows/Install-TranscrIA.ps1checks your machine (Windows version, NVIDIA GPU, RAM, disk space per drive), asks two questions (target drive C:/D:/E:, bundled or slim image), then drives WSL2 + Docker Desktop + the Docker quickstart end to end. It is re-runnable after every reboot and each step was verified against official Microsoft/Docker/NVIDIA documentation.What has NOT happened yet: nobody has watched it run on a real Windows machine. The honest status in our docs is "real-machine validation in progress" — this issue is that validation.
What a report looks like
The most likely rough edges (flagged in the script's comments): the first Docker Desktop launch, the Ubuntu first-boot step, and winget behavior on a fresh machine. If it breaks there, that is exactly what we want to hear about — the last two external reports each produced a same-week fix.