FireFox 67 - 64Bit won't start after auto update

[Roman78]

We now had several computer which after a Firefox 67 64-Bit update, Firefox would not start any more. This is always after a auto update. We have to remove Firefox and reinstall it by hand. What could be the reason.

OS: Windows 7 Professional

We now had 9 computer whit this problem.

[kerft]

I wonder if, similar but not the same as this thread, http://forums.mozillazine.org/viewtopic ... &t=3050350 , try to rename the file or move it away - compatibility.ini in the profile folder http://kb.mozillazine.org/Profile_folder_-_Firefox

[jscher2000]

We now had several computer which after a Firefox 67 64-Bit update, Firefox would not start any more. This is always after a auto update. We have to remove Firefox and reinstall it by hand. What could be the reason.

OS: Windows 7 Professional

We now had 9 computer whit this problem.

Maybe the event log could have some info on Windows stopping a transgression during startup?

Is this in an enterprise where the TEMP folder might be locked down? Something related to the new way of handling profiles may create a "temporary" profile under the Windows TEMP folder in the user profile. I haven't seen a complete description of what happens.

[Roman78]

Just checked the Logfile of one who just failed (today we count 5 more).

This is the error report:

Version=1
EventType=PCA2
EventTime=132034078627701693
Consent=1
ReportIdentifier=c07ca908-803e-11e9-91a4-1c1b0d9080b9
Response.type=4
Sig[0].Name=Problemsignatur 01
Sig[0].Value=firefox.exe
Sig[1].Name=Problemsignatur 02
Sig[1].Value=67.0.0.7075
Sig[2].Name=Problemsignatur 03
Sig[2].Value=Firefox
Sig[3].Name=Problemsignatur 04
Sig[3].Value=Firefox
Sig[4].Name=Problemsignatur 05
Sig[4].Value=Mozilla Corporation
Sig[5].Name=Problemsignatur 06
Sig[5].Value=100
Sig[6].Name=Problemsignatur 07
Sig[6].Value=0
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=1031
File[0].CabName=PCW8AC1.tmp
File[0].Path=PCW8AC1.tmp
File[0].Flags=65536
File[0].Type=5
File[0].Original.Path=C:\Users\xxxx\AppData\Local\Temp\PCW8AC1.tmp
File[1].CabName=ACG8AD2.tmp
File[1].Path=ACG8AD2.tmp
File[1].Flags=65536
File[1].Type=5
File[1].Original.Path=C:\Users\xxxx\AppData\Local\Temp\ACG8AD2.tmp
FriendlyEventName=Systemeigener Host für Skriptdiagnose
ConsentKey=PCA2
AppName=Firefox
AppPath=C:\Program Files (x86)\Mozilla Firefox\firefox.exe

and:

<?xml version="1.0" encoding="UTF-16"?>
<CompatWizardResults ApplicationName="C:\Program Files (x86)\Mozilla Firefox\firefox.exe" ApplicationPath="C:\Program Files (x86)\Mozilla Firefox\firefox.exe" MediaType="Fixed" CompatibilityResult="Failure">
<LAYER NAME="VISTASP2" />
</CompatWizardResults>

First off all, i don't know why it installs into the x86 folder. Maybe because it was the 32-Bit version getting updated to the 64-Bit version. Secondly... CompatibilityResult="Failure" LAYER NAME="VISTASP2" what does that mean?

The 32-bit version of FF67 is working. Also logging in with high access (local admin) rights seems to work. The windows Tempfolder indeed has some restrictions.

[jscher2000]

<?xml version="1.0" encoding="UTF-16"?>
<CompatWizardResults ApplicationName="C:\Program Files (x86)\Mozilla Firefox\firefox.exe" ApplicationPath="C:\Program Files (x86)\Mozilla Firefox\firefox.exe" MediaType="Fixed" CompatibilityResult="Failure">
<LAYER NAME="VISTASP2" />
</CompatWizardResults>

First off all, i don't know why it installs into the x86 folder. Maybe because it was the 32-Bit version getting updated to the 64-Bit version. Secondly... CompatibilityResult="Failure" LAYER NAME="VISTASP2" what does that mean?

When Firefox on 64-bit Windows switched from 32-bit preferred to 64-bit preferred, the same folder was re-used, so for older installations, it is not unusual to still be under the Program Files (x86) path. (If you plan to remove that installation and you use Office, you should change your default browser away from Firefox first to avoid this problem: https://www.slipstick.com/problems/this ... trictions/.)

Is it possible that firefox.exe is set to launch in compatibility mode for an older version of Windows?