Upgrade of VBR to 12.1 with Hardened Repo

[Matthias.Mehrtens]

Hi, there was a recent patch with version "12.1.1.56" available a few weeks ago (this one had no date-suffix added to its name). Comparing the hashes shows that it's different from the newer one named "12.1.1.56_20240127", but VBR console and log files still show "12.1.1.56" as version info (there's no additional date-suffix or anything similar, or at least I haven't found it yet). How can I tell whether the new "12.1.1.56_20240127" patch has already been applied?

[HannesK]

Hello,
what would be the use-case of knowing it? If a customer had the old patch exe, he would have fixed the issue already manually. There should be no reason to install the patch twice.

Best regards,
Hannes

[Gostev]

Please be aware that this is not a product patch to start with: it's an ISO repack with the same binaries and a fix in the hardened repository upgrade process. If we were to produce an actual product patch (i.e. modify core binaries), it would require rebuilding the entire VBR with a new build number e.g. 12.1.1.57, meaning it would have been easy for you to see that you don't have the latest build installed.