-
-
Notifications
You must be signed in to change notification settings - Fork 460
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
[BUG] Can't find Winget package #2402
Comments
I think I have the same issue. When updating to UniGetUI today, I did see a screen popup to install something (...) with a lot of errors (red text). So I think something did not install correctly. In my new version I do not see any WinGet packages when I go to 'Installed on this system'. These are the errors I see when I use this command: Install-Module Microsoft.WinGet.Client :
|
I think you have PowerShell misconfigured: |
In the settings, under 'package managers' -> WinGet, I used 'Reset Winget Sources'. There is a green check 'Winget is enabled and ready to go'. Winget Version: |
I'll check that out! Thanks. |
@XinSSS, your issue is caused by WinGet failing to connect to Catalogs, and I can't fix this from UniGetUI |
Is there any way to fix this? |
I don't know, I have never seen it. Perhaps you can open an issue at microsoft/winget-cli, they may be able to help you |
I think I got it fiex. I had some restrcvited plicy serttings I needed to change. https://learn.microsoft.com/nl-nl/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7.4 After that I was able to use Install-Module Microsoft.WinGet.Client and the I reset the Winget Source in the application settings. After a restart of UniGetUI the packages (and updates) showed up. Excellent! |
@marticliment I can only roll back to version 3.0.2, which works fine. |
This happened to me as well. In my case, it was because I had Cobalt installed and it offered conflicting Powershell commands. Fix for me was to uninstall that and restart UniGetUI and let it grab the dependency again. |
Similar problem, module is installed, but unigetui still can't find it. |
you need to disable updates again in 3.0.2 |
I only have PowerShell 7 and Oh My Posh. Not sure if my problem is related to this. I need to research it. |
I had the same problem. Tried everything. In my case it helped to copy the module to the root module folder: the folder: copied to c:\Program Files\WindowsPowerShell\Modules\ |
This is the result of installing Microsoft.WinGet.Client using wingetui. If you use administrator privileges, its installation location will be C:\Program Files\WindowsPowerShell\Modules. Unfortunately for me, I tried all the locations but it didn't work. |
Think I'm having the same issue. Winget just forced an update on me, then keeps telling me that the Powershell module is not installed. It appears to download and install it, but then after WinGet restarts it says the module needs to be installed and repeats the process. |
Update: I got it working, it appears to have been blocked because the module is flagged as unsafe, assuming because it's new? If you open an admin PowerShell terminal, ensure you uninstall the current version: |
This should be fine |
Were you able to uninstall it with the command |
I have uninstalled it in Windows PowerShell until an error message appears, and then tried to reinstall it. |
And neither does it work? |
The installation was also smooth after uninstall, but it just didn't take effect in wingetui, I don't know why. |
I will investigate. Meanwhile, please downgrade to 3.0.2 and disable updates |
FWIW I couldn't downgrade. WinGet 3.0.2 just kept crashing after I upgraded to 3.1. Assuming there was some config file I couldn't find somewhere that is not backwards compatible so just keep that in mind. |
Any crash logs? |
I didn't know where they were stored and I couldn't open WinGet to check tbh haha. I instead upgraded back to 3.1 and got the module working (what I posted above) so that 3.1 appears to be working as expected now (for me at least). |
Hello, To all users facing issues with version 3.1.0, please try the new 3.1.1 beta, which aims to fix this issues. UniGetUI 3.1.1-beta0 release: https://github.com/marticliment/UniGetUI/releases/tag/3.1.1-beta0 Excuse me for the inconveniences. |
@marticliment
Package manager log
|
Please confirm these before moving forward
UniGetUI Version
3.1.0
Windows version, edition and architecture
Windows 11 22H2 22621.3296
Describe your issue
I can't find winget package after update.
I have run command
Install-Module Microsoft.WinGet.Client
in powershell.Steps to reproduce the issue
No response
UniGetUI Log
Package Managers Logs
Relevant information
No response
Screenshots and videos
The text was updated successfully, but these errors were encountered: