vibranceGUI v2.10.4
Two downloads. Take x64 unless you are on 32-bit Windows. Each zip is two files, no installer — unzip anywhere and run vibrance.GUI.exe. The title bar names the build: vibranceGUI (NVIDIA, x64, 2.10.4).
This is the last version you should have to download by hand. From here on, vibranceGUI can install its own updates — if you tell it to.
One-click updates
v2.10.3 added a tray notification when a newer version existed. Clicking it opened the download page and left the rest to you. Now it offers to do it.
Click the notification and vibranceGUI asks: here is the version you have, here is the version available, here is the folder about to be written to — install it? Say yes and it downloads the right build for your architecture, checks it, replaces its own files and restarts. Say no and it opens the download page, exactly as before.
It will never update itself without being asked. Not in the background, not silently, not "helpfully". That is a deliberate limit, and the reason is in this project's own recent history: v2.9.0 and v2.10.0 shipped an x64 build that could not detect an NVIDIA GPU at all, and it took a month and an outside bug report to find. A silent updater would have pushed that onto every machine running a perfectly good v2.8.0. A bad release should reach the people who chose to take it, not everybody at once.
What it is careful about
- The download is checked against the SHA-256 GitHub publishes for that exact file, before anything on your disk is touched. A corrupted or truncated download is refused rather than installed.
- Your old version is kept, renamed alongside the new one, until the next time vibranceGUI starts. If an update fails halfway through it is rolled back, so you end up with the version you had rather than half of two.
- If it cannot write to its own folder — because you unzipped it into Program Files, typically — it tells you and offers the browser instead. It will not ask for administrator rights.
Where that checksum stops helping
It proves the file is the one GitHub is serving. It does not prove the file is safe. These builds are unsigned, so if this GitHub account were ever compromised, the checksum would be replaced along with the file and the check would pass. Nothing except code signing fixes that, and this fork does not have it.
There is a second, more ordinary risk worth saying out loud: an unsigned program that downloads and runs another unsigned program is precisely the behaviour antivirus software is built to notice. If Defender or SmartScreen starts complaining about vibranceGUI, this feature is the most likely reason.
If any of that bothers you, the update is still just a zip with two files in it, and you can keep installing it by hand. Untick "Check for a new version on startup" and the app will not contact GitHub at all.
Everything else
Unchanged from v2.10.3 and the releases before it, whose notes still apply in full — including the caveats about what has and has not been watched working on real hardware. The restore-after-a-crash behaviour still has not been seen working end to end by anyone, and the x64 build still has not been played with beyond starting correctly.
813 automated checks across sixteen fixtures, green on both architectures. The update mechanism was also exercised end to end against the live release: a test installation holding v2.10.1 was upgraded to v2.10.3, with the checksum verified, a deliberately corrupted download correctly rejected, and the old version recoverable from its backup throughout.
Reporting problems
https://github.com/SwatX18/vibranceGUI/issues — the form asks for the title bar string first, which names the vendor, architecture and version in one line.
If you run an official build from vibrancegui.com rather than one of mine, report to juv's tracker instead — none of this fork's changes are in that build.
This is a fork build and it is unsigned. It is not an official juv release.