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

Include Windows Terminal in Windows Sandbox #13870

Open
Stanzilla opened this issue Aug 29, 2022 · 7 comments
Open

Include Windows Terminal in Windows Sandbox #13870

Stanzilla opened this issue Aug 29, 2022 · 7 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Tracking-External This bug isn't resolved, but it's following an external workitem.

Comments

@Stanzilla
Copy link
Contributor

Description of the new feature/enhancement

Currently, Windows Sandbox does not come with Windows Terminal, it would be nice to have it installed in there by default.

Proposed technical implementation details (optional)

@Stanzilla Stanzilla added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 29, 2022
@ghost ghost added 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 labels Aug 29, 2022
@zadjii-msft
Copy link
Member

Huh. I kinda just imagined that Windows Sandbox would use the same build as the host OS, so if you're on Windows 11, the Terminal would be preinstalled there just the same as it is on the host...

@Stanzilla
Copy link
Contributor Author

Huh. I kinda just imagined that Windows Sandbox would use the same build as the host OS, so if you're on Windows 11, the Terminal would be preinstalled there just the same as it is on the host...

I thought the same but it looks like it is super stripped down, can't even install store apps etc.

@roysubs
Copy link

roysubs commented Sep 18, 2022

Windows Sandbox is a completely stripped down image. Hence, Microsoft won't include requests for application X, Y, Z to be included. The problem here is that no Store (Metro) app can be installed in Windows Sandbox (including Terminal). Hopefully, Microsoft will include Store support in a future update as this is quite a big omission, considering that it is Microsoft's own app deployment technology for Windows(!)

@carlos-zamora carlos-zamora added Product-Terminal The new Windows Terminal. Tracking-External This bug isn't resolved, but it's following an external workitem. and removed 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 Mar 20, 2023
@carlos-zamora
Copy link
Member

Tracking internally with MSFT:36913286

@arc-hbas
Copy link

@carlos-zamora any updates from that internal track?

@carlos-zamora
Copy link
Member

Nope. No updates still.

@arc-hbas
Copy link

Thanks for the quick reply @carlos-zamora!

For those of you still wanting some way to execute Windows Terminal within a sandbox, I would suggest downloading and extracting the portable ZIP (see details here). You can automate this somewhat with windows sandbox by creating a wsb configuration file (see here) and executing a script on logon to download and extract the Windows Terminal portable zip.

DownloadWindowsTerminal.ps1

Invoke-WebRequest "https://aka.ms/terminal-canary-zip-x64" -OutFile "$home\Downloads\Terminal.zip"
Expand-Archive "$home\Downloads\Terminal.zip" -DestinationPath "$env:ProgramFiles\Windows Terminal"

# Other logic to add start menu and desktop shortcuts....

Windows Sandbox Dev.wsb

<Configuration>
  <MappedFolders>
    <MappedFolder>
      <HostFolder>C:\Users\{USER}\Desktop\ForSandbox</HostFolder>
      <ReadOnly>true</ReadOnly>
    </MappedFolder>
  </MappedFolders>
  <LogonCommand>
    <!-- Logon PS script how-to: https://stackoverflow.com/a/64812427/10388359 -->
    <Command>powershell -ExecutionPolicy Unrestricted -Command "start powershell {-noexit -File C:\Users\WDAGUtilityAccount\Desktop\ForSandbox\DownloadWindowsTerminal.ps1}"</Command>
  </LogonCommand>
</Configuration>

Here's a blog post that explains quite a bit more on how to pre-setup a dev-like environment. Author provides other scripts that generally work out of the box (minus one issue with winget).

Anyhow, thought I'd share.

Still would be nice if this worked out-of-the-box and would save us a bunch of prep time (installing winget + terminal takes ~5 mins!).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Tracking-External This bug isn't resolved, but it's following an external workitem.
Projects
None yet
Development

No branches or pull requests

5 participants