Closed MilesTEG1 closed 1 year ago
I'm experiencing the same issue. It seems like to happen when I use the “Use system Winget” option.
Use system winget is a feature that will only work under special circumstances, this is why it is set under Experimental Features.
Hello @MilesTEG1, can you please try Source Reset option under Winget settings?
Hi @marticliment.
I'm also experiencing this issue. Resetting winget sources gives the following error:
Adding source: winget -> https://cdn.winget.microsoft.com/cache An unexpected error occurred while executing the command: 0x80190193 : Forbidden (403).
Going to https://cdn.winget.microsoft.com/cache in my browser shows
The specified resource does not exist. RequestId:15eb0a07-a01e-0054-017b-f843ed000000 Time:2023-10-06T17:35:03.3471509Z.
Would this have anything to do with the CDN migration taking place? https://github.com/microsoft/winget-cli/issues/3652#issuecomment-1750973872
ETA. Winget CLI (v1.6.2771) seems to be working fine though.
It is likely this has to do with the CDN migration (set of activities). The database inside the source.msix has been modified. We shrunk it by ~50% by refactoring a few things.
We would recommend using the COM API to call WinGet so the dependency on parsing the SQLite database doesn't cause failures. It would also be good to ensure the latest version of WinGet is maintained on the client device.
We have some upcoming work to enable WinGet to update itself without causing a failure when operations are in progress like winget import
The URL for the PreIndexed package is: https://cdn.winget.microsoft.com/cache/source.msix which is why the browser is throwing errors.
Thanks.
Hello @MilesTEG1, can you please try Source Reset option under Winget settings?
I already tried this before sending this issue. But I can do it again. Doing it, I have this, like @babblebauble:
What version of WinGet is installed on the system? It's likely it needs to be upgraded.
What version of WinGet is installed on the system? It's likely it needs to be upgraded.
My version is:
winget --version
v1.6.2771
I just noticed the path in the image. It looks like WinGet UI is bringing its own version of WinGet along with it. That version is probably being impacted with the CDN migration.
Latest version of Winget UI is indeed using an older version of WinGet (1.5.1881).
Latest stable version of WinGet CLI is working fine on my end.
+1 I'm experiencing the same , search "Ditto" it's missing the result , replacing with the latest v1.6.2771 solved the issue.
C:\Program Files\ueli>winget search ditto
Name Id Version Source
------------------------------------------------
Ditto Clipboard 9NBLGGH3ZBJQ Unknown msstore
Ditto Ditto.Ditto 3.24.246.0 winget
Next WingetUI version will have winget 1.6 bundled
We would recommend using the COM API to call WinGet so the dependency on parsing the SQLite database doesn't cause failures. It would also be good to ensure the latest version of WinGet is maintained on the client device.
This is a feature I am working on, but I haven't managed to acces the API from python nor from C#.NET, so I am still trying to figure that out
@marticliment feel free to send me a direct e-mail and I'll see if I can get one of our engineers to take a look. We could probably give some pointers. We can also work on improving some of the public documentation. I will have to check our open-source licensing guidelines regarding making it a reference implementation. We tend to prefer the MIT license which doesn't have any extra requirements on our end, but I'll check.
i have same issue, https://github.com/marticliment/WingetUI/issues/1442
Hello,
WingetUI version 2.1.1 has been released with winget 1.6.2771. While winget 1.6.2771 does fix this issue, winget functionality will not be restored instantaneously. A period of time might pass until winget works again.
I will leave this issue open until you confirm that the issue gets fixed on your clients
It's fixed in my environment.
thanks for the quick fix!
My system winget now works; can the system winget option be added back? My blacklist appears to have been reset which is very annoying.
system winget should still be available
I don't see the option in my settings
It's located in the "Experimental settings and developer options" section of WingetUI Settings.
Ah.
I realized now, that "Microsoft Smart App Control" was most likely at fault here.
No, that's the little accent color box that shows up and asks you if you want to run or not like smartscreen
Not quite. Smart App Control can block entire apps, aswell as program parts from running I had to deactivate this, and wgui works now again.
That is probably a very different problem. This issue was caused by winget maintenance
Please confirm these before moving forward
Describe your issue
On my new computer, I want to search and find some app through WinGetUI like OhMyPosh, but there is nothing found (as you can see on the screenshot). But with winget in a terminal, I can find it (see the screenshot).
I installed severals app but no one was available on the winget source. Some was on winget msstore. But I had to install with chocolatey source.
For OhMyPosh, I found something with
oh my posh
but not on winget source, only msstore or chocolatey.Steps to reproduce the issue
search OhMyPosh with wingetUI: no results search OhMyPosh with CLI winget command: result found.
WingetUI Log
Package Managers Logs
Relevant information
ANother thing that may be related: I cannot install Rustdesk because of an error in the hash. But there is no problem to install it from cli with winget command.
Screenshots and videos