Skip to content
Search PyroSoft

Bourbon 26 development journal · Part 3 of 10

Making setup and repair less disruptive

Better readiness checks and more careful handling of active sessions.

By Mike Rodriguez2 min readDevelopment work: Aug 30 – Sep 6, 2026Updated New

When you open a gaming tool, a status check should tell you what's ready. It shouldn't quietly start a virtual machine or disturb another session just to find out. The late August Bourbon work focused on making that distinction much more dependable.

Version 26.8.30.13 improved recognition of existing verified Game Porting Toolkit installations and repaired the managed Windows stack after updates while keeping the Library available. Steam recovery checked the CEF packages actually present in the installation. Civilization IV and its expansions also received a dedicated DirectX 9 route instead of asking the graphics stack for geometry features that route couldn't provide.

The optional OS Experience work received its own safety changes. Read-only checks stopped launching UTM in the background, and recovery preserved existing VM bundles. That matters if you've already got a guest doing something useful. Looking at Bourbon's status shouldn't become an instruction to restart your other work.

The September 6 candidate continued in that direction. Runtime-specific networking checks avoided treating a healthy WineCX profile like a broken Wine Staging installation. Busy drive mappings were preserved, support output was redacted more carefully, and prepared Steam profiles could offer Open Steam without changing game assignments.

There was still a real problem on the board: fresh Windows Steam sign-in had rendered black on the M2 test Mac. The candidate notes explicitly left that unresolved. I want this history to include those moments, because a useful repair path and a successful packaging run don't automatically prove the client itself renders correctly. August's release record and September's candidate record describe different levels of completion, and the next work needed to follow the remaining visible failure.

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.