Wintty Pro Enterprise
Wintty Pro Enterprise is Pro packaged for fleets. The build is the same terminal: persistent sessions that keep running when the app closes or updates, a terminal multiplexer, read aloud, streamer mode, Group Policy management, and default terminal registration. Sessions are scriptable too: the winttyc command-line tool lists, opens, and drives them from PowerShell. What changes is how the software reaches your machines and how you pay for it: a per-machine MSI your deployment tools distribute, and licensing arranged with us directly rather than through personal GitHub sponsorships.
GitHub sponsorships tie access to a personal account, which is the wrong shape for a fleet. Software the company bought should deploy to the machines the company manages, with no per-user sign-in in the loop.
The MSI
Pro Enterprise installs per machine, into Program Files\Wintty. The MSI writes one Start menu shortcut carrying the app identity and puts nothing on PATH. An upgrade replaces the previous install in place against a pinned UpgradeCode, so pushing a new version is a standard major upgrade with no uninstall pass first.
The install is visible to fleet tooling in the registry. HKLM\Software\Wintty\Install carries InstallVariant, set to Enterprise, and InstallVersion, set to the release version. Uninstall removes both, so one detection rule covers every machine and reports nothing after removal.
Three ways to deploy it
Intune. Wrap the MSI with Microsoft's Win32 Content Prep Tool and assign the wrapped app to your device groups. Detection points at the registry key above, so Intune knows which machines have which version.
SCCM. Configuration Manager deploys the same MSI as an application with the same registry detection. Nothing in the package is Intune-specific or SCCM-specific; it is one MSI either way.
Group Policy. Group Policy Software Installation can assign the MSI to computers, where it installs at startup. Settings come from the Group Policy settings below.
Group Policy settings
Six settings are Group Policy managed, read from the registry under SOFTWARE\Policies\Wintty. They apply in a fixed precedence: HKLM policy first, then HKCU policy, then the user's own preference, then the JSON config file, then defaults. A value set at HKLM outranks everything under it, so a locked setting stays locked.
DefaultProfile sets the profile managed users start with.
UpdateChannel picks the update feed: stable, beta, or tip. Set it to none and the app stops checking for updates, so your tooling owns updates from then on.
AllowedShells limits which shells the terminal will run, matched against the command line. An empty allowlist means unrestricted.
DisableContextMenu removes the context menu integration.
LogPath moves the app's log files where your collectors already read, an SCCM share for example.
RequireDefaultTerminalHandoff makes Wintty the default terminal for managed users. It writes the same DelegationConsole and DelegationTerminal values the Windows Terminal administrative template has covered since Preview 1.22, and re-checks the setting at every launch, so a user change does not survive the next start. The client refuses to write the nil-GUID value that would point the handoff at nothing.
The policy reference lists the registry key and value type for each policy.
Licensing and trust
Purchasing is arranged with us directly: invoicing, seat counts, and an entitlement that belongs to the organisation rather than to individual GitHub accounts.
Every install is Authenticode signed by Ship Digital Ltd through Azure Artifact Signing, with RFC 3161 timestamps so the signature outlives the certificate. Between the signature and the registry values above, your tools can verify both whose build this is and which version sits on each machine.
Machines without DirectX 12
Wintty Pro renders through DirectX 12 and checks for feature level 12_0 at startup; a machine without a qualifying adapter is turned away with an explanation rather than a blank pane. Pro Legacy is the same terminal on a DirectX 11 renderer for those machines, using WARP, Microsoft's CPU rasterizer, where no adapter qualifies. Remote Desktop is where this comes up most. Tested on Windows 11; Windows 10 is untested.
Talk to us
Tell us about your fleet and what your purchasing process needs to see, and we will find an arrangement that works. Reach out to @polyMatto on X, or by email, which is easy enough to find.