Along with cumulative update KB4346783 Windows 10 build 17134.254 for April 2018 update, Microsoft has released Update KB4343893 Windows 10 Build 16299.637 for devices that are still running Fall Creators Update (version 1709). And cumulative update KB4343889 Windows 10 build 15063.1292 for users still running creators update version 1703.
According to the changelog, Microsoft hasn’t fixed any major security issue with these cumulative updates and it’s quite normal as the vulnerabilities were addressed earlier this month. Such as addressed an issue with Edge where the browser stopped working after setting a DLL rule in AppLocker.
-
- Addresses an issue in Microsoft Foundation Class (MFC) applications that may cause applications to flicker.
- Addresses an issue that causes win32kfull.sys to stop working (Stop 3B) when canceling journal hook operations or disconnecting a remote session.
- Addresses an issue that caused users to press Ctrl+Alt+Delete twice to exit assigned access mode when autologon was enabled.
- Addresses an issue that prevented the Device Guard PackageInspector.exe application from including all the files needed for an application to run correctly once the Code Integrity policy was completed.
- Addresses an issue that prevents users of PIV/CAC smart cards from authenticating to use enterprise resources or prevents Windows Hello for Business from configuring on first logon.
- Addresses an issue that causes Microsoft Edge to stop working after setting a DLL rule in AppLocker.
- Addresses an issue that, in some cases, failed to clear decrypted data from memory after a CAPI decryption operation was completed.
- Addresses an issue that causes the Wi-Fi EAP-TTLS (CHAP) authentication to fail if a user saves credential information before authentication.
- Addresses an issue that causes high CPU usage on machines with built-in Sierra broadband modules when switching from WLAN to LAN. The WWanSvc service continually claims additional memory until the machine becomes unresponsive and a black screen appears.
- Addresses an issue that prevents a checkpoint created on a Windows Server 2016 cluster from being reapplied. This occurs when VMs are running on a cluster-shared volume (CSV), and the error is “Failed to read from stream. HRESULT = 0xC00CEE3A.”
- Addresses an issue where changes to the %HOMESHARE% path aren’t reflected in the folder redirection configuration. As a result, folder redirection for a known folder doesn’t work.
- Addresses an issue that requires a password to be input twice if you connect to a locked device using Remote Desktop Connect.
- Addresses an issue that causes devices that have 802.1x Extensible Authentication Protocol (EAP) enabled to randomly stop working with the stop code ”0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL”. The issue occurs when the kernel memory pool becomes corrupted. Crashes will generally occur in wifi.sys.
- Provides a stability resolution for native Peripheral Component Interconnect Express (PCIe) enumeration and the runtime D3 (RTD3) state.
- Addresses an issue that may remove a Dynamic Host Configuration Protocol (DHCP) option from a reservation after changing the DHCP scope settings.
- Addresses an issue that may prevent the Start menu from opening after refreshing your PC.
- Extends the Key Management Service (KMS) to support the upcoming Windows 10 client Enterprise LTSC and Windows Server editions. For more information, see KB4347075.
The patch also comes with a couple of issues. Microsoft has shared the workaround for the issues. You can check out the list of known issues below.
| Some non-English platforms may display the following string in English instead of the localized language: ”Reading scheduled jobs from file is not supported in this language mode.” This error appears when you try to read the scheduled jobs you’ve created and Device Guard is enabled | Microsoft is working on a resolution and will provide an update in an upcoming release. |
When Device Guard is enabled, some non-English platforms may display the following strings in English instead of the localized language:
|
Microsoft is working on a resolution and will provide an update in an upcoming release. |
If you’re still running Windows 10 Creators Update then your Device receive KB4343889 which will bump the OS To build 15063.1292 And contains the falowing changelog.
-
- Addresses an issue that causes win32kfull.sys to stop working (Stop 3B) when cancelling journal hook operations or disconnecting a remote session.
- Addresses an issue in Microsoft Foundation Class (MFC) applications that may cause applications to flicker.
- Addresses an issue that displays incorrect changes to folder contents.
- Addresses an issue that prevented the Device Guard PackageInspector.exe application from including all the files needed for an application to run correctly once the Code Integrity policy was completed.
- Addresses an issue that prevents users of PIV/CAC smart cards from authenticating to use enterprise resources or prevents Windows Hello for Business from configuring on first logon.
- Addresses an issue that causes Microsoft Edge to stop working after setting a DLL rule in AppLocker.
- Addresses an issue that prevents users from logging on when an Azure Active Directory account domain changes.
- Addresses an issue that causes PowerShell scripts to stop working when attempting operations such as Get-Credentials.
- Addresses an issue that, in some cases, failed to clear decrypted data from memory after a CAPI decryption operation was completed.
- Addresses an issue that causes high CPU usage on machines with built-in Sierra broadband modules when switching from WLAN to LAN. The WWanSvc service continually claims additional memory until the machine becomes unresponsive and a black screen appears.
- Addresses an issue that causes the Wi-Fi EAP-TTLS (CHAP) authentication to fail if a user saves credential information before authentication.
- Addresses an issue that causes a connection failure when the Remote Desktop Service does not read the bypass list for a proxy that has multiple entries.
The patch doesn’t have any known issues which is a good thing for those on Creators Update.
As usual, Genuine Devices connected to Microsoft server will download and install the new patches automatically. However, if you’re keen to install them then you can either head to Microsoft Update Catalog to download the patch or go to Settings>Update and Security>Windows Update and Check for Updates to download and install updates manually.
Download KB4343893 for Windows 10 Build 16299.637 – x86 and x64.
The post Windows 10 Build 16299.637 Version 1709 is now available check whats new ! appeared first on How To Fix Windows.
This post first appeared on How To Fix Windows - Get Solved All Windows 10 Problems, please read the originial post: here
