<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: E89.26 Client Requires .NET Core Windows Runtime in Endpoint</title>
    <link>https://community.checkpoint.com/t5/Endpoint/E89-26-Client-Requires-NET-Core-Windows-Runtime/m-p/282864#M11667</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I ran into something similar, so here is what I found. Your log already gives the main clue: &lt;STRONG&gt;Error 27592&lt;/STRONG&gt; says the installer needs &lt;STRONG&gt;.NET Core Windows Runtime&lt;/STRONG&gt; and &lt;STRONG&gt;ASP.NET Core Runtime&lt;/STRONG&gt; for the selected blades. This is not the classic .NET Framework requirement we have had for years, it is the newer .NET runtime.&lt;/P&gt;
&lt;P&gt;The reason it works differently when you run it by hand is the installation wizard. When you launch the package manually, the wizard detects the missing prerequisite and offers to install it (that is the "Install Prerequisites" screen you saw). A silent MSI install through SCCM does not go through the wizard, so it stops with the error instead.&lt;/P&gt;
&lt;P&gt;Check Point describes the same behavior for .NET Framework in &lt;A href="https://support.checkpoint.com/results/sk/sk182480" target="_blank" rel="noopener"&gt;sk182480&lt;/A&gt;: with the wizard, the .NET installation and reboot are handled for you; without the wizard, the install exits with an error and has to be run again. The same sk also mentions that if the exported package does not include the .NET installer, the installation fails.&lt;/P&gt;
&lt;P&gt;What I would try with SCCM:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Package the &lt;STRONG&gt;.NET Desktop Runtime&lt;/STRONG&gt; and the &lt;STRONG&gt;ASP.NET Core Runtime&lt;/STRONG&gt; as separate SCCM applications and add them as &lt;STRONG&gt;dependencies&lt;/STRONG&gt; of the Harmony Endpoint application, so they are installed before the MSI runs.&lt;/LI&gt;
&lt;LI&gt;Test on a pilot machine first to confirm which runtime version E89.26 expects. I could not find the exact version documented yet, so it is worth confirming with TAC or checking the install log after installing the runtime.&lt;/LI&gt;
&lt;LI&gt;When you export the package, leave &lt;STRONG&gt;"Minimize package size"&lt;/STRONG&gt; unchecked so the dependencies are bundled as much as possible.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="evidence 1.jpg" style="width: 542px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/35401iFB855966626B26F4/image-size/large?v=v2&amp;amp;px=999" role="button" title="evidence 1.jpg" alt="evidence 1.jpg" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;If anyone from Check Point can confirm the exact runtime version required from E89.26 onwards, that would help a lot of people planning the upgrade from E88.x.&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;</description>
    <pubDate>Fri, 25 Sep 2026 18:30:22 GMT</pubDate>
    <dc:creator>jorgeluiznim</dc:creator>
    <dc:date>2026-09-25T18:30:22Z</dc:date>
    <item>
      <title>E89.26 Client Requires .NET Core Windows Runtime</title>
      <link>https://community.checkpoint.com/t5/Endpoint/E89-26-Client-Requires-NET-Core-Windows-Runtime/m-p/282862#M11666</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Looking to upgrade our clients from E88.60 to E89.26 and we see the following errors in the install logs.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;MSI (s) (F4!F0) [16:44:06:758]: Product: Check Point Endpoint Security -- Error 27592.The following products need to be installed in order to continue installation of selected blades: .NET Core Windows Runtime, ASP.NET Core Runtime. Installation started.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Error 27592.The following products need to be installed in order to continue installation of selected blades: .NET Core Windows Runtime, ASP.NET Core Runtime. Installation started.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We're installing it silently via SCCM and would have thought that .Net Core would have also been installed with the Checkpoint msi if it is required?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;When we run it manually we get prompted that Microsoft .Net Core is required.&lt;/P&gt;&lt;P&gt;Is this a recent requirement in the newer clients?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2026 16:27:11 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/E89-26-Client-Requires-NET-Core-Windows-Runtime/m-p/282862#M11666</guid>
      <dc:creator>J_B</dc:creator>
      <dc:date>2026-09-25T16:27:11Z</dc:date>
    </item>
    <item>
      <title>Re: E89.26 Client Requires .NET Core Windows Runtime</title>
      <link>https://community.checkpoint.com/t5/Endpoint/E89-26-Client-Requires-NET-Core-Windows-Runtime/m-p/282864#M11667</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I ran into something similar, so here is what I found. Your log already gives the main clue: &lt;STRONG&gt;Error 27592&lt;/STRONG&gt; says the installer needs &lt;STRONG&gt;.NET Core Windows Runtime&lt;/STRONG&gt; and &lt;STRONG&gt;ASP.NET Core Runtime&lt;/STRONG&gt; for the selected blades. This is not the classic .NET Framework requirement we have had for years, it is the newer .NET runtime.&lt;/P&gt;
&lt;P&gt;The reason it works differently when you run it by hand is the installation wizard. When you launch the package manually, the wizard detects the missing prerequisite and offers to install it (that is the "Install Prerequisites" screen you saw). A silent MSI install through SCCM does not go through the wizard, so it stops with the error instead.&lt;/P&gt;
&lt;P&gt;Check Point describes the same behavior for .NET Framework in &lt;A href="https://support.checkpoint.com/results/sk/sk182480" target="_blank" rel="noopener"&gt;sk182480&lt;/A&gt;: with the wizard, the .NET installation and reboot are handled for you; without the wizard, the install exits with an error and has to be run again. The same sk also mentions that if the exported package does not include the .NET installer, the installation fails.&lt;/P&gt;
&lt;P&gt;What I would try with SCCM:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Package the &lt;STRONG&gt;.NET Desktop Runtime&lt;/STRONG&gt; and the &lt;STRONG&gt;ASP.NET Core Runtime&lt;/STRONG&gt; as separate SCCM applications and add them as &lt;STRONG&gt;dependencies&lt;/STRONG&gt; of the Harmony Endpoint application, so they are installed before the MSI runs.&lt;/LI&gt;
&lt;LI&gt;Test on a pilot machine first to confirm which runtime version E89.26 expects. I could not find the exact version documented yet, so it is worth confirming with TAC or checking the install log after installing the runtime.&lt;/LI&gt;
&lt;LI&gt;When you export the package, leave &lt;STRONG&gt;"Minimize package size"&lt;/STRONG&gt; unchecked so the dependencies are bundled as much as possible.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="evidence 1.jpg" style="width: 542px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/35401iFB855966626B26F4/image-size/large?v=v2&amp;amp;px=999" role="button" title="evidence 1.jpg" alt="evidence 1.jpg" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;If anyone from Check Point can confirm the exact runtime version required from E89.26 onwards, that would help a lot of people planning the upgrade from E88.x.&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2026 18:30:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/E89-26-Client-Requires-NET-Core-Windows-Runtime/m-p/282864#M11667</guid>
      <dc:creator>jorgeluiznim</dc:creator>
      <dc:date>2026-09-25T18:30:22Z</dc:date>
    </item>
  </channel>
</rss>

