It is hard to find Microsoft.VCLibs.140.00.UWPDesktop

Hi everyone,
After installing the suggested VClibs at - https://github.com/microsoft/terminal/issues/2369
the installer still shows:

(They said to open a new issue report)
Best Regards

Build this App on your own and make an appx.
It creates also the dependencies (Microsoft.VCLibs.x64.14.00.appx, Microsoft.VCLibs.x64.14.00.Desktop.appx)
Extract the downloaded msixbundle File and copy the created dependencies (Microsoft.VCLibs.x64.14.00.appx, Microsoft.VCLibs.x64.14.00.Desktop.appx) in the same Folder as the CascadiaPackage_xxx_x64.msix is and install it.

@bitcrazed I'm assigning this one to you per https://github.com/microsoft/terminal/issues/2369#issuecomment-535763987
The link you provided is to the desktop application redistributable, not the UWPDesktop redistributable.

Is there a reason why the dependencies are not in the Package?
The app installer needs always the dependencies, also if the dependencies are already installed...

The dependencies are not in the package because the dependencies need to be able to be updated without us releasing an update.

Thanks for the quick reply!
Is it possible to attach the dependencies as seperate download for those who has no access to the store?

The dependencies are not in the package because the dependencies need to be able to be updated without us releasing an update.

@DHowett
i think i've seen FluentTerminal managing to handle that as they ship the dependencies respectively (aside the msixbundle) and an installation script that way the install script managed to properly install everything
it also fixes the part where the store could / update be able to install it later on
that seems like it would be the perfect way for users here.

I've got the same issue on my side.
I think the project is too deeply connected to the windows store. It's depend of some package which is not accessible by everyone.
Is it possible to remove the dependance of the store ?

For now, in order to use it, I have to manually

build it from vs,
right click publish (shame)
generate my own certificate to sign it during publish
set a specific version, bad because it differs from official package
have to do it twice because there is a bug in the CascadiaPackage.??proj (because of the condition testing pfx existing before you need it so the first publish won’t sign the package ...)
ship it on a corpo shared server
ask user to activate DevMode
then manually run install.ps1

@DHowett-MSFT i’m very interested to know how that msbuild check can be fixed without running the assistant twice
Repro :
git clean -fdx > right click : publish
You’d see for example that the “bundle” combo of the wizard is set to “never” because the pfx check if it exists same for Signing
Also does the .vsconfig works on MsBuild tool 2019 ? So that I can build it from a CI ?

Thanks for your feedback on this everyone. It's very closely related to #3457 but will leave open for now since we're actively looking into several options here.
On the one hand, we'd like to reduce in-package dependencies so that we don't have to ship updates to the Terminal if, in this case, VC140 is updated. But on the other hand, it's not easy to find the correct out-of-package VC140 redist. We're exploring a few things right now. Stay tuned while we figure out some logistics.

What about first before changing anything add an artifact here with the content of the output folder of the build
The exact same step I mentioned earlier but from your CI

Update will still not work
probably still require devMode
but some team does have Visual Studio so they cannot build it
It’s just the full folder output to zip and push to github
This will not fix anything but until things are fixed that a good way to embrace users

As I mentioned in a previous comment this is what does FluentTerminal for the exact same issue
And so for it works great for them
another terminal ^^, that can be installed without store access

@tebeco Appreciate your thoughts here, but we're keen to try to minimize/avoid shipping others' dependencies and binaries for a variety of (predominantly servicing) reasons. We're discussing with several teams as I type and will update this thread with info once we've arrived at a workable solution.

Thx a lot for the “insight view”
Will wait “patiently” here ^^
For now I’ll continue to do manual build for our teammates

So my issue was closed and pointed to this thread.  However, I see no resolution.
I installed the UWPDesktop from the release notes, and still cannot install terminal.

So far i found absolutly no workaround at work either

I get the same thing as @tebeco on an offline Windows 10 Enterprise host. From what I've been able to determine, it seems like a permissions issue. If you manually try to go to the directory in file explorer, you can not, even as administrator. I changed ownership to the local Administrators group  and provided authenticated users group read access but that didn't seem to do the trick. This is on 1909 and sideloading is enabled.

@DHowett I thought of a potential solution that does involve another team in MS. It's probably been thought about already but just in case: Just like Office can receive updates through Windows Update but is an external download/install, so too can Windows Terminal do the same. Make sure it can be available for WSUS and then you'll be able to push this great app to anybody running the required build version of Windows (just be sure Server 2016 and 2019 are also supported).

Still the same issue with v0.9.433.0
My issue report: https://github.com/microsoft/terminal/issues/4562

(very sorry for the images size, as depending on you extensions, they could be rendered way bigger than i though)
I do confirm that it's still an issue with 0.9.x msixbundle.
I think both comments from @WSLUser are spots on :

I get the same thing as @tebeco on an offline Windows 10 Enterprise host. From what I've been able to determine, it seems like a permissions issue. If you manually try to go to the directory in file explorer, you can not, even as administrator. I changed ownership to the local Administrators group and provided authenticated users group read access but that didn't seem to do the trick. This is on 1909 and sideloading is enabled. I did install everything listed on the install notes.

@DHowett I thought of a potential solution that does involve another team in MS. It's probably been thought about already but just in case: Just like Office can receive updates through Windows Update but is an external download/install, so too can Windows Terminal do the same. Make sure it can be available for WSUS and then you'll be able to push this great app to anybody running the required build version of Windows (just be sure Server 2016 and 2019 are also supported).

as @bitcrazed said, it's being discussed, which is great
Thought, i would love to know, is it possible to simply publish artifacts, while a concensus / decision is made ?
For now i had to manually build it myself for co-worker, but since 0.8.x it stopped building while following this instruction of this repository
It seems that this #1386 suggest to apply "the same" idea => install from build artifiacts
see : https://github.com/microsoft/terminal/issues/1386#issuecomment-506419057

Can it be pushed to AzureDevops Artifacts for example ?

See if this helps https://github.com/microsoft/terminal/issues/1386#issuecomment-591177598

why would i attempt to click an unknown / un trusted domain ?
especially to install binaries from an unofficial source
you may first want to have explain what is the purpose of the website before just sending a link and ask for user to click.
i'm not saying it does not work, just that there's no way you could trust a third part shipping magic binaries
Especially when you could first ask here to windows/terminal team if they might be able to address it

I'm not sure if this will help or not, but while trying to get things installed without using the Microsoft Store (disabled by GPO in my company), I ran into the following:

I installed the package from the Microsoft site. The details of the file (details tab in file properties) indicate the version is 14.0.24222.0
The installation via Chocolatey fails and provides an ActivityID. Looking at the logs for that activity has a message like

Windows cannot install package Microsoft.WindowsTerminal_0.9.433.0_x64__8wekyb3d8bbwe because this package depends on a framework
that could not be found. Provide the framework "Microsoft.VCLibs.140.00" published by "CN=Microsoft Corporation, O=Microsoft
Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with
this package to install. The frameworks with name "Microsoft.VCLibs.140.00" currently installed are:
{Microsoft.VCLibs.140.00_14.0.26706.0_x64__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.26706.0_x86__8wekyb3d8bbwe}`

So, it seems like the problem may be that the required version is higher than what is being provided by the download page, however, the version after installation doesn't match the file version info, so I'm not sure if there is a different version string that is being looked for.

Did a little bit more digging. I'm not super familiar with Windows package development.
Here is a summary of file version identifiers I found:
From the Details tab of the file properties of the downloaded .exe: 14.0.24222.0
From the APPX Retail x64 version: 14.0.24217.0
From the APPX Debug x64 version: 14.0.24222.0
From the AppPackageLog:
Min Version=14.0.27323.0
List of installed frameworks: 14.0.26706.0
So, there are many version numbers that are all very similar and I know that it's all confusing me. Perhaps we could get which one of these versions we should be looking for and which ones are red herrings. Otherwise, all I can figure out is that the redist package being used in development isn't publicly available at this time, so no one outside of Microsoft will be able to install this package without building it ourselves (which isn't an option for me).

I think the problem is much simpler and stupider.
Intro
Trying to install "The Terminal" (for example by choco install microsoft-windows-terminal), it throws an error where it trying to find a Microsoft.VCLibs.140.00.UWPDesktop platform, at least 14.0.27323.0 version. But win10 in many (or most) cases has older version. For example, Microsoft.VCLibs.140.00.UWPDesktop_14.0.26905.0_x64__8wekyb3d8bbwe. And everyone looked for those digits: 14.0.26905 vs 14.0.27323. You can even check that like this:
> Get-AppxPackage -allusers *Microsoft.VCLibs.140.00.UWPDesktop* | Select Name, PackageFullName

Name                               PackageFullName
----                               ---------------
Microsoft.VCLibs.140.00.UWPDesktop Microsoft.VCLibs.140.00.UWPDesktop_14.0.26905.0_x64__8wekyb3d8bbwe

Where we should look instead
> Get-AppxPackage -allusers *Microsoft.VCLibs.140.00* | Select Name, PackageFullName

Name                               PackageFullName
----                               ---------------
Microsoft.VCLibs.140.00.UWPDesktop Microsoft.VCLibs.140.00.UWPDesktop_14.0.26905.0_x64__8wekyb3d8bbwe
Microsoft.VCLibs.140.00            Microsoft.VCLibs.140.00_14.0.27323.0_x64__8wekyb3d8bbwe
Microsoft.VCLibs.140.00            Microsoft.VCLibs.140.00_14.0.27323.0_x86__8wekyb3d8bbwe
Microsoft.VCLibs.140.00            Microsoft.VCLibs.140.00_14.0.26706.0_x64__8wekyb3d8bbwe
Microsoft.VCLibs.140.00            Microsoft.VCLibs.140.00_14.0.26706.0_x86__8wekyb3d8bbwe

I think its pretty self explanatory. But in case... The Terminal requirement seeks for "YetAnotherCrap.UWPDesktop_100500". The Microsoft provides us only with "YetAnotherCrap_100500". Without that UWPDesktop part in the name.
P.S.
Yes, I downloaded those vc140 libs also by link from readme.md.
Yes, I tried to install every piece (terminal, libs...) throug choco and/or through Windows Store. Tried every approach.
Yes, I tried to delete that ugly old UWPDesktop_14.0.26905 version. But...
Remove-AppxPackage -Package "Microsoft.VCLibs.140.00.UWPDesktop_14.0.26905.0_x64__8wekyb3d8bbwe"

...cmdlet says that package are dependency for Microsoft.DesktopAppInstaller and Microsoft.MicrosoftOfficeHub, so it wont be deleted in any case. Means windows are totally not able to make it, because there is no force-mode to ignore dependencies.

sorry for pinging everyone here but someone from my team might have found a workaround
DISCLAMER : it looks ugly but is pretty simple and works for the msixbundle install.
PRE-REQUISITE:
I am a local administrator of my workstation
BLOCKING PART:
The store is locked down by GPO so i'm welcomed with an error msg on the opening page of the store
This was one of the issue that blocked the msix in earlier version as it probably tried to install these from network/store
I noticed that since 0.8 or 0.9 the issue for the VCLibs seems to be properly install on our computer at work.
by that i mean that i just download + double click the msixbundle and seems to properly install it dependencies
the remaining issue was the fact that once install there is a VERY obscur error about "access denied" "network" and C:\Program Files\WindowsApps\Microsoft....Terminal.0.9...
i have no idea why "network" and "C:" are tied together ^^
I tried to access the full page path ... it DOES exists but even with the UAC prompt i am denied
we tried the same for the root folder C:\Program Files\WindowsApps
same error
WORKAROUND (Beware as i have no idea if it can break stuff ... that's why i'm posting here to be sure)

be sure you can elevated your right to local admin (UAC Grant)
open explorer on C:\Program Files
you might have to display hidden folder
select WindowsApps
right click > properties > security tab
advance > change owner
set your windows account
check the "all object and subitem" (can't remember the exact wording)
validate .... wait for few minute to finish
ok / ok
install the msixbundle
the "Launch" button won't work

WONT WORK :

do not click the launch the from the installer
shortcut from Start Menu won't work either
you won't be able to open "ABOUT" (crash on access denied)

WORKS:
(even though i though we could not do that)
It seems that now running the exe from the msixbundle in C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_VERSION_HERE\WindowsTerminal.exe
by version i mean "0.9.443_....." and the other folder "2020.Neutral....." (i have no idea yet about this details)
Once it run just right click and pin it to the task bar
so now my questions goes to
@cinnamon-msft @bitcrazed @DHowett
i think this is a terrible idea
but as i do not understand internal mechanism of either Store/WTD/Windows :

what can i break by doing that ?
why the "About" still crash on access denied ?
should the msixbundle check and set properly these right if it seems necessary ?
how/why the StartMenu is still broken, should it be changed for such installation ?

And another one clue about "UWPDesktop" part at name.
Part of AppxManifest.xml inside CascadiaPackage_0.9.433.0_x64.msix that inside Microsoft.WindowsTerminal_0.9.433.0_8wekyb3d8bbwe.msixbundle.
  <Dependencies>
    <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.18362.0" MaxVersionTested="10.0.18362.0" />
    <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.27323.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
    <PackageDependency Name="Microsoft.VCLibs.140.00.UWPDesktop" MinVersion="14.0.27323.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
  </Dependencies>

I'm not sure, but accordingly to official documentation there is no Optional flag, so this is looks like it is not just making difference between names with and without UWPDesktop part (as I wrote at comment above), but also trying to require them both!

@TeBeCo what you’ve described is the same as unzipping the MSIXBundle and using the exe inside it with the added step of corrupting the permissions on your system. If you’re going to go to all that effort, just unzip the msix bundle like I suggested to you in the original issue you filed 😄

ahhh i forgot that ^^
maybe that was when the VCLibs were not installed and was still stuck because the msix did not contained or installed the dependencies IIRC
sorry about that
yeah for the permissions that's what i was afraid of.
that's why i tried to write huge disclaimer as it's probably not recommended at all but was not sure before asking here to be honest
i'll go ok and try an unzip on future version
do you want me to edit or remove the previous comment to avoid user to corrupt their own permissions ?
i guess it's normal to be denied on that folder ?
even for normal installation? (i mean no special GPO / store not locked down)
if it's normal is the "network access denied" know ?
and why do the "network error" if fixed by a folder right ^^
i'm trying to understand things part by part as i don't have the full picture in my head

@tebeco please do. That folder is managed by the windows application installer, and it's not intended to be edited by the local administrator. I'm not certain what could happen, but I would be worried to find out :smile:

do you have further info on the others questions regarding the current behavior / error msg etc ... at the end of this comment :
https://github.com/microsoft/terminal/issues/3097#issuecomment-597796444
because i wonder if the unzip would fix the dependencies issue, i might have installed them manually
or the installation might install them and only after unzipping could work

If I knew why you were hitting a "network error" installing and launching packaged applications, you'd be the first to know :smile: it's a mystery to all of us.

what can i do to help ?
if you do have a custom build or msixbundle that your team can send on another feed or whatever with more logs
can i trace it somehow ?
i looked in the EventViewer but was not lucky
i'm very very much whiling to help
and i might have a spare laptop at work to serve as a dummy for this test (at least for now)
just tell me what can i do. i would even suggest a debug session but the firewall here is kinda nasty
and not sure if i can use the "support card" for that to escaladate as it's absolutely not blocking anyone ;) :trollface:

Any news on this, I have the same issue running 1903.  I can't install from the Store, but downloaded the MSIX and Choco pkg to no avail.   Unzipping the MSIX and running the exe does work through (apart from AZure CLI not working so far).  Can we at least remove the dependency so the install completes and go from there??
I have these VCLibs with after installing this https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/

I also have VS2019 installed too.

Reassigning to @DHowett and @cinnamon-msft
FWIW, you may be missing some VCLibs.140 UWPDesktop packages:

The Win10 SDK alone does not install some of these packages.
Please bear with us while we figure some of this out - there's a complex dance in-play.

I am using chocolatey for this and also encountered this.  The strange thing is: I literally just setup my machine this way last weekend and it worked fine, but now it's not on a reinstall.  The particularly odd thing is that choco did successfully install the vcredis140 package!  Errors and confirmation all below.  The vcredist140 version seems perhaps too high now?...
Error from choco install terminal (I use upgrade to install):
PS C:\Windows\system32> choco upgrade -y microsoft-windows-terminal
Chocolatey v0.10.15
2 validations performed. 1 success(es), 1 warning(s), and 0 error(s).

Validation Warnings:
 - A pending system reboot request has been detected, however, this is
   being ignored due to the current Chocolatey configuration.  If you
   want to halt when this occurs, then either set the global feature
   using:
     choco feature enable -name=exitOnRebootDetected
   or pass the option --exit-when-reboot-detected.

Upgrading the following packages:
microsoft-windows-terminal
By upgrading you accept licenses for the packages.
microsoft-windows-terminal is not installed. Installing...
Progress: Downloading microsoft-windows-terminal 0.10.781.0... 100%
Progress: Downloading microsoft-windows-terminal 0.10.781.0... 100%

microsoft-windows-terminal v0.10.781.0 [Approved]
microsoft-windows-terminal package files upgrade completed. Performing other installation steps.
Progress: 0% - Processing                                                                                ERROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation.

Windows cannot install package Microsoft.WindowsTerminal_0.10.781.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00.UWPDesktop" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00.UWPDesktop" currently installed are:
Windows cannot install package Microsoft.WindowsTerminal_0.10.781.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00.UWPDesktop" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00.UWPDesktop" currently installed are: {Microsoft.VCLibs.140.00.UWPDesktop_14.0.26905.0_x64__8wekyb3d8bbwe}

NOTE: For additional information, look for [ActivityId] b2d4ad61-09bb-0006-23c9-d4b2bb09d601 in the Event Log or use the command line Get-AppPackageLog -ActivityID b2d4ad61-09bb-0006-23c9-d4b2bb09d601

The upgrade of microsoft-windows-terminal was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'.
 See log for details.

Chocolatey upgraded 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - microsoft-windows-terminal (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'.
 See log for details.

Here is the status of my vcredist:
PS C:\Windows\system32> choco upgrade -y vcredist140
Chocolatey v0.10.15
2 validations performed. 1 success(es), 1 warning(s), and 0 error(s).

Validation Warnings:
 - A pending system reboot request has been detected, however, this is
   being ignored due to the current Chocolatey configuration.  If you
   want to halt when this occurs, then either set the global feature
   using:
     choco feature enable -name=exitOnRebootDetected
   or pass the option --exit-when-reboot-detected.

Upgrading the following packages:
vcredist140
By upgrading you accept licenses for the packages.
vcredist140 v14.24.28127.4 is the latest version available based on your source(s).

Chocolatey upgraded 0/1 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
PS C:\Windows\system32> Get-AppxPackage -AllUsers *vclibs* | sort PackageFullName | Select Name, Version, PackageFullName

Name                               Version      PackageFullName
----                               -------      ---------------
Microsoft.VCLibs.140.00.UWPDesktop 14.0.26905.0 Microsoft.VCLibs.140.00.UWPDesktop_14.0.26905.0_x64__8wekyb3d8bbwe
Microsoft.VCLibs.140.00            14.0.27810.0 Microsoft.VCLibs.140.00_14.0.27810.0_x64__8wekyb3d8bbwe
Microsoft.VCLibs.140.00            14.0.27810.0 Microsoft.VCLibs.140.00_14.0.27810.0_x86__8wekyb3d8bbwe

The needed packages can be downloaded from the Microsoft Store currently here:
https://www.microsoft.com/store/productId/9NBLGGH4RV3K
For whatever reason this page is hidden. The direct links currently are:
x86:
http://tlu.dl.delivery.mp.microsoft.com/filestreamingservice/files/7940bc27-6f7a-4b37-949b-4c8d9ed94460?P1=1587105490&P2=402&P3=2&P4=AtQJnsmggRcHcsZyjMqotvtXkl8BtKNjjNTLNMXElMvbb9bW9BzGGAt1R0abu%2Ff55938xk%2FSQvuhGqi8Do4kow%3D%3D
http://dl.delivery.mp.microsoft.com/filestreamingservice/files/1d146565-6dae-41ce-a1d7-febc36317f36
x64:
http://tlu.dl.delivery.mp.microsoft.com/filestreamingservice/files/0e19f025-0004-48c2-b699-ee1a275389b7?P1=1587105510&P2=402&P3=2&P4=VDFc2TYZIE76bGINYMsEM4%2FuLyj6Q9aWopsazPUOFeN9O%2BWZ2VweF%2FddYWmYAsEPf8fxw3z9GJ1y6ZoLsNd14w%3D%3D
http://dl.delivery.mp.microsoft.com/filestreamingservice/files/7d52a905-fc42-4c82-a642-70b3bede55dc
ARM:
http://tlu.dl.delivery.mp.microsoft.com/filestreamingservice/files/c14c0261-8f5d-432c-81ca-3518a53c9581?P1=1587105510&P2=402&P3=2&P4=FjeknMnvJynzKWZYBeAIihMNefCIjfLAYJ6xXMXN8IVbdmQJ97bFaz395nYlKl%2BMd5mt%2FyS4GfvuYI%2F8HcBMhQ%3D%3D
http://dl.delivery.mp.microsoft.com/filestreamingservice/files/67fb1b12-2236-4b18-8079-f3f3cd27a707
ARM64:
http://tlu.dl.delivery.mp.microsoft.com/filestreamingservice/files/0b0a31d6-85a8-4f63-ad1a-6a31afe4ee1c?P1=1587105510&P2=402&P3=2&P4=EApKlQwATjqsOibgA87H69FzpEU%2FCFOQ%2FARRv9J82CUe6a4CtVAQBcDUk1mCV4JK3Ghg62UWi0fX2MS0F7Wq%2FA%3D%3D
http://dl.delivery.mp.microsoft.com/filestreamingservice/files/83533985-0915-4337-b849-532913e9d544
I am unsure of these links being timed or session-based, so if they do expire, here is how to get them again:

Visit: https://store.rg-adguard.net/ (This is a third-party site, disable ads and javascript before visiting to be sure.)
Select URL (link) from the drop down.
Enter: https://www.microsoft.com/store/productId/9NBLGGH4RV3K

This will pull real/valid links from Microsofts store. You can verify the links before downloading them to trust their locations as needed. The appx's are downloaded from Microsofts servers directly, so they are safe.
Doing this will get you the needed requirement to get this installed and working.

@atom0s Thanks for the info.  The store.rg-adguard.net seemed a bit shady to me, but I can confirm that process worked for me.  To restate your solution and my path to resolution:
Problem:
choco install microsoft-windows-terminal would fail with errors about missing packages for
Microsoft.VCLibs.140.00.UWPDesktop or Microsoft.VCLibs.140.00
Get-AppxPackage | where name -like "Microsoft.VC*" | select Name, Version, PackageFamilyName would show these packages but not with the latest/required versions
Solution:

Visit the somewhat shady feeling site: https://store.rg-adguard.net/ to download appx packages directly out of the microsoft store.  The links generated are from microsoft.com domains.
Search by PackageFamilyName for Microsoft.VCLibs.140.00.UWPDesktop_8wekyb3d8bbwe

For me, the generated link for x64 was: Microsoft.VCLibs.140.00.UWPDesktop_14.0.27810.0_x64__8wekyb3d8bbwe.appx

Search by PackageFamilyName for Microsoft.VCLibs.140.00_8wekyb3d8bbwe

For me the generated link for x64 was: Microsoft.VCLibs.140.00_14.0.27810.0_x64__8wekyb3d8bbwe.appx

run Add-AppxPackage -Path .\Microsoft.VCLibs.140.00.UWPDesktop_14.0.27810.0_x64__8wekyb3d8bbwe.appx
run Add-AppxPackage -Path .\Microsoft.VCLibs.140.00_14.0.27810.0_x64__8wekyb3d8bbwe.appx
run choco install microsoft-windows-terminal which now succeeds

Working well on my side too.
Thanks @atom0s ! (and @camp-007 for the clearest explanation :) )

the msixbundle would then work too if you want to avoid choco

I installed Microsoft.VCLibs.140.00.UWPDesktop_8wekyb3d8bbwe and Microsoft.VCLibs.140.00_8wekyb3d8bbwe by this way (https://github.com/microsoft/terminal/issues/3097#issuecomment-615373769),
Then download the Microsoft.WindowsTerminal_0.10.781.0_8wekyb3d8bbwe.msixbundle from releases page, and installed the app.
But can't open it, when click the start button, there is nothing, after a few miutes, show this error:

due to time out, this operation is return in English. (my pc is without network access)

@atom0s Your solution actually worked for me! I've attempted every other workaround posted by the devs and others here for months, and nothing has ever worked.
This seems like a byzantine process to through to install a terminal console. Not sure why Terminal so strictly require the bleeding edge release of the C++ runtime each update. Even downloading the latest release from the MS website doesn't work for me.
Only this goofy third-party search engine giving downloads from the Store seems to work.

@atom0s thank you for solution. It works on some systems. x86 installs on every machine without any problmes. But my primary notebook, are not able to install x64 version of that package. Says:

App installation failed with error message: Ошибка 0x80073D02: не удалось выполнить установку, так как требуется закрыть следующие приложения: Microsoft.DesktopAppInstaller_1.0.32912.0_x64__8wekyb3d8bbwe. (0x80073d02)

Means: "Error 0x80073D02: cannot perform an installation, because you need to close those applications". The trick is: installation of .appx file (as I understand) performed by DesktopAppInstaller. So it literally asks to close itself, because it cannot perform its own functions, because of itself. Wut?
P.S.
Guys/girls/persons/kind-folks from Microsoft... Im risking to trigger your holy rage by that question, but I feel like I must to ask. Even if no one will answer, it will seed the idea. Can't you please just follow the RPM system so we all can to sigh with a relief at last? I know that in *nix world it is not the newest and best. Yet for Windows it will be like divine revelation and next level ascension.

For me, I had to run the appx files directly, not from the command line. As for your issue in general, you could try killing everything running on your system including Explorer, and directly run the appx as a new task through Task Manager while everything is shut off and see if it bypasses that kind of issue of being in-use.

In the interest of making Terminal easily accessible in environments where the store isn’t available, we’re going to ship our dependencies inside our package for now. We’ll revisit this once we have a better story.
This issue will close when the PR that integrates our dependencies merges (in a minute or so.)

@DHowett-MSFT It appears that ever since PR #5256. The appx-Release  bundle is no longer generated. Shipping the deps only helps when a release is published but what if we want to roll a custom build? We should be able to grab the appx. Visual Studio still shouldn't be required.

@WSLUser If you are smart enough roll a custom build, you're capable enough of finding and installing its dependencies. Also, we haven't changed how the CI pipelines publish app packages, and the build changes in the msbuild projects only impact builds with a specific flag turned on.

5256 was made because we spent too much time rebuilding unchanged code for flavors that we've never picked up any regressions in. Our CI is not a contract. You are not supposed to rely on the availability of any bundles from our CI. It's not a contract.

Yes, and I did notice #5679 did publish an artifact, except the x64 build failed due to circular graph, so anybody not using x64 could grab it. That graph issue usually just requires a rebuild. Obviously no point to rebuild for that PR as it's for v1 but I was hoping to update my offline machine with the latest appx bundle now that the deps are shipped as part of it.

Seems to work now!
A minor inconvienance is that it will install successfully, but you need to wait few minutes (or launch Microsoft Store, can't be sure) for it to start working properly. When you click on the icon in Start Menu it will behave as if installation was still in progress (even progressbar is still present).

Does this issue happen again? See https://github.com/microsoft/terminal/issues/13345

Leaving here for future folks. These are from the Release Notes:

Why are there so many packages? How do I choose?
This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of
which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a
platform issue related to our dependencies.
If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that
you use the Win10 bundle. You will need the Visual C++ runtime redistributable.
In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.
Despite these distributions having different version numbers, they are built from the same code and there is no
functional difference between them.
If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11
version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this
way.

As with prior releases, you need to install Microsoft.VCLibs.UWPDesktop.140.00 or make sure it is installed prior to installing Terminal. If you are using Terminal unpackaged, you will need to make sure you have the systemwide "Microsoft Visual C++ Redistributable" installed, and choose the Win10 version of our msixbundle. Yeah, it's strange!

@atom0s Thanks for the info. The store.rg-adguard.net seemed a bit shady to me, but I can confirm that process worked for me. To restate your solution and my path to resolution:
Problem:
choco install microsoft-windows-terminal would fail with errors about missing packages for Microsoft.VCLibs.140.00.UWPDesktop or Microsoft.VCLibs.140.00
Get-AppxPackage | where name -like "Microsoft.VC*" | select Name, Version, PackageFamilyName would show these packages but not with the latest/required versions
Solution:

Visit the somewhat shady feeling site: https://store.rg-adguard.net/ to download appx packages directly out of the microsoft store.  The links generated are from microsoft.com domains.

Search by PackageFamilyName for Microsoft.VCLibs.140.00.UWPDesktop_8wekyb3d8bbwe

For me, the generated link for x64 was: Microsoft.VCLibs.140.00.UWPDesktop_14.0.27810.0_x64__8wekyb3d8bbwe.appx

Search by PackageFamilyName for Microsoft.VCLibs.140.00_8wekyb3d8bbwe

For me the generated link for x64 was: Microsoft.VCLibs.140.00_14.0.27810.0_x64__8wekyb3d8bbwe.appx

run Add-AppxPackage -Path .\Microsoft.VCLibs.140.00.UWPDesktop_14.0.27810.0_x64__8wekyb3d8bbwe.appx

run Add-AppxPackage -Path .\Microsoft.VCLibs.140.00_14.0.27810.0_x64__8wekyb3d8bbwe.appx

run choco install microsoft-windows-terminal which now succeeds

yeap this still works just fine :)

In case someone wants to install via official URL + chocolatey, please use the following (tested on Windows Server 2022):
$tempUwpASPX = Join-Path -Path $env:TEMP -ChildPath "Microsoft.VCLibs.x64.14.00.Desktop.appx"
Invoke-WebRequest -Uri "https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx" -OutFile $tempUwpASPX
Add-AppxPackage -Path $tempUwpASPX
choco install -y microsoft-windows-terminal

Source of URLs is https://learn.microsoft.com/en-us/troubleshoot/developer/visualstudio/cpp/libraries/c-runtime-packages-desktop-bridge#how-to-install-and-update-desktop-framework-packages

The issue https://github.com/PowerShell/PowerShell/issues/13138 stays, however, on Windows 10... 🤷
$ Add-AppxPackage -Path $tempUwpASPX
Add-AppxPackage: The 'Add-AppxPackage' command was found in the module 'Appx', but the module could not be loaded due to the following error: [Operation is not supported on this platform. (0x80131539)]
For more information, run 'Import-Module Appx'.
$ Import-Module Appx
Import-Module: Operation is not supported on this platform. (0x80131539)

Ah okay the workaround to import it was possible, but well (file was already downloaded before via Invoke-WebRequest as shown above):
PowerShell 7.4.2
Loading personal and system profiles took 3198ms.
PS C:\Windows\System32> Import-Module -Name Appx -UseWindowsPowerShell
WARNING: Module Appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax.
PS C:\Windows\System32> $tempUwpASPX = Join-Path -Path $env:TEMP -ChildPath "Microsoft.VCLibs.x64.14.00.Desktop.appx"
PS C:\Windows\System32> ^C
PS C:\Windows\System32> Add-AppxPackage -Path $tempUwpASPX
PS C:\Windows\System32> choco upgrade -y microsoft-windows-terminal
Chocolatey v2.2.2
Upgrading the following packages:
microsoft-windows-terminal
By upgrading, you accept licenses for the packages.

You have microsoft-windows-terminal v1.17.11461 installed. Version 1.20.11271 is available based on your source(s).
Progress: Downloading microsoft-windows-terminal 1.20.11271... 100%

microsoft-windows-terminal v1.20.11271 [Approved]
microsoft-windows-terminal package files upgrade completed. Performing other installation steps.
ERROR: Cannot convert the "System.Object[]" value of type "System.Object[]" to type "System.Version".
The upgrade of microsoft-windows-terminal was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'.
 See log for details.

Chocolatey upgraded 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - microsoft-windows-terminal (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'.
 See log for details.

Log shows:
2024-06-03 16:52:14,872 15624 [INFO ] - [NuGet] Resolving dependency information took 0 ms
2024-06-03 16:52:16,604 15624 [DEBUG] - Running beforeModify step for 'microsoft-windows-terminal'
2024-06-03 16:52:16,610 15624 [DEBUG] - Backing up package files for 'microsoft-windows-terminal'
2024-06-03 16:52:16,644 15624 [DEBUG] - Attempting to create directory "C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal".
2024-06-03 16:52:16,646 15624 [DEBUG] - Moving C:\ProgramData\chocolatey\lib\microsoft-windows-terminal to C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461
2024-06-03 16:52:16,649 15624 [DEBUG] - Moving 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal'
to 'C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461'
2024-06-03 16:52:18,668 15624 [DEBUG] - Attempting to create directory "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal".
2024-06-03 16:52:18,671 15624 [DEBUG] - Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461\microsoft-windows-terminal.nupkg"
to "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\microsoft-windows-terminal.nupkg".
2024-06-03 16:52:18,792 15624 [DEBUG] - Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461\microsoft-windows-terminal.nuspec"
to "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\microsoft-windows-terminal.nuspec".
2024-06-03 16:52:18,795 15624 [DEBUG] - Attempting to create directory "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal".
2024-06-03 16:52:18,797 15624 [DEBUG] - Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461\legal\LICENSE.txt"
to "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal\LICENSE.txt".
2024-06-03 16:52:18,800 15624 [DEBUG] - Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461\legal\VERIFICATION.txt"
to "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal\VERIFICATION.txt".
2024-06-03 16:52:18,802 15624 [DEBUG] - Attempting to create directory "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools".
2024-06-03 16:52:18,804 15624 [DEBUG] - Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461\tools\chocolateyInstall.ps1"
to "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1".
2024-06-03 16:52:18,807 15624 [DEBUG] - Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461\tools\chocolateyUninstall.ps1"
to "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyUninstall.ps1".
2024-06-03 16:52:18,809 15624 [DEBUG] - Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461\tools\Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle"
to "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle".
2024-06-03 16:52:20,448 15624 [DEBUG] - Deleting file C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1
2024-06-03 16:52:20,449 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1".
2024-06-03 16:52:20,453 15624 [DEBUG] - Deleting file C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyUninstall.ps1
2024-06-03 16:52:20,454 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyUninstall.ps1".
2024-06-03 16:52:20,460 15624 [DEBUG] - Capturing package files in 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal'
2024-06-03 16:52:20,505 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\microsoft-windows-terminal.nupkg'
 with checksum '83C744E6DFD576B8FF4307257CC8B184'
2024-06-03 16:52:20,506 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\microsoft-windows-terminal.nuspec'
 with checksum 'DAA9B55A7C0E8644AA9BCF5AF2E04A0A'
2024-06-03 16:52:20,508 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal\LICENSE.txt'
 with checksum 'B377DB62B5A030F560ED5BBCA25EA5BE'
2024-06-03 16:52:20,510 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal\VERIFICATION.txt'
 with checksum '4B3374D05B3D01573E163C2BAE73A9FD'
2024-06-03 16:52:20,554 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle'
 with checksum '424C8354E5D913DE7A0F48A2E4D5357B'
2024-06-03 16:52:20,558 15624 [DEBUG] - Ensuring removal of installation files.
2024-06-03 16:52:20,597 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\microsoft-windows-terminal.nupkg'
 with checksum '83C744E6DFD576B8FF4307257CC8B184'
2024-06-03 16:52:20,598 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\microsoft-windows-terminal.nupkg".
2024-06-03 16:52:20,602 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\microsoft-windows-terminal.nuspec'
 with checksum 'DAA9B55A7C0E8644AA9BCF5AF2E04A0A'
2024-06-03 16:52:20,603 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\microsoft-windows-terminal.nuspec".
2024-06-03 16:52:20,605 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal\LICENSE.txt'
 with checksum 'B377DB62B5A030F560ED5BBCA25EA5BE'
2024-06-03 16:52:20,606 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal\LICENSE.txt".
2024-06-03 16:52:20,608 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal\VERIFICATION.txt'
 with checksum '4B3374D05B3D01573E163C2BAE73A9FD'
2024-06-03 16:52:20,609 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal\VERIFICATION.txt".
2024-06-03 16:52:20,654 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle'
 with checksum '424C8354E5D913DE7A0F48A2E4D5357B'
2024-06-03 16:52:20,655 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle".
2024-06-03 16:52:20,662 15624 [DEBUG] - Attempting to delete directory "C:\ProgramData\chocolatey\lib\microsoft-windows-terminal".
2024-06-03 16:52:20,665 15624 [DEBUG] - Removing nupkg if it still exists.
2024-06-03 16:52:20,666 15624 [DEBUG] - Resolving resource DownloadResource for source https://chocolatey.org/api/v2/
2024-06-03 16:52:20,746 15624 [DEBUG] - Attempting to delete file "".
2024-06-03 16:52:20,757 15624 [INFO ] - [NuGet]   GET https://community.chocolatey.org/api/v2/package/microsoft-windows-terminal/1.20.11271
2024-06-03 16:52:23,281 15624 [INFO ] - [NuGet]   OK https://community.chocolatey.org/api/v2/package/microsoft-windows-terminal/1.20.11271 2522ms
2024-06-03 16:52:23,292 15624 [INFO ] - [NuGet] Acquiring lock for the installation of microsoft-windows-terminal 1.20.11271
2024-06-03 16:52:23,311 15624 [INFO ] - [NuGet] Acquired lock for the installation of microsoft-windows-terminal 1.20.11271
2024-06-03 16:52:59,465 15624 [INFO ] - [NuGet] Installed microsoft-windows-terminal 1.20.11271 from https://chocolatey.org/api/v2/ with content hash JXjzDFmEFWMe0RyqonllQpxs7i2sXIyfz0O3UifdcyithRz1HUed1Fflw413W2MiCvTxhJm6sg10UYjL5Pa63w==.
2024-06-03 16:52:59,531 15624 [INFO ] - [NuGet] Adding package 'microsoft-windows-terminal.1.20.11271 : vcredist140 (, )' to folder 'C:\ProgramData\chocolatey\lib'
2024-06-03 16:52:59,851 15624 [INFO ] - [NuGet] Added package 'microsoft-windows-terminal.1.20.11271 : vcredist140 (, )' to folder 'C:\ProgramData\chocolatey\lib'
2024-06-03 16:52:59,855 15624 [DEBUG] - Attempting to delete file "C:\Users\kruegerro\AppData\Local\Temp\chocolatey\ChocolateyScratch\microsoft-windows-terminal/1.20.11271\microsoft-windows-terminal.1.20.11271.nupkg".
2024-06-03 16:52:59,859 15624 [DEBUG] - Attempting to delete file "C:\Users\kruegerro\AppData\Local\Temp\chocolatey\ChocolateyScratch\microsoft-windows-terminal/1.20.11271\.nupkg.metadata".
2024-06-03 16:52:59,860 15624 [DEBUG] - Attempting to delete file "C:\Users\kruegerro\AppData\Local\Temp\chocolatey\ChocolateyScratch\microsoft-windows-terminal/1.20.11271\microsoft-windows-terminal.1.20.11271.nupkg.sha512".
2024-06-03 16:52:59,863 15624 [INFO ] -
microsoft-windows-terminal v1.20.11271 [Approved]
2024-06-03 16:52:59,887 15624 [INFO ] - microsoft-windows-terminal package files upgrade completed. Performing other installation steps.
2024-06-03 16:53:00,191 15624 [DEBUG] - Setting installer args for microsoft-windows-terminal
2024-06-03 16:53:00,192 15624 [DEBUG] - Setting package parameters for microsoft-windows-terminal
2024-06-03 16:53:00,195 15624 [DEBUG] - Contents of 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1':
2024-06-03 16:53:00,203 15624 [DEBUG] - $ErrorActionPreference = 'Stop';

$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$fileName       = "$toolsDir\Microsoft.WindowsTerminal_1.20.11271.0_8wekyb3d8bbwe.msixbundle"
$version        = "1.20.11271.0"
$PreRelease     = "False"

$WindowsVersion=[Environment]::OSVersion.Version
if ($WindowsVersion.Major -ne "10") {
 throw "This package requires Windows 10."
}
#The .msixbundle format is not supported on Windows 10 version 1709 and 1803. https://docs.microsoft.com/en-us/windows/msix/msix-1709-and-1803-support
$IsCorrectBuild=[Environment]::OSVersion.Version.Build
if ($IsCorrectBuild -lt "18362") {
 throw "This package requires at least Windows 10 version 1903/OS build 18362.x."
}

$AppxPackageName = "Microsoft.WindowsTerminal"

if ($PreRelease -match "True") {
 $AppxPackageName += "Preview"
}

[version]$AppxVer = (Get-AppxPackage -Name $AppxPackageName -AllUsers -PackageTypeFilter Bundle).Version

if ($AppxVer -gt [version]$version) {
 # you can't install an older version of an installed appx package, you'd need to remove it first
 Write-Warning "The installed $version version is newer than this package version, it may have autoupdated on your current OS..."
} elseif ($AppxVer -Match [version]$version) {
   if($env:ChocolateyForce) {
     # you can't install the same version of an appx package, you need to remove it first
     Write-Host Removing already installed version first.
     Remove-AppxPackage -AllUsers -Package (Get-AppxPackage -Name $AppxPackageName -AllUsers -PackageTypeFilter Bundle)
   } else {
   Write-Host The $version version of Windows-Terminal is already installed. If you want to reinstall use --force
   return
 }
}

Add-ProvisionedAppPackage -Online -SkipLicense -PackagePath $fileName

2024-06-03 16:53:00,212 15624 [DEBUG] - Calling built-in PowerShell host with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = '';[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::SystemDefault; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1' -installArguments '' -packageParameters '' -preRunHookScripts $null -postRunHookScripts $null']
2024-06-03 16:53:00,219 15624 [DEBUG] - Redirecting System.Management.Automation.resources, Version=<IP_ADDRESS>, Culture=de-DE, PublicKeyToken=31bf3856ad364e35, requested by ''
2024-06-03 16:53:00,877 15624 [DEBUG] - Host version is 5.1.19041.1, PowerShell Version is '5.1.19041.4291' and CLR Version is '4.0.30319.42000'.
2024-06-03 16:53:01,088 15624 [INFO ] - VERBOSE: Exporting function 'Format-FileSize'.
2024-06-03 16:53:01,090 15624 [INFO ] - VERBOSE: Exporting function 'Get-ChecksumValid'.
2024-06-03 16:53:01,091 15624 [INFO ] - VERBOSE: Exporting function 'Get-ChocolateyConfigValue'.
2024-06-03 16:53:01,093 15624 [INFO ] - VERBOSE: Exporting function 'Get-ChocolateyPath'.
2024-06-03 16:53:01,094 15624 [INFO ] - VERBOSE: Exporting function 'Get-ChocolateyUnzip'.
2024-06-03 16:53:01,096 15624 [INFO ] - VERBOSE: Exporting function 'Get-ChocolateyWebFile'.
2024-06-03 16:53:01,097 15624 [INFO ] - VERBOSE: Exporting function 'Get-EnvironmentVariable'.
2024-06-03 16:53:01,100 15624 [INFO ] - VERBOSE: Exporting function 'Get-EnvironmentVariableNames'.
2024-06-03 16:53:01,101 15624 [INFO ] - VERBOSE: Exporting function 'Get-FtpFile'.
2024-06-03 16:53:01,103 15624 [INFO ] - VERBOSE: Exporting function 'Get-OSArchitectureWidth'.
2024-06-03 16:53:01,104 15624 [INFO ] - VERBOSE: Exporting function 'Get-PackageParameters'.
2024-06-03 16:53:01,105 15624 [INFO ] - VERBOSE: Exporting function 'Get-PackageParametersBuiltIn'.
2024-06-03 16:53:01,107 15624 [INFO ] - VERBOSE: Exporting function 'Get-ToolsLocation'.
2024-06-03 16:53:01,108 15624 [INFO ] - VERBOSE: Exporting function 'Get-UACEnabled'.
2024-06-03 16:53:01,110 15624 [INFO ] - VERBOSE: Exporting function 'Get-UninstallRegistryKey'.
2024-06-03 16:53:01,111 15624 [INFO ] - VERBOSE: Exporting function 'Get-VirusCheckValid'.
2024-06-03 16:53:01,113 15624 [INFO ] - VERBOSE: Exporting function 'Get-WebFile'.
2024-06-03 16:53:01,114 15624 [INFO ] - VERBOSE: Exporting function 'Get-WebFileName'.
2024-06-03 16:53:01,116 15624 [INFO ] - VERBOSE: Exporting function 'Get-WebHeaders'.
2024-06-03 16:53:01,117 15624 [INFO ] - VERBOSE: Exporting function 'Install-BinFile'.
2024-06-03 16:53:01,119 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyEnvironmentVariable'.
2024-06-03 16:53:01,120 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyExplorerMenuItem'.
2024-06-03 16:53:01,122 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyFileAssociation'.
2024-06-03 16:53:01,123 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyInstallPackage'.
2024-06-03 16:53:01,124 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyPackage'.
2024-06-03 16:53:01,126 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyPath'.
2024-06-03 16:53:01,127 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyPinnedTaskBarItem'.
2024-06-03 16:53:01,129 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyPowershellCommand'.
2024-06-03 16:53:01,131 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyShortcut'.
2024-06-03 16:53:01,133 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyVsixPackage'.
2024-06-03 16:53:01,135 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyZipPackage'.
2024-06-03 16:53:01,136 15624 [INFO ] - VERBOSE: Exporting function 'Install-Vsix'.
2024-06-03 16:53:01,138 15624 [INFO ] - VERBOSE: Exporting function 'Set-EnvironmentVariable'.
2024-06-03 16:53:01,139 15624 [INFO ] - VERBOSE: Exporting function 'Set-PowerShellExitCode'.
2024-06-03 16:53:01,141 15624 [INFO ] - VERBOSE: Exporting function 'Start-ChocolateyProcessAsAdmin'.
2024-06-03 16:53:01,142 15624 [INFO ] - VERBOSE: Exporting function 'Test-ProcessAdminRights'.
2024-06-03 16:53:01,144 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-BinFile'.
2024-06-03 16:53:01,146 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-ChocolateyEnvironmentVariable'.
2024-06-03 16:53:01,147 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-ChocolateyPackage'.
2024-06-03 16:53:01,148 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-ChocolateyZipPackage'.
2024-06-03 16:53:01,150 15624 [INFO ] - VERBOSE: Exporting function 'Update-SessionEnvironment'.
2024-06-03 16:53:01,151 15624 [INFO ] - VERBOSE: Exporting function 'Write-FunctionCallLogMessage'.
2024-06-03 16:53:01,153 15624 [INFO ] - VERBOSE: Exporting alias 'Get-ProcessorBits'.
2024-06-03 16:53:01,154 15624 [INFO ] - VERBOSE: Exporting alias 'Get-OSBitness'.
2024-06-03 16:53:01,156 15624 [INFO ] - VERBOSE: Exporting alias 'Get-InstallRegistryKey'.
2024-06-03 16:53:01,157 15624 [INFO ] - VERBOSE: Exporting alias 'Generate-BinFile'.
2024-06-03 16:53:01,158 15624 [INFO ] - VERBOSE: Exporting alias 'Add-BinFile'.
2024-06-03 16:53:01,160 15624 [INFO ] - VERBOSE: Exporting alias 'Start-ChocolateyProcess'.
2024-06-03 16:53:01,162 15624 [INFO ] - VERBOSE: Exporting alias 'Invoke-ChocolateyProcess'.
2024-06-03 16:53:01,164 15624 [INFO ] - VERBOSE: Exporting alias 'Remove-BinFile'.
2024-06-03 16:53:01,165 15624 [INFO ] - VERBOSE: Exporting alias 'refreshenv'.
2024-06-03 16:53:01,172 15624 [DEBUG] - Loading community extensions
2024-06-03 16:53:01,179 15624 [DEBUG] - Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-compatibility\chocolatey-compatibility.psm1'
2024-06-03 16:53:01,181 15624 [INFO ] - VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-compatibility\chocolatey-compatibility.psm1'.
2024-06-03 16:53:01,209 15624 [DEBUG] - Function 'Get-PackageParameters' exists, ignoring export.
2024-06-03 16:53:01,210 15624 [DEBUG] - Function 'Get-UninstallRegistryKey' exists, ignoring export.
2024-06-03 16:53:01,212 15624 [DEBUG] - Exporting function 'Install-ChocolateyDesktopLink' for backwards compatibility
2024-06-03 16:53:01,215 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyDesktopLink'.
2024-06-03 16:53:01,217 15624 [DEBUG] - Exporting function 'Write-ChocolateyFailure' for backwards compatibility
2024-06-03 16:53:01,220 15624 [INFO ] - VERBOSE: Exporting function 'Write-ChocolateyFailure'.
2024-06-03 16:53:01,222 15624 [DEBUG] - Exporting function 'Write-ChocolateySuccess' for backwards compatibility
2024-06-03 16:53:01,225 15624 [INFO ] - VERBOSE: Exporting function 'Write-ChocolateySuccess'.
2024-06-03 16:53:01,227 15624 [DEBUG] - Exporting function 'Write-FileUpdateLog' for backwards compatibility
2024-06-03 16:53:01,230 15624 [INFO ] - VERBOSE: Exporting function 'Write-FileUpdateLog'.
2024-06-03 16:53:01,232 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyDesktopLink'.
2024-06-03 16:53:01,233 15624 [INFO ] - VERBOSE: Importing function 'Write-ChocolateyFailure'.
2024-06-03 16:53:01,235 15624 [INFO ] - VERBOSE: Importing function 'Write-ChocolateySuccess'.
2024-06-03 16:53:01,236 15624 [INFO ] - VERBOSE: Importing function 'Write-FileUpdateLog'.
2024-06-03 16:53:01,238 15624 [DEBUG] - Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-core\chocolatey-core.psm1'
2024-06-03 16:53:01,240 15624 [INFO ] - VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-core\chocolatey-core.psm1'.
2024-06-03 16:53:01,284 15624 [INFO ] - VERBOSE: Exporting function 'Get-AppInstallLocation'.
2024-06-03 16:53:01,286 15624 [INFO ] - VERBOSE: Exporting function 'Get-AvailableDriveLetter'.
2024-06-03 16:53:01,288 15624 [INFO ] - VERBOSE: Exporting function 'Get-EffectiveProxy'.
2024-06-03 16:53:01,289 15624 [INFO ] - VERBOSE: Exporting function 'Get-PackageCacheLocation'.
2024-06-03 16:53:01,291 15624 [INFO ] - VERBOSE: Exporting function 'Get-WebContent'.
2024-06-03 16:53:01,293 15624 [INFO ] - VERBOSE: Exporting function 'Register-Application'.
2024-06-03 16:53:01,295 15624 [INFO ] - VERBOSE: Exporting function 'Remove-Process'.
2024-06-03 16:53:01,297 15624 [INFO ] - VERBOSE: Importing function 'Get-AppInstallLocation'.
2024-06-03 16:53:01,298 15624 [INFO ] - VERBOSE: Importing function 'Get-AvailableDriveLetter'.
2024-06-03 16:53:01,300 15624 [INFO ] - VERBOSE: Importing function 'Get-EffectiveProxy'.
2024-06-03 16:53:01,302 15624 [INFO ] - VERBOSE: Importing function 'Get-PackageCacheLocation'.
2024-06-03 16:53:01,304 15624 [INFO ] - VERBOSE: Importing function 'Get-WebContent'.
2024-06-03 16:53:01,306 15624 [INFO ] - VERBOSE: Importing function 'Register-Application'.
2024-06-03 16:53:01,308 15624 [INFO ] - VERBOSE: Importing function 'Remove-Process'.
2024-06-03 16:53:01,311 15624 [DEBUG] - Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-dotnetfx\chocolatey-dotnetfx.psm1'
2024-06-03 16:53:01,312 15624 [INFO ] - VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-dotnetfx\chocolatey-dotnetfx.psm1'.
2024-06-03 16:53:01,331 15624 [INFO ] - VERBOSE: Exporting function 'Install-DotNetFramework'.
2024-06-03 16:53:01,333 15624 [INFO ] - VERBOSE: Exporting function 'Install-DotNetDevPack'.
2024-06-03 16:53:01,336 15624 [INFO ] - VERBOSE: Importing function 'Install-DotNetDevPack'.
2024-06-03 16:53:01,338 15624 [INFO ] - VERBOSE: Importing function 'Install-DotNetFramework'.
2024-06-03 16:53:01,340 15624 [DEBUG] - Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-misc-helpers\chocolatey-misc-helpers.psm1'
2024-06-03 16:53:01,342 15624 [INFO ] - VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-misc-helpers\chocolatey-misc-helpers.psm1'.
2024-06-03 16:53:01,378 15624 [INFO ] - VERBOSE: Exporting function 'Enable-AutoPin'.
2024-06-03 16:53:01,379 15624 [INFO ] - VERBOSE: Exporting function 'Show-Patreon'.
2024-06-03 16:53:01,381 15624 [INFO ] - VERBOSE: Exporting function 'Show-PayPal'.
2024-06-03 16:53:01,383 15624 [INFO ] - VERBOSE: Exporting function 'Show-ToastMessage'.
2024-06-03 16:53:01,385 15624 [INFO ] - VERBOSE: Exporting function 'Start-CheckandStop'.
2024-06-03 16:53:01,386 15624 [INFO ] - VERBOSE: Exporting function 'Start-CheckandThrow'.
2024-06-03 16:53:01,388 15624 [INFO ] - VERBOSE: Exporting function 'Start-WaitandStop'.
2024-06-03 16:53:01,389 15624 [INFO ] - VERBOSE: Exporting function 'Start-WaitandStopActual'.
2024-06-03 16:53:01,390 15624 [INFO ] - VERBOSE: Exporting function 'Test-Dependency'.
2024-06-03 16:53:01,395 15624 [INFO ] - VERBOSE: Exporting function 'Test-URL'.
2024-06-03 16:53:01,397 15624 [INFO ] - VERBOSE: Importing function 'Enable-AutoPin'.
2024-06-03 16:53:01,398 15624 [INFO ] - VERBOSE: Importing function 'Show-Patreon'.
2024-06-03 16:53:01,400 15624 [INFO ] - VERBOSE: Importing function 'Show-PayPal'.
2024-06-03 16:53:01,401 15624 [INFO ] - VERBOSE: Importing function 'Show-ToastMessage'.
2024-06-03 16:53:01,403 15624 [INFO ] - VERBOSE: Importing function 'Start-CheckandStop'.
2024-06-03 16:53:01,404 15624 [INFO ] - VERBOSE: Importing function 'Start-CheckandThrow'.
2024-06-03 16:53:01,406 15624 [INFO ] - VERBOSE: Importing function 'Start-WaitandStop'.
2024-06-03 16:53:01,407 15624 [INFO ] - VERBOSE: Importing function 'Start-WaitandStopActual'.
2024-06-03 16:53:01,409 15624 [INFO ] - VERBOSE: Importing function 'Test-Dependency'.
2024-06-03 16:53:01,410 15624 [INFO ] - VERBOSE: Importing function 'Test-URL'.
2024-06-03 16:53:01,413 15624 [DEBUG] - Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-os-dependency\chocolatey-os-dependency.psm1'
2024-06-03 16:53:01,414 15624 [INFO ] - VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-os-dependency\chocolatey-os-dependency.psm1'.
2024-06-03 16:53:01,422 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win11'.
2024-06-03 16:53:01,424 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win10'.
2024-06-03 16:53:01,425 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win81'.
2024-06-03 16:53:01,428 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win80'.
2024-06-03 16:53:01,429 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win8'.
2024-06-03 16:53:01,431 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win7'.
2024-06-03 16:53:01,432 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-WinMinimumBuild'.
2024-06-03 16:53:01,434 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-WinRequiredBuild'.
2024-06-03 16:53:01,436 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win10'.
2024-06-03 16:53:01,437 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win11'.
2024-06-03 16:53:01,438 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win7'.
2024-06-03 16:53:01,440 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win8'.
2024-06-03 16:53:01,441 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win80'.
2024-06-03 16:53:01,443 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win81'.
2024-06-03 16:53:01,445 15624 [INFO ] - VERBOSE: Importing function 'Confirm-WinMinimumBuild'.
2024-06-03 16:53:01,447 15624 [INFO ] - VERBOSE: Importing function 'Confirm-WinRequiredBuild'.
2024-06-03 16:53:01,449 15624 [DEBUG] - Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-visualstudio\chocolatey-visualstudio.extension.psm1'
2024-06-03 16:53:01,450 15624 [INFO ] - VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-visualstudio\chocolatey-visualstudio.extension.psm1'.
2024-06-03 16:53:01,601 15624 [INFO ] - VERBOSE: Exporting function 'Add-VisualStudioComponent'.
2024-06-03 16:53:01,602 15624 [INFO ] - VERBOSE: Exporting function 'Add-VisualStudioWorkload'.
2024-06-03 16:53:01,604 15624 [INFO ] - VERBOSE: Exporting function 'Get-VisualStudioInstaller'.
2024-06-03 16:53:01,606 15624 [INFO ] - VERBOSE: Exporting function 'Get-VisualStudioInstallerHealth'.
2024-06-03 16:53:01,607 15624 [INFO ] - VERBOSE: Exporting function 'Get-VisualStudioInstance'.
2024-06-03 16:53:01,609 15624 [INFO ] - VERBOSE: Exporting function 'Get-VisualStudioVsixInstaller'.
2024-06-03 16:53:01,610 15624 [INFO ] - VERBOSE: Exporting function 'Install-VisualStudio'.
2024-06-03 16:53:01,612 15624 [INFO ] - VERBOSE: Exporting function 'Install-VisualStudioInstaller'.
2024-06-03 16:53:01,614 15624 [INFO ] - VERBOSE: Exporting function 'Install-VisualStudioVsixExtension'.
2024-06-03 16:53:01,617 15624 [INFO ] - VERBOSE: Exporting function 'Remove-VisualStudioComponent'.
2024-06-03 16:53:01,619 15624 [INFO ] - VERBOSE: Exporting function 'Remove-VisualStudioProduct'.
2024-06-03 16:53:01,621 15624 [INFO ] - VERBOSE: Exporting function 'Remove-VisualStudioWorkload'.
2024-06-03 16:53:01,623 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-VisualStudio'.
2024-06-03 16:53:01,625 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-VisualStudioVsixExtension'.
2024-06-03 16:53:01,627 15624 [INFO ] - VERBOSE: Importing function 'Add-VisualStudioComponent'.
2024-06-03 16:53:01,628 15624 [INFO ] - VERBOSE: Importing function 'Add-VisualStudioWorkload'.
2024-06-03 16:53:01,631 15624 [INFO ] - VERBOSE: Importing function 'Get-VisualStudioInstaller'.
2024-06-03 16:53:01,632 15624 [INFO ] - VERBOSE: Importing function 'Get-VisualStudioInstallerHealth'.
2024-06-03 16:53:01,634 15624 [INFO ] - VERBOSE: Importing function 'Get-VisualStudioInstance'.
2024-06-03 16:53:01,635 15624 [INFO ] - VERBOSE: Importing function 'Get-VisualStudioVsixInstaller'.
2024-06-03 16:53:01,637 15624 [INFO ] - VERBOSE: Importing function 'Install-VisualStudio'.
2024-06-03 16:53:01,638 15624 [INFO ] - VERBOSE: Importing function 'Install-VisualStudioInstaller'.
2024-06-03 16:53:01,640 15624 [INFO ] - VERBOSE: Importing function 'Install-VisualStudioVsixExtension'.
2024-06-03 16:53:01,641 15624 [INFO ] - VERBOSE: Importing function 'Remove-VisualStudioComponent'.
2024-06-03 16:53:01,642 15624 [INFO ] - VERBOSE: Importing function 'Remove-VisualStudioProduct'.
2024-06-03 16:53:01,644 15624 [INFO ] - VERBOSE: Importing function 'Remove-VisualStudioWorkload'.
2024-06-03 16:53:01,646 15624 [INFO ] - VERBOSE: Importing function 'Uninstall-VisualStudio'.
2024-06-03 16:53:01,648 15624 [INFO ] - VERBOSE: Importing function 'Uninstall-VisualStudioVsixExtension'.
2024-06-03 16:53:01,651 15624 [DEBUG] - Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-windowsupdate\chocolatey-windowsupdate.psm1'
2024-06-03 16:53:01,652 15624 [INFO ] - VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-windowsupdate\chocolatey-windowsupdate.psm1'.
2024-06-03 16:53:01,689 15624 [INFO ] - VERBOSE: Exporting function 'Install-WindowsUpdate'.
2024-06-03 16:53:01,691 15624 [INFO ] - VERBOSE: Exporting function 'Test-WindowsUpdate'.
2024-06-03 16:53:01,694 15624 [INFO ] - VERBOSE: Importing function 'Install-WindowsUpdate'.
2024-06-03 16:53:01,695 15624 [INFO ] - VERBOSE: Importing function 'Test-WindowsUpdate'.
2024-06-03 16:53:01,697 15624 [INFO ] - VERBOSE: Exporting function 'Format-FileSize'.
2024-06-03 16:53:01,698 15624 [INFO ] - VERBOSE: Exporting function 'Get-ChecksumValid'.
2024-06-03 16:53:01,700 15624 [INFO ] - VERBOSE: Exporting function 'Get-ChocolateyConfigValue'.
2024-06-03 16:53:01,701 15624 [INFO ] - VERBOSE: Exporting function 'Get-ChocolateyPath'.
2024-06-03 16:53:01,703 15624 [INFO ] - VERBOSE: Exporting function 'Get-ChocolateyUnzip'.
2024-06-03 16:53:01,704 15624 [INFO ] - VERBOSE: Exporting function 'Get-ChocolateyWebFile'.
2024-06-03 16:53:01,706 15624 [INFO ] - VERBOSE: Exporting function 'Get-EnvironmentVariable'.
2024-06-03 16:53:01,708 15624 [INFO ] - VERBOSE: Exporting function 'Get-EnvironmentVariableNames'.
2024-06-03 16:53:01,709 15624 [INFO ] - VERBOSE: Exporting function 'Get-FtpFile'.
2024-06-03 16:53:01,711 15624 [INFO ] - VERBOSE: Exporting function 'Get-OSArchitectureWidth'.
2024-06-03 16:53:01,713 15624 [INFO ] - VERBOSE: Exporting function 'Get-PackageParameters'.
2024-06-03 16:53:01,714 15624 [INFO ] - VERBOSE: Exporting function 'Get-PackageParametersBuiltIn'.
2024-06-03 16:53:01,716 15624 [INFO ] - VERBOSE: Exporting function 'Get-ToolsLocation'.
2024-06-03 16:53:01,717 15624 [INFO ] - VERBOSE: Exporting function 'Get-UACEnabled'.
2024-06-03 16:53:01,719 15624 [INFO ] - VERBOSE: Exporting function 'Get-UninstallRegistryKey'.
2024-06-03 16:53:01,720 15624 [INFO ] - VERBOSE: Exporting function 'Get-VirusCheckValid'.
2024-06-03 16:53:01,722 15624 [INFO ] - VERBOSE: Exporting function 'Get-WebFile'.
2024-06-03 16:53:01,726 15624 [INFO ] - VERBOSE: Exporting function 'Get-WebFileName'.
2024-06-03 16:53:01,728 15624 [INFO ] - VERBOSE: Exporting function 'Get-WebHeaders'.
2024-06-03 16:53:01,730 15624 [INFO ] - VERBOSE: Exporting function 'Install-BinFile'.
2024-06-03 16:53:01,731 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyEnvironmentVariable'.
2024-06-03 16:53:01,733 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyExplorerMenuItem'.
2024-06-03 16:53:01,734 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyFileAssociation'.
2024-06-03 16:53:01,736 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyInstallPackage'.
2024-06-03 16:53:01,738 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyPackage'.
2024-06-03 16:53:01,739 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyPath'.
2024-06-03 16:53:01,741 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyPinnedTaskBarItem'.
2024-06-03 16:53:01,742 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyPowershellCommand'.
2024-06-03 16:53:01,744 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyShortcut'.
2024-06-03 16:53:01,746 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyVsixPackage'.
2024-06-03 16:53:01,747 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyZipPackage'.
2024-06-03 16:53:01,749 15624 [INFO ] - VERBOSE: Exporting function 'Install-Vsix'.
2024-06-03 16:53:01,750 15624 [INFO ] - VERBOSE: Exporting function 'Set-EnvironmentVariable'.
2024-06-03 16:53:01,752 15624 [INFO ] - VERBOSE: Exporting function 'Set-PowerShellExitCode'.
2024-06-03 16:53:01,753 15624 [INFO ] - VERBOSE: Exporting function 'Start-ChocolateyProcessAsAdmin'.
2024-06-03 16:53:01,755 15624 [INFO ] - VERBOSE: Exporting function 'Test-ProcessAdminRights'.
2024-06-03 16:53:01,757 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-BinFile'.
2024-06-03 16:53:01,758 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-ChocolateyEnvironmentVariable'.
2024-06-03 16:53:01,760 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-ChocolateyPackage'.
2024-06-03 16:53:01,762 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-ChocolateyZipPackage'.
2024-06-03 16:53:01,763 15624 [INFO ] - VERBOSE: Exporting function 'Update-SessionEnvironment'.
2024-06-03 16:53:01,765 15624 [INFO ] - VERBOSE: Exporting function 'Write-FunctionCallLogMessage'.
2024-06-03 16:53:01,766 15624 [INFO ] - VERBOSE: Exporting function 'Install-ChocolateyDesktopLink'.
2024-06-03 16:53:01,768 15624 [INFO ] - VERBOSE: Exporting function 'Write-ChocolateyFailure'.
2024-06-03 16:53:01,770 15624 [INFO ] - VERBOSE: Exporting function 'Write-ChocolateySuccess'.
2024-06-03 16:53:01,771 15624 [INFO ] - VERBOSE: Exporting function 'Write-FileUpdateLog'.
2024-06-03 16:53:01,772 15624 [INFO ] - VERBOSE: Exporting function 'Get-AppInstallLocation'.
2024-06-03 16:53:01,774 15624 [INFO ] - VERBOSE: Exporting function 'Get-AvailableDriveLetter'.
2024-06-03 16:53:01,776 15624 [INFO ] - VERBOSE: Exporting function 'Get-EffectiveProxy'.
2024-06-03 16:53:01,777 15624 [INFO ] - VERBOSE: Exporting function 'Get-PackageCacheLocation'.
2024-06-03 16:53:01,779 15624 [INFO ] - VERBOSE: Exporting function 'Get-WebContent'.
2024-06-03 16:53:01,780 15624 [INFO ] - VERBOSE: Exporting function 'Register-Application'.
2024-06-03 16:53:01,782 15624 [INFO ] - VERBOSE: Exporting function 'Remove-Process'.
2024-06-03 16:53:01,783 15624 [INFO ] - VERBOSE: Exporting function 'Install-DotNetDevPack'.
2024-06-03 16:53:01,785 15624 [INFO ] - VERBOSE: Exporting function 'Install-DotNetFramework'.
2024-06-03 16:53:01,787 15624 [INFO ] - VERBOSE: Exporting function 'Enable-AutoPin'.
2024-06-03 16:53:01,788 15624 [INFO ] - VERBOSE: Exporting function 'Show-Patreon'.
2024-06-03 16:53:01,790 15624 [INFO ] - VERBOSE: Exporting function 'Show-PayPal'.
2024-06-03 16:53:01,791 15624 [INFO ] - VERBOSE: Exporting function 'Show-ToastMessage'.
2024-06-03 16:53:01,793 15624 [INFO ] - VERBOSE: Exporting function 'Start-CheckandStop'.
2024-06-03 16:53:01,794 15624 [INFO ] - VERBOSE: Exporting function 'Start-CheckandThrow'.
2024-06-03 16:53:01,796 15624 [INFO ] - VERBOSE: Exporting function 'Start-WaitandStop'.
2024-06-03 16:53:01,797 15624 [INFO ] - VERBOSE: Exporting function 'Start-WaitandStopActual'.
2024-06-03 16:53:01,799 15624 [INFO ] - VERBOSE: Exporting function 'Test-Dependency'.
2024-06-03 16:53:01,801 15624 [INFO ] - VERBOSE: Exporting function 'Test-URL'.
2024-06-03 16:53:01,803 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win10'.
2024-06-03 16:53:01,804 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win11'.
2024-06-03 16:53:01,806 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win7'.
2024-06-03 16:53:01,807 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win8'.
2024-06-03 16:53:01,809 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win80'.
2024-06-03 16:53:01,810 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-Win81'.
2024-06-03 16:53:01,812 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-WinMinimumBuild'.
2024-06-03 16:53:01,813 15624 [INFO ] - VERBOSE: Exporting function 'Confirm-WinRequiredBuild'.
2024-06-03 16:53:01,816 15624 [INFO ] - VERBOSE: Exporting function 'Add-VisualStudioComponent'.
2024-06-03 16:53:01,817 15624 [INFO ] - VERBOSE: Exporting function 'Add-VisualStudioWorkload'.
2024-06-03 16:53:01,819 15624 [INFO ] - VERBOSE: Exporting function 'Get-VisualStudioInstaller'.
2024-06-03 16:53:01,821 15624 [INFO ] - VERBOSE: Exporting function 'Get-VisualStudioInstallerHealth'.
2024-06-03 16:53:01,822 15624 [INFO ] - VERBOSE: Exporting function 'Get-VisualStudioInstance'.
2024-06-03 16:53:01,824 15624 [INFO ] - VERBOSE: Exporting function 'Get-VisualStudioVsixInstaller'.
2024-06-03 16:53:01,825 15624 [INFO ] - VERBOSE: Exporting function 'Install-VisualStudio'.
2024-06-03 16:53:01,827 15624 [INFO ] - VERBOSE: Exporting function 'Install-VisualStudioInstaller'.
2024-06-03 16:53:01,828 15624 [INFO ] - VERBOSE: Exporting function 'Install-VisualStudioVsixExtension'.
2024-06-03 16:53:01,831 15624 [INFO ] - VERBOSE: Exporting function 'Remove-VisualStudioComponent'.
2024-06-03 16:53:01,833 15624 [INFO ] - VERBOSE: Exporting function 'Remove-VisualStudioProduct'.
2024-06-03 16:53:01,835 15624 [INFO ] - VERBOSE: Exporting function 'Remove-VisualStudioWorkload'.
2024-06-03 16:53:01,837 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-VisualStudio'.
2024-06-03 16:53:01,838 15624 [INFO ] - VERBOSE: Exporting function 'Uninstall-VisualStudioVsixExtension'.
2024-06-03 16:53:01,839 15624 [INFO ] - VERBOSE: Exporting function 'Install-WindowsUpdate'.
2024-06-03 16:53:01,841 15624 [INFO ] - VERBOSE: Exporting function 'Test-WindowsUpdate'.
2024-06-03 16:53:01,843 15624 [INFO ] - VERBOSE: Exporting alias 'Get-ProcessorBits'.
2024-06-03 16:53:01,844 15624 [INFO ] - VERBOSE: Exporting alias 'Get-OSBitness'.
2024-06-03 16:53:01,847 15624 [INFO ] - VERBOSE: Exporting alias 'Get-InstallRegistryKey'.
2024-06-03 16:53:01,849 15624 [INFO ] - VERBOSE: Exporting alias 'Generate-BinFile'.
2024-06-03 16:53:01,850 15624 [INFO ] - VERBOSE: Exporting alias 'Add-BinFile'.
2024-06-03 16:53:01,851 15624 [INFO ] - VERBOSE: Exporting alias 'Start-ChocolateyProcess'.
2024-06-03 16:53:01,853 15624 [INFO ] - VERBOSE: Exporting alias 'Invoke-ChocolateyProcess'.
2024-06-03 16:53:01,855 15624 [INFO ] - VERBOSE: Exporting alias 'Remove-BinFile'.
2024-06-03 16:53:01,856 15624 [INFO ] - VERBOSE: Exporting alias 'refreshenv'.
2024-06-03 16:53:01,858 15624 [INFO ] - VERBOSE: Importing function 'Add-VisualStudioComponent'.
2024-06-03 16:53:01,859 15624 [INFO ] - VERBOSE: Importing function 'Add-VisualStudioWorkload'.
2024-06-03 16:53:01,861 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win10'.
2024-06-03 16:53:01,864 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win11'.
2024-06-03 16:53:01,866 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win7'.
2024-06-03 16:53:01,867 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win8'.
2024-06-03 16:53:01,869 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win80'.
2024-06-03 16:53:01,872 15624 [INFO ] - VERBOSE: Importing function 'Confirm-Win81'.
2024-06-03 16:53:01,873 15624 [INFO ] - VERBOSE: Importing function 'Confirm-WinMinimumBuild'.
2024-06-03 16:53:01,875 15624 [INFO ] - VERBOSE: Importing function 'Confirm-WinRequiredBuild'.
2024-06-03 16:53:01,877 15624 [INFO ] - VERBOSE: Importing function 'Enable-AutoPin'.
2024-06-03 16:53:01,879 15624 [INFO ] - VERBOSE: Importing function 'Format-FileSize'.
2024-06-03 16:53:01,880 15624 [INFO ] - VERBOSE: Importing function 'Get-AppInstallLocation'.
2024-06-03 16:53:01,882 15624 [INFO ] - VERBOSE: Importing function 'Get-AvailableDriveLetter'.
2024-06-03 16:53:01,883 15624 [INFO ] - VERBOSE: Importing function 'Get-ChecksumValid'.
2024-06-03 16:53:01,885 15624 [INFO ] - VERBOSE: Importing function 'Get-ChocolateyConfigValue'.
2024-06-03 16:53:01,886 15624 [INFO ] - VERBOSE: Importing function 'Get-ChocolateyPath'.
2024-06-03 16:53:01,888 15624 [INFO ] - VERBOSE: Importing function 'Get-ChocolateyUnzip'.
2024-06-03 16:53:01,889 15624 [INFO ] - VERBOSE: Importing function 'Get-ChocolateyWebFile'.
2024-06-03 16:53:01,891 15624 [INFO ] - VERBOSE: Importing function 'Get-EffectiveProxy'.
2024-06-03 16:53:01,892 15624 [INFO ] - VERBOSE: Importing function 'Get-EnvironmentVariable'.
2024-06-03 16:53:01,895 15624 [INFO ] - VERBOSE: Importing function 'Get-EnvironmentVariableNames'.
2024-06-03 16:53:01,898 15624 [INFO ] - VERBOSE: Importing function 'Get-FtpFile'.
2024-06-03 16:53:01,900 15624 [INFO ] - VERBOSE: Importing function 'Get-OSArchitectureWidth'.
2024-06-03 16:53:01,902 15624 [INFO ] - VERBOSE: Importing function 'Get-PackageCacheLocation'.
2024-06-03 16:53:01,904 15624 [INFO ] - VERBOSE: Importing function 'Get-PackageParameters'.
2024-06-03 16:53:01,906 15624 [INFO ] - VERBOSE: Importing function 'Get-PackageParametersBuiltIn'.
2024-06-03 16:53:01,908 15624 [INFO ] - VERBOSE: Importing function 'Get-ToolsLocation'.
2024-06-03 16:53:01,910 15624 [INFO ] - VERBOSE: Importing function 'Get-UACEnabled'.
2024-06-03 16:53:01,913 15624 [INFO ] - VERBOSE: Importing function 'Get-UninstallRegistryKey'.
2024-06-03 16:53:01,915 15624 [INFO ] - VERBOSE: Importing function 'Get-VirusCheckValid'.
2024-06-03 16:53:01,917 15624 [INFO ] - VERBOSE: Importing function 'Get-VisualStudioInstaller'.
2024-06-03 16:53:01,919 15624 [INFO ] - VERBOSE: Importing function 'Get-VisualStudioInstallerHealth'.
2024-06-03 16:53:01,920 15624 [INFO ] - VERBOSE: Importing function 'Get-VisualStudioInstance'.
2024-06-03 16:53:01,922 15624 [INFO ] - VERBOSE: Importing function 'Get-VisualStudioVsixInstaller'.
2024-06-03 16:53:01,923 15624 [INFO ] - VERBOSE: Importing function 'Get-WebContent'.
2024-06-03 16:53:01,925 15624 [INFO ] - VERBOSE: Importing function 'Get-WebFile'.
2024-06-03 16:53:01,927 15624 [INFO ] - VERBOSE: Importing function 'Get-WebFileName'.
2024-06-03 16:53:01,928 15624 [INFO ] - VERBOSE: Importing function 'Get-WebHeaders'.
2024-06-03 16:53:01,930 15624 [INFO ] - VERBOSE: Importing function 'Install-BinFile'.
2024-06-03 16:53:01,931 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyDesktopLink'.
2024-06-03 16:53:01,933 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyEnvironmentVariable'.
2024-06-03 16:53:01,934 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyExplorerMenuItem'.
2024-06-03 16:53:01,936 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyFileAssociation'.
2024-06-03 16:53:01,937 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyInstallPackage'.
2024-06-03 16:53:01,939 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyPackage'.
2024-06-03 16:53:01,940 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyPath'.
2024-06-03 16:53:01,942 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyPinnedTaskBarItem'.
2024-06-03 16:53:01,945 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyPowershellCommand'.
2024-06-03 16:53:01,947 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyShortcut'.
2024-06-03 16:53:01,948 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyVsixPackage'.
2024-06-03 16:53:01,950 15624 [INFO ] - VERBOSE: Importing function 'Install-ChocolateyZipPackage'.
2024-06-03 16:53:01,951 15624 [INFO ] - VERBOSE: Importing function 'Install-DotNetDevPack'.
2024-06-03 16:53:01,953 15624 [INFO ] - VERBOSE: Importing function 'Install-DotNetFramework'.
2024-06-03 16:53:01,954 15624 [INFO ] - VERBOSE: Importing function 'Install-VisualStudio'.
2024-06-03 16:53:01,956 15624 [INFO ] - VERBOSE: Importing function 'Install-VisualStudioInstaller'.
2024-06-03 16:53:01,957 15624 [INFO ] - VERBOSE: Importing function 'Install-VisualStudioVsixExtension'.
2024-06-03 16:53:01,960 15624 [INFO ] - VERBOSE: Importing function 'Install-Vsix'.
2024-06-03 16:53:01,962 15624 [INFO ] - VERBOSE: Importing function 'Install-WindowsUpdate'.
2024-06-03 16:53:01,965 15624 [INFO ] - VERBOSE: Importing function 'Register-Application'.
2024-06-03 16:53:01,966 15624 [INFO ] - VERBOSE: Importing function 'Remove-Process'.
2024-06-03 16:53:01,968 15624 [INFO ] - VERBOSE: Importing function 'Remove-VisualStudioComponent'.
2024-06-03 16:53:01,970 15624 [INFO ] - VERBOSE: Importing function 'Remove-VisualStudioProduct'.
2024-06-03 16:53:01,972 15624 [INFO ] - VERBOSE: Importing function 'Remove-VisualStudioWorkload'.
2024-06-03 16:53:01,976 15624 [INFO ] - VERBOSE: Importing function 'Set-EnvironmentVariable'.
2024-06-03 16:53:01,979 15624 [INFO ] - VERBOSE: Importing function 'Set-PowerShellExitCode'.
2024-06-03 16:53:01,981 15624 [INFO ] - VERBOSE: Importing function 'Show-Patreon'.
2024-06-03 16:53:01,982 15624 [INFO ] - VERBOSE: Importing function 'Show-PayPal'.
2024-06-03 16:53:01,984 15624 [INFO ] - VERBOSE: Importing function 'Show-ToastMessage'.
2024-06-03 16:53:01,986 15624 [INFO ] - VERBOSE: Importing function 'Start-CheckandStop'.
2024-06-03 16:53:01,988 15624 [INFO ] - VERBOSE: Importing function 'Start-CheckandThrow'.
2024-06-03 16:53:01,991 15624 [INFO ] - VERBOSE: Importing function 'Start-ChocolateyProcessAsAdmin'.
2024-06-03 16:53:01,993 15624 [INFO ] - VERBOSE: Importing function 'Start-WaitandStop'.
2024-06-03 16:53:01,996 15624 [INFO ] - VERBOSE: Importing function 'Start-WaitandStopActual'.
2024-06-03 16:53:01,999 15624 [INFO ] - VERBOSE: Importing function 'Test-Dependency'.
2024-06-03 16:53:02,001 15624 [INFO ] - VERBOSE: Importing function 'Test-ProcessAdminRights'.
2024-06-03 16:53:02,003 15624 [INFO ] - VERBOSE: Importing function 'Test-URL'.
2024-06-03 16:53:02,005 15624 [INFO ] - VERBOSE: Importing function 'Test-WindowsUpdate'.
2024-06-03 16:53:02,007 15624 [INFO ] - VERBOSE: Importing function 'Uninstall-BinFile'.
2024-06-03 16:53:02,009 15624 [INFO ] - VERBOSE: Importing function 'Uninstall-ChocolateyEnvironmentVariable'.
2024-06-03 16:53:02,011 15624 [INFO ] - VERBOSE: Importing function 'Uninstall-ChocolateyPackage'.
2024-06-03 16:53:02,013 15624 [INFO ] - VERBOSE: Importing function 'Uninstall-ChocolateyZipPackage'.
2024-06-03 16:53:02,015 15624 [INFO ] - VERBOSE: Importing function 'Uninstall-VisualStudio'.
2024-06-03 16:53:02,016 15624 [INFO ] - VERBOSE: Importing function 'Uninstall-VisualStudioVsixExtension'.
2024-06-03 16:53:02,018 15624 [INFO ] - VERBOSE: Importing function 'Update-SessionEnvironment'.
2024-06-03 16:53:02,020 15624 [INFO ] - VERBOSE: Importing function 'Write-ChocolateyFailure'.
2024-06-03 16:53:02,022 15624 [INFO ] - VERBOSE: Importing function 'Write-ChocolateySuccess'.
2024-06-03 16:53:02,023 15624 [INFO ] - VERBOSE: Importing function 'Write-FileUpdateLog'.
2024-06-03 16:53:02,025 15624 [INFO ] - VERBOSE: Importing function 'Write-FunctionCallLogMessage'.
2024-06-03 16:53:02,027 15624 [INFO ] - VERBOSE: Importing alias 'Add-BinFile'.
2024-06-03 16:53:02,029 15624 [INFO ] - VERBOSE: Importing alias 'Generate-BinFile'.
2024-06-03 16:53:02,031 15624 [INFO ] - VERBOSE: Importing alias 'Get-InstallRegistryKey'.
2024-06-03 16:53:02,033 15624 [INFO ] - VERBOSE: Importing alias 'Get-OSBitness'.
2024-06-03 16:53:02,035 15624 [INFO ] - VERBOSE: Importing alias 'Get-ProcessorBits'.
2024-06-03 16:53:02,037 15624 [INFO ] - VERBOSE: Importing alias 'Invoke-ChocolateyProcess'.
2024-06-03 16:53:02,038 15624 [INFO ] - VERBOSE: Importing alias 'refreshenv'.
2024-06-03 16:53:02,040 15624 [INFO ] - VERBOSE: Importing alias 'Remove-BinFile'.
2024-06-03 16:53:02,041 15624 [INFO ] - VERBOSE: Importing alias 'Start-ChocolateyProcess'.
2024-06-03 16:53:02,065 15624 [DEBUG] - ---------------------------Script Execution---------------------------
2024-06-03 16:53:02,069 15624 [DEBUG] - Running 'ChocolateyScriptRunner' for microsoft-windows-terminal v1.20.11271 with packageScript 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1', packageFolder:'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal', installArguments: '', packageParameters: '', preRunHookScripts: '', postRunHookScripts: '',
2024-06-03 16:53:02,077 15624 [DEBUG] - Running package script 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'
2024-06-03 16:53:09,950 15624 [INFO ] - VERBOSE: Exportfunktion "Get-AppxLastError".
2024-06-03 16:53:09,952 15624 [INFO ] - VERBOSE: Exportfunktion "Get-AppxLog".
2024-06-03 16:53:09,954 15624 [INFO ] - VERBOSE: Exportieren des Alias "Add-AppPackage".
2024-06-03 16:53:09,956 15624 [INFO ] - VERBOSE: Exportieren des Alias "Get-AppPackage".
2024-06-03 16:53:09,958 15624 [INFO ] - VERBOSE: Exportieren des Alias "Get-AppPackageManifest".
2024-06-03 16:53:09,960 15624 [INFO ] - VERBOSE: Exportieren des Alias "Remove-AppPackage".
2024-06-03 16:53:09,961 15624 [INFO ] - VERBOSE: Exportieren des Alias "Get-AppPackageVolume".
2024-06-03 16:53:09,963 15624 [INFO ] - VERBOSE: Exportieren des Alias "Add-AppPackageVolume".
2024-06-03 16:53:09,965 15624 [INFO ] - VERBOSE: Exportieren des Alias "Remove-AppPackageVolume".
2024-06-03 16:53:09,966 15624 [INFO ] - VERBOSE: Exportieren des Alias "Mount-AppPackageVolume".
2024-06-03 16:53:09,968 15624 [INFO ] - VERBOSE: Exportieren des Alias "Dismount-AppPackageVolume".
2024-06-03 16:53:09,970 15624 [INFO ] - VERBOSE: Exportieren des Alias "Move-AppPackage".
2024-06-03 16:53:09,972 15624 [INFO ] - VERBOSE: Exportieren des Alias "Get-AppPacakgeDefaultVolume".
2024-06-03 16:53:09,974 15624 [INFO ] - VERBOSE: Exportieren des Alias "Set-AppPackageDefaultVolume".
2024-06-03 16:53:09,976 15624 [INFO ] - VERBOSE: Exportieren des Alias "Get-AppPackageLastError".
2024-06-03 16:53:09,978 15624 [INFO ] - VERBOSE: Exportieren des Alias "Get-AppPackageLog".
2024-06-03 16:53:10,820 15624 [ERROR] - ERROR: Cannot convert the "System.Object[]" value of type "System.Object[]" to type "System.Version".
2024-06-03 16:53:10,824 15624 [DEBUG] - Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = '';[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::SystemDefault; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1' -installArguments '' -packageParameters '' -preRunHookScripts $null -postRunHookScripts $null'] exited with '-1'.
2024-06-03 16:53:10,826 15624 [DEBUG] - Calling command ['"C:\WINDOWS\System32\shutdown.exe" /a']
2024-06-03 16:53:10,918 15624 [DEBUG] - Command ['"C:\WINDOWS\System32\shutdown.exe" /a'] exited with '1116'
2024-06-03 16:53:11,190 15624 [DEBUG] - Capturing package files in 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal'
2024-06-03 16:53:11,234 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\microsoft-windows-terminal.nupkg'
 with checksum '665D872458236F6AF8735E101DFD3D45'
2024-06-03 16:53:11,235 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\microsoft-windows-terminal.nuspec'
 with checksum 'D22EC088BC8A4A3E35C4BC6DF0594605'
2024-06-03 16:53:11,238 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal\LICENSE.txt'
 with checksum 'B377DB62B5A030F560ED5BBCA25EA5BE'
2024-06-03 16:53:11,240 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\legal\VERIFICATION.txt'
 with checksum '80DED745D63BD54E10A9B12849E99697'
2024-06-03 16:53:11,242 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'
 with checksum 'FCE4567EE0849E8A91F8504F4C404C52'
2024-06-03 16:53:11,243 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyUninstall.ps1'
 with checksum 'B3BDB5539D0A9CC6AB3716A7F75031FE'
2024-06-03 16:53:11,291 15624 [DEBUG] -  Found 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\Microsoft.WindowsTerminal_1.20.11271.0_8wekyb3d8bbwe.msixbundle'
 with checksum 'D655ABE79CC068DC380F3D42FC566C6D'
2024-06-03 16:53:11,302 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\microsoft-windows-terminal.1.20.11271\.arguments".
2024-06-03 16:53:11,303 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\microsoft-windows-terminal.1.20.11271\.extra".
2024-06-03 16:53:11,305 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\microsoft-windows-terminal.1.20.11271\.version".
2024-06-03 16:53:11,307 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\microsoft-windows-terminal.1.20.11271\.sxs".
2024-06-03 16:53:11,308 15624 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\microsoft-windows-terminal.1.20.11271\.pin".
2024-06-03 16:53:11,317 15624 [DEBUG] - Attempting to delete directory "C:\ProgramData\chocolatey\lib-bad\microsoft-windows-terminal".
2024-06-03 16:53:11,331 15624 [DEBUG] - Sending message 'HandlePackageResultCompletedMessage' out if there are subscribers...
2024-06-03 16:53:11,332 15624 [ERROR] - The upgrade of microsoft-windows-terminal was NOT successful.
2024-06-03 16:53:11,336 15624 [ERROR] - Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'.
See log for details.
2024-06-03 16:53:11,338 15624 [DEBUG] - Attempting to create directory "C:\ProgramData\chocolatey\lib-bad\microsoft-windows-terminal".
2024-06-03 16:53:11,340 15624 [DEBUG] - Moving C:\ProgramData\chocolatey\lib\microsoft-windows-terminal to C:\ProgramData\chocolatey\lib-bad\microsoft-windows-terminal\1.20.11271
2024-06-03 16:53:11,341 15624 [DEBUG] - Moving 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal'
to 'C:\ProgramData\chocolatey\lib-bad\microsoft-windows-terminal\1.20.11271'
2024-06-03 16:53:13,358 15624 [DEBUG] - Attempting rollback
2024-06-03 16:53:13,359 15624 [DEBUG] - Moving C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461 to C:\ProgramData\chocolatey\lib\microsoft-windows-terminal
2024-06-03 16:53:13,361 15624 [DEBUG] - Moving 'C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal\1.17.11461'
to 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal'
2024-06-03 16:53:15,368 15624 [DEBUG] - Attempting to delete directory "C:\ProgramData\chocolatey\lib-bkp\microsoft-windows-terminal".
2024-06-03 16:53:15,381 15624 [WARN ] -
Chocolatey upgraded 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
2024-06-03 16:53:15,384 15624 [INFO ] -
2024-06-03 16:53:15,386 15624 [ERROR] - Failures
2024-06-03 16:53:15,388 15624 [ERROR] -  - microsoft-windows-terminal (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'.
See log for details.
2024-06-03 16:53:15,390 15624 [DEBUG] - Sending message 'PostRunMessage' out if there are subscribers...
2024-06-03 16:53:15,392 15624 [DEBUG] - Exiting with -1


Breaks page thumbnails

The extension works great, especially since Personal Blocklist stopped working entirely, but it also seems to break extensions that insert page thumbnails, like SearchPreview, which Personal Blocklist didn't.
Could you somehow improve coexistence?

Thank you for reporting an issue. I have uploaded a new version that improves compatibility with SearchPreview (except that thumbnails are not inserted to blocked pages). Please try it.


xpcall error handler should throw instead of being silent

Currently, the following code:
local s, e = xpcall(error, function(r)
	print(r);
	error("oh noes!")
end, "cat")

print(s, e)

...will not throw any error and the xpcall result will be false, error in error handling. Instead, it would be nice if the error handler threw itself with the error (so for above, oh noes would be thrown). The issue right now is that it's difficult to debug the error handler if it has an error itself. The only workaround is to put a pcall inside your error handler, which is a bit hacky honestly
local s, e = xpcall(error, function(r)
  local s, e = pcall(function()
    error("oh noes")
  end)

  print(s, e) --> false, oh noes
end, "cat")

print(s, e)

Are you referring to the case when the argument to xpcall is not callable/not a function, or to a case when it errors at runtime?

The function that's passed as the handler should raise its error if it does so. For example
xpcall(function()
  error("oh no!")
end, function()
  error("oh no it broke again!")
end)

This would throw oh no it broke again

Ah, I see. I don't think this can happen.

The existing behavior is documented in xpcall and has been consistent in all 5.x Lua releases, so this would introduce an incompatibility
This would be a breaking change, as any code that uses xpcall with an error handler that isn't guaranteed to work may break the logic of the script - I don't know that we can even safely deploy it
Many callers would probably need to use pcall(xpcall, fun, err) instead of xpcall(fun, err) which seems like a regression in usability


Relationship between TelemetryContexts

Hi,
I don't really understand this flow. Since the session is not available in the telemetry initializer, we have to first copy the session into one TelemetryContext and then in the TelemetryInitializer copy it from that into another TelemetryContext:

What is the relationship between these two TelemetryContexts - do they have different purpose/scope?
If the session is available when populating the first TelemetryContext (in Global.asax) why isn't it available in the TelemetryInitializer?
If I want to ad additional items from the session to the TelemetryContext I always have to do it in at least two places. Since we have multiple web applications using the same TelemetryInitializer we have to have this copied for each application - instead of having it just in the TelemetryInitializer. It feels like I am misunderstanding something...

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e999ab71-aabf-9917-6f50-8fce3e19a0ae
Version Independent ID: b072be7c-c060-00af-4027-8422473f74a1
Content: Send user context IDs to enable usage experiences in Azure Application Insights
Content Source: articles/application-insights/app-insights-usage-send-user-context.md
Service: application-insights
GitHub Login: @NumberByColors
Microsoft Alias: daviste

Thanks for the feedback! We are currently investigating and will update you shortly.

It does look like we could use a bit more explanation in the logic behind our code samples here.  I'm going to assign this to the document author so they can update the document accordingly.

What is the relationship between these two TelemetryContexts - do they have different purpose/scope?

One context is on event representing the whole incoming request (RequestTelemetry). Lifetime of it is entire request execution. While it is being executed there are work happening that can produce other telemetry events. Like outgoing requests. Which also needs to be associated with the user and session. Telemetry Initializer is only used for those "enclosed" telemetry events.

If the session is available when populating the first TelemetryContext (in Global.asax) why isn't it available in the TelemetryInitializer?

Telemetry initializer happens either too early (Begin callback) or too late (End callback). Session store is only active after certain callback and is destroyed before the End callback by design.

If I want to ad additional items from the session to the TelemetryContext I always have to do it in at least two places. Since we have multiple web applications using the same TelemetryInitializer we have to have this copied for each application - instead of having it just in the TelemetryInitializer. It feels like I am misunderstanding something...

Yes. I explained earlier why this is the case. If you only need those items associated with the telemetyr representing incoming request - you can only do it once.

#please-close


[441] Filter by user type

Context
Changes proposed in this pull request
Guidance to review
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Separate admin 'Users' and 'Provider Users' into separate tabs