Cory Knox

> Just need someone to approve this :-) I think Paul intended to approve it and instead just enabled the auto merge. I've approved it. Thanks for the contribution @flcdrg...

That's why we ask for the logs. From the output and what you've said, it seems that chocolatey is seeing updates to both of those packages, then when it attempts...

> Choco is seeing the possible upgrade but is supposed to not upgrade since axivion requires openjdk 17 instead of 22. Yes. That's the process Chocolatey takes when it is...

I think you've got something going on with your Chocolatey install, and hence the reason that we ask for the full logs. On a fresh system with the package I...

> I created a fresh choco package as well and the bug disappeared. The problem must be in the choco package. However I am not allowed to share the package...

Thank you for reporting this. I didn't get the exact same results as you when run in a Vagrant box, but I got a close approximation (the temp variable changed...

I think I've tracked down what the issue is, and have opened PR #3787 for it. Essentially, the username when you're running as SYSTEM is actually `COMPUTERNAME$`.

@gep13 I think you're right about the relation to #3503. When I was looking through to track where I could fix that one, I stumbled upon this line: https://github.com/chocolatey/choco/blob/8fc766e4e71d0be43534f0ef6720417b2c65e6de/src/chocolatey/infrastructure/cryptography/DefaultEncryptionUtility.cs#L64 It...

I can confirm that the change I made in #3540 in my tests results in this error not terminating except in the scenario where termination is desired (upgrade with remembered...

Thanks for getting this fixed up @pauby