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

Windows Terminal install fails #13

Open
trossr32 opened this issue Sep 19, 2022 · 3 comments
Open

Windows Terminal install fails #13

trossr32 opened this issue Sep 19, 2022 · 3 comments
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed wontfix This will not be worked on

Comments

@trossr32
Copy link
Collaborator

Windows Terminal is currently installed via chocolatey but this process is now failing. Looks like this is currently not possible without manual intervention: microsoft/terminal#3097 (comment)

Suggest attempting to use winget for WT install instead.

@trossr32 trossr32 added the bug Something isn't working label Sep 19, 2022
@trossr32
Copy link
Collaborator Author

Can't install winget on the Windows Sandbox easily because of this issue: microsoft/winget-cli#1779

Can't use scoop as it won't install in an admin terminal and it seems you are always the admin in the sandbox.

May as well leave this issue open as a reminder to periodically check to see if winget is improved or the cholatey issue is fixed. Or someone has a better idea!

@trossr32 trossr32 added the help wanted Extra attention is needed label Sep 19, 2022
@trossr32
Copy link
Collaborator Author

trossr32 commented Mar 1, 2023

Windows terminal install via chocolatey seems to be working again (Windows 10).

@BanterBoy can you test this in your Win 11 environment and close this ticket if Windows Terminal installs successfully in the sandbox for you, please?

@trossr32
Copy link
Collaborator Author

trossr32 commented Mar 4, 2023

Tried looking at this again this morning but got caught up in a tirade of appx and msixbundle bullshit. The crux is that MS does not support Microsoft Store in a Windows Sandbox, and trying to install manually is a complete PITA.

In theory this is supposed to work (and might in a non-sandbox environment):

function Test-InstallWingetLatest {
    [string]$downloadUri

    try {
        $json = Invoke-WebRequest -Uri https://api.github.com/repos/microsoft/winget-cli/releases/latest | 
            ConvertFrom-Json
        
        $downloadUri = $json.assets | 
            Where-Object { $($_.browser_download_url) -like '*msixbundle' } | 
                ForEach-Object { $_[0].browser_download_url }
    }
    catch {
        return
    }

    if ([string]::IsNullOrWhiteSpace($downloadUri)) {
        return
    }

    Invoke-WebRequest -Uri $downloadUri -OutFile .\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle
    Invoke-WebRequest -Uri https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx -OutFile Microsoft.VCLibs.x64.14.00.Desktop.appx
    Add-AppxPackage Microsoft.VCLibs.x64.14.00.Desktop.appx
    Add-AppxPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle
}

But in a sandbox there's no Windows.UI.Xaml (v2.7) dependency installed, which is required. There doesn't seem to be an obvious way of finding and installing this.

The only other option would perhaps be to pull wt from github and try to build and deploy, but that seems to be far too much effort when one could just use Powershell and wt is a nice to have.

Going to abandon further investigation into this; suggest the wt feature is removed from the script. MS may never allow MS Store to be available in a sandbox, so this may never get resolved. Just a limitation of the system 🤷‍♂️

@trossr32 trossr32 added the wontfix This will not be worked on label Mar 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants