Right clicking a software panel during the "finding out whether there is a new version" phase = exception

[ndsvw]

Checklist

• I confirm there are no unresolved issues reported on the Chocolatey Status page.
• I have verified this is the correct repository for opening this issue.
• I have verified no other issues exist related to my problem.
• I have verified this is not an issue for a specific package.
• I have verified this issue is not security related.
• I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

I right clicked the panel of some installed software when the GUI was still trying to find out whether there is a new version of any of the installed software.

What is Expected?

No unhandled exception

How Did You Get This To Happen?

1. Open ChocolateyGUI and make sure, you are on the "Installed apps" site and everything is loaded
2. In a separate window run choco cache remove to clear the HTTP cache to ensure checking for outdated takes longer
3. Click the button check for new versions
4. Go over a few installed apps and right click them quickly

Reproduction recordings:

• https://github.com/user-attachments/assets/5de96335-a050-4d7c-94e7-1cd3626d20d1
• https://github.com/user-attachments/assets/481c829b-8a85-4085-a2e7-5f6be1ef5fbf

System Details

• Operating System: Windows 11 24H2 Sandbox
• Windows PowerShell version: 5.1
• Chocolatey CLI Version: 2.6.0
• Chocolatey Licensed Extension version: N/A
• Chocolatey License type: Free
• Terminal/Emulator: N/A

Installed Packages

Id|Version
chocolatey|2.6.0
chocolatey-compatibility.extension|1.0.0
chocolatey-core.extension|1.4.0
chocolatey-dotnetfx.extension|1.0.1
chocolateygui|2.1.1
dotnetfx|4.8.0.20220524
gh|2.86.0
git|2.53.0
git.install|2.53.0
glab|1.82.0
glab.portable|1.82.0
kanata|1.10.0
KB2919355|1.0.20160915
KB2919442|1.0.20160915
notepadplusplus.install|8.9.1
vscode|1.109.0
vscode.install|1.109.0

Output Log

See https://gist.github.com/corbob/9b9a344287caef200174619476c43bc4

Additional Context

The above linked output log includes the full Windows Event for the exception.

┆Issue is synchronized with this Clickup task by Unito

[github-actions]

To vote for this issue, please add a 👍 emoji to the issue description. Votes in comments are not recorded.

[pauby]

@gep13 could you triage this issue?

[gep13]

@pauby this is a strange one.

I have been trying to get this to happen reliably, but I can't figure it out. I have tried 5-10 different times, and I was able to get the same error, but only once. I followed the exact same steps as when I was able to get it to happen, but I can't get it to happen again.

The exception itself doesn't make sense to be either. It would suggest some sort of incompatiblity between the installed version of Chocolatey GUI, and Chocolatey CLI, but this can't be the case, since I have tested running the pin/unpin command through Chocolatey GUI, and this is working as expected.

@ndsvw are you in a position to provide some more detailed steps about exactly how you are able to get this to happen? Perhaps record a video of this happening? That might help us get to a point where we are able to reliably reproduce the issue. Thanks!

[ndsvw]

Hello,

I found a way to very reliably reproduce it on my machine (75% of the time).

1. Open Chocolatey UI and make sure, you are on the "Installed apps" site and everything is loaded
2. Click the button check for new versions
3. Go over a few installed apps and right click them quickly

2 videos that show it happening:
https://github.com/user-attachments/assets/5de96335-a050-4d7c-94e7-1cd3626d20d1
https://github.com/user-attachments/assets/481c829b-8a85-4085-a2e7-5f6be1ef5fbf

[corbob]

Thank you for these reproduction steps @ndsvw. I can confirm that I've been able to reproduce this error with the steps you provided. For the sake of having complete details, I'll update this issue with the logs from my test system and some additional details.

[corbob]

I'll add this here as a detail for working on this: I found I had better success when I cleared the HTTP cache to ensure there's some time to the outdated process. This still wasn't perfect and it sometimes took a few attempts. I believe Fiddler has the ability to artificially restrict your network connectivity, so that may be a good debugging tool. Utilizing Bandwidth control on the network adapter in Hyper-V may also help.