<?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 Multiple Cortex XDR Agent Upgrades Failing with &amp;quot;The installer has timed out&amp;quot; Error in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/multiple-cortex-xdr-agent-upgrades-failing-with-quot-the/m-p/1259068#M126751</link>
    <description>&lt;P data-path-to-node="4"&gt;Hi team,&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;We are currently encountering a mass upgrade failure across multiple endpoints during both Auto Upgrade and Manual Server Upgrade attempts. While a single endpoint successfully upgraded using our standard profile and group configuration, the remaining endpoints consistently fail.&lt;/P&gt;
&lt;P data-path-to-node="6"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="6"&gt;Issue Summary:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL data-path-to-node="7"&gt;
&lt;LI&gt;
&lt;P data-path-to-node="7,0,0"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="7,0,0"&gt;Symptom:&lt;/STRONG&gt; The upgrade tasks transition to a "Failed" status with the specific error message: &lt;STRONG data-index-in-node="92" data-path-to-node="7,0,0"&gt;"The installer has timed out."&lt;/STRONG&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P data-path-to-node="7,1,0"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="7,1,0"&gt;Scope:&lt;/STRONG&gt; Multiple endpoints are affected within the same policy group, ruling out a general console or profile configuration issue.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P data-path-to-node="7,2,0"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="7,2,0"&gt;Suspected Root Cause:&lt;/STRONG&gt; We suspect local MSI database corruption on the affected endpoints from previous installation cycles, causing the upgrade package to fail when attempting to stop services or verify the existing installation signature.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-path-to-node="8"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="8"&gt;Next Steps &amp;amp; Planned Action:&lt;/STRONG&gt; To resolve this efficiently across all affected endpoints, we intend to execute a clean wipe using Palo Alto's official cleaner tool followed by a fresh agent installation. We are currently coordinating with the accounts team to orchestrate this mass deployment via Microsoft Intune.&lt;/P&gt;
&lt;P data-path-to-node="9"&gt;If anyone has successfully pushed a console-side workaround for this specific timeout loop without running a local cleaner script, please share your insights.&lt;/P&gt;
&lt;P data-path-to-node="10"&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Wed, 15 Jul 2026 08:59:37 GMT</pubDate>
    <dc:creator>Z.Zikri</dc:creator>
    <dc:date>2026-07-15T08:59:37Z</dc:date>
    <item>
      <title>Multiple Cortex XDR Agent Upgrades Failing with "The installer has timed out" Error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/multiple-cortex-xdr-agent-upgrades-failing-with-quot-the/m-p/1259068#M126751</link>
      <description>&lt;P data-path-to-node="4"&gt;Hi team,&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;We are currently encountering a mass upgrade failure across multiple endpoints during both Auto Upgrade and Manual Server Upgrade attempts. While a single endpoint successfully upgraded using our standard profile and group configuration, the remaining endpoints consistently fail.&lt;/P&gt;
&lt;P data-path-to-node="6"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="6"&gt;Issue Summary:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL data-path-to-node="7"&gt;
&lt;LI&gt;
&lt;P data-path-to-node="7,0,0"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="7,0,0"&gt;Symptom:&lt;/STRONG&gt; The upgrade tasks transition to a "Failed" status with the specific error message: &lt;STRONG data-index-in-node="92" data-path-to-node="7,0,0"&gt;"The installer has timed out."&lt;/STRONG&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P data-path-to-node="7,1,0"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="7,1,0"&gt;Scope:&lt;/STRONG&gt; Multiple endpoints are affected within the same policy group, ruling out a general console or profile configuration issue.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P data-path-to-node="7,2,0"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="7,2,0"&gt;Suspected Root Cause:&lt;/STRONG&gt; We suspect local MSI database corruption on the affected endpoints from previous installation cycles, causing the upgrade package to fail when attempting to stop services or verify the existing installation signature.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-path-to-node="8"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="8"&gt;Next Steps &amp;amp; Planned Action:&lt;/STRONG&gt; To resolve this efficiently across all affected endpoints, we intend to execute a clean wipe using Palo Alto's official cleaner tool followed by a fresh agent installation. We are currently coordinating with the accounts team to orchestrate this mass deployment via Microsoft Intune.&lt;/P&gt;
&lt;P data-path-to-node="9"&gt;If anyone has successfully pushed a console-side workaround for this specific timeout loop without running a local cleaner script, please share your insights.&lt;/P&gt;
&lt;P data-path-to-node="10"&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jul 2026 08:59:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/multiple-cortex-xdr-agent-upgrades-failing-with-quot-the/m-p/1259068#M126751</guid>
      <dc:creator>Z.Zikri</dc:creator>
      <dc:date>2026-07-15T08:59:37Z</dc:date>
    </item>
  </channel>
</rss>

