[Solved] AOS 10.2.0.187 under XP - still deactivated by Mozilla

Hi,

how can I activate it? It was deactivated under W7, too, but reactivated ba now. Concerns my Twin os
AMD_Athlon 1800+.
:wink:
=Snake=

I don’t know why this is, when you have FireFox esr version 45.9, I wouldn’t have thought FF would have applied the change to that version. Are you able to get a later ESR version for your XP system ?

Mine is on ESR version 52.9.0, not the latest and I don’t know if that is impacted as I haven’t used AOS for a very long time.

Thx, David, for your answer. No chance to update FF esr (see screenshot). This machine doesn’t support SSE2.

Ah, fortunately my CPU on my XP system supports SSE2. Unfortunately the later ESR builds don’t support XP.

You want to keep that AMD_Athlon 1800+ it might be worth something in a few years time :slight_smile:

Well, I’m afraid I have to, for we’re here at our camping flat. So I’m waiting, that I can use AOS under XP, too.

AOS just had been reactivated (like under W7 with careful use!) by Mozilla! Thx for any help. :slight_smile:

You’re welcome.

EDIT just read this:

[b]Add-ons disabled or failing to install in Firefox[/b]

For users who cannot update to the latest version of Firefox or Firefox ESR, we plan to distribute an update that automatically applies the fix to versions 52 through 60. This fix will also be available as a user-installable extension. For anyone still experiencing issues in versions 61 through 65, we plan to distribute a fix through a user-installable extension. These extensions will not require users to enable Studies, and we’ll provide an update when they are available. (May 8. 19:28 EDT)

Looks like this is what fixed it.

Yes. I think so, too. Thx again. :slight_smile:

No problem.

It’s just weird that Mozilla were able to screw this up in non-current ESR and Regular versions. Which is confirmed by their ability to retrospectively fix the screw up in non-current ESR and Regular versions, with 'no action required by the user’ I’m not sure which is worse.

no action required by the user ?
That’s not exactly what I understood in mozilla’s note.
what I’m reading from their plan:

we plan to distribute an update that automatically applies the fix to versions 52 through 60.
even if the fix should be automatically applied , the update, as for it , will not be done in the background but with a patch -->action required for the patch

or

This fix will also be available as a [b]user-installable extension[/b].
--> action required for the extension

I don’t know what about the first solution but as far as the second is concerned is currently available and requires user action.
https://addons.mozilla.org/en-US/firefox/addon/disabled-add-on-fix-52-56/

Basically my concern was:
A. The primary issue, add-ons no longer working in an old unsupported version of the ESR, which still supports legacy add-ons. For this to fail would have required changes to the underlying program.

B. Which is basically resolved by the same change to the underlying program, requiring no user action. They broke it doing this and then fixed it the same way.

Hell this is meant to be an unsupported ESR version (and OS), either its unsupported or it isn’t, no middle ground.

Well, it’s a bit curious for me, that, when a theme was closed (signed as ‘solved’), other users have to write their meaning. I don’t mind, but I think, that your last sentence has to be continued in a new thread, for it’s not only mozilla, which is involved, but also MS (and it’s my experience within the last 11 months, that MS does everything [even distributing ‘W7-.NET’ updates, that kill every os during installation!
Last week I just finished the 12th clean W7 install during that time!

Considering this topic is/was called “AOS 10.2.0.187 under XP - still deactivated by Mozilla” and is directly about Mozilla. Even if it has been marked Solved or not , it is about how Mozilla got into This mess in the first place.

If it were only about MS or its many browsers and the stuff they have got up to, then yes that would be totally off topic and should be on a new topic.

Sorry, but I don’t have the power to start that new topic. Thx for confirming, David.

@ =Snake=
There is nothing to stop you creating your own new topic in the same way you created this one.

If however, if it is about MS and you’re experience within the last 11 months, that MS does everything [even distributing ‘W7-.NET’ updates, that kill every os during installation!. Then it could well be a candidate for inclusion in the General Sub Forum if it is sort of related to Avast being caught in the middle of it. Otherwise, it might well be considered off-topic, but the General sub-forum is not to strict.

@DavidR

Sorry, but I don't have the power to start that new topic.
off-topic: Sorry, that I couldn't send you a pm.

I have to care for me, for my cancer (Non-Hodgkin-Lymphom, stadium IV) returned after 40 years!
If you would create that new topic, I would be at your side.
:frowning:

I’m sorry to hear about your health issue.

However, I wouldn’t know where to start:
In general I haven’t had any MS Update issues (since they dropped support for XP/Vista).
My old Acer Netbook with Win7 Starter edition I no longer use that, it had some WU issues. That was more to do with being unable to update than issues after updates.

Ok, so let’s be clever and keep our feet calm.