Windows 10: Compatibility Update KB4023057 (08 01 2019)
The above tweet by security researcher Kevin Beaumont now addresses another Issue. In McAfee Endpoint Protection, developers have introduced a rule called RDP. Might have something to do with the BlueKeep vulnerability. It only blocks the July 2019 updates. This user confirms that he received the July 2019 updates only after uninstalling the McAfee security solution. Any of you who have noticed that?
Windows 10: Compatibility Update KB4023057 (08 01 2019)
[German]Microsoft has released the KB4505903 cumulative update on June 25, 2019 for the Windows 10 May 2019 Update (Versions 1903) after an extensive testing period with Windows Insiders. At least, this update is available via Microsoft Update Catalog.
Inhaltdateisynchronisierung ist fehlgeschlagen. Ursache: File cert verification failure. Quelldatei: /c/msdownload/update/software/secu/2019/07/windows8-rt-kb4504418-x86_cbfca28e203c05cf0d8bf6e8c56d81c9bd170789.psf Zieldatei: c:\WSUS\WsusContent\89\CBFCA28E203C05CF0D8BF6E8C56D81C9BD170789.psf.
Inhaltdateisynchronisierung ist fehlgeschlagen. Ursache: File cert verification failure. Quelldatei: /c/msdownload/update/software/secu/2019/07/windows8-rt-kb4504418-x64_7fc2ec35606f12f6065408850962706ebd9c9816.psf Zieldatei: c:\WSUS\WsusContent\16\7FC2EC35606F12F6065408850962706EBD9C9816.psf.
[German]Systems that have certain versions of the Intel Rapid Storage Technology (Intel RST) drivers installed cannot be updated to the Windows 10 May 2019 Update. Microsoft has set an upgrade blockade. And for machines in a domain, there are boot issues with MIT Kerberos when installing the May update (KB4497935).
Microsoft and Intel have discovered compatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers in conjunction with the Windows 10 May 2019 update. I became aware of the issue via tweet and this article. If the device to be updated has an Intel RST driver version installed between 220.127.116.112 and 18.104.22.1683, it cannot install the May 2019 update. Microsoft points this out in KB article 4514156.
The upgrade wizard then displays the above message and the update is terminated. Microsoft has therefore set an upgrade blockade for such systems. The issue can be easily solved, because the driver versions 22.214.171.1244 or higher are compatible. For affected devices it is recommended to install Intel RST version 126.96.36.199.1044. A device on which these drivers are installed can install the Windows 10 May 2019 update after the next reboot.
A second issue affects Windows 10 systems with the May 2019 update (version 1903) that are embedded in a domain. Devices that are connected to a domain that is configured to use MIT Kerberos realms will not boot after KB4497935 is installed or will get into a reboot loop. This affects both domain controllers and domain members. Microsoft specifies the following platforms:
After extensive testing with insiders and an unintended release on June 25, 2019, Microsoft finally released the two updates KB4505903 (CU) and KB4508433 (SSU) for Windows 10 Version 1903 on June 26, 2019. I have added the necessary additions to the blog post Windows 10 V1903 Update KB4505903 (07/26/2019).
Microsoft has released a safety alert effective July 24, 2019. Microsoft has probably updated several Servicing Stack Updates (SSUs) for Windows 10. The latest SSUs can be found on the website ADV990001.
The website contains the information that a Security Intelligence Update version 1.299.891.0 was released on 31.7.2019. The update is to be installed automatically and can be downloaded there for the various platforms, from Microsoft Security Essentials (Windows 7) to Windows Defender (Windows 8.1, Windows 10) to System Center 2012 Configuration Manager and Microsoft Forefront Protection & Co. The website also tells you how to trigger updates manually using commands from the command prompt.
However, if you select older updates, you will find entries to detect potentially unwanted applications/software (PUA) or Trojans. The Trojans Winnti, the Ransomware Ryuk or the Exploit Exploit:O97M/CVE-2017-11882 for exploiting the vulnerability CVE-2017-11882 in the old Office Formula Editor (see Hacker are misusing CVE-2017-11882 in Office EQNEDT32.EXE) are detected by the update version 1.299.843.0 of July 30, 2019.
[German]Does cumulative update KB4505903, released July 26, 2019, for Windows 10 V1903 fills the system disk with useless event entries? I received a message from a blog reader, that indicates this behavior. Now we have been able to identify MicrosoftOfficeHub as a root cause.
Cumulative Update KB4505903 is available for Windows Version 1903 and Windows Server Version 1903. The patch was released on July 26, 2019 after extensive tests with Windows insiders and various improvements by Microsoft and increases the build number to 18362.267. The update contains quality improvements, but no new operating system functions. I had reported about details in the blog post Windows 10 V1903 Update KB4505903 (07/26/2019).
It should be noted that Microsoft does not distribute this update in corporate environments. What I also find strange are the Windows 10 versions 1507, 1511, 1607, 1703, 1709 and 1803 mentioned by Microsoft in the blog post to which this update applies. But Windows 10 versions 1507 through 1703 will only get updates in the Enterprise versions (see my blog post Patchday Windows 10 Updates (May 14, 2019)). So it might be an attempt, to upgrade these old systems to Windows 10 Version 1903.
The update deeply interferes with the existing Windows 10 installation, cleans user-set update blockers, creates free disk space on the system drive if necessary, resets the network connection and more. More details about this cyclically released update can be found in the article Windows 10: Update KB4023057 re-released (02/14/2019). Another special feature is that this update is installed as an app and may cause installation errors (see my older blog post Windows 10: Update KB4023057 re-released (01/16/2019)).
Similar articles:Windows 10: Update KB4023057 released (Dec. 7, 2018)Windows 10 reliability update KB4023057 (02/08/2018)Windows 10: Update KB4023057 re-releasedWindows 10 Updates KB4295110/KB4023057 (08/09/2018)Windows 10: Update KB4023057Windows 10: What is REMSH.exe for?Windows 10: Update KB4023057 released (Sept. 6, 2018)Windows 10: What are Rempl.exe, Remsh.exe, WaaSMedic.exe?Windows 10: Update KB4023057 re-released (01/16/2019)
If I remember well, KB4023057 was and still is one of the most weird and unexplained updates in the recent times. This update has never been offered to WSUS, but only to Windows Update. This would indicate that it meant for unmanaged end-users and unmanaged small business users.My understanding was that it was meant to facilitate a smooth upgrade to 1703, but it is offered on Windows Update also to Windows 10 Enterprise LTSB version 1607 and Windows 2016 Server which is LTSB version 1607 as well, which are normally not upgraded to the next major version and an upgrade is not offered on any regular channel.This patch may be harmless, but why it was released and where it actually applies, it is still a mystery. @abbodi86 is likely to have the right explanation, even if this covers only partially what this patch does. -us/help/4023057/update-to-windows-10-versions-1507-1511-1607-and-1703-for-update-relia
-us/help/4021701/ -us/help/4021702/ -us/help/4049411/ -us/help/4073543/ -us/help/4033631/windows-10-update-kb4033631 -us/help/4056254/windows-10-update-facilitation-service -us/help/4023057/update-to-windows-10-versions-1507-1511-1607-and-1703-for-update-relia -us/help/4023814/some-versions-of-windows-10-display-a-notification-to-install-the-late
However, what if it was too late and the process led to your system losing important files and data? Tragic right? Well not to fret because in case you have lost data from Windows update failure, we recommand you to use the professional windows data recovery software-Tenorshare 4DDiG data recovery software, which can help you get your lost data back from windows update error 0x8024a205.
On Non-Enterprise editions of Windows 10, KB4023057 installs a new application called Microsoft Update Health Tools: -us/topic/kb4023057-update-for-windows-10-update-service-components-fccad0ca-dc10-2e46-9ed1-7e392450fb3a. Added logic to ensure that the Windows Update Medic Service is deactivated including after re-enabling and deactivating Windows Updates using the Update tab.
Added System Clean Up options to Common Options dialog. This removed the need for these to be typed and run manually.1. Deployment Image Servicing and Management (DISM)Reduces the size of the WinSxS folder by uninstalling and deleting packages with components that have been replaced by other components with newer versions. Should be run after a Windows update.2. Native Image Generator (NGEN).Optimizes the .NET Framework. Should be run after an update of .NET Framework.3. CompactCompact (Windows 10/ Server 2016/2019). Enables CompactOS to compress specific Windows system files to free up space. Can take several minutes to execute.4. Disk Cleanup.Deletes temporary and unnecessary files.
Microsoft on Tuesday made the seventh Windows 10 feature update dubbed May 2019 Update or version 1903 available to non-Insiders. In addition to security and performance improvements, the update includes new features like a new light theme, Windows Sandbox for app testing, and the ability to pause updates (including Home versions).