-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Wrong id is selected when dealing with x86/x64 app on the same computer #414
Comments
Do you have same problem with latest WAU version? |
Hi @Romanitho , I'm using the Winget-AutoUpdate-Intune fork through Intune and they not yet updated to the latest version. i will do some standalone test and let you know, thank you. |
thanks ;) |
Hi @Romanitho, I did the test with the latest stable version (1.17.8) and i had the same issue, the logs below: ################################################## CHECK FOR APP UPDATES - 10/16/2023################################################## Thank you |
very weird. I tired to reproduce the problem, but it works as expected on my side 🤔 |
A part of my logs:
|
We also have this C++ issue. It only seems to affect C++ versions. We had to exclude them as it would attempt to install daily while not updating the correct x86 or x64 version. I did not spend a lot of time trying to understand why, just acknowledge c++ detection was broken. While not helpful, I just mention this to help you understand there is an issue here. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
I'm seeing this as well. Is this issue considered solved?
|
@Romanitho, sorry to bother you, but are you making progress with this problem or is it considered closed? |
also discussed in #568 |
Thanks for the update. I'm working around the issue in this particular case for now, by deploying the update as a win32 app in Intune, with the help of Intune App Factory. But I am sort of expecting it to resurface eventually. If so I will invest more time into troubleshooting on my end. |
So there's something strange going on. The x86 package of VCRedist 2015-2022 is a version below the x64 package in the official Winget repo. As I mentioned above I included the redistributables to my "Intune App Factory" library and this was were I first noticed this. PS C:\> winget search Microsoft.VCRedist.2015+
Name Id Version Source
-------------------------------------------------------------------------------------------------------
Microsoft Visual C++ 2015-2022 Redistributable (x86) Microsoft.VCRedist.2015+.x86 14.38.33130.0 winget
Microsoft Visual C++ 2015-2022 Redistributable (x64) Microsoft.VCRedist.2015+.x64 14.38.33135.0 winget But this alone doesn't explain why WAU tries to install a version (14.38.33135.0) of the x86 edition of VCRedist 2022 that doesn't actually exist. Anyway... I manually created Win32App of the newer version of the x86 installer and now this issue is gone in my case. Here's my "Intune recipee" on how to create an "upgrade package" for Microsoft.VCRedist.2015+.x86:
Following these instructions will result in an "upgrade package" and will only install where applicable (AKA where VCRedist.2015+.x86 is already installed). The detection script also handles future higher versions distributed through Winget, so it shouldn't cause any conflicts on your devices. |
Here are some links that seems to be related |
You can use "--architecture" to specify the architecture for the install command if it's not defaulting to the proper architecture.
…________________________________
From: Pelle ***@***.***>
Sent: 21 February 2024 12:28
To: Romanitho/Winget-AutoUpdate ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [Romanitho/Winget-AutoUpdate] [Bug]: Wrong id is selected when dealing with x86/x64 app on the same computer (Issue #414)
Here are some links that seems to be related
microsoft/winget-pkgs#118664<microsoft/winget-pkgs#118664>
microsoft/winget-cli#2129<microsoft/winget-cli#2129>
microsoft/winget-cli#3940<microsoft/winget-cli#3940>
—
Reply to this email directly, view it on GitHub<#414 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASAJCPVFKADZLKJF7YOHCUTYUXK5TAVCNFSM6AAAAAA5YTNPEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWGQ2DOOBWHE>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
We are also seeing this, specifically on the vcredists: `07:52:09 - Updating Microsoft Visual C++ 2013 Redistributable (x8 from 12.0.40660.0 to 12.0.40664.0... ███▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 1024 KB / 9.39 MB We do have both architectures installed on the server, if that makes a difference. Happy to do additional troubleshooting/investigation to get to the bottom of this. |
what do you have if you run: |
I get this: So it seems winget itself is not matching correctly. |
So not directly related to WAU :/ |
The problem
Hi,
We're currently have an issue to update package that exist on the same computer as x86 and x64 version.
We have "Microsoft Visual C++ 2015-2022 Redistributable" installed and while the version x64 is detected as needing to be updated, the update command line select the version x86 to do the update which ultimately led us to an infinite loop.
Have you seen that behavior before? do you know how to solve that issue?
Thank you for your help,
Best,
What version of WAU has the issue?
1.17.6-2
What version of Windows are you using (ex. Windows 11 22H2)?
Windows 10H22
What version of winget are you using?
v1.6.2771
Log information
Additional information
No response
The text was updated successfully, but these errors were encountered: