UniGetUI 3.1.0 beta 0

[marticliment]

IMPORTANT:
This is the first beta release to implement the UniGetUI rebranding.
Instaling this release will automatically migrate settings and other data to new folders (WingetUI -> UniGetUI), so rolling back to older versions of WingetUI may cause settings to be reset.

Note: When it comes to features, this release should be quite similar to the stable 3.1.0 release

Changes

• Packages will be loaded and stored by a Package Loader, instead of being loaded by the interface.
• Package lists have been rebuilt to use ItemsView, causing UniGetUI to use less ram (~290mb max -> ~210mb max)
• The Widgets API has been optimized. Packages load up to way faster on the widgets.
• The Package Manager logs have been rebuilt from the grounds up.
  • Package Manager logs for each manager can be isolated
  • Normal and Verbose views available
• Improvements to keyboard navigation
• Chocolatey can be set to not be installed by the UniGetUI Installer
• Lots of internal code changes and optimizations.
• Other bugfixes

SHA256: 79D8266736B46D8B8959DD775702B275AE4B1936EE6485D01C31A1F62418B8DB

---

This discussion was created from the release UniGetUI 3.1.0 beta 0.

[MarcLaf]

Just tried this release and none of the Winget updates are showing, only PowerShell Gallery. Tried disabling and re-enabling Winget but no good.

[marticliment]

if you run powershell.exe which version does start?
Running powershell.exe -Version 5 does launch Windows PowerShell (PowerShell v5)?

[MarcLaf]

Ohh I use PS7 by default for everything and only Windows PowerShell when absolutely necessary. I'll try it again.

[MarcLaf]

Still not working for me - Might just have to remove and roll back to WinGetUI

[MarcLaf]

Rolled back to WinGetUI and Winget packages work but Powershell modules update is now broken :-(
Ah well, I'll get it straightened out eventually!

[leowankerddd]

@marticliment ,

I also was missing every winget program after upgrading/installing the beta.

I ran the command you recommended and then re-ran the beta and everything was there. Thanks.
Install-Module Microsoft.WinGet.Client

Windows told me that I was installing from an untrusted Repository.

[RobertoPuraVida]

Testing the Beta0. Still, no “installed Applications” are visible. No SOURCES are shown. Like with alpha0 and alpha1. Back to 3.0.2 and all is okay again. Tested as well the Beta0 as portable installation, same result: No installed applications found.

[marticliment]

And running powershell.exe -ExecutionPolicy Bypass -File ".\EnsureWinGet.ps1"?

[marticliment]

And if you paste the contents of the EnsureWinGet.ps1 file directly into the powershell, what happens?

[RobertoPuraVida]

C:\Users\Robert>powershell -ExecutionPolicy Bypass -File ".\EnsureWinGet.ps1"
Microsoft.WinGet.Client is not installed or is not on the latest version
Attempting to uninstall an older version of Microsoft.WinGet.Client...
PackageManagement\Uninstall-Package : Es wurde keine Übereinstimmung für die angegebenen Suchkriterien und Modulnamen
'Microsoft.WinGet.Client' gefunden.
In C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:2194 Zeichen:21

• ... $null = PackageManagement\Uninstall-Package @PSBoundParameters

•                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : ObjectNotFound: (Microsoft.Power...ninstallPackage:UninstallPackage) [Uninstall-Package]
    , Exception
  • FullyQualifiedErrorId : NoMatchFound,Microsoft.PowerShell.PackageManagement.Cmdlets.UninstallPackage

Installing Microsoft.WinGet.Client...

Name Version Source Summary

---

nuget 2.8.5.208 https://onege... NuGet provider for the OneGet meta-package manager
Microsoft.WinGet.Client was installed successfully
Checking for updates for Microsoft.WinGet.Client module...
Microsoft.WinGet.Client is up-to-date
Checking for updates for Microsoft.WinGet.Client module...
Microsoft.WinGet.Client is up-to-date

[RobertoPuraVida]

I first uninstalled the Modul winget.client and let the script run. UniGetUI is still delivering the installed packages.

[marticliment]

Whey you say you use PowerShell 7 by default, powershell.exe does start powershell 7 or Windows PoserShell 5?

[BroMarduk]

*Edited to reflect proper PowerShell versions

Having similar issues. I have 4 versions of PowerShell 5 x64, 5 x86, 7 x64 and 7 x86. Installed Microsoft.WinGet.Client in each.
Uninstalled WinGetUI, installed UniGetUI...

If I run the EnsureWInGet PS script, I get

Microsoft.WinGet.Client is up-to-date

a couple of times in each PowerShell window.

Any suggestions?

[marticliment]

I need more info about the Multiple PowerShell Versions:

• the command powershell.exe which shell launches?
• On which PWSH version are you running the EnsureWinGetClient script?
• The PowerShell gallery manager on UniGetUI, which version reports?

[BroMarduk]

Powershell 7 x64 runs by default if I type from Start Menu, If I type powershell.exe in a Command Prompt it is 5.1 x64

I ran EnsureWinGetClient script on all 4 (PS7 x64, PS7 x86, PS5 x64, PS5 x86). I got the up-to-date message.

This is what I get for PowerShell Versions:

[skanda890]

None of the packages from Winget and Local are being shown

[marticliment]

Can you please attach WinGet Logs?

[skanda890]

Can you please attach WinGet Logs?

See #2344 and #2007

[marticliment]

Try to run the command Install-Module Microsoft.WinGet.Client on a powershell window

[BroMarduk]

Latest Beta 3.1.0 Beta 1 fixed my issues.