Group Policy to control default Terminal setting #22640

Closed
opened 2026-01-31 08:19:15 +00:00 by claunia · 1 comment
Owner

Originally created by @htcfreek on GitHub (Dec 10, 2024).

Since a year or longer I can choose if WT is the default conhost.

Is it possible to implement a policy that allows company admins to control this centralized?

Originally created by @htcfreek on GitHub (Dec 10, 2024). Since a year or longer I can choose if WT is the default conhost. Is it possible to implement a policy that allows company admins to control this centralized?
claunia added the Needs-TriageIn-PRNeeds-Tag-Fix labels 2026-01-31 08:19:15 +00:00
Author
Owner

@DHowett commented on GitHub (Dec 10, 2024):

Right now, enterprise administrators can use Group Policy to roll out registry changes as documented in this knowledgebase article.

@DHowett commented on GitHub (Dec 10, 2024): Right now, enterprise administrators can use Group Policy to roll out registry changes as documented in [this knowledgebase article](https://support.microsoft.com/en-us/windows/command-prompt-and-windows-powershell-for-windows-11-6453ce98-da91-476f-8651-5c14d5777c20).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22640