marticliment
[BUG] Upgrade fom 3.3.0 to 3.3.1 was a desaster
Please confirm these before moving forward
- [x] I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
- [x] I have tested that this issue has not been fixed in the latest (beta or stable) release.
- [x] I have checked the FAQ section for solutions.
- [x] This issue is about a bug (if it is not, please use the correct template).
UniGetUI Version
3.3.1
Windows version, edition, and architecture
Windows 10 x64
Describe your issue
in an office with several Windows 10 PCs I had to reinstall unigetUI manually with the exe-installer. Automatic upgrade was not possible while in fact 3.2.0 and 3.3.0 were incredibly good programmed.
Automatic upgrade was not possible. I think Martí got the crash reports.
Steps to reproduce the issue
No response
UniGetUI Log
plz no
Package Managers Logs
no plz no
Relevant information
No response
Screenshots and videos
No response
Hello @hueldoeu, can you please specify on the errors received? Which AVs are you using? Did it fail on all machines?
yes it fail on all 3 heavily used PCs of an office. But to be honest, sometimes we have the feeling that the upgrade from Windows 8.1 to Windows 10 in 2016 didn't go quite well or that Lenovo PCs aren't so unproblematic at all.
No AV, only Defender, now called MS Defender Antivirus.
Environment details:
Windows version: Microsoft Windows NT 10.0.19045.0
Language: de
APP Version: 3.3.1
APP Build number: 99
Executable: C:\Program Files\WingetUI\UniGetUI.exe
Command-line arguments: "C:\Program Files\WingetUI\UniGetUI.dll"
Integrity report:
Missing files:
- /IntegrityTree.json
Exception type: FileNotFoundException (System.IO.FileNotFoundException)
Crash HResult: 0x80070002 (2147942402, -2147024894)
Crash Message: Could not load file or assembly
'CommunityToolkit.WinUI.Controls.TokenizingTextBox, Version=8.2.0.0,
Culture=neutral, PublicKeyToken=null'. Das System kann die angegebene Datei
nicht finden.
Crash Data:
No extra data was provided
Crash Trace:
at
UniGetUI.UniGetUI_XamlTypeInfo.XamlTypeInfoProvider.InitTypeTables()
at
UniGetUI.UniGetUI_XamlTypeInfo.XamlTypeInfoProvider.LookupTypeIndexByName(String
typeName) in
C:\SomePrograms\WingetUI-Store\src\UniGetUI\obj\x64\Release\net8.0-windows10.0.26100.0\win-x64\XamlTypeInfo.g.cs:line
744
at
UniGetUI.UniGetUI_XamlTypeInfo.XamlTypeInfoProvider.GetXamlTypeByName(String
typeName) in
C:\SomePrograms\WingetUI-Store\src\UniGetUI\obj\x64\Release\net8.0-windows10.0.26100.0\win-x64\XamlTypeInfo.g.cs:line
167
at
ABI.Microsoft.UI.Xaml.Markup.IXamlMetadataProvider.Do_Abi_GetXamlType_1(IntPtr
thisPtr, IntPtr fullName, IntPtr* result)
No inner exceptions found
This is from PC on. 1. On PC no. 2 I have discovered that unigetUI 3.3.1 had been saved in some mysterious folder somewhere in AppData however I have deinstalled it and forcely commanded unigetUI-Installer to use C:\Program Data\WingetUI\
Am Fr., 1. Aug. 2025 um 20:28 Uhr schrieb Martí Climent < @.***>:
marticliment left a comment (marticliment/UniGetUI#3950) https://github.com/marticliment/UniGetUI/issues/3950#issuecomment-3145411992
Hello @hueldoeu https://github.com/hueldoeu, can you please specify on the errors received? Which AVs are you using? Did it fail on all machines?
— Reply to this email directly, view it on GitHub https://github.com/marticliment/UniGetUI/issues/3950#issuecomment-3145411992, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACWALQ2SN42HQDKY7ZQ2DVT3LOWTJAVCNFSM6AAAAACC4HNGDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNBVGQYTCOJZGI . You are receiving this because you were mentioned.Message ID: @.***>
Not gonna lie, it looks like the update did not fully work. The first thing I can see is the missing integrity manifest (added this version), which also suggests that more files may be missing. Hasn't UniGetUI offered to reinstall itself? It should have shown a crash dialog with a button to automatically reinstall itself.
Integrity report:
Missing files:
- /IntegrityTree.json
Also, which is the installation method used to install UniGetUI? Are you using the default installer or portable installations?
I have indeed received the reports, but to be honest, I can't really think of a new bug in 3.3.1, around 65k users have already updated, and as or right now I haven't seen any important spike in crash reports (aside from a common minor spike during update periods, but this has always happened, so I wouldn't say it is an issue with specifically 3.3.1). Nevertheless, I am seeing that a specific DLL is being flagged most of the times, so I will contact CommunityToolkit Devs (the DLL is a dependency from them) to see if they can digitally sign that DLL.
On PC no. 2 I have discovered that unigetUI 3.3.1 had been saved in some mysterious folder somewhere in AppData
Idk if you had installed 3.1.1-beta1-msix in the past, but if you did, this is expcted to happen (it was a bug with that beta version)
Not gonna lie, it looks like the update did not fully work.
You mean the Windows Upgrade from Windows 8.1 to Windows 10?
if you had installed 3.1.1-beta1-msix in the past
No beta had been installed.
Hasn't UniGetUI offered to reinstall itself?
no. let me put a screenshot of what i saw.
It should have shown a crash dialog with a button to automatically reinstall itself.
there was something else like click on OK and nothing happens (or was it reinstall?), click on Cancel and the crash report will be sent.
Am Fr., 1. Aug. 2025 um 20:58 Uhr schrieb Martí Climent < @.***>:
marticliment left a comment (marticliment/UniGetUI#3950) https://github.com/marticliment/UniGetUI/issues/3950#issuecomment-3145486063
On PC no. 2 I have discovered that unigetUI 3.3.1 had been saved in some mysterious folder somewhere in AppData
Idk if you had installed 3.1.1-beta1-msix in the past, but if you did, this is expcted to happen (it was a bug with that beta version)
— Reply to this email directly, view it on GitHub https://github.com/marticliment/UniGetUI/issues/3950#issuecomment-3145486063, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACWALQ7VZDDGD6DAVHBS7533LO2DVAVCNFSM6AAAAACC4HNGDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNBVGQ4DMMBWGM . You are receiving this because you were mentioned.Message ID: @.***>
Then the installer wasn't also copied, it perhaps may have crashed...
The missing files I can see from now are:
- IntegrityTree.json
- The CommunityToolkit mentioned DLL file
- The installer, which should have copied itself to the install location.
It looks like the installer is crashing, or something is going wrong during the update process. I will see what I can do.
Do you still have any of the crashing installations? Perhaps you could send me a zip file so I can further investigate it...
I've had the same issue if I want to upgrade from 3.3.0 to 3.3.1 with the function on startup and after the installer crashed (it can be seen on the hint in the installationprocess while it will try to reverse the changes), the old installation (3.3.0) will be corrupted (missing files) - the installer has no error-output on this issue, so it may crash internally. After a new install via MS Store the version 3.3.1 get be installed and is still working ... I've verified this with different clients with the same result.
Is it possible that the issue has something to do with the installation as App via the store (other path, or different previleges), instead of installing with the normal installer?
No, the installer used on Microsoft Store is exactly the same as the autoupdater and the installer that can be downloaded from GitHub. What I can think is that 3.3.0 and 3.3.1 have a new digital certificate, compared to 3.3.2 and older, so perhaps AVs may be randomly killing the installer because of a less recognized certificate? (certificates build more trust the more they are seen, and the installer has not suffered changes since before than version 3.2.0, which installed fine everywhere)
No, the installer used on Microsoft Store is exactly the same as the autoupdater and the installer that can be downloaded from GitHub. What I can think is that 3.3.0 and 3.3.1 have a new digital certificate, compared to 3.3.2 and older, so perhaps AVs may be randomly killing the installer because of a less recognized certificate? (certificates build more trust the more they are seen, and the installer has not suffered changes since before than version 3.2.0, which installed fine everywhere)
The meaning of my question address a behavior of MS-Store-Installation who are sandboxed, as you can read here: about CVE 2020-1488
P.S.: Sorry for the late response, that's while I'm very busy at the moment.
Not all of them. Recently msstore has allowed installations of unsandboxed win32 apps, UniGetUI being one of the many examples of them.
Not all of them. Recently msstore has allowed installations of unsandboxed win32 apps, UniGetUI being one of the many examples of them.
If the upgrade on previously normal installations works fine (I didn't have tested this), then it may be possible, that this issue is a result of a bug in unsandboxed msstore-installs (some parts leave maybe sandboxed, or so on). As you know, not all fixes and changes from ms are allways 100% bugfree ;-)
I can echo the experience of upgrading from 3.2 and 3.3 to 3.3.1 with both upgrades silently crashing and then not being able to start due to "missing files". Both upgrades were done from within the app; 1 was on Win11 x64 and the other on Win 11 arm64. Both also reinstalled winget and removed entries from User/System ENV that resulted in prolong troubleshooting and reinstallations. I was able to get UniGet successfully reinstalled on both machines, however, on Win11 x64 it is able to detect updates to packages but on Win11 arm64 (using both app and native winget) it does not return any results. If I run winget manually I can see the updates.
Lots of errors like this are visible in the log:
[2025-08-06 2:06:40 PM] No manifest content could be loaded for package Microsoft.Graph.Users.Act. on manager PowerShell7
[2025-08-06 2:06:40 PM] Failed to download the PowerShell7 manifest at Url=https://marticliment.com/unigetui//Packages(Id='Microsoft.Graph.Users.Act.',Version='2.25.0') with status code NotFound
[2025-08-06 2:06:40 PM] No manifest content could be loaded for package Microsoft.Graph.Users.Act. on manager PowerShell7
[2025-08-06 2:06:41 PM] Failed to download the PowerShell7 manifest at Url=https://marticliment.com/unigetui//Packages(Id='Microsoft.Graph.Users.Fun.',Version='2.29.1') with status code NotFound
[2025-08-06 2:06:41 PM] No manifest content could be loaded for package Microsoft.Graph.Users.Fun. on manager PowerShell7
[2025-08-06 2:06:41 PM] Failed to download the PowerShell7 manifest at Url=https://marticliment.com/unigetui//Packages(Id='Microsoft.Graph.Users.Fun.',Version='2.25.0') with status code NotFound
After further digging into Package Managers, I noticed that no sources were available for PS7 and tried to add it without success
Starting adding source operation for source=PSGallerywith Manager=PowerShell7
Running PreOperation (1/1)...
Starting adding source operation for source=PSGallerywith Manager=PowerShell7
Starting operation...
Executing process with StartInfo:
- FileName: "C:\Program Files\PowerShell\7\pwsh.exe"
- Arguments: "-NoProfile -Command Register-PSRepository -Default"
Start Time: "2025-08-06 2:29:54 PM"
[31;1mInstall-PackageProvider: [31;1mUnable to find repository with SourceLocation ''. Use Get-PSRepository to see all available repositories.[0m
[31;1mImport-PackageProvider: [31;1mNo match was found for the specified search criteria and provider name 'NuGet'. Try 'Get-PackageProvider[0m
[31;1m[31;1m-ListAvailable' to see if the provider exists on the system.[0m
[31;1mGet-PackageProvider: [31;1mUnable to find package provider 'NuGet'. It may not be imported yet. Try 'Get-PackageProvider -ListAvailable'.[0m
[31;1mRegister-PSRepository: [31;1mNuGet provider is required to interact with NuGet-based repositories. Please ensure that '2.8.5.201' or newer version of NuGet provider is installed.[0m
End Time: "2025-08-06 2:29:59 PM"
Process return value: "1" (0x1)
Could not add source PSGallery to PowerShell7
PreOperation 1 out of 1 failed, and was tagged as necessary. Aborting...
Could not add source PSGallery to PowerShell7
After battling with it some more and manually re-registering PSGallery via PS7 CLI, I was able to successfully add it to UniGet. After a restart, it showed only a single package:
Package update operation for Package=PackageManagement with Manager=PowerShell7
Installation options: <InstallOptions instance (only non-default values are shown)
OverridesNextLevelOpts: False>
Overriden options: <Scope=;RunAsAdministrator=;WG_SpecifyVersion=;PS_NoScope=False>
Version: 1.4.4 -> 1.4.8.1
Starting operation...
After this update, I relaunched UniGet and was able to see the list of packages that required an update.
It should. 3.3.2 changes:
- All dlls are signed by my signature. It happened that libraries were getting optiimized by msbuild, breaking microsoft's original signature.
- The installer is copied first, and the integrity tree file second, so in the event of a crash, the auto-repaoir option should always be available.
- The installer (inno setup) has been updated to a newer version, perhaps this also helped?
i had 3 problematic PC's (the ones who "update did not fully work not gonna lie") and the install wizard got stuck on them if uniget 3.3.1 was active in the background. i had enough time to end unigetUI and remove it from the RAM so that upgrade process finished successfully.
on the third pc i was too slow to remove unigetUI from ram while the install wizard gave me only about 3 seconds to end unigetUI until unigetUI 3.3.1 asked me to repair unigetUI and after repair was done, unigetUI 3.3.2 appeared.