-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Winget command missing from server 2019 #144
Comments
PS C:\Users\huang\Desktop> Add-AppPackage .\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.appxbundle
run |
I can't get it to install at all in windows server 2019, running the package gives me the error: PS C:\Downloads> Add-AppxPackage .\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.appxbundle
|
Use this method to install the missing dependencies: |
Thanks for the comment, but I would prefer to not go to a shady website on a windows server instance to get links to download tools... feels like microsoft should support their own operating system. |
I agree, but for what it's worth I believe you are actually still downloading the packages from Microsoft. I think that the site is just providing the direct link which is hosted by Microsoft. You could still visit it on another machine/VM/etc. to get the link if you're interested enough. |
Windows Server 2019 does not support execution aliases. |
How to create winget alias - https://github.com/al-cheb/winget_install_script/blob/main/Install-WinGet.ps1
|
We aren't targeting Windows Server 2019 as a supported SKU for the Windows Package Manager. There are several challenges with dependencies like the Store for updates, App Execution Aliases. You may be able to overcome the hurdles and get the Windows Package Manager installed, but it is not supported in this environment. |
@denelon thanks for the follow up. Are there better chances for Server 2022? Will Windows Server support be removed from the milestone altogether? |
We're still looking at all the dependencies on Windows Server 2022. It looks a bit more straight forward, but still doesn't have the Microsoft Store as a default package. That would potentially inhibit automatic updates to the Windows Package Manager. Unfortunately, it will likely not be a "supported" SKU, but we're considering it as "experimental" if we can make sure all of the appropriate teams and dependencies are all aligned for Windows Server 2022. |
One of the options we're looking at is being able to include the Windows Package Manager in the Microsoft Store "msstore" source for updates. One of the challenges is related to enterprises disabling the Microsoft Store source by policy. That would effectively nullify our ability to get updates. Several chicken and egg problems to resolve here. |
Hi @denelon I fully agree with your challenges and concern. As you can mostly only speak for your product, I would propose to make a check for this policy (it is in registry policies) and if set throw an error message when trying to download. In my professional role I always try to convince enterprises to block the app access to private MS Store via GPO but not blocking the communication as preinstalled apps would not update, neither modern drivers would work correctly as DCH driver have thankfully separated their tools into the store. I am curious how this will work with Windows 11 when the business store is gone. In addition to this it would also compromise the ability to use the business store (as long it will remain) for enterprise deployments. Doubt that enterprises that fully block the store would use Winget. These enterprises from SMB to SMC mostly use
I hope this helps you to consider the options I see regularly in the wild. |
I think winget for windows server core is very needed and critical |
A workaround for this is available. |
Winget command missing from server 2019
Environment
Steps to reproduce
Expected behavior
Winget should be available from the command line.
Actual behavior
Winget is not available from the command line.
The only way to get it to work,
Get-AppxPackage Microsoft.DesktopAppInstaller | %{ Invoke-CommandInDesktopPackage -PackageFamilyName $_.PackageFamilyName -AppId winget -Command C:\Windows\System32\cmd.exe -PreventBreakaway }
The text was updated successfully, but these errors were encountered: