VentoyStudio, a GUI to generate autounattend.xml and ventoy.json for Windows images

[Tim0219800]

Ventoy already has everything needed to apply an answer file: auto_install,
several templates per image, a boot menu to pick between them, variable
expansion. What it has never had is something to write those files.

So I built one: VentoyStudio, a small Windows GUI that generates the
autounattend.xml and merges the matching auto_install entry into
ventoy/ventoy.json.

https://github.com/Tim0219800/VentoyStudio

What it does

• reads the ISO without mounting it — version, build, editions, language (UDF
  first, ISO9660 as a fallback)
• local account, no mandatory Microsoft account, OOBE fully pre-answered
• debloat, dark theme, wallpaper, taskbar settings
• 71 winget packages in a searchable catalogue, or any id you type
• a custom PowerShell script at first logon
• several profiles per image, with autosel, timeout and the
  auto_install_uefi / _legacy suffixes — the part no other tool exposes
• installs Ventoy itself on a blank drive, or removes it

What it deliberately does not do

It never modifies Ventoy, GRUB or your ISOs. It never writes
DiskConfiguration, so the disk and partitions stay the user's choice in Setup.
It writes no LabConfig keys either, since Ventoy already applies the hardware
bypass earlier and more cleanly than an answer file can — the UI only exposes
the ability to turn that default off.

ventoy.json is merged, never regenerated: plugins it does not manage
survive byte for byte.

Status

Validated end to end by a full Windows 11 25H2 install in a VM — from the drive
to the desktop, no questions asked, software installed. 157 frontend and 67
backend tests. MIT licensed. Ventoy is not bundled: it is downloaded from its
official release and its SHA-256 verified before anything runs.

The binaries are unsigned, so Windows will show a SmartScreen warning. SHA-256
sums are in the release notes.

Feedback welcome, especially on the auto_install edge cases — a lot of the
behaviour I relied on is only visible in ventoy_plugin.c, and I would rather
be told now if I read something wrong.