mirror of
https://github.com/storytold/craft-launcher.git
synced 2026-11-02 18:07:04 +00:00
Jeremy
46cffe6527
A real run showed three separate prompts are fragile: they look identical, so a refused
install was followed by a refused put-back (read as a retry), leaving FilmCraft uninstalled.
For an all-users copy, removal, install and put-back now run in one elevated session, as
Update all's batch does, with both checked packages held unchanged meanwhile. Saying no
changes nothing; once it is yes, the put-back needs no second answer. The session's exit
code says which step stopped it. Product codes must have the exact {GUID} shape to reach
it. Per-user copies need no permission and keep the step-by-step route, which is also the
fallback when the elevated session cannot start.
The generated script is tested for real with cmd.exe standing in for msiexec. Those tests
take a lock: in parallel the stand-in sometimes never started (out-of-range code, no
marker), which the script rightly treated as a failed step.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>