Question First, UniGetUI breaks. I check Winget instead. Then, it breaks as well

Jun 14, 2020
126
19
4,595
I recently started using UniGetUI as a free and open source means of keeping my software up to date through a GUI. However, out of the blue, it stopped working for me. Packages wouldn't even show up in the GUI list anymore.

I decided to check the Winget command directly so I opened PowerShell to see if that could help me nail down the issue. However, when I did this, I can't use Winget to fetch updates anymore either. Now, when I try "winget upgrade -r", it returns with an error saying,
Failed when searching source: winget
An unexpected error occurred while executing the command:
0x8a15000f : Data required by the source is missing

I tried switching over to Command Prompt just in case it was a difference related to PowerShell but CMD gave me the same error code. I tried running it in both in administrator mode, no luck. I ran "winget list" and it gave me the full readout. I tried a few other switches with it and it seems to be working for most things, but it continues to give me that error code. It's not because nothing needs an update; I ran PatchMyPC to double check and it listed a few programs as needing updated. I've also run SFC to see if anything is corrupted, but nothing seems to come up. I also checked Event Viewer to see if I could find anything that might indicate what's going on but no, aside from that error code, nothing gives me a hint as to what's going on here.

I would say it's just because I run a standard account 99% of the time for security but that doesn't make any sense because both UniGetUI and Winget both worked flawlessly until just about a week ago. I even gave it a bit of time hoping maybe it was just a server issue but it's still doing this and it's starting to really irk me.

I also did try to do a search for this issue online but they recommended doing things such as resetting the sources, checking to ensure certain domains weren't blocked, things along that line but none of them fixed the issue for me. I'm honestly not sure what else I can do at this point but I figured I'd run it by the forum and see if any of you have any suggestions?

I'm running Windows 10 Pro (x64) 22H2 (build 19045.4780).