<?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: XDR agent reboot recover everytime in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xdr-agent-reboot-recover-everytime/m-p/1263805#M9548</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/307134"&gt;@tlmarques&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;Based on the reboot message &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;“Reinício agendado em 1 minuto devido ao recover do cortex”&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, the reboot appears to have been initiated by the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Cortex XDR Health Helper (&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;CODE dir="ltr"&gt;&lt;STRONG&gt;&lt;SPAN&gt;xdrhealth&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/CODE&gt;&lt;STRONG&gt;&lt;SPAN&gt;) / recovery mechanism&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; to remediate an agent issue.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;-This can occur when an endpoint reconnects after being offline for an extended period and starts synchronizing agent/content updates. If an installation or upgrade is interrupted or encounters a driver/service issue, the recovery mechanism may initiate a reboot to complete the remediation. If the underlying issue remains, this can result in repeated reboots.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;&lt;STRONG&gt;&lt;SPAN&gt;Recommended checks:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL data-spread="false"&gt;
&lt;LI&gt;&lt;SPAN&gt;Review &lt;/SPAN&gt;&lt;CODE dir="ltr"&gt;&lt;SPAN&gt;xdrhealth.log&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; for Health Helper and reboot activity.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Check &lt;/SPAN&gt;&lt;CODE dir="ltr"&gt;&lt;SPAN&gt;MsiSuspendedInstallation.log&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; for interrupted MSI installation/rollback activity.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Review &lt;/SPAN&gt;&lt;CODE dir="ltr"&gt;&lt;SPAN&gt;trapsd.log&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; for agent, driver, or recovery-related errors.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;If the endpoint remains in a reboot loop, boot into &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Safe Mode&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, cleanly remove the Cortex XDR agent, and reinstall the required supported agent version.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;For the wider environment:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;For a large deployment, we recommend using &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;staged/delayed agent and content upgrades&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; and identifying long-term offline endpoints before allowing them to reconnect and synchronize. This can help avoid a large number of endpoints upgrading simultaneously.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you feel this has answered your query, please let us know by clicking&amp;nbsp;&lt;STRONG&gt;like&amp;nbsp;&lt;/STRONG&gt;and on&lt;STRONG&gt;&amp;nbsp;"mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;</description>
    <pubDate>Mon, 07 Sep 2026 14:42:46 GMT</pubDate>
    <dc:creator>susekar</dc:creator>
    <dc:date>2026-09-07T14:42:46Z</dc:date>
    <item>
      <title>XDR agent reboot recover everytime</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xdr-agent-reboot-recover-everytime/m-p/1262930#M9525</link>
      <description>&lt;P class="isSelectedEnd"&gt;Hi guys,&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;Recently, we identified several computers running Cortex XDR version 9.2.0.120 with Content Version 2340-38788.&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;After the machines start, connect to the tenant, and receive the latest content/information, they start rebooting approximately every minute.&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;The Windows message displayed is:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P class="isSelectedEnd"&gt;“You’re about to be signed out”&lt;BR /&gt;“Reinício agendado em 1 minuto devido ao recover do cortex”&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P class="isSelectedEnd"&gt;The machine then restarts after one minute. The message indicates that the restart is being scheduled due to Cortex recovery.&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;So far, the only solution we have found is to boot the machine into Safe Mode, stop the Cortex XDR services, and then remove/uninstall Cortex XDR.&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;After that, we reboot the machine, reinstall Cortex XDR, and the problem is resolved.&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;One additional point that may be relevant: most of our PCs are currently running Cortex XDR version 9.3.0.231 with Content Version 2390-40333.&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;The fact that these affected machines are running 9.2.0.120 / Content 2340-38788 may indicate that they were offline for some time and therefore did not receive the latest Cortex XDR version/content.&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;However, even if the machines were offline for an extended period, we don't understand why they would enter Recovery Mode after reconnecting and receiving the latest information. Being offline should not, by itself, explain why Cortex would trigger this behavior.&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;This is very important for us to understand because we have more than 8,000 devices, and I’m concerned that this issue could potentially start affecting a much larger number of machines.&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;Has anyone experienced this behavior before, particularly with Cortex XDR 9.2.0.120 / Content Version 2340-38788?&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;Do you know what could trigger the Cortex Recovery mechanism in this scenario, and whether there are any known issues related to upgrading from this older version/content?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;Any information about the root cause, known issues, or recommended troubleshooting steps would be greatly appreciated.&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2026 14:04:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xdr-agent-reboot-recover-everytime/m-p/1262930#M9525</guid>
      <dc:creator>tlmarques</dc:creator>
      <dc:date>2026-08-26T14:04:56Z</dc:date>
    </item>
    <item>
      <title>Re: XDR agent reboot recover everytime</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xdr-agent-reboot-recover-everytime/m-p/1263805#M9548</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/307134"&gt;@tlmarques&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;Based on the reboot message &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;“Reinício agendado em 1 minuto devido ao recover do cortex”&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, the reboot appears to have been initiated by the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Cortex XDR Health Helper (&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;CODE dir="ltr"&gt;&lt;STRONG&gt;&lt;SPAN&gt;xdrhealth&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/CODE&gt;&lt;STRONG&gt;&lt;SPAN&gt;) / recovery mechanism&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; to remediate an agent issue.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;-This can occur when an endpoint reconnects after being offline for an extended period and starts synchronizing agent/content updates. If an installation or upgrade is interrupted or encounters a driver/service issue, the recovery mechanism may initiate a reboot to complete the remediation. If the underlying issue remains, this can result in repeated reboots.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;&lt;STRONG&gt;&lt;SPAN&gt;Recommended checks:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL data-spread="false"&gt;
&lt;LI&gt;&lt;SPAN&gt;Review &lt;/SPAN&gt;&lt;CODE dir="ltr"&gt;&lt;SPAN&gt;xdrhealth.log&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; for Health Helper and reboot activity.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Check &lt;/SPAN&gt;&lt;CODE dir="ltr"&gt;&lt;SPAN&gt;MsiSuspendedInstallation.log&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; for interrupted MSI installation/rollback activity.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Review &lt;/SPAN&gt;&lt;CODE dir="ltr"&gt;&lt;SPAN&gt;trapsd.log&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; for agent, driver, or recovery-related errors.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;If the endpoint remains in a reboot loop, boot into &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Safe Mode&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, cleanly remove the Cortex XDR agent, and reinstall the required supported agent version.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;For the wider environment:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;For a large deployment, we recommend using &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;staged/delayed agent and content upgrades&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; and identifying long-term offline endpoints before allowing them to reconnect and synchronize. This can help avoid a large number of endpoints upgrading simultaneously.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you feel this has answered your query, please let us know by clicking&amp;nbsp;&lt;STRONG&gt;like&amp;nbsp;&lt;/STRONG&gt;and on&lt;STRONG&gt;&amp;nbsp;"mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;</description>
      <pubDate>Mon, 07 Sep 2026 14:42:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xdr-agent-reboot-recover-everytime/m-p/1263805#M9548</guid>
      <dc:creator>susekar</dc:creator>
      <dc:date>2026-09-07T14:42:46Z</dc:date>
    </item>
  </channel>
</rss>

