[BUG/ISSUE] Badly parsed update

[AbitFishy]

Before submitting the issue

• [X ] I have checked that the bug is not a duplicate or, if it is, it needs to be reopened
• [ X] I have checked that I am running the latest version of WingetUI
• [X ] I have tried resetting and reinstalling WingetUI and the issue persisted or happened again
• [ X] I have checked the FAQ section for solutions
• [ X] I have read the contributing guidelines and I agree with the Code of Conduct

Describe the bug

There is an update available via winget source called "The following packages have an upgrade available, but" that looks like an obvious parsing error of winget's output.

now when I try to update it, it obviously fails with the no package found error:

To Reproduce

Steps to reproduce the behaviour:

1. Open or freshly install or reset WingetUI
2. Look at updates

Expected behaviour

A package that actually exists to show up under updates

Screenshots

see above

The Log

winget log.txt

Additional context

I'm using the built-in winget
The "loading" in the info screen never seems to finish

[marticliment]

Does this always happen, or reopening the info windows helps?

Because winget has issues with the info command sometimes

[Heart1010]

I hang in here... updated to v1.6.3 and also have a 'strange upgradable package' in the list now:

update: Microsoft Teams line (a few lines above marked entry) looks also not correct, do it?

[marticliment]

Yes, it is also not good. I will try to fix that.

[marticliment]

Meanwhile you can disable the updater and sticik with 1.6.2

[Heart1010]

Meanwhile you can disable the updater and sticik with 1.6.2

Tried downgrading to v1.6.2 but what should I say.... also with v1.6.2 I have the same 'broken' lines as shown above in the screenshot in the update list tab 🤔

[marticliment]

I mean, it actually makes sense, since v1.6.3 does not introduce changes to the winget engine, so it might just have been a coincidence

[Nereithr]

I mean, it actually makes sense, since v1.6.3 does not introduce changes to the winget engine, so it might just have been a coincidence

Can confirm the issue began for me in 1.6.2, here is a link to a comment in issue #369 with a bit more info on how I encountered the bug.

[Mikey1993]

Yup, also got bad parsing for this one here with the latest 1.6.3 version:

[AbitFishy]

Does this always happen, or reopening the info windows helps?

Sorry for the delay, yes, the loading the dialog box always happens with this "package" even after following all the troubleshooting steps the checkboxes had me do

[ppvnf]

was this fixed by 1885604?

[marticliment]

Yep