<?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: GlobalProtect auto-update fails, application breaks in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-auto-update-fails-application-breaks/m-p/578093#M5011</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/296402479"&gt;@richferrara&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This isn't a terribly uncommon problem with GlobalProtect upgrades being pushed out from the firewall instead of installing through something like SCCM/Intune. Every time I push out an update I can expect a couple people to run into this issue, usually because they restart during the upgrade when the connection drops or they have something installed on their network which prevents GlobalProtect from downloading the update properly.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If this keeps happening to you I'd be looking at the machine for anything that stands out as abnormal from a functionally upgrading client and making you connect to a different network for the upgrade to rule out local variables. Assuming that everyone else is working correctly it's unlikely to be a policy, but checking the logs on their end would also be a good idea.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think one of the reasons that you're having such an issue with this however likely has to do with the fact that your version is reporting as 6.0.1. That's extremely outdated at this point, and I have to image that what IT is re-installing on your machine is automatically attempting to update whenever it hits the firewall. They should just be deploying what they have activated on the firewall to you so you at least don't have to deal with this until they push the next update.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 22 Feb 2024 16:31:51 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2024-02-22T16:31:51Z</dc:date>
    <item>
      <title>GlobalProtect auto-update fails, application breaks</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-auto-update-fails-application-breaks/m-p/578092#M5010</link>
      <description>&lt;P&gt;I am a software engineer on Long Island, NY. My company uses GlobalProtect VPN to allow us to connect remotely to our internal network. We were originally using SonicWall but transitioned to GlobalProtect when our company was sold two years ago.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I am logged in from home, GlobalProtect will periodically check whether a new version is available. If it finds a new version, it attempts to automatically download and install the update. This update never works, and after it fails GlobalProtect becomes permanently non-functional. It just says "Not Connected", and if I click on the Connect button, nothing happens. Some websites suggested going into the Manage Portals screen, deleting all the portal names, and re-adding them. I've tried that and it didn't work. The only fix so far has been to have our I.T. department uninstall and reinstall GlobalProtect on my laptop. They've already had to do this 3-4 times because the failure keeps happening. As far as I know, I am the only employee in my department who is having this problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am running 64-bit Windows 10 Enterprise, version 21H2. GlobalProtect is version 6.0.1-19.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 16:22:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-auto-update-fails-application-breaks/m-p/578092#M5010</guid>
      <dc:creator>richferrara</dc:creator>
      <dc:date>2024-02-22T16:22:36Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect auto-update fails, application breaks</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-auto-update-fails-application-breaks/m-p/578093#M5011</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/296402479"&gt;@richferrara&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This isn't a terribly uncommon problem with GlobalProtect upgrades being pushed out from the firewall instead of installing through something like SCCM/Intune. Every time I push out an update I can expect a couple people to run into this issue, usually because they restart during the upgrade when the connection drops or they have something installed on their network which prevents GlobalProtect from downloading the update properly.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If this keeps happening to you I'd be looking at the machine for anything that stands out as abnormal from a functionally upgrading client and making you connect to a different network for the upgrade to rule out local variables. Assuming that everyone else is working correctly it's unlikely to be a policy, but checking the logs on their end would also be a good idea.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think one of the reasons that you're having such an issue with this however likely has to do with the fact that your version is reporting as 6.0.1. That's extremely outdated at this point, and I have to image that what IT is re-installing on your machine is automatically attempting to update whenever it hits the firewall. They should just be deploying what they have activated on the firewall to you so you at least don't have to deal with this until they push the next update.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 16:31:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-auto-update-fails-application-breaks/m-p/578093#M5011</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2024-02-22T16:31:51Z</dc:date>
    </item>
  </channel>
</rss>

