Leaderboard

Merry Christmas! http://o.rths.ml/gpc/files1.rt/K-Meleon1.5.4en-US.tls12.7z most of GRE components are replaced with Retrozilla-based build (but not all)

I encountered the same: not only that, some other functions (file uploading among them) got invalid. I find the simple workaround is to switch general.useragent.compatMode.firefox value to false. The true value used to work, so it must be some change at Github's side. If you would not change the compatMode, the working user agent is Mozilla/5.0 (Windows NT 5.1; rv:68.9) Goanna/4.5 Basilisk/52.9.0

RoyFox +1, and element of HongKong in the logo.

https://www.upload.ee/files/10887690/Download_YouTube_Videos_as_MP4_1.8.10.zip.html http://saveimg.ru/show-image.php?id=4ecdbe1669499e4df029ab85cd6e6ea5

Happy Holidays to U All

Happy Holidays to U All

Granted, "MSE" has other meanings, but this thread's Jarhead title could easily be overlooked by anyone searching for information about Microsoft Security Essentials. (Edit: I approve of the thread's new title.) The GUI should "show MSE as being up to date in Windows 7" with respect to definition updates for an unknown period of time after January 14. As recently as December 11, my assumption was that MSE definition updates would cease after January 14. (Windows 8.1 and 10 have Windows Defender, MSE was never officially supported on any server, and today's Microsoft is a leaner and meaner corporation than the MS of yesteryear.) However, my assumption has been proven wrong: The official Microsoft Extended Security Update FAQ mentioned in the above-referenced article was indeed updated on December 18: Nearly all MSE users running Windows 7 are no doubt using version 4.10.209.0, which cannot be installed on XP and is only half as old as the version that many XP diehards are nostalgic about.

That article does not say that exactly - the assumption is it will but until MS unequivocally say that I won't believe it and even then I bet there will be a time limit. With XP MSE worked fine long after official support had ended but then out of the blue users suddenly found they could not update MSE automatically or through MSE itself when installed on an XP machine (that included VMs too). It all had to be done manually. Then that ended, again without warning, and we had to rely on the helpful people here and elsewhere who came up with a way installing the new MSE definition updates which wouldn't have otherwise been possible. But within a few months even that was torpedoed by MS and we were stuck with finding a decent alternative AV to replace MSE that worked with XP. It'll be the same thing with Win7 eventually.

Mathwiz said: > Anyone who finds the suggested "Whistler" branding for NM 28 objectionable, > should let us know now, while there's still time to change it. Seems pretty innocuous to me, > but you never know what might turn folks off unless you ask! Nothing objectionable, but turning off from completely "unknown" browsers without even taking a short look is quite normal. Therefore, to give clueless users at least a tiny hint about origins and intentions, I'd find it helpful to keep stubs like -fox- and -moon- in some way, and add "X" somewhere as hint if the XP-capability is crucial for a build. Of course, not only for completely clueless newbies, but also helpful for the rest of us to easier remember what's what :-)

1.5.13 installed on v1909 VMs and working without messages at logon. Thank you for making Windows 10 palatable for another 6 months. Just sent you another 20 Euro. Hope it helps make your holidays brighter! -Noel

Speaking of planned obsolescence, a recent Windows 10 update has blocked all versions of VMware Workstation below version 15.1 from running: https://communities.vmware.com/thread/619878 That means that users of 14.x, which was released in September 2017, will have to purchase an upgrade licence in order to keep using software that is far from obsolete, given that even version 10 can run Windows 10 as a guest.

I'm sorry I was kinda vague in my previous post. What I meant to say is that the KB4524752 update will be offered to Win7 Professional users thru Windows Update while those using Home Basic/Premium or Ultimate of Win7 editions will be offered the KB4493132 update instead of KB4524752 on the list of available updates thru WU. And of course neither KB4493132 nor KB4524752 will show up for those using Win7 Enterprise & Server 2008 R2 editions.