Skip to content
Search PyroSoft

Bourbon 26 development journal · Part 5 of 10

Activation, installers and knowing which program we launched

Small recovery fixes followed by more careful Windows software analysis.

By Mike Rodriguez2 min readDevelopment work: Oct 2 – 8, 2026Updated New

Sometimes the right update is a small one. Bourbon 26.10.2.5 fixed itch.io sign-in for people activating after a purchase, signing back in or setting up another Mac. Existing activated copies kept working. There was no reason to rebuild bottles or reinstall games to recover a purchase check.

The October 8 work then expanded the focus to Windows programs and installers. Opening an installer on a fresh setup prepared the core Wine runtime first. When an installation produced several similarly named programs, Bourbon preferred a unique exact match and asked for a selection when the result was ambiguous. If you explicitly chose a utility, that choice stayed yours.

That's the kind of detail that makes a launcher feel predictable. Picking a companion updater when you asked for the main application isn't helpful, even if both files technically run. The same update included a specific DPI correction for the verified PuTTY 0.84 x64 build, with explicit user overrides preserved.

Process tracking also became more precise. Launches retained records tied to their bottle and executable, Stop coordinated with the observer, and retries waited for the previous process to exit. A selected graphics backend alone stopped being enough reason to blame that backend for an unknown failure.

This is also where the current private development history has an import boundary. The October 8 import captured the existing Bourbon source; it wasn't the day all of those earlier features were first written. The older release notes supply that part of the timeline.

The practical result was a more careful handoff from analysis to execution. Detecting requirements could help choose a setup, while actual program windows and behavior still decided whether that setup worked.

Bourbon 26 development journal

View the journal

Live10 entries so farUpdated New (10 entries updated in the last 14 days)

  1. Part 1Bourbon 26: choosing the right way to playDevelopment work: Jul 31, 2026Updated , new
  2. Part 2When the menus work but the game world is blackDevelopment work: Aug 17, 2026Updated , new
  3. Part 3Making setup and repair less disruptiveDevelopment work: Aug 30 – Sep 6, 2026Updated , new
  4. Part 4Smart Play starts figuring out unfamiliar gamesDevelopment work: Sep 29 – 30, 2026Updated , new
  5. Part 5Activation, installers and knowing which program we launchedDevelopment work: Oct 2 – 8, 2026Updated , new
  6. Part 6Giving SteamOS its own place in BourbonDevelopment work: Oct 9 – 12, 2026Updated , new
  7. Part 7Keeping older tools and newer Steam clients in their own lanesDevelopment work: Oct 13 – 16, 2026Updated , new
  8. Part 8Native Steam integration and a library you can use from the couchDevelopment work: Oct 17 – 18, 2026Updated , new
  9. Part 9The audit that put saves and reset safety firstDevelopment work: Oct 19, 2026Updated , new
  10. Part 10Moving Bourbon safely, then making the verification fasterDevelopment work: Oct 19 – 20, 2026New

Arrow keys move through the results, Enter opens one, Command or Control with Enter opens it in a new tab. Tab and Shift+Tab change which kind of results are shown.