


Preview release: %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json.Stable release: %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json.The exact location depends on the app variant you installed, but it’s always in the user profile: The location of the Windows Terminal settings file is hard-coded (not a great design choice). Hard-Coded Settings File Location Where is the Settings File Located?

This provisions the package so that any user logging into the machine will have the installation registered for them. If you’re provisioning a Windows image, you can preinstall Windows Terminal with the PowerShell cmdlet Add-AppXProvisionedPackage.

There is no per-machine (AKA, all users) installation option, which really is a shame and poses multiple problems. Problems Terminal Cannot Be Installed per Machine (for All Users)Īs an MSIX application, Windows Terminal can only be installed per user. Please login as the user and explicitly install this package. The application cannot be started for the target user. If you expect Windows Terminal to behave like any other application, you might get the following error: It presents entirely new problems, however, in a secure setup with a standard user for day-to-day operations and a separate admin account for tasks that require elevation. Feature-wise, Windows Terminal is a fantastic replacement for the dated console host.
