Closed Bug 1842956 Opened 2 years ago Closed 2 years ago

upgrade install version 115.0.2 fails on Windows 11 22H2

Categories

(Firefox :: Installer, defect)

Firefox 115
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: balpgm55, Unassigned)

Details

Steps to reproduce:

Downloaded offline install package version 115.0.2.
Ran as administrator.

Actual results:

Files are extracted to C:\Users\Appdata....\setup.exe.
Error message appears that Firefox can only be installed on wintows 7 or later, asks me to hit ok or cancel.

Expected results:

Should have received window asking for standard or custom install

Worked successfully on windows 11 version 21H2. Note that I am submitting this report on a different computer than the one that encountered the error. My admin accounts do not have internet access. Please let me know if there are any files you need to see and how to create them.

The Bugbug bot thinks this bug should belong to the 'Core::Security: PSM' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Security: PSM
Product: Firefox → Core
Component: Security: PSM → Installer
Product: Core → Firefox

Please make sure you do not enable Compatibility Mode.

(In reply to Masatoshi Kimura [:emk] from comment #2)

Please make sure you do not enable Compatibility Mode.

I know nothing about "Compatibility Mode". Is this a common setting? Are we going to see a wave of install failures with the Windows 7 deprecation due to this setting?

Flags: needinfo?(VYV03354)

This has nothing to do with compatability mode. The offline installer was downloaded from https://www.mozilla.org/en-US/firefox/all/#product-desktop-release and then right clicked and "Run As Administrator" was selected.

I am retracting this report. The problem was that applocker was blocking SYSTEM.DLL from executing since it was under AppData. Somehow my rule that allows administrators to run all DLL's was deleted.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.