topic Re: New global protect install for Windows x64 v6.3.3c828 has broken MSI in Prisma Access Discussions

New global protect install for Windows x64 v6.3.3c828 has broken MSI

Dave-Richards — Wed, 26 Nov 2025 16:30:10 GMT

Hi,

We have just downloaded the latest GP for Windows x64 v6.3.3c828. The MSI properties indicate that the product code is {B316DC7F-EB20-4A36-AA0A-96099FA142DB} however when it installs it installs as the previous version product code {CD809CD6-9D01-417E-9E76-D19EEE77E74F}.

We have verified that the version installed and running is the c828 version, but the registry keys indicate that it is using the old version of the product code.

For those that dont know, MSI product codes are globally unique world wide so should be different between two versions of the Windows MSI installer.

Re: New global protect install for Windows x64 v6.3.3c828 has broken MSI

kiwi — Tue, 02 Dec 2025 11:07:41 GMT

Hi @Dave-Richards ,

I recommend opening a $\text{TAC}$ case for this.

If I'm not mistaken, the consensus under the $\text{MSI}$ framework is clear: Minor Upgrades (or Hotfixes) are generally expected to keep the same $\text{ProductCode}$ as the base version.

$\text{6.3.3c828}$ is a hotfix (more precisely $\text{6.3.3-h4}$ ), in which case it should be considered a Minor Upgrade and require no change in $\text{ProductCode}$ .

That being said, the fact that you are seeing a new $\text{ProductCode}$ in the $\text{MSI}$ file's properties but the registry retains the old $\text{ProductCode}$ is inconsistent and prevents deployment tools (like $\text{SCCM}$ or $\text{Intune}$ ) from reliably detecting and applying the update.

Kind regards,

Re: New global protect install for Windows x64 v6.3.3c828 has broken MSI

Dave-Richards — Tue, 02 Dec 2025 11:18:39 GMT

Hi,

My understanding, and general experience from all the MSIs i have deployed over the years, is that each MSI code is unique no matter whether its a minor or major version.

Adobe is one of the few companies that keeps the same product code and just changes the version number, but having to check both the product code and version number using deployment tools sometimes leads to problems if the product code has not been copied correctly.

I have to raise TACs via our third party company and am attempting to do that but wanted to raise on here as i hoped they would notice it quicker.