Leaderboard

You should give Pi-Hole a try. I do use it to protect all machines in my LAN. Big advantage is one single dedicated RaspberryPi protects all machines, and one has just one central ad/malware trap to configure and tweak. One RaspberryPi 3B or 3B+ is not much of a cost for such 24/7 protection. Of course, this is just my 2¢, and YMMV!

Version 20.06.1 - option -Get-Range added ex. GWT -Get-Range N:\Win10.iso bootmgr;boot*.efi;*\boot.sdi

It can also happen that XP doesn't detect phone properly as media device if both USB debugging and MTP are enabled on it. If you don't mind just one feature being available at the time, the solution is easy, enable the one feature that is needed and leave other disabled. If both are desired, there is a trick that works. When both are enabled, you'll initially get MTP entry in Device Manager with exclamation mark and the error that device isn't configured. Open said MTP entry, go to Details tab, select Device Instance ID, leave the properties window open. Launch Registry Editor (regedit.exe), navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB. Refer to the value sown in the MTP properties window you've opened in 1. step to know where exactly you should navigate from USB onward. Right-click on the key you've just navigated to->right click->Permissions...->make sure Everyone is selected->tick the checkbox at Full Control/Allow, confirm the new settings. On the right-pane, open CompatibleIDs entry with a double-click, then insert USB\MS_COMP_MTP at the beginning. Should work fine if added to the end, but this particular ID is usually at the beginning. You may undo permissions changes from 4. step; when you open Permissions window, make sure Everyone is selected, click Remove (the checkbox at Full Control/Allow should be gone now) and confirm. Back to the Device Manager MTP Properties window, you may trigger driver update from the Driver tab. If it asks about searching for the driver on Windows Update, say No, not this time, then let it detect it automatically (Install the software automatically option).

In fact, the number of computers with windows XP installed is much, much larger. Almost all payment terminals, ATMs and cash registers still work on XP. Also, a lot of computers are used in organizations where there is not even access to the Internet. And also in special equipment in hospitals, auto diagnostics and so on.

What's the point of your post? The link has been in the first message of the topic the whole time...

That's because FxESR 52 gets by default the (supported) Polymer v1 (Pm1) layout; only versions of Firefox older than 44 (Fx <=43) are being served the Classic layout, the one to be retired in March; if you use a UAO on FxESR 52 to spoof it as Fx 43, you'll get the older layout with the deprecation infobar: BTW, Firefox (Quantum) versions newer than 62 (63 =< Fx) are being served the newer Polymer v2 (Pm2) layout, which, on the outside, looks a lot like Pm1, but on the inside it's quite a different beast... FxESR 52 and the UXP browsers don't currently support it; of course FxESR 52 isn't maintained anymore, but MCP devs are already making talk about "upgrading" UXP to support Pm2 in the coming months; Google have not yet indicated for how long they'll keep supporting Pm1 Pm1 is considerably more resource hungry compared to the out-going Classic style, and this fact alone will create problems for older browsers capable of handling Pm1 but which are installed on old hardware (which seems to be the case with many XP/Vista users here... ) Of course, the forced migration to Pm1 will disable many user YT customisations, in the forms of XUL extensions, userstyles, userscripts etc., which were initially targeting the Classic layout; sadly, it'll be game over for those older browsers (on, perhaps, even older OSes/hardware) that can't cope with Pm1 at all... Some relevant links: https://support.google.com/youtube/thread/27596769 https://www.reddit.com/r/youtube/comments/eyjy4i/misc_fd_youtube_is_removing_the_old_design_soon/ https://forum.palemoon.org/viewtopic.php?f=3&t=23566 Chrome 49 has adequate support for Pm1, so if OP wants to continue using it for YT past March 2020, OP must: Install the User Agent Switcher extension from GWS: https://chrome.google.com/webstore/detail/user-agent-switcher/kchfmpdcejfkipopnolndinkeoipnoia Set a "Permanent Spoof" for youtube.com domain (aka SSUAO) and pretend to be Firefox 60 (e.g. Mozilla/5.0 (Windows NT 6.3; rv:60.0) Gecko/20100101 Firefox/60.0); then, every time a YT URL is loaded, OP will get the supported Pm1 layout without any nags about an unsupported browser: However, that workaround will, sadly, come to an end when evil Google decide to remove Pm1, too (which can be anytime, I hazard a guess and predict some time towards the end of this year) .

If you're a true supermegaueberultraparanoid person, get yourself a full-body Velostat gimp-suit, 'cause just a cap is not enough. Else, a good hardware firewall, MBAM 3.0 premium and a PEBCAK trap ought to suffice (and if not, just redeploy the latest backup) for you to hang loose.