Microsoft Released Windows CLU kb4579311_buildno_19041.572 to Windows 10 v2004 20H1 and buildno_19042.572 to Windows 10 v2004 20H2 and to Windows 10 s

  • Thread starter RAJU.MSC.MATHEMATICS
  • Start date
R

RAJU.MSC.MATHEMATICS

On 13th October 2020, Microsoft released another Windows Cumulative Update KB4579311 build no 19041.572 and 19042.572 to Windows 10 v2004 and to Windows 10 server v2004.


Also, this windows update is compatible with windows 10 v2004 build no 19042 20H2

I am sharing the direct download links from www.catalog.update.microsoft.com



For windows client, 10 v2004 and windows server v2004 CLU kb4579311 64bit os. You can download from here


For Windows 10 client v2004 CLU kb4579311 32bit os. You can download from here


Highlights of this update

## Updates to improve security when using Microsoft Office products.

## Updates for verifying usernames and passwords.

## Updates to improve security when Windows performs basic operations.


Improvements and fixes

## Addresses an issue with a possible elevation of privilege in win32k.

## Addresses an issue with the Group Policy service that might recursively delete critical files in alphabetic order from %systemroot%\system32.

This issue occurs when a policy has been configured to delete cached profiles. These file deletions might cause stop error “0x5A

(CRITICAL_SERVICE_FAILED)” boot failures.

## Addresses an issue with creating null ports using the user interface.

## Security updates to Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Media, Windows Fundamentals, Windows Authentication, Windows Virtualization, and Windows Kernel.


If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.


Known issues in this update::

symptom 01::

Users of the Microsoft Input Method Editor (IME) for Japanese or Chinese languages might experience issues when attempting various tasks. You might have issues with input, receive unexpected results, or might not be able to enter text.


Workaround 01::

For more information and workaround steps, please see KB4564002.

We are working on a resolution and will provide an update in an upcoming release.


symptom 02::

When installing a third-party driver, you might receive the error, “Windows can’t verify the publisher of this driver software”. You might also see the error, “No signature was present in the subject” when attempting to view the signature properties using Windows Explorer.


Workaround 01::

This issue occurs when an improperly formatted catalog file is identified during validation by Windows. Starting with this release, Windows will require the validity of DER-encoded PKCS#7 content in catalog files. Catalogs files must be signed per section 11.6 of describing DER-encoding for SET OF members in X.690.


Workaround 02::

If this happens you should contact the driver vendor or device manufacturer (OEM) and ask them for an updated driver to correct the issue.



For more information about the resolved security vulnerabilities, please refer to the Security Update Guide.

Before installing this update::
$$ Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU).

$$ SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU and applying Microsoft security fixes. For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.


$$ If you are using Windows Update, the latest SSU (KB4577266) will be offered to you automatically. , to get standard alone update visit here




Sources are taken from::




Thanks for reading my post, if you found this post is useful means, then recommend this post to windows users and then give me upvotes.
11cab5a0-5ad9-4dea-91e1-ab85ca4e4625?upload=true.jpg
















Continue reading...
 
Back
Top Bottom