28.0.0 won't run Topic is solved

[person45]

Report.wer

Once more, getting details about the crash is essential.

Since people seem to think it's related to the graphics card/driver, I remember the developers for the old Opera having a hard time getting hardware acceleration to work. In Advanced Preferences I turned off everything that indicated acceleration and it didn't help. My card is the GTX 750.

Is it possible to open palemoon in a safe mode with hardware acceleration off?

It's possible this is one area that wasn't fully tested for. The operating systems were tested, but not every GPU and driver because of the cost.

[therube]

Safe Mode disables Hardware Acceleration.
Separately, HA alone can be disabled (so outside of Safe Mode).

[MRCS4]

person45 -
"Wait a second, on the same operating system, it will work on one drive but not on another?"
Not the same OS, one is Win7 32-bit and the other is 64-bit. The crux of it, as it turns out, is that I didn't have EMET installed on the 64-bit.

therube -
Thanks for the link to Safe Mode. I was looking for something like that. It will be very helpful in the future.

"which additional exploit box needs to be unchecked"
Following up on this comment of mine, PM will not run with any of the exploit boxes checked, including the ones in Mitigation Settings at the upper right. This deserves starting a separate topic.

[ky331]

It appears my problem was fixed with the release of PM 28.0.1: MalwareBytes Anti-EXPLOIT 1.12.1.109 is NOT blocking PM 28.0.0.1 (on my 32-bit Win 8.1 system)

[New Tobin Paradigm]

You mean Pale Moon 28.0.0.1 (the forth version slot is for out of band releases). There is no such thing as Pale Moon 28.0.1.. yet.

[MRCS4]

In my previous post about updating the Redistributable I had assumed Visual Studio 2017, but I see from the release notes that 2015 is being used. For those interested, here's the link to the latest version.

Microsoft Visual C++ 2015 Redistributable Update 3
https://www.microsoft.com/en-us/downloa ... x?id=53587
14.0.24212.0
8/18/2016
(patch KB2999226 included in release)