Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
gusbemacbe opened this issue Dec 2, 2021 · 1 comment
Labels
Issue-Question For questions or discussion Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Answered Related to questions that have been answered

Comments

@gusbemacbe
Copy link

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?

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Dec 2, 2021
@zadjii-msft
Copy link
Member

zadjii-msft commented 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 zadjii-msft added Issue-Question For questions or discussion Resolution-Answered Related to questions that have been answered labels Dec 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Question For questions or discussion Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests

2 participants