Description of problem: The guest-tools are showing the wrong product version, which makes them unable to maintain. Version-Release number of selected component (if applicable): virtio-win-1.9.19-1.el8.noarch.rpm virtio-win-1.9.24-1.el8_4.noarch.rpm virtio-win-1.9.24-2.el8_5.noarch.rpm How reproducible: 100% Steps to Reproduce: 1. mount /usr/share/virtio-win/virtio-win-1.9.??.el8??.iso to Server 2022 2. Open File Explorer in Windows and browse to CDROM content 3. Open properties dialog virtio-win-guest-tools.exe (context-menu -> properties) and select 'Details' Actual results: virtio-win-1.9.19-1.el8.noarch.rpm -> Product Version: 1.9.18 virtio-win-1.9.24-1.el8_4.noarch.rpm -> Product Version: 1.9.19 virtio-win-1.9.24-2.el8_5.noarch.rpm -> Product Version: 1.9.19 Expected results: virtio-win-1.9.19-1.el8.noarch.rpm -> Product Version: 1.9.19-1 virtio-win-1.9.24-1.el8_4.noarch.rpm -> Product Version: 1.9.24-1 virtio-win-1.9.24-2.el8_5.noarch.rpm -> Product Version: 1.9.24-2 Additional info: It's possible to install virtio-win-guest-tools' from package 'virtio-win-1.9.19-1.el8.noarch.rpm' and upgrade it with the one from 'virtio-win-1.9.24-1.el8_4.noarch.rpm' At this stage, we had Version 1.9.18 installed initially [step_1.jpg] and updated it to version 1.9.19 [step_2.jpg]. After this, it's not possible to upgrade to the version from package 'virtio-win-1.9.24-2.el8_5.noarch.rpm' as this version (1.9.19) is already installed. [step_3_failing.jpg) Please check screenshots with appropriate information on the specific version details each version. - virtio-win-1.9.19-1.el8.png - virtio-win-1.9.24-1.el8_4.png - virtio-win-1.9.24-2.el8_5.png
I tested virtio-win-1.9.26-1.el9_0 pkg. The Virtio-win iso is labelled version: virtio-win-1.9.26 The installer product version: 1.9.26, which is the same with above. Btw, I see "File version: 1.9.26.0" from virtio-win-guest-tools properties, I'm wondering if it is expected and will not impact others. Thanks, Xiaoling
I am moving it to VERIFIED per comment 14 and comment 15, please feel free to reopen if the issue still occurs.