-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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_Source: Deployment failed #0: 0x8000FFFF #276
Comments
I had this problem also, thank you for the workaround steps. |
I've the same problem when I applied same steps above it's fixed. |
the work around did work. unfortunately after installing a few packages i'm starting to get this error on all packages, even running |
We are having the same issue. For us, it appears to be company-wide. We don't use AD or GP. We do use Workspace One. We think it might have to do with that. |
I've had a similar issue but your workaround worked for me as well.
I'm using CoreDNS as a DNS Server, which forwards everything to |
Just here to say me too ... I've spent over an hour and got no further than the original poster. The latest 0.2.2941 AppInstallerCLI.exe is still failing with Oh and confirming workaround of:
UPDATE: CLI search then appears to work but it still fails to install anything failing due to
|
I've been fighting this error for weeks now. It might work for a bit, then would fail to update sources, so I would try everything with no luck until the next time I attempted to use it and would succeed for unknown reasons until it stopped again. Always resulting in some error similar to
Today this command worked, though I'm not sure which force was the good one.
|
Wow, that just seemed to fix my issue....will know after more testing. Thanks @cryolithic , |
Thanks @cryolithic your steps helped... I was getting this:
These are the all steps for other windows noobs like me (I'm arriving from OSX):
cd $HOME\AppData\Local\Microsoft\WindowsApps
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 # Fix "Invoke-WebRequest : The request was aborted: Could not create SSL/TLS secure channel."
Invoke-WebRequest -Uri https://winget.azureedge.net/cache/source.m
six -OutFile source.msix
Add-AppxPackage -Path .\source.msix -Confirm -ForceTargetApplicationShutdown # NOTE: "-ForceUpdateFromAnyVersion" was not a valid arg
winget source reset --force
winget search vlc # works When I try to install from a non-admin shell, I get an "error 2". Is Admin always required for install or is this a side effect of creating source.msix as admin? |
This Issue should be resolved with changes that were made a few releases ago related to the Mark of the Web. |
Hi @denelon are you sure about this? FYI I just tried downloading/running the latest v-0.2.10971-preview and it still fails for me with same
Also tried 'unblocking' it to reset it's InternetZone, same result. Whilst this could be something special about my machine, I suspect as others have reported it's a common problem. |
@RPitt thank you for responding. Yes, please submit feedback via [Windows]+[f] and select "Apps / Windows Package Manager". That will send us logs to diagnose. |
This looks like an issue with installing the "App Installer". We're going to look through logs to see if we have the information necessary to troubleshoot. This is being marked as "Area-External" since it's not related to the Windows Package Manger itself. It's really related to how the App Installer is handled in Windows deployment. |
I believe that the original issue was resolved with #627. If there are issues with installing the DesktopAppInstaller package itself I think that a new issue should be opened with details from a more current release, but note that those would likely be external to winget-cli as that is Windows MSIX deployment related. Filing feedback via Feedback Hub is the best way to get Windows issues on the right teams. |
Work laptop, latest Windows 10 release, running as Administrator but there are group policy restrictions in place.
Failed to install winget using DesktopAppInstaller. CLI tools worked but took additional and unexpected steps.
Double clicking the AppXBundle file gave a deployment error 0x8000FFFF, but using the Add-AppxPackage worked fine. However, running
winget source update
gave an additional error (log below). I resolved this by downloading the sources from https://winget.azureedge.net/cache/source.msix and installing through Add-AppxPackage.Winget now appears to be working correctly.
Logfile output is:
Environment is:
The text was updated successfully, but these errors were encountered: