-
|
This release represents our first stable Windows Package Manager 1.9 build for Windows 10 (1809+), and Windows 11. This release includes the ability to enable experimental features unless blocked by Group Policy Objects (GPO) Sixel support is here to display icons and a new progress visualization. To try out this new feature, you must be using a terminal that supports sixels, such as the latest Windows Terminal Preview build. To enable this feature, include the following snipping in your settings file: {
"$schema": "https://aka.ms/winget-settings.schema.json",
"visual": {
"enableSixels": true,
"progressBar": "sixel"
}
}WinGet Configuration files with DSC Resources requiring elevation can now be handled more gracefully. The "Configure Self Elevation" experimental feature can be enabled with the following snippet in your settings file: {
"$schema": "https://aka.ms/winget-settings.schema.json",
"experimentalFeatures": {
"configureSelfElevate": true
}
}Use "securityContext: elevated" under "directives:" for any resources requiring administrator. WinGet will trigger a single User Account Control (UAC) prompt when the configuration is run under user context. Resources requiring elevation are run elevated, and the rest are run in user context. The following example shows how the .NET Tutorial - Hello World in 5 minutes will be updated to provide a better user experience. # yaml-language-server: $schema=https://aka.ms/configuration-dsc-schema/0.2
properties:
resources:
- resource: Microsoft.WinGet.DSC/WinGetPackage
id: install-dotnet8-SDK
directives:
description: Install .NET 8 SDK
securityContext: elevated
settings:
id: Microsoft.DotNet.SDK.8
source: winget
- resource: Microsoft.WinGet.DSC/WinGetPackage
id: install-vs-code
directives:
description: Install Visual Studio Code
settings:
id: Microsoft.VisualStudioCode
source: winget
- resource: Microsoft.VSCode.DSC/VSCodeExtension
id: install-csharp-dev-kit
dependsOn:
- install-vs-code
directives:
description: Install C# Dev Kit
allowPrerelease: true
settings:
name: ms-dotnettools.csdevkit
exist: true
configurationVersion: 0.2.0What's Changed
New Contributors
Full Changelog: v1.8.1911...v1.9.25180 This discussion was created from the release Windows Package Manager 1.9.25180. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
|
Hey have a bunch of machines upgraded to this latest release = now running winget as system is a no go. IsCOMCall:0; Caller: winget-cli Even running winget via cmd line under system context returns nothing at all - cant bring up and help etc. |
Beta Was this translation helpful? Give feedback.
-
|
Do you get the same results with the Microsoft.WinGet.Client PowerShell module? Note, installing packages in system context is going to need support for "System":
|
Beta Was this translation helpful? Give feedback.
-
|
On Windows 11.
`PS C:\NotBackedUp> Get-WinGetPackage /?
Even if i do get-wingetpackage -query [appname] it says the cmdlet is not supported in windows powershell. |
Beta Was this translation helpful? Give feedback.
-
|
What version of the module is installed? I just installed it from the PowerShell Gallery in Windows PowerShell and ran Get-WinGetPackage (I truncated the output). |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I get the same issue running as SYSTEM after upgrading this morning from v1.8.1911 to v1.9.25180 - checking the version returns nothing.
Same IsCOMCall:0 in the winget logs here C:\Windows\Temp\WinGet\defaultState |
Beta Was this translation helpful? Give feedback.
-
|
Your right about Vlibs being the issue. If you install the latest 2015 VC redist then winget kicks into life from here... Working now after deploying the VC++ Redist. |
Beta Was this translation helpful? Give feedback.
-
|
We now understand this issue as being the confluence of a change to default behavior in VC builds (that started with our 1.9 release builds) combined with a Windows 11 bug whose fix is not quite released yet. We are going to release an updated 1.9 package that uses the older build behavior to prevent this. Installing the latest VC runtime is indeed the correct mitigation until we have released an updated package. The scope of impact is broader than SYSTEM usage of winget.exe, which continues to be unsupported. |
Beta Was this translation helpful? Give feedback.
Your right about Vlibs being the issue.
If you install the latest 2015 VC redist then winget kicks into life from here...
winget show Microsoft.VCRedist.2015+.x64https://download.visualstudio.microsoft.com/download/pr/368cc6bf-087b-49f9-93e6-ab05b70a58e0/814E9DA5EC5E5D6A8FA701999D1FC3BADDF7F3ADC528E202590E9B1CB73E4A11/VC_redist.x64.exe
Working now after deploying the VC++ Redist.