Terminal is one of those apps where many people lovingly fine-tune the app’s appearance and behavior, all of which goes into the settings file. Why is it a problem that there is an individual per-user settings file whose location cannot (easily) be changed? Consider our scenario: we want to use Windows Terminal from two different user accounts, a standard user and an admin user, both of which have individual user profiles.
Machine Wide Provisioning (Install for All Users).Add per-machine storage support to MSIX.There are two feature requests for a per-machine installation of Windows Terminal that I’m aware of: If you install a Store app from your standard user, it won’t be available in your admin account. Windows Store apps are always installed per user. The default installation type is via Windows Store, which is also the only way to keep Terminal updated automatically. In our scenario, we’re primarily concerned with the following: 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.
0 kommentar(er)
