Update KB4505658 for Windows 10 version 1809 is out
Microsoft released the long-awaited KB4505658 update for Windows 10 version 1809 on July 22, 2019. The update is the second cumulative update for the month following KB4507466 and KB4507465 for Windows 10 version 1803 and 1709 which were released on July 16, 2019 following the release of the security updates for July 2019 a week earlier.
The second cumulative update for Windows 10 version 1903, the current version of the Windows 10 operating system, is still missing.
KB4505658 addresses numerous issues in Windows 10 version 1809.
Note: We suggest that you install the update only if you are affected by one of the issues and need to fix it asap. Updates may introduce other issues and it is recommended to wait to avoid being hit by those. If you do need to install it, make sure you create a backup before you proceed. Check out the free Backup & Recovery if you are not sure which backup program to use for that operation.
KB4505658 for Windows 10 version 1809
KB4505658 is already available on Windows Update. A click on the check for updates button returns the new update on systems that use Windows Update. It is not available on business and Enterprise updating solutions, but can be downloaded as a standalone update package from the Microsoft Update Catalog website.
KB4505658 addresses the following issues:
- Fixes a performance issue on some sites that use WebAssembly.
- Fixed an issue that caused IE to stop working when dragging tabs to create new browser windows.
- Fixed an issue that prevented the PIN prompt from appearing in Internet Explorer when authenticating.
- Fixed a Windows Notifications system issue that caused "nonsense" characters to be displayed instead of single quotes.
- Fixed a Windows Search issue that caused newly installed or updated applications from not being returned.
- Fixed an Office 2010 issue that caused Save and Save As from not working on systems with high contrast mode.
- Fixed a migration issue that caused SharedPC policies from being migrated properly.
- Fixed an issue that caused Hardware Support applications from "installing in a timely manner".
- Fixed a Windows Log issue that prevented the processing of notifications if the log was full.
- Fixed a Microsoft Account or Azure Active Directory account recognizing issue until the user signed out and on again.
- Fixed the Netlogon service error "0xC000007A – ERROR_PROC_NOT_FOUND."
- Fixed a Windows Hello for Business authentication issue on Windows Server 2016 with Server Core installed.
- Fixed an issue that caused some Windows Server containers or Hyper-V containers to have empty names.
- Fixed an input and output issue when Multipath I/O (MPIO) failover occurs.
- Fixed the error ExceptionCode c0000005 (Access violation) related to windows.storage.dll.
- Reinforced the Certificate Revocation List on Internet Key Exchange Version 2 machines for VPN connections.
- Fixed error "ERROR_PORT_NOT_AVAILABLE(633)" when using Always On VPN with the IKEv2 protocol.
- Fixed an issue that changed the status of Work Folders in File Explorer to 0x80C802A0 (ECS_E_SYNC_UPLOAD_PLACEHOLDER_FAILURE)Â after selecting Free up space.
- Fixed a Remote Desktop Server connection issue caused by a user using drive reconnects disconnecting.
- Fixed an error caused when "certain data persistence memory technologies" were used.
- Addressed an issue that caused Microsoft Application Virtualization scripting from working.
- Addressed an issue that damaged the Microsoft Message Queuing feature and prevented it from recovering or restarting.
- Fixed an issue with the Windows-Eyes screen reader application that prevented some features from working as expected.
- Fixed an issue that prevented certain permissions from being kept when selecting "keep my files" after using Reset this PC.
- Fixed a system reliability issue when upgrading from Windows 10 version 1703.
- Fixed an enrolling in Windows Enterprise commercial data pipeline issue.
- Time Zone information update for Brazil
Microsoft lists four existing known issues on the support page. The update fixed the Windows-Eyes known issue but the following four issues are still not fixed:
- Certain operations may fail on Cluster Shared Volumes.
- Devices with "some Asian language packs installed" may get the error "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND".
- Devices may boot into a black screen on first boot after installing the update.
- Devices that use Preboot Execution Environment images may receive the "Status: 0xc0000001, Info: A required device isn't connected or can't be accessed" error.
Now You: When do you install available updates? Any experience with this one?
There is a new servicing stack update too, KB4512937, which is a prerequisite for this update. I do not understand why they don’t include the latest SSU (13 MiB) in the main package (261 MiB).
Fixing so many things for 1809 while 1903 is still stopped somewhere over the rainbow for my laptop. And then, all these fixed issues and problems will become nothing relevant at all because version 1903 will have its own bugs and issues as well. And go on, and go on, in one neverending race to nowhere. I can’t understand this amazing way of wasting time for free, seriously.
My last update was 1803. I will not update again unless there is some seriously critical issue that comes up and gets addressed. There was too much work involved to get everything back to working correctly. I just don’t trust Microsoft anymore – they play too many games and want to turn Windows and all of their products into data-mining apps.
These are the most amazing errors and updates of all. I still expect them to one day just declare Windows unfixable.
From version 1809 the registry setting “HibernateEnabled” was renamed “HibernateEnabledDefault”. If you use cmd (powercfg.exe /hibernate off), it is created in addition to the “HibernateEnabledDefault” parameter “HibernateEnabled” with all of the control circuits of the supply. As a result, we have a conflict that can lead to incorrect shutdown of the PC. I had so – at shutdown of the PC it rebooted and only after the second shutdown, switched off normally.
unrelated to this but Microsoft has just released the KB4505903 cumulative update for v1903 on 7/26, along with a new KB4508433 SSU for 1903
First attempt hosed Ethernet connection. Had to revert.