• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: packaging
• Labels:

  None
• Environment:

  Windows Server 2022
  

1. 

   Screenshot 2023-05-30 112118.png

   125 kB

   2023-05-30 10:22

[JENKINS-71361] Windows DisplayVersion registry value does not match the installed version

Chris created issue - 2023-05-30 10:22

Collapse comment: Marcin added a comment - 2023-05-31 13:50

Marcin added a comment - 2023-05-31 13:50

We have the same problem but with the newest version of Jenkins.
Today I have upgraded to the newest available version but registry shows as

DisplayName: 2.277.2

DisplayVersion: 2.255.277.2

 

It makes me a lot problemes becasue CrowdStrike discovered Jenkins as unpatched and sends us a lot of alerts.
Can anyone fix it?

Expand comment: Marcin added a comment - 2023-05-31 13:50

Marcin added a comment - 2023-05-31 13:50 We have the same problem but with the newest version of Jenkins. Today I have upgraded to the newest available version but registry shows as DisplayName: 2.277.2 DisplayVersion: 2.255.277.2   It makes me a lot problemes becasue CrowdStrike discovered Jenkins as unpatched and sends us a lot of alerts. Can anyone fix it?

Basil Crow made changes - 2023-06-06 18:01

Component/s		New: packaging [ 20120 ]
Component/s	Original: core [ 15593 ]

Collapse comment: Mark Waite added a comment - 2023-06-26 11:07

Mark Waite added a comment - 2023-06-26 11:07

When you install Jenkins 2.387.3, there is a registry key called DisplayVersion which is set as 2.255.3873 which is incorrect

Actually, that is not incorrect. That is intentional because the Windows version fields allow 8 bits for the left most field, 8 bits for the second field, and more bits for the later fields.

The Jenkins version 2.387.3 cannot be represented directly in the Windows DisplayVersion value because 387 is greater than the maximum value of 255.

With regard to CrowdStrike, you'll need to advise them that they are making an invalid assumption about the behavior of Jenkins when installed with the MSI package. The MSI package assumes that the initial installation is performed from the MSI, then upgrades are performed without using the MSI.

Expand comment: Mark Waite added a comment - 2023-06-26 11:07

Mark Waite added a comment - 2023-06-26 11:07 When you install Jenkins 2.387.3, there is a registry key called DisplayVersion which is set as 2.255.3873 which is incorrect Actually, that is not incorrect. That is intentional because the Windows version fields allow 8 bits for the left most field, 8 bits for the second field, and more bits for the later fields. The Jenkins version 2.387.3 cannot be represented directly in the Windows DisplayVersion value because 387 is greater than the maximum value of 255. With regard to CrowdStrike, you'll need to advise them that they are making an invalid assumption about the behavior of Jenkins when installed with the MSI package. The MSI package assumes that the initial installation is performed from the MSI, then upgrades are performed without using the MSI.