KB4469342 for Windows 10 version 1809 released
Microsoft with version 1809 is adopting a very different technique for cumulative updates. In the version, Microsoft releases the update for Insiders in the slow ring or release preview, revises the update at least a couple of times and then ships it to the general public. KB4469342 is no different, which was published 4 times and then eventually released to the general public. Let us see what is new in the update.
What’s new in KB4469342
The list is quite a large one:
- Addresses an issue in Microsoft Edge with using the drag-and-drop feature to upload folders from the Windows desktop to a file hosting service website, such as Microsoft OneDrive. In some scenarios, files contained in the folders fail to upload, with possibly no error reported on the web page to the user.
- Addresses an issue that degrades Internet Explorer performance when you use roaming profiles or you don’t use the Microsoft Compatibility List.
- Addresses updated time zone information for Fiji.
- Addresses time zone changes for Moroccan daylight standard time.
- Addresses time zone changes for Russian daylight standard time.
- Addresses an issue that causes display settings to stop working when changing a multi-monitor configuration.
- Addresses an issue that displays a black screen on some servers when waking a display from sleep.
- Addresses an issue with long delays in taking a photo when using the Camera app in certain lighting conditions.
- Addresses an issue that prevents live TV Hulu content from playing in Microsoft Edge; instead, a black screen appears.
- Addresses an issue that stops Bluetooth® headsets from receiving audio input after several minutes of listening.
- Addresses an issue that causes the Brightness slider preference to be reset to 50% when the device restarts.
- Addresses an issue with the OEM manufacturing processes when running sysprep /generalize.
- Addresses an issue with Microsoft Intune that causes devices to be incorrectly marked as not compliant because a firewall incorrectly returns a ‘Poor’ status. As a result, the affected devices will not receive conditional access compliance approval and may be blocked from access to corporate resources such as email.
- Addresses a performance issue with vSwitch on network interface cards (NIC) that do not support Large Send Offload (LSO) and Checksum Offload (CSO).
- Updates the Wi-Fi policy for service set identifier (SSID) filtering to avoid filtering out Wi-Fi Direct devices.
- Addresses an issue that causes rasman.exe to stop responding.
- Addresses an issue in which regedit.exe fails to add double null terminator to REG_MULTI_SZ values in the Windows registry. The missing terminator may prevent services and applications from reading REG_MULTI_SZ values that regedit.exe adds after installing the operating system.
- Addresses an issue with RemoteApp visibility that may cause the main window to disappear until the user clicks the screen.
- Addresses an issue that prevents some users from setting Win32 program defaults for certain app and file type combinations using the Open with… command or Settings > Apps > Default apps.
- Addresses an issue that may cause mapped drives to fail to reconnect after starting and logging onto a Windows device.
Known issues in KB4469342
There are two known issues with KB4468342 which are:
|After installing this update, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.||Microsoft is working on a resolution and estimates a solution will be available mid-December 2018.|
|nVidia has notified Microsoft of an issue where Microsoft Edge may crash or hang while playing video. This issue occurs following an nVidia driver update.||nVidia has released an updated driver to address this issue. Please follow the instructions found in nVidia’s support article.|
More information about this update can be found here.
To download KB4469342, please run Windows updates or use the direct download links from below:
If you run into any issues with the KB4469342, let us know in comments…