KB4340917 update released for Windows 10 version 1803
Microsoft released KB4340917 for Windows 10 version 1803, the April 2018 Update, which brings the version of the operating system to 17134.191 after installation.
It is the second update that Microsoft released for the latest stable version of Windows 10 version 1803 after last week's release of KB4345421 which addressed several issues introduced by the July 2018 Patch Day.
Up until today, only Windows 10 version 1803 received a second cumulative update after Patch Tuesday this month. It is possible that updates for previous versions of Windows 10 will be provided by Microsoft eventually.
KB4340917
KB4340917 contains the following fixes and improvements according to the release notes:
- Fixed an issue with OpenType fonts that would not print in Win32 applications.
- Fixed a memory leak with DNS Response Rate Limiting in LogOnly mode.
- Addressed Remote App session issue that resulted in black screens when maximizing application windows on a secondary monitor.
- Addressed an IME issue with Japanese input in applications such as Microsoft Outlook.
- Addressed Quality of Service QOS parameters for Bluetooth connections related to peripherals.
- Fixed a SQL Server memory leak that would see memory usage grow over time when encrypting data using a symmetric key that has a certificate.
- Fixed an authentication issue in wireless PEAP environments with SSO that would send two authentication requests instead of just one; this could result in premature accuont lockouts. To enable the changes, admins need to create the Dword value DisableAuthRetry with the value of 1 on HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\26
- Fixed a roaming user profiles issue that caused the AppData\Local and AppData\Locallow folders to synchronize incorrectly during logon and logoff.
- Addressed a Push to Install service registration issue.
- Universal CRT Ctype family of functions improvements in regards to handling EOF as valid input.
- Fixed additional time zone information issues.
- 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.
KB4340917 is available through Windows Update on systems with automatic update functionality enabled. You can run a manual check for updates to have it picked up immediately by pressing Windows-I, opening Updates & Security, and
The update is also available for direct download on the Microsoft Update Catalog website.
Now You: What is your experience with the new update?
Spectre Microsoft patch KB4100347 is updated.
http://www.catalog.update.microsoft.com/search.aspx?q=4100347
Has this update fixed device census error? (https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/device-census-stopped-working-problem/ff471d48-c12e-4b9e-b0a3-8a2749b73300?page=2)
It looks like the Microsoft Edge’s hub has regained its small width.
Thanks, Martin, So I could early in the morning upgrade before I really do something, main window 10, to the version 1803 build 17134.191.
Personly I am convinced true experience that when I upgrade/update after a restart or fresh booting up of the system any update/upgrade goes (even much) smoother (with downloading and implementing) and faster (shutting down and starting up again)?
And I also experienced over the years that this is even more evident visibly noticeable so when then doing any update/upgrade whit a fresh upstarted system that even more important to me almost never ever the system rejects any upgrade/upgrade?
Do you (Or anybody else) have that same experience?
I agree with your technique essentially. I exit almost all apps and wait a minute or two for CPU usage to go to about 1%. Then I manually initiate a Windows Update. Works well for me. I like to observe the update process while I am there, rather than waking up to a surprise that may be hard to figure out.
This seems to be a good option as other programs won’t interfere with the updating. So, rebooting before you install updates may be a good option if you run into issues otherwise or notice a speed up.
With this update I especially like the “Installing updates 22% Don’t turn off the computer” – screen that now hasn’t moved for 2+ hours. Is this a new feature? Even though it’s very sexy, informative, calm and soothing, I need my computer for other things. Writing this on my KDE Neon laptop that just got a gazillion updates and installed them in roughly 30 seconds. Luckily I have backup computers that actually function flawlessly. Thank you Redmond, again, you never fail at failing! Impressive.
“Is this a new feature?”
I don’t think so — I’ve been seeing this feature fairly often for a while now.
Twelve hours ago using Windows Update, my CPU caused KB4100347 to be installed as well as KB4340917. After restart, I left the PC running without interruption from me, as System Explorer showed a varied but high CPU usage for 15 or so minutes. Both updates went OK.
https://support.microsoft.com/en-us/help/4100347/intel-microcode-updates-for-windows-10-version-1803-and-windows-server
which is less stable, Windows 10 or Windows millennium edition? LOL
Has this build fixed device census errors?
https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/ever-since-kb4284835-june-cumulative-windows-10/8f931366-a479-4d22-a578-bd5675241e00
What matters is Windows users continue to think when an update is pushed by MS, they need to install it rather than delay it. Apparently, they still haven’t learned it’s okay to wait two weeks or even one month for nearly all updates–including security updates.
With a couple of other programs for security running on computers, it’s all going to be okay. No need to rush, or if that’s the choice, stop complaining bitterly.
KB4340917 update for 1803 still has one known issue listed:
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))
I would not be surprised if another new cumulative update for 1803 comes on July 31 (5th Tuesday).