Skip to content

Getting started

Windows 10 or 11, x64, with the .NET 10 Desktop Runtime. Setup checks for it and offers the download page if it is missing.

  1. Download the latest WinMux-<version>-win-x64-setup.exe from the releases page.

  2. Optionally, check it against checksums.txt, published with every release:

    Terminal window
    (Get-FileHash -Algorithm SHA256 .\WinMux-0.7.9-win-x64-setup.exe).Hash.ToLower()
  3. Run it. It installs for your Windows account only, into %LOCALAPPDATA%\Programs\WinMux, and asks for no administrator rights.

WinMux needs the .NET 10 Desktop Runtime; setup offers the download page if it is missing. After that, WinMux keeps itself current — see Updates. It is listed in Settings → Apps → Installed apps, and uninstalling it there removes the program folder but keeps your sessions and settings in %APPDATA%\WinMux.

Terminal window
git clone https://github.com/rennerdo30/winmux
cd winmux
.\scripts\run.ps1

run.ps1 builds the solution and launches it. .\scripts\publish.ps1 produces the same versioned zip the releases carry.

  1. Split the window. Split right and Split down on the toolbar, or Ctrl+B then % and ".

  2. Put something in a pane. New opens a terminal. Its dropdown lists every profile you have, including installed applications found through the Start Menu.

  3. Make a tab group. Tab group turns the focused pane into a stack of tabs. Tab groups nest, so a tab can contain a split that contains more tabs, and each group’s strip can sit on any edge.

  4. Save it. The session saves itself continuously; the disk icon forces it now, and its dropdown has Save as… if you want several named layouts.

Open it again tomorrow and the panes come back, in the same shape, in the same directories.

Ordinary startup restores your saved panes without adding another CMD. To request one CMD at a specific folder on either cold or warm startup, run:

Terminal window
WinMux.exe --open-directory "C:\path to\folder"

From Explorer’s address bar or Windows Run, use winmux --open-directory "C:\path to\folder". If WinMux is restoring, the new tab waits until its panes are ready. Without a saved session, the default CMD and file browser both use the requested folder, with just one CMD in total. Relative paths use the caller’s directory. Missing, invalid or unavailable folders are refused before session/settings work; use a mapped drive for a UNC folder because CMD cannot use UNC working directories.

While WinMux is already running, bare winmux still adds a CMD tab at the caller’s folder to the active window. A bare cold launch restores only; it does not infer folder intent from Explorer or the working directory. Existing CMD panes saved by earlier versions are kept.

A positional session file cannot accompany --open-directory; specify only one session file. --keymap path.json and --no-prefix still work on cold startup, including with a folder request. Session/keymap/no-prefix arguments are refused while WinMux is already running.

Sessionsession.toml in %APPDATA%\WinMux, or whatever you opened
Settingssettings.toml in your user profile
Profilesprofiles.toml, beside the settings
Application quirksforeign-app-quirks.json beside the executable — editable

Every one of them is text, and the Settings page shows you the exact paths.