New
#1
Again a very fast cumulative update , brought me to build 191.........
July 24, 2018 - KB4340917 (OS Build 17134.191)
Applies to: Windows 10, version 1803
Improvements and fixes
This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:
- Addresses an issue that causes devices within Active Directory or Hybrid AADJ++ domains to unexpectedly unenroll from Microsoft Intune or third-party MDM services after installing provisioning package updates (PPKG). This issue occurs on devices that are subject to the Auto MDM Enrollment with AAD Token Group Policy. If you ran the script Disable-AutoEnrollMDMCSE.PS1 as a workaround for this issue, run Enable-AutoEnrollMDMCSE.PS1 from a PowerShell window in Administrator mode after installing this update.
- Addresses additional issues with updated time zone information.
- Improves the ability of the Universal CRT Ctype family of functions to handle EOF as valid input.
- Addresses an issue with registration in the "Push to Install" service.
- Addresses an issue with Roaming User Profiles where the AppData\Local and AppData\Locallow folders are incorrectly synchronized at user logon and logoff. For more information, see KB4340390.
- Addresses issues related to peripherals that use Quality of Service (QoS) parameters for Bluetooth connections.
- Addresses an issue that causes SQL Server memory usage to grow over time when encrypting data using a symmetric key that has a certificate. Then, you execute queries that open and close the symmetric key in a recursive loop.
- Addresses an issue where using an invalid password in a wireless PEAP environment that has SSO enabled submits two authentication requests with the invalid password. The excess authentication request may cause premature account lockouts in environments with low account lockout thresholds. To enable the changes, add the new registry key DisableAuthRetry (Dword) on HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\26 using regedit, and set it to 1.
- Addresses an issue that prevents OpenType fonts from printing in Win32 applications.
- Addresses an issue with DNS Response Rate Limiting that causes a memory leak when enabled with LogOnly mode.
- Addresses an issue in a RemoteApp session that may result in a black screen when maximizing an app window on a secondary monitor.
- Addresses an issue in IME that causes unexpected finalization of strings during Japanese input in applications such as Microsoft Outlook.
If you installed earlier updates, only the new fixes in this package will be downloaded and installed on your device.
Known issues in this update
Symptom Workaround After you install any of the July 2018 .NET Framework Security Updates, a COM component fails to load because of “access denied,” “class not registered,” or “internal failure occurred for unknown reasons” errors. The most common failure signature is the following:
Exception type: System.UnauthorizedAccessException
Message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))For more information, see KB4345913.
Microsoft is working on a resolution and will provide an update in an upcoming release.
How to get this update
To download and install this update, go to Settings > Update & Security > Windows Update and select Check for updates.
To get the standalone package for this update, go to the Microsoft Update Catalog website.
File information
For a list of the files that are provided in this update, download the file information for cumulative update 4340917.
Source: https://support.microsoft.com/en-us/...date-kb4340917
Direct download links for KB4340917 MSU file from Microsoft Update Catalog:
Download KB4340917 MSU for Windows 10 v1803 32-bit (x86) - 397.9 MB
Download KB4340917 MSU for Windows 10 v1803 64-bit (x64) - 713.1 MB
Again a very fast cumulative update , brought me to build 191.........
Another one already? This is crazy. Downloading it now from WU.
Installing now. Zipped through the (first PC's) prep phase. But sat at 100% on "Preparing to download" for about a minute before the download began. Download also pretty quick, will probably be under a minute as well. Firing up the other PCs now...
--Ed--
PS: Installation took under 2 minutes to complete. Expect to be restarting shortly. AND done before my lunch break officially ends on the hour here...
As I saw for the 17134.165 CU
...the first PC to check for updates was sending as much data through the Wi-Fi as it was receiving, while the second was only receiving. It seems this 'download updates from other PCs on your network' actually works.
Edit: both went smoothly. Even the one that went BSOD when it first tried updating to .167
Yep, it’s getting to be a bit of a joke. Looking at the list of ‘improvements’ they mean very little to me or Joe Public. I’m all updated and installed ok but surely MS must realise the frequency of these is a bit much. No average user wants to be constantly updating their machines. Stick to 2nd Tuesday and only issue very very urgent updates out of band. Then everyone knows where they stand. I suppose on the plus side cumulative updates do seem much much quicker these days.
Just update to .191 in about 10 minutes. Two other systems in the office waiting on the update. No Issues.
WEK