dencorso

Sure. OTOH, you might have guessed that much by yourself, without having to refer to any blog nor to FF's official site for it, right?

R.I.P. Gora. You'll sure be much missed!

Unless your machine gives you a bona-fide BSOD in the next 72h, I'll just think it was just a glitch in the matrix. This is the most important ultra-high-level troubleshooting technique: it's called ostrich algorithm...

Of course you can! Click on your username just below the MSFN logo at the topmost part of the page and then click on Attachments, in he drop-down menu...

I have two machines running fine from their 1st (and only) install, and that's from 2007 (SP3 is from 2008, remember?). Of course, they've been kept up to date, to this day.

I don't think so. Were it so, most of we all should be getting BSODs, too, right?

This other tester works OK for me, as well as Javatester also does (both with FF 49.0.2). @Dave-H: Glad you got it sorted out!

Urm... no. Sorry to disagree, but I do get the message below (with FF 49.0.2) on the page you gave a link to, heinoganda.

It seems to. At least Javatester behaves as expected...

And one in ~35 PPL has XP! Yes!!!

Using internal SATA (or PATA aka IDE) HDD/SDD bigger than 2TiB (not 2TB) is courting failure. Do NOT do it! Using external, USB, HDD/SDD bigger than 2TiB (not 2TB), because the USB stack works OK with 4KiB sectors. For more on this, there's an extant sticky thread on this forum, so do read it.

Well, in case that figure is correct, considering XP has about 10% of the market, that means the full PC universe comprises some 2 billion (= 2x109) machines.

Ditto! The only instance of calling home is quoted (in part) below: With this, they counted all (or most) the currently active XP machines (all XP were still receiving MRT, IIRR).

Probably not... I guess you'll have to download the installer and install over your (then) current FF once. Thenceforward, all subsequent updates will happen as usual. Extended Support Release. Yes, for some time. See this: FF ESR FAQ. ...And try to hang loose for a change, will you?

It may. Then again, you may want to run it further on. As for the damage... it just sent some telemetry to MS. It seems to be harmless, but one never knows. What is done is done (it happened to me, too...), but what can be prevented... why not? Hence, I consider it prudent to add the registry tweak described by Woody. BTW, I've just installed a new XP SP3 machine (it's not fully finished yet, to tell the truth), and MS got no telemetry from it that is preventable by that tweak.

Well, since nobody posted about it till now, it's up to me to do it, sh here it goes: Woody's warning (and his solution!) in this post on his blog also applies to XP !!! The latest (and last) MRT.EXE provided by MS on August 2016(at the WU/MU site) is actually v. 5.39.12900.0 (the very 1st to phone home) !!! So, be sure to add the registry fix described by Woody (or fall back to the previous version of MRT.EXE).

You do rock, jumper, you sure do!

Dyn DNS kissed the dust on Oct 21, 2016, due to DDoS! Read about it at the Register <link>

Was it this (<link>) the driver you've got from the internet?

Info on POSReady updates/hotfixes is scanty, anyway, to say the least...

Same here!

It shows pink for me, too. I don't think it should be up to me to change the secondary theme color, since it changed of its own volition to start with... That's easy: none at all. We're just users (MS customers... current or former), nothing more.

Done! Thanks for the heads up!

Wow! Well, it didn't, not too long ago, so that what you should really have said is: Microsoft Update Catalog now also works with other Internet browsers, at long last!

Ditto.