Leaderboard

I made an unofficial update to BlackWingCat's Extended Core because the official Extended Core is not on BlackWingCat's new website, and I wanted to make an English version of Extended Core v16d because I cannot read Japanese. Most of the files in this update are from Extended Core v16a because they are the same as the ones in Extended Core v16d except for the language. Update: Made installer with SFXCAB utility. The new installer can be slipstreamed with nLite. ┌───────┐ │ Download │ └───────┘ Files not from Extended Core v16a: acpi.sys from http://blog.livedoor.jp/blackwingcat/archives/1974336.html ndis.sys from Extended Kernel v16d videoprt.sys from KB829884-v9 ntoskrnl.exe* ntkrnlmp.exe* ntkrnlpa.exe* ntkrpamp.exe* *All of these files are from Extended Core v16d but modified (see below) Modifications made to NT Kernel & System (the 4 exe files with '* next to them): All Japanese resources replaced with resources from Extended Core v16a. Exports for ExVerifySuite and RtlIntegerToUnicode added because the code for the functions was present but the exports were not added to the export table. New boot screen for Windows 2000 Professional:

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230506-3219d2d-uxp-725b27a0f-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230506-3219d2d-uxp-725b27a0f-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230506-3219d2d-uxp-725b27a0f-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230506-d849524bd-uxp-725b27a0f-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230506-d849524bd-uxp-725b27a0f-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230506-d849524bd-uxp-725b27a0f-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230506-d849524bd-uxp-725b27a0f-xpmod.7z Official UXP changes picked since my last build: - Remove unmaintained WebGL conformance test suite. (733451d1b) - Revert "Issue #61 - Place Skia in libxul" (260f8e154) - Issue #61 - Follow-up: Fix gkmedias.dll link bustage related to Skia. (6e2f70a70) - Issue #61 - Follow-up: Fix xul.dll link bustage related to Skia. (4584069f2) - No issue - Correct handling of async (arrow) functions declared inside constructors (ffe6d48af) - No issue - [MailNews] Fix build bustage due to recent MIME API changes (2048f4df5) - Issue #1451 - Split hunspell library out of xul. (cbbc15ad8) - Issue #1451 - Fix hunspell build bustage in FreeBSD. (d75c6c181) - Issue #1691 - Part 1: Provide a way of associating a private value with a script or module. (1a6b3a822) - Issue #1691 - Part 2: Implement call import and import meta in the parser. https://bugzilla.mozilla.org/show_bug.cgi?id=1427610 https://bugzilla.mozilla.org/show_bug.cgi?id=1484948 (a8ab41b4c) - Issue #1691 - Part 3: Finish implementing import meta. https://bugzilla.mozilla.org/show_bug.cgi?id=1427610 (3f4985ce6) - Issue #1691 - Part 4: Finish implementing call import. https://bugzilla.mozilla.org/show_bug.cgi?id=1499140 (7a6dab0b3) - Issue #1691 - Part 5: Don't pre-create module metadata object when compiling. https://bugzilla.mozilla.org/show_bug.cgi?id=1489477 (c965fbdd1) - Issue #1691 - Part 5b: Stop modules from entraining the top-level JSScript. https://bugzilla.mozilla.org/show_bug.cgi?id=1489477 (5c09a3b3c) - Issue #1691 - Part 6a: Support private values which contain pointers to cycle-collected C++ objects https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 (1b811bd71) - Issue #1691 - Part 6b: Initial browser support for dynamic import from module scripts. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 Factor out script fetch options from script load request classes. https://bugzilla.mozilla.org/show_bug.cgi?id=1480720 Remove support for version parameter from script loader. https://bugzilla.mozilla.org/show_bug.cgi?id=1428745 (86e0057ea) - Issue #1691 - Part 6c: Fix a few issues with the earlier commits. Need PNK_CALL_IMPORT and PNK_IMPORT_META in the node children list or it will abort. When porting ScriptFetchOptions support, I had 2 constructors, I picked the wrong one. Missed adding the preference javascript.options.dynamicImport to all.js. (9a19e9d16) - Issue #1691 - Part 6d: Optimize handling of internally-created Promise objects. https://bugzilla.mozilla.org/show_bug.cgi?id=1358879 The patch uses a different test: PROMISE_FLAG_DEFAULT_REJECT_FUNCTION which doesn't exist in our codebase. It was added in this bug, which appears to be partly complete: https://bugzilla.mozilla.org/show_bug.cgi?id=1313049 (c3daecc21) - Issue #1691 - Part 6e: Fix problems due to divergent codebases. This gets basic dynamic import working. Fix a problem in Part 5b where Mozilla used toGCThing() and we don't. Fix a problem in Part 4 where runtime() returns nullptr in our codebase since it runs on JS Helper thread. We need to get the runtime via runtimeFromAnyThread() instead. (e7d0b58e5) - Issue #1691 - Part 7a: Add a JS API to get the private value for the calling script or module. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 (62be54216) - Issue #1691 - Part 7b: Make load request element optional. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 (ba01d99e3) - Issue #1691 - Part 7c: Refactor ModuleScript into ClassicScript class and LoadedScript base class so we can represent all scripts that can perform dynamic import. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 (41eda05e5) - Issue #1691 - Part 7d: Allow dynamic import in cases where there's no referencing script or module. Support dynamic import from classic scripts by creating ClassicScript objects and associating them with the compiled. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 This patch is incomplete, some code in ScriptLoader::EvaluateScript() could not be applied for missing dependencies. Part 7e will apply the missing dependencies and finish the patch. (d5d7bb5e4) - Issue #1691 - Part 7e: Dependencies for required to finish part 7d. https://bugzilla.mozilla.org/show_bug.cgi?id=1331662 Reimplement EvaluateString using the ExecutionContext class. https://bugzilla.mozilla.org/show_bug.cgi?id=1316078 Extract redudant code into StartOffThreadParseTask. Use an ExclusiveContext instead of a JSContext in XDR functions. Add a script decoder as a valid off-main-thread parse-task. https://bugzilla.mozilla.org/show_bug.cgi?id=900784 Add nsJSUtils functions for encoding and decoding the bytecode. https://bugzilla.mozilla.org/show_bug.cgi?id=1316081 Add XDRIncrementalEncoder to replace delazified LazyScript in the encoded XDR buffer. Add an XDRIncrementalEncoder instance on the ScriptSource. Expose a new JSAPI to incrementally encode bytecode when it is generated. https://bugzilla.mozilla.org/show_bug.cgi?id=1334091 XDR function use the sourceObject instead of the enclosingScript as argument. (993476283) - Issue #1691 - Part 7f: Split up compile and execute so we can use ClassicScript. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 Refactor nsJSUtils::ExecutionContext to separate compilation and execution steps and allow extraction of compiled JSScript. https://bugzilla.mozilla.org/show_bug.cgi?id=1366773 Move buffer argument from JS::StartIncrementalEncoding to JS::FinishIncrementalEncoding. (c69a47c39) - Issue #1691 - Part 8: Fix --enable-debug builds and continue dynamic module import changes. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 Support import from timeout handlers by associating the initiating script with the compiled JSScript. Fix error message that covers all import() failures that don't throw a JS exception. https://bugzilla.mozilla.org/show_bug.cgi?id=1331662 Partial - Replace nsJSUtils::EvaluateString calls by ExecutionContext scopes. Left EvaluateString() in nsXBLProtoImplField.cpp until ExecutionContext errors can be fixed. (1109559a5) - Issue #1691 - Part 9: Make import() work when the active script is in another document. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 Associate event handler with active script when they are compiled. (be916ef7c) - Issue #1691 - Part 10: Add and use method to annotate CC crashes with a class name. https://bugzilla.mozilla.org/show_bug.cgi?id=1277260 Make PtrInfo into a class and mark it final. Also fix an erroneous debug assert because mBaseURL not set in one code path. (7e056a6f7) - Issue #1691 - Part 11: Fix incorrect reference counting in ModuleScript class. (edb82ec9f) - Issue #1691 - Part 12: Fix return value in ExecScript() and debug assert in ParseTask. https://bugzilla.mozilla.org/show_bug.cgi?id=1331662 Replace nsJSUtils::EvaluateString calls by ExecutionContext scopes. ExecutionContext: The mRetValue is not used even though it is checked in various asserts. This is how it is in the Mozilla code even years later, only the passed in value is used. ParseTask: JoinDecode() and JoinCompile() run the same code but the type is different causing a debug assert when it checks the type Script vs ScriptDecode. (a892a7590) - Issue #1691 - Part 13: Remove MUST_MATCH_TOKEN* macros in Parser. https://bugzilla.mozilla.org/show_bug.cgi?id=1501928 This was helpful in debugging one of the crashes, the macros made debugging a nightmare. (bc895eba9) - Issue #1691 - Part 14: Fix a debug assert and memory leak. PNK_IMPORT_META and PNK_CALL_IMPORT are binary nodes... They function similar to list nodes, so they worked there, but debug mode asserts because of the wrong type. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 Fixed a memory leak due to missing code in SourceScriptObject::finalize(). Thanks FranklinDM! (79ea755b7) - Issue #1691 - Part 15: Make |new import()| a syntax error. https://bugzilla.mozilla.org/show_bug.cgi?id=1508672 (f2b179156) - Issue #1691 - Part 16: Dynamically imported modules can throw any value as an exception. https://bugzilla.mozilla.org/show_bug.cgi?id=1508672 (1ac1e90b6) - Bug 1432272 - Make Fetch API use the global's base URL instead of the entry document's base URL (62e2fbc4e) - Issue #2218 - Part 1: Add nsExpirationTracker::NotifyEndTransaction(Locked) callbacks for subclasses to know when an aging iteration is complete (fa787f4a6) - Issue #2218 - Part 2: Make SurfaceCache free ImageSurfaceCache objects outside of the lock (93644fd33) - Issue #2073 - Follow-up: Use internal Move instead of std::move for consistency (b7f217e5a) - Issue #2213 - Follow-up: Fix derieved Generator prototypes after previous change (a27e8bf98) - Issue #2173 - Follow-up: Use common ancestor of PNK_(OPT)DOT in ASTSerializer::expression (e31a058ce) - Issue #1894 - Follow-up: Fix return value ordering in IonMonkey nullish coalescing (aece6260f) - Issue #1285 - Follow-up: Correctly handle follow-up compilations of RegExp with named capturing groups (0a74a5758) - Issue #2221 - Enable link-time optimization for Spidermonkey by default if building it shared. (b592711bb) - Issue #1691 - Follow-up: Fix CallSelfHostedFunction deprot introduced by Part 4. (45b34592b) - Issue #1862 - Follow-up: Replace deprecated Harfbuzz functions with current ones. (51426d105) - Issue #1691 - Follow-up: use error message with no arguments for bad import statements (73a99c155) - Issue #2142 - Fold BytecodeEmitter::checkTypeSet into BytecodeEmitter::emitCheck (014ebe8ae) - Issue #2142 - Extend newSuperCall for JSOP_SPREADSUPERCALL (6f56a494e) - Issue #2142 - Change InitPropertyOperation to accept a PropertyName directy and use DefineDataProperty (627d0da7d) - Issue #2142 - Add predicate functions count_if and any_of to ListNode iterator (3b9b111b2) - Issue #2142 - Ensure 'await' is always a restricted identifier when parsing modules (faed047e3) - Issue #2142 - Reduce calls to FindReservedWord when checking for forbidden identifiers during parsing (6abb54ff1) - Issue #2142 - Add internal option for fields, but always true (afa7bddc9) - Issue #2142 - Implement syntax for public/private fields and computed field names (51db22ff2) - Issue #2142 - Improve TokenPos handling in BCE (ab7721e4d) - Issue #2142 - Add PropertyEmitter, ObjectEmitter, ClassEmitter, LexicalScopeEmitter, DefaultEmitter (1b89be6d0) - Issue #2142 - Add FunctionEmitter, FunctionScriptEmitter, and FunctionParamsEmitter with current methods (e6335ded8) - Issue #2142 - Handle fields in derived classes (235ca7794) - Issue #2142 - Factor out PropertyName parsing from Parser::propertyName() (014953c53) - Issue #2142 - Implement ASI for fields (447261cf8) - Issue #2142 - Use JSOP_INITPROP for field initializers (849ab4417) - Issue #2142 - Restrict contents of direct eval in fields (8c6750014) - Issue #2142 - Fix several scoping issues in field initializers (bcb6203e4) - Issue #2142 - Pass through arguments in synthesized constructors for derived classes (1031b1fc4) - Issue #2142 - Emit field keys in correct order (f374ab472) - Issue #2142 - Don't treat PNK_NAME specially emitAssignmentOrInit (f0b06f5ad) - Issue #2142 - Set anonymous function name in field initializer (c20611496) - Issue #2142 - Optimize .initializers scoping and emitter (e0b5528c2) - Issue #2142 - Support SuperProperty in field initializers (b187006a7) - Issue #2142 - Parse and process static class fields (c3b19191f) - Issue #2142 - Track isFieldInitializer on JSScript instead of Scope (22a9d46ef) - Issue #2142 - Implement class static block (1fac189ae) - Issue #2142 - Remove the temporary fields option (ba9647a12) - Issue #2097 - Implement logical assignment operators (10951a169) - Issue #2097 - Handle Logical Assignment in Ion CFG (a7d8cecdb) - Issue #1691 - Follow-up: Fix videojs and potentially other problems. When rewriting the ExecutionContext code in ScriptLoader I accidentally removed some required code. (a1f787fc8) - Issue #2225 - Implement Element.replaceChildren (ae50e9e01) - Issue #1656 - remove vim control lines from js/src (e6ff567de) - Issue #1656 - Remove more vim control lines. (d388e478a) - Issue #1656 - Remove more vim control lines. (c9b8a576d) - Issue #1656 - Remove more vim control lines. (2f117eeca) - Issue #1656 - Remove more vim control lines. (a39fd9e75) - Issue #1656 - Remove more vim control lines. (f1759b33f) - No Issue - Do not parse or return body for XHRs with HEAD/CONNECT method or content-length=0 (84eadbe3c) - Issue #1691 - Follow-up: Ship dynamic module imports enabled by default. (5b7f259ab) Official Pale-Moon changes picked since my last build: - [Pale-Moon] Issue MoonchildProductions/UXP#1451 - Support hunspell as shared library (2be4e3e69) Official Basilisk changes picked since my last build: - [Basilisk] Issue MoonchildProductions/UXP#1451 - Support hunspell as shared library (61874576e) My changes since my last build: - partly import changes from tenfourfox: #651: M1761233 M1687303 M1633019 M1797336 M1799748 M1801102 (fb91afbb4) (ba3e46b17) - follow-up Issue #1691 - Part 6b, fix code that codepath is removed by upstream but remaining here (80d11ebc3) - Issue #2142 - follow-up rev 51db22ff, removing `static` keyword from upstream force-push rev aa6d42e5fc..63a00fdd25 (fa52ac972)

