Leaderboard

Vistapocalypse - I have Avast AV Free 18.8.2356 and installed KB4500331 ten days ago. No problems so far that I see. But then again, I use duct tape.

Yep, in Windows XP Professional is there:

... And while you were at it, you could have also used a slightly modified id string for Tab Tally 1.3.0 (or 1.2.0 etc.) for it to install in either Serpent 55.0.0 or Serpent 52.9.0: }, "applications": { "gecko": { "id": "@tab-tally-st" } } St55 still contacts AMO to check for WE add-on updates, so, based on your settings, you'll be either upgraded automatically to v1.4.0 or be prompted to do so manually... St52 currently doesn't check AMO for WE updates (due to MCP implemented changes), but this can be partially or fully restored (search one of my previous posts in this thread for how-to-do it ). Installing Tab Tally with a different to the default extension id means you won't ever be offered any additional updates from AMO (and this is a known hack if one wants to stay at a specific version of an extension without having to disable extension updates in the browser)... ... and that is why you can also remove the whole META-INF directory!

@Z3r3 Welcome to MSFN! I am pleased that the MSE Definition Updater Version 1.9 does its work for you.

I'm not sure if this counts as a bug in XP or in Windows 10. The PoC uses schtasks.exe and schedsvc.dll from a Windows XP system on a Windows 10 system. Files from XP work on Windows 10, but when they do, they use priveledge escalation. https://web.archive.org/web/20190522011933/https://github.com/SandboxEscaper/polarbearrepo/tree/master/bearlpe

A bit of a necro-post to add my own experience with Hibernate. I've tried all the solutions suggested as regards BIOS/UEFI, wake on LAN and power management settings but I'd regularly get my PC waking up from Hibernation apparently at random rather than when you used the keyboard. Except it was not random - I eventually found the culprit(s) were other electrical devices connected to my home's ring main. But it was not just any device or a device plugged in the same mains electricity socket or even in the same room. It was two particular TVs and either of their digital STBs. Nothing else I've tested has the same effect - not a microwave, powerful lamp, heater, hairdryer, hi-fi or anything drawing significant current, it is just those two TVs. Put the PC into Hibernation then turn on either TV/STB and it'll wake the PC nine times out of ten. But if I turn the TV/STB on before Hibernation there is no problem and if I turn the TV/STB off whilst it is in Hibernation, in the same circumstances, there is no problem either. It would seem that Hibernation maybe storing the electrical state of the system. There has to be a residual current being used to be able to wake the PC up from the USB keyboard. Turning the TV/STBs on must be being detected and treated as a keyboard stroke. But why only those two devices I can not begin to guess.

@Nojus2001, you're definitely not alone. A weather forum I used to visit that closed sometime late last year or early this year was revealed to be running on Server 2003 until the bitter end. I'm sure that it's found itself mired into tonnes of big corporate networks too. It makes a wonderful workstation OS as well. And this is my 15-hour-old XP x64 install: :

I appreciate all the concern for Windows Vista on page 199 of this thread! You might be interested to know that Microsoft has just revised Customer guidance for CVE-2019-0708, which now advises those running Vista to install KB4499180 for Server 2008. The KB article has also been revised to include Windows Vista.

Sorry I fixed localized problem on v3.0b.

Try with Autoruns (MS/Sysinternals), it could be something on an external drive or a DVD, see: https://superuser.com/questions/1060908/windows-explorer-opens-at-every-startup Or good ol' by Mike Lin: https://www.portablefreeware.com/?id=249#comments jaclaz

alright it works. new Saturday binaries will work with 1.3 compat mode.

Pls lead me to the UOC Patch

Doesn't seem to matter though. I never claimed (or implied) that staying at NSS 3.44 Beta (instead or reverting to 3.43 Stable) would have allowed for the UXP browsers to successfully connect to the linked test server, i.e. https://tls13.1d.pw As I was already talking about the NSS library, I simply found an opportunity to mention the version downgrade I had observed; just that ... Today I borrowed briefly sister's Windows 7 SP1 64-bit laptop, where I updated stable Firefox (Quantum) to latest release 67.0 and Firefox ESR (Quantum) to latest release 60.7.0; to my great astonishment, both these Firefox versions connect successfully to the TLS 1.3 test server being discussed in this very thread; I dug around and found v60.7.0 comes with NSS 3.36.7, while v67.0 comes with NSS 3.43, the same one to be found inside the latest UXP forks released by Roy; so, despite my initial assessment, the "bug" observed here ("SSL_ERROR_RX_MALFORMED_SERVER_HELLO" error code when trying to connect to test server with latest New Moon 28/Serpent 52.9.0) doesn't appear to be only dependent on used NSS version and has been already fixed in latest Firefox Quantum releases! I persevered with my searches and, in the end, I stumbled upon a similar issue that was also affecting the Waterfox fork: https://github.com/MrAlex94/Waterfox/issues/783#issuecomment-458907249 So it looks as though the proper fix for this issue lies inside Bugzilla bug #1430268 fixed in mercurial commit: https://hg.mozilla.org/mozilla-central/rev/fafb731 @roytam1: Do you think you can somehow backport bug #1430268 to the UXP platform and thus apply it to both NM28/St52? Is a test-build even possible? If yes, then the OP (@Bersaglio) won't have to use a Chinese browser to connect with... OT: I don't mistrust myself the Chinese browsers any more than I do American ones like Google Chrome or Russian ones like Yandex Browser; all government security agencies are pretty much the same in my eyes... ; in this day and age, there's no such thing as privacy if you decide to connect to the live web...

The latest version of Qihu's 360 Extreme Explorer (v11.0.2086.0, released May 16th 2019 - its default UA declares a Chromium 69.0.3497.100 compatibility ) will also pass the test : But this is on Windows Vista SP2 32-bit, not on XP SP3 32-bit (hence, one of you XP users would have to test... ) EDIT: Make sure in "flags" that chrome://flags/#tls13-variant is set to "Enabled (Final)"

Some months ago I complained about the poor performance of Hotmail after their last update became final. They gave me an URL to access the older version, which works much better with XP compatible browsers. It also solves the problem with Chrome 49. https://outlook.live.com/owa/?path=/fb

Do not panic! For everything there are solutions: Office 2010: Antivirus: In Firefox, due to a crash in all versions, all add-ons stopped working, this problem has affected all operating systems. Fix: TeamViewer 14 version works in XP. Skype 7 version no longer works in any OS.

Well, assuming that we still use that old plain text unencrypted chat with old protocols, yes, but we don't. We are old, not stupid xD