Replies

In my previous post I did that: wrote “here” and that word linked to https://davidmathlogic.com/colorblind/ (scroll down to the ‘Accessible palettes’ section).

3 users thanked author for this post.

SueW, OscarCP, GoneToPlaid

The blue links and other small visual adjustments made to the Login and Calendar widgets seem to have been introduced recently: comparing the current WP theme file where the CSS styles are defined with a previous version (a snapshot taken last week) shows over 40 new lines that added style changes to the .sidebar element. People still seeing the “old” brown links might just try to clear the browser’s cache and fully refresh the website to reload it and get the new contents.

OscarCP made a really good point regarding the links readability: the use of “pure blue” might be problematic for colorblind people. Instead of “pure blue” (#0000ff) for the normal links and “pure dark blue” (#000099) for the visited links, perhaps the Askwoody site development team could use more suitable alternatives, such as (for e.g.) #0c7bdc and #4b0092 – as suggested here (scroll down to the ‘Accessible palettes’ section).

1 user thanked author for this post.

jburk07

The latest definitions (v1.301.1684.0, signed Sep 18, 2019 22:38 [UTC]) seem, indeed, to have fixed the bug (Quick and Full scan appear to be working fine again), which was not introduced solely by the latest 4.18.1908.7 engine: scans were OK right after the engine upgrade, but they got broken afterwards, somewhere along by subsequently released definitions. Trying to roll the engine back to the previous 4.18.1907.4 version only made no difference.

Additional help (KB) for future reference (in case anyone’s interested):

1. Rolling back to a previous engine
   On Windows 10, Defender usually keeps a copy of the previous engine(s) at the

   %ProgramData%\Microsoft\Windows Defender\Platform

   folder. That means you may roll back Defender’s engine to the previous 4.18.1907.4 version by typing, from an administrative prompt, the following command:

   "%ProgramData%\Microsoft\Windows Defender\Platform\4.18.1907.4-0\MpCmdRun.exe" -revertplatform

   (as described in Microsoft’s KB4052623 support article)

   If successful, the command will output the following message:

   MpUpdatePlatform returned successfully.

   Besides rolling back Defender’s engine to the previous 4.18.1907.4 version, the current engine’s ‘4.18.1908.7-0’ sub-folder will also be removed from

   %ProgramData%\Microsoft\Windows Defender\Platform

   However, the related scheduled tasks (under the Task Scheduler’s ‘Microsoft\Windows\Windows Defender’ library folder) are not removed: because they will continue to (wrongly) refer to the newer 4.18.1908.7 engine, the first time you check for updates you may get an error and be prompted to restart the anti-malware protection. Once you do that, however, subsequent updates will bring back the newer 4.18.1908.7 engine (along with the latest available definitions).

2. Getting the latest engine
   The latest engine (described as “AntiMalware Platform Update”) may also be manually installed and downloaded from Microsoft Catalog: search for KB4052623 and download the three files. You then need to check their properties to determine the right one you actually need (depending on your architecture): ‘x86fre’ (32-bit), ‘amd64fre’ (64-bit) or ‘arm64fre’ (ARM).
3. Getting the latest definitions
   The Security Intelligence Updates webpage provides direct links for the latest “stable” definitions. However, sometimes these links aren’t necessarily offering the latest available definitions: occasionally, these are slightly “behind”.If that is the case and you absolutely need to get more recent definitions you should head straight to the Release Notes and take a note of the latest definitions version (the first entry from the drop-down list). Then, you may use the direct link to the versioned signature file (32-bit, 64-bit or ARM architecture):
   • hxxps://definitionupdates.microsoft.com/download/DefinitionUpdates/VersionedSignatures/AM/<VERSION>/x86/mpam-fe.exe
   • hxxps://definitionupdates.microsoft.com/download/DefinitionUpdates/VersionedSignatures/AM/<VERSION>/amd64/mpam-fe.exe
   • hxxps://definitionupdates.microsoft.com/download/DefinitionUpdates/VersionedSignatures/AM/<VERSION>/arm64/mpam-fe.exe

   For e.g. the direct link to the current 1.301.1684.0 64-bit definitions is:
   https://definitionupdates.microsoft.com/download/DefinitionUpdates/VersionedSignatures/AM/1.301.1684.0/amd64/mpam-fe.exe

5 users thanked author for this post.

wavy, geekdom, abbodi86, woody, WildBill

Your legacy 32-bit ‘?????.exe’ application seems to be using the deprecated clCreateCommandQueue() function (that has been replaced by clCreateCommandQueueWithProperties() on OpenCL 2.0) from the external OpenCL library, which is missing (system-wide) but the binary should be able to use it if you place it at the same directory.

Try to get the valid v1.x ‘OpenCL.dll‘ library from the vendor’s media, or find it in your system

dir /b /s /a G:\OpenCL.dll

(see the file Properties>Details, File version should read “1.x.x.x”, ideally “1.2.x.x”)

and copy it to the binary’s directory (G:\v22\Programs).

NOTE: Although this little tweak might (hopefully) do the trick, keep in mind that malware might also take advantage of that very same technique (see DLL planting).

[Speccy]

Perhaps the answer you’re looking for lies within the Acknowledgments webpage: CVE-2019-0708 refers the UK’s National Cyber Security Centre (NCSC).

• This reply was modified 3 years, 5 months ago by Speccy. Reason: Edited (irrelevant, off-topic info removed)

A recently upgraded (from v1709) system I’m managing is currently a beta testing v1803 machine (build 17134.885 [KB4507435 – July 9, 2019]): so far, so good (no pushed offers here).

Group Policy defined deferrals in place:
-SAC
-Feature deferral: 200 days
-Quality deferral: 30 days
-Preview builds disabled
-Do not allow update deferral policies to cause scans against Windows Update (*)

(*) The last one might be particularly important: Susan Bradley pointed out that if this policy is disabled or undefined, the Windows Update client might initiate automatic scans against WU even if update deferral policies are enabled…

Please consider following PKCano’s advice: download the 896Mb KB4509478 cumulative update from Microsoft Catalog and try to install it.

Earlier this month I had similar issues attempting to update a v1709 system with KB4503284 (the update was not failing, it simply didn’t install at all: instead, it displayed a rather unusual, unexpected and puzzling “not applicable to your computer” error message).

So I took the opportunity and upgraded the system to v1803. I was planning to update it with KB4503286 (June 11, build 17134.829) too but, after reading this thread and the list of issues and fixes on Microsoft’s website, I ended up installing KB4509478 (June 26, build 17134.860).

All went well, it worked for me. Might work for you, also. 😉

Same as Mark here: 1709 Pro, deferrals on, no update offers so far. Screenshot attached.

 

1 user thanked author for this post.

woody

Minor glitch: If you’re updating a Windows 10 Version 1709 system, the Master Patch List has an incorrect link since friday.

UPDATED [as of June 4, ~03:50 PM UTC-6]: Link fixed (thank you Susan! 🙂

(just edited/updated the original post)

UPDATED [as of June 4, ~03:52 PM UTC-6]: Link fixed (thank you Susan! 🙂

1 user thanked author for this post.

Fred

One of Susan’s Master Patch List May links for Windows 10 Version 1709 is incorrectly pointing to the Windows 10 Version 1803 one instead:

• The 05/14/2019 4499179 (Version 1709) update link is pointing to the 4499167 (Version 1803) update

UPDATED [as of June 4, ~03:54 PM UTC-6]: Link fixed (thank you Susan! 🙂

+1 for Pale Moon (I only mentioned Comodo’s forks because IMHO they might be generally well-suited for most users – but yes, Pale Moon also comes to mind). 🙂
To deal with Firefox’s memory consumption there’s a little, nice utility that has proved its value over the years (and, if you like it, it is well worth donating to the developer):
https://www.rizonesoft.com/downloads/firemin/

One well maintained, well supported and security-focused “fork” you might wish to consider as a rather decent alternative to the “main” Firefox version is Comodo’s IceDragon:
https://www.comodo.com/home/browsers-toolbars/icedragon-browser.php

The current version (v64.0.4.15) is a custom-build “fork” of Firefox 64.0.2 with specific, additional enhancements (that, for the most part, are optional and may be left enabled or turned off, depending on your privacy concerns) such as SiteInspector and the Secure DNS Service.

Chrome users might also resort to Comodo Dragon (based upon Chromium) as a “forked” alternative to the “main” version, when “colossal blunders” happen.

Heads up: Firefox 66.0.4 (which includes a proper fix to the whole mess) is not available yet at
https://www.mozilla.org/en-US/firefox/all/
(as I write this, the release notes
https://www.mozilla.org/en-US/firefox/66.0.4/releasenotes
are still being prepared) but impatient users may already find it at
https://ftp.mozilla.org/pub/firefox/releases/66.0.4/

2 users thanked author for this post.

Lori, Cesar

The 8-ball says: “-Read abbodi86’s post.” 🙂
KB4490628 (SSUv3) is OK but, unless you’re an advanced user (technically skilled) – or you simply don’t mind being an earlier adopter (and play along with whatever comes up) – you’re better off (read: safer) WAITING a few more days until we hit MS-DEFCON 3 or above. 😉

2 users thanked author for this post.

RDRguy, Elly