VibeFuse v0.1.41 fixes the default Terminal on a computer that did not build the app.
What was going wrong
On the computer where VibeFuse is developed, `C:\vibefuse` already exists and is writable, and Windows PowerShell is installed. A downloaded copy on another Windows PC often cannot create `C:\vibefuse` (that needs an administrator), and the installer previously created that folder so only administrators could write to it. Starting the Terminal then failed before a shell appeared.
What changed
- If `C:\vibefuse` cannot be written, VibeFuse keeps its data in `%LOCALAPPDATA%\VibeFuse` instead of crashing.
- The installer grants Users permission to modify `C:\vibefuse` when it creates that folder.
- The Terminal looks for PowerShell 7, then Windows PowerShell, then Command Prompt, and skips a saved folder that does not exist on this PC.
- If Windows cannot create a pseudoconsole, the terminal host retries with the console files shipped inside VibeFuse.
- A failure is written into the terminal in red instead of leaving a blank widget.
Get it
Re-download VibeFuseInstaller.exe from fuseintelligence.org/downloads/VibeFuse/ or open Settings → About → Update.