starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[Discussion] Windows Terminal without PowerShell for corporation in reference to #6010 #16036

New Issue
Closed
opened 2026-01-31 04:55:39 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 04:55:39 +00:00
Owner
Copy Link

Originally created by @gusbemacbe on GitHub (Dec 2, 2021).

Hello,

I was reading the discussion of the issue #6010, that it is possible to install an offline and unregistered version of Windows Terminal with an offline licence.

But our case is different.

The company, where we work as software analysts, developers and engineers, allow us to demand the addition of software to their own software central since they do not depend on PowerShell and on winget.

The company disables PowerShell and does not allow us to re-enable it. It does not allow us to install software that set PowerShell as default (except VSCode, in which we can change manually from PowerShell to Command Prompt or Git Bash). For this reason, Windows Terminal can not be approved, although we can change manually the default shell of Windows Terminal. The problem is PowerShell.

I was reading the README, that PowerShell is one prerequisites, but I saw the issue #6010, that they could install offline and unregistered version of Windows Terminal without depending on PowerShell.

Is there how the company install Windows Terminal without PowerShell and without winget?

Originally created by @gusbemacbe on GitHub (Dec 2, 2021). Hello, I was reading the discussion of the issue #6010, that it is possible to install an offline and unregistered version of Windows Terminal with an offline licence. But our case is different. The company, where we work as software analysts, developers and engineers, allow us to demand the addition of software to their own software central **since they do not depend on PowerShell and on winget**. The company disables PowerShell and does not allow us to re-enable it. It does not allow us to install software that set PowerShell as default (except VSCode, in which we can change manually from PowerShell to Command Prompt or Git Bash). For this reason, Windows Terminal can not be approved, although we can change manually the default shell of Windows Terminal. The problem is PowerShell. I was reading the README, that PowerShell is one prerequisites, but I saw the issue #6010, that they could install offline and unregistered version of Windows Terminal without depending on PowerShell. Is there how the company install Windows Terminal without PowerShell and without winget?
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 04:55:40 +00:00
claunia commented 2026-01-31 04:55:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 2, 2021):

PowerShell absolutely isn't a pre-requisite for installing the Terminal. You can use the Terminal with PowerShell, but if your company is dead set on blocking PowerShell, then you can always change the default shell to Command Prompt[1]. The Terminal will automatically default to powershell, but it doesn't need powershell, and it doesn't ship with powershell.

If you can't use winget, or the Store, then you can always download the msix from the https://github.com/microsoft/terminal/releases page, and unzip that. If the msix doesn't install, then you can always just run the windowsterminal.exe in that zip file "unpackaged", and it should work totally fine.

[1]: lmao that they block powershell but not cmd.exe, I'm sure you can do just as much with command prompt as you can with powershell, but hey, silly IT departments gonna silly IT.

edit: closing the issue because this seems answered. If you have any follow ups, we can continue the discussion here.

@zadjii-msft commented on GitHub (Dec 2, 2021): PowerShell absolutely isn't a pre-requisite for installing the Terminal. You can use the Terminal with PowerShell, but if your company is dead set on blocking PowerShell, then you can always change the default shell to Command Prompt<sup>[1]</sup>. The Terminal will automatically default to powershell, but it doesn't _need_ powershell, and it doesn't ship _with_ powershell. If you can't use winget, or the Store, then you can always download the msix from the https://github.com/microsoft/terminal/releases page, and unzip that. If the msix doesn't install, then you can always just run the `windowsterminal.exe` in that zip file "unpackaged", and it should work totally fine. <sup>[1]</sup>: lmao that they block powershell but not `cmd.exe`, I'm sure you can do just as much with command prompt as you can with powershell, but hey, silly IT departments gonna silly IT. edit: closing the issue because this seems answered. If you have any follow ups, we can continue the discussion here.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16036
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?