Endpoint recommended version is about a year old

[Alex-]

sk117536 and the Infinity portal still show as recommended version a release which is from April 2025 for MacOS and May 2025 for Windows.

Meanwhile, our customers are going forward with their OS deployments, encounter various issues mainly linked to performance and are confused by the message this is giving for the product. That least release for Windows is from December 2025, 5 months ago.

Some customers go on and upgrade to the latest version out of necessity without knowing if there's going any impact on stability and features since they're not marked as recommended.

Can anyone clarify the EDR roadmap.

[Chris_Atkinson]

I'm told an announcement on the next recommended release is near / imminent.

Please continue to watch https://support.checkpoint.com/results/sk/sk117536 for updates.

[Lesley]

I cannot help with the question with the roadmap. But if you tell you have performance related issue and I can see performance related issues solved in the latest release you have a good argument to use this version. 

I would in general follow the rule if there are issue solved in a higher release that is not recommended to pick this version anyway. Those versions are made for a reason. People think recommended is more safe but sometimes a later version is just the better option. If it is for a gateway or an endpoint client

With OS updates you are always depended on the 3d party. If Windows comes with a new version tomorrow it takes Check Point time to build a new version if this is needed. It can happen they change so much that the endpoint software does not work correctly and CP needs to get in contact with the vendor to fix this. That is also the reason for this disclaimer below from CP:

Disclaimer: In cases where changes introduced by the OS vendor (Microsoft or Apple) prevent the existing solution from providing parts of its functionality Check Point will work with the OS vendor on restoring the capabilities, while providing full transparency to the field. No time limitations will apply in this case, as Check Point cannot control the third party.

[Alex-]

That's not how this works in the fast-moving market of EDR. Imagine if GAIA had a recommended JHF that's 1 year old and you get a string of releases without clear commitment other than "use them if you need them". Recommended statuses bring with them a sense of clarity.

Teams who manage EDR can have different metrics than teams who manage infrastructure. They receive the end-user complaints, can easily switch as this is pure software and so on. Perception is key.

If following this up is an issue, drop the "Recommended" approach for EDR and move to rolling releases.

[Lesley]

I mean the following. You have an issue and you read release notes of the not the recommended version. Then it makes sense if you read items that might solve the issue right? Or do i understand it incorrectly? TAC will work the same, if they see something that is solved in higher not recommended version they will advise that. See it as a label that works for MOST customers, not all some benefit from a not recommended version. 

If you have issues that are not solved on any version, and the version is very old that now you can download that is a different story. But there is always a delay between Microsoft changes and how fast they are reflected in endpoint version if needed. It will always take 2 parties to solve these kind of issues. This is not something you can do beforehand