Skip to content

Wan2GP Desktop Launcher v3.0.1 — legacy launch fix + safe migration

Choose a tag to compare

@GKartist75 GKartist75 released this 20 Aug 16:55
· 79 commits to main since this release
f32a635

Wan2GP Desktop Launcher v3.0.1

Bug-fix release — fixes the v3.0.0 launch failure for users coming from an old
roaming AppData install, and makes migration + updates safe and opt-in.

🐞 What was broken (v3.0.0)

Some users upgrading from an older install whose data lived in the roaming AppData
profile (%APPDATA%\wan2gp-desktop) reported that v3.0.0 showed no window at
all
— only deleting Roaming\wan2gp-desktop and reinstalling helped.

Root cause: v3.0.0 ran the data-dir migration synchronously, before the first
window paint
. On a roaming-source install that move could stall (AV scanning a
large AppData tree, locked files handled late), blocking the pre-paint path so the
renderer never got its first frame. Removing the roaming folder fixed it because the
migration became a no-op.

✅ What's fixed (v3.0.1)

  • Migration is now deferred + opt-in. The app starts first, then offers a
    "Migrate to new location" dialog (startup prompt, dashboard MODELS banner,
    or Manage). Legacy roaming users always get a window now.
  • You choose where data goes. The dialog lets you pick the data dir,
    checkpoints, LoRAs, and outputs — preferred defaults pre-filled
    (C:\Wan2GP + C:\Wan2GP-Models), all editable. Nothing is hard-coded.
  • Clean move. Flattens the repo (no C:\Wan2GP\Wan2GP doubling), rewrites
    wgp_config.json model paths to the chosen locations, removes the now-empty
    roaming wrapper. Locked files are skipped, not fatal.
  • Progress feedback. Live progress bar on the slow copy-fallback path (big
    model folders never look frozen).
  • Auto-update is now manual-only. The Manage toggle is renamed
    "Check for updates on launch" and defaults OFF. autoDownload and
    autoInstallOnAppQuit are forced off in code, so closing the app never
    installs an update
    — only the explicit Check for updates → Download → Install
    & Restart
    flow does.

📦 Per-hardware GPU kernel wheels (auto-installed, same set as v3.0.0)

The installer detects your GPU and pulls the exact wheels it needs, re-synced on
every update. v3.0.1 pins:

Wheel Version
Python (uv) 3.11.14 (RTX 20–50) / 3.10.9 (GTX 10)
PyTorch + CUDA 2.10.0 + CUDA 13.0
Triton latest (~3.7.1)
SageAttention 1.0.6 (RTX 20) / 2.2.0 (RTX 30–50)
Sparge Attention 0.1.0
Flash-Attention 2.8.3
Nunchaku 1.2.1
GGUF llama.cpp CUDA 1.0.11
Lightx2v 0.0.2 (RTX 50 FP4 only)
bitsandbytes 0.49.2 (NF4)

RTX 20 → Sage 1.0.6 + Flash + Nunchaku + GGUF. RTX 30/40 → add Sparge + Sage 2.2.0.
RTX 50 → add Lightx2v. GTX 10/16 stay on the legacy CUDA 12.8 stack.

🔄 How to upgrade

  • From v3.0.0: install v3.0.1 over it. No automatic data move — use the in-app
    Migrate to new location if you still keep models in AppData.
  • From an old roaming install (the v3.0.0-stuck case): install v3.0.1. It now
    opens normally; then run Migrate to new location (or uninstall → close →
    delete Roaming\wan2gp-desktop → reinstall).

⚠️ Notes

  • Unsigned installer — the "unknown publisher" warning is normal for open-source
    software without a code-signing certificate. Local builds are unsigned; signing
    only happens on CI with the SignPath secrets.
  • Full change log: CHANGELOG-v3.0.1.md

Credits

  • DeepBeepMeep — creator of Wan2GP.
  • Tophness / Steve Jabz — original Wan2GP install scripts the launcher's
    pipeline is built on.
  • All Wan2GP Desktop Launcher users — thank you for the bug reports that
    surfaced the v3.0.0 launch failure.