It’s quite a relief to me that you have treated Avast fairly even though you are embarked on a quest to find something better. (Good luck with your quest, but I’m still not convinced there is anything better for XP/Vista.) In fact you overstated the features of Avast Free 18.8 in your first paragraph: As your “Protection” screenshot shows, those features are locked in Avast Free, although I’m sure you had them with Avast Premier. (Malwarebytes Premium includes Ransomware Protection, but unfortunately that feature is inactive on XP/Vista. )

Avast Free Antivirus The most used and very often recommended antivirus program for Windows XP is probably Avast Free Antivirus, and that for years. It is supposed to use advanced algorithms for detecting viruses, malware, spyware and other threats in real-time. The Core Shields are: File Shield, Behavior Shield, Web Shield and Email Shield (only Outlook and Thunderbird are supported). Furthermore, it is supposed to protect against rootkits, and it offers additionally a Software Updater and Wi-Fi Inspector. Avast Free Antivirus still protects Windows XP owners with regular virus definition updates. But Avast no longer provides program updates, new features, bug fixes, or support for Windows XP. It was tested by AV-TEST and achieved a detection rate of almost 100% in November and December 2018 (see below). Key Features: Real-time protection against malware and online threats. Automatic analysis of suspicious files with CyberCapture. Network scanning and Wi-Fi security with Wi-Fi Inspector. Behavioral monitoring with Behavior Shield. Comprehensive scanning with Smart Scan. Creating a Rescue Disk for emergency use. Browser cleanup to improve online security. Password management with autofill feature. Game Mode to optimize computer performance during gameplay. Homepage: https://www.avast.com/windows-xp-antivirus https://web.archive.org/web/20181120211126/https://www.avast.com/free-antivirus-download Version number: 18.8.4084.0 (18.8.2356) Date of release: 15.11.2018 System Requirements: A PC with 256 MB+ RAM and 1.5 GB of hard disk space. Avast Antivirus is compatible with Windows 11, 10, 8.1, 8, 7, Vista, XP SP3. Version history and release notes: Review: https://www.expertreviews.co.uk/software/1406757/avast-free-antivirus-2018-review-the-best-free-security-suite Tests: Avast in general: https://www.av-test.org/en/antivirus/home-windows/manufacturer/avast/ https://www.av-comparatives.org/tests/summary-report-2018/#avast Screenshot with the final test results from AV-TEST: Screenshot with the Product of the Year 2018 award from AV-Comparatives: Avast Free Antivirus 18.7 & 18.8 in detail: https://www.av-test.org/en/antivirus/home-windows/windows-10/december-2018/avast-free-antivirus-18.7--18.8-184902/ Download links: Online installer: https://install.avcdn.net/av/avast/iavs9x/avast_free_antivirus_setup_online.exe Offline installer: https://install.avcdn.net/iavs9x-xp/avast_free_antivirus_setup_offline.exe Avast VPS update for versions 12+: https://install.avcdn.net/vpsnitro/vpsupd.exe Avast Uninstall Utility (Avast Clear) in the correct version of 18.8.4084.0: https://web.archive.org/web/20181116091922if_/http://iavs9x.avg.u.avcdn.net/iavs9x/avastclear.exe How to uninstall Avast using Avast Clear: Sometimes it's not possible to uninstall Avast the standard way using the Add/Remove Programs in control panel. In this case, you can use the uninstallation utility Avast Clear: Download avastclear.exe on your desktop. Start Windows in Safe Mode. Execute the avastclear.exe. If you installed Avast in a different folder than the default, browse for it. (Note: Be careful! The content of any folder you choose will be deleted!). Click REMOVE. Restart your computer. Screenshots: I only used Avast Free Antivirus for a very short time. The version of Avast I had installed for years was Avast Premier. Unfortunately, I have a split opinion about Avast. On the one hand, it's great that Avast offers such a program for Windows XP at all, although this operating system was abandoned by Microsoft in 2014. And then also free of charge and with real-time protection. That is rather rare. Avast continues to roll out definition updates for this old version on a regular base. Furthermore, it has an excellent detection rate of almost 100%. On the other hand, I had various problems with Avast. Exceptions that were set for alarms of the background guard were simply ignored. Avast partly operates according to its own standards and does not always respect the user's settings, which I rather consider as disenfranchisement of the user. I don't like that, and it's simply a no go. Another bad habit of Avast, and unfortunately that of many other manufacturers, is to offer features that are apparently free. For example, SecureLine VPN. In fact, you have to pay for it. I find something like this to be more of a cost trap. That's why I didn't list this feature above. And I had serious problems to uninstall Avast completely. That was actually another no go. Furthermore, I don't like the disk space consumption of Avast products which is always very high. One main reason for that is probably the implementing of (unnecessary) features or those which only can be used if you pay for them. More details about problems in terms of Avast, you will find here: Despite all points of criticism, Avast Free Antivius is a program offering a very good protection and definitely an option for Windows XP, but I personally can't and won't recommend it here due to my reservations and experiences from the past. Kind regards, AstroSkipper

