Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër
Arkivuar

ProductCode (ProductID) after Firefox Setup 68.5.0esr.msi is installed - Not the same as .MSI installer

agcastle2000

The ProductCode (ProductID) after Firefox Setup 68.5.0esr.msi is installed does not match to the ProductCode (ProductID) of the Firefox Setup 68.5.0esr.msi. We use SCCM to create the application deployment for Firefox ESR x64 and to install all the endpoints. When creating the deployment, SCCM automatically extracts the ProductCode, and uses the same to detect the presence of the application - if it's not present, it installs. The main issue is that when SCCM checks again the presence after it's installed, the deployment fails because the ProductCode after it's installed is different than what came with the MSI installer. I noticed that this is the case as well for Firefox Setup 68.4.0x esr.msi whereas in the past this was not the case.

See the attached file to see the screenshots.

The ProductCode (ProductID) after Firefox Setup 68.5.0esr.msi is installed does not match to the ProductCode (ProductID) of the Firefox Setup 68.5.0esr.msi. We use SCCM to create the application deployment for Firefox ESR x64 and to install all the endpoints. When creating the deployment, SCCM automatically extracts the ProductCode, and uses the same to detect the presence of the application - if it's not present, it installs. The main issue is that when SCCM checks again the presence after it's installed, the deployment fails because the ProductCode after it's installed is different than what came with the MSI installer. I noticed that this is the case as well for Firefox Setup 68.4.0x esr.msi whereas in the past this was not the case. See the attached file to see the screenshots.
Foto të bashkëngjitura ekrani

Krejt Përgjigjet (1)

Can you check to see if this bug covers your situation?

https://bugzilla.mozilla.org/show_bug.cgi?id=1505436