Win7 will never be abandonware as long as Microsoft exists. Abandonware is to be products that have an abandoned license or copyright, and has nothing to do with whether a product is actively being sold or supported. I personally don't care about the Thorium website, or the developer, or the browser, or warez, or whatever else. The forum has rules about what can be posted about and what is directly linked to, and this is only because in the past we have received complains and nasty letters from lawyers about things. So we don't allow those types of posts as a measure to protect the forum from disappearing entirely. And sure, you don't need to point out the gray area that exists with the rules, with regards to extended kernels or updates (updates are the big thing really) so let's hope MS continues to not care about those things so we can still talk about them here.

Just in case, what jaclaz said is CLEARLY here: Nothing more, nothing less.[1] To be even more clear, I did not start anything, I was asked explicitly for something and answered to the best of my knowledge (on something that I don't use, never used and don't foresee using in the near future and that I neither recommend, endorse, nor judge, criticize or comment in any way). jaclaz [1] last character is a full stop or period.

And now a general statement about this thread. I collect and present information about security programs for Windows XP here in the most structured way possible. I also share the knowledge I have acquired as a Windows XP user for 22 years now. I don't have to do all this, I am well supplied here with everything that is necessary to use Windows XP as securely as possible in the future. All I do here is preserving and sharing knowledge and information to help others in using Windows XP safely for as long as possible. Nothing more, nothing less!

D.Draker - we are on the same page on this one, "personality conflicts" aside. Honestly, we really are. But as I read kar1's comments, I have to agree with him as well. There is a "fine line" and it is all "relative" (or is "subjective" a better word?) on just when and where that line is crossed. I am not trying to go off-topic and it is kind of all tied together. For one, the future of Chrome on Win7 is likely (I reiterate "likely", this is purely speculative) going to follow the lead of what the XP Crowd has been doing since Chrome abandoned XP. ie, one or two years behind. There is decompiling, recompiling, backporting, debug, dependency checks, trial-and-error, et cetera - "software doesn't write itself". Will that workflow "work" for the Win7 Crowd? Only time will tell. It is all "speculative" as soon as the word "future" enters the scene. There is also "intended audience" if this Future Chrome on Win7 is going to gain true traction. What I perceive a "car" to be in the future may very well differ from what you perceive a "car" to be in the future - it's all speculative... and subjective... Secondly, I propose that we have to view the previously-mentioned browser and in turn the previously-mentioned web site the same way we (MSFN) views Extended Kernels. I guarantee that Microsoft does not view an Extended Kernel in the same way that the end-consumer views an Extended Kernel. And unless I'm mistaken, even MSFN Forum Rules do not allow "links" to Extended Kernels (I could be wrong on this, this falls back on "intended audience" and I do not use Extended Kernels nor follow those MSFN Threads). But MSFN does allow us all to use the phrase "extended kernel" even though it may be indexed by search engines. You see how that "fine line" comes into play? Does the Future of Chrome on Win7 force the intended audience to utilize an Extended Kernel? Or will traction only be gained by giving in to the demands of the Vanilla Win7 Crowd and the Future of Chrome on Win7 not require an Extended Kernel? Only time will tell... And have a great day, my friend, and note that I strived to word this reply without triggering any "personality conflicts"

Did you do the tests yourself ? Do you always trust what they write in the papers ? Whom that testing website belongs to ? Where do they have their headquarters ? Ivan's bedroom ? We still shall continue to support our Italian friends, we are doing it for centuries, I mostly buy Italian clothes for almost half of a century already. She bought the PRO version of Vir.IT eXplorer for her weak PC. That having been said, I'm leaving, and leaving you with Mina7869 and legacysan, perhaps it's too cruel, sorry, I have no control over it. And I wish you a speedy recovery from your tiredness. I know a good Italian vitamins. Kind regards, D.Draker.

Do not post a link to that website and do not mention the types of things that are on that website. Even mentioning the names will cause those terms to be indexed by search engines and leading to here. So don't do it, use a generic term. I edited some posts to remove the specific terms and replace them with warez.

Windows 7 was excellent, like it even better than XP.

Agreed! Operating Systems should not have "features" - NONE. If I want a "snipping tool", I'll add it myself from available third-party apps. If I want a "firewall", I'll add it myself from available third-party apps. If I want an antivirus "defender", I'll add it myself from available third-party apps. If I want a "candy crush" kiddy game, I'll add it myself from available third-party apps. If I want "3D" paint or printer apps, I'll add it myself from available third-party apps. If I want "people" contacts right on the taskbar, I'll add it myself from available third-party apps. If I want to "share" files, I'll add it myself from available third-party apps. If I want an all-in-one sytem-level "Cortana" tracking, I'll add it myself from available third-party apps. If I want to "sync" files, I'll add it myself from available third-party apps. If I want my Start Menu to feed me advertisements, I'll add it myself from available third-party apps. The Operating System should just "operate", bloatfree. Something like that...

I found the problem comes from win32k.sys 5.0.2195.7603, 5.0.2195.7624, 5.0.2195.7636, 5.0.2195.7640 has same problem X3 Externded kernel v5.0.2195.7641 is based on 7640 https://forums.moneysavingexpert.com/discussion/5174319/font-problems-in-vista-after-windows-update-kb3013455