While Microsoft released a cumulative update for Windows 10 version 1809 just two days ago, another one is being released today. As usual, it's an optional update with a long list of fixes. If you choose not to take it, these fixes will be included in the mandatory Patch Tuesday update.
The update is KB4495667, and it brings the build number to 17763.475. You can manually download it here, and it contains the following fixes:
Allows the built-in Administrator account to run Microsoft Office setup after downloading the installer in Microsoft Edge.
Addresses an issue that causes Internet Explorer Automation to fail in certain instances.
Addresses an issue that may prevent Custom URI Schemes for Application Protocol handlers from starting the corresponding application for local intranet and trusted sites on Internet Explorer.
Addresses an issue that prevents certain apps from launching when you set folder redirection for the Roaming AppData folder to a network path.
Addresses an issue in Gdi32full.dll that causes an application to stop responding.
Addresses an issue that may cause the UI to stop responding for several seconds when scrolling in windows that have many child windows.
Addresses an issue that may cause a touch screen to stop working after restart.
Enables a touch keyboard to support new Japanese Era characters. For more information, see KB4469068.
Addresses an issue that causes ShellExperienceHost.exe to stop working when the start date for the Japanese Era is not on the first day of the month. For more information, see KB4469068.
Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.
Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.
Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.
Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era. For more information, see KB4469068.
Updates fonts to support the new Japanese Era. For more information, see KB4469068.
Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.
Addresses an issue that causes the Clock and Calendar flyout control to display the day of the week incorrectly mapped to a date in the month of the new Japanese Era. For more information, see KB4469068.
Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.
Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.
Allows existing devices that are managed by Configuration Manager to be enrolled in Microsoft Intune using Co-management without any user interaction. It does not require an active user to be logged in, and there are no Multi Factor Authentication (MFA) prompts. This update also allows the Co-managed mobile device management (MDM) enrollment to use the device credential it received when the device is enabled to join Hybrid Azure Active Directory (AADJ).
Improves access to detailed troubleshooting and diagnostic logs from managed devices, such as business PCs, when using a PC cloud management service. PC cloud management services include Microsoft Intune or other Mobile Device Management (MDM) providers for Windows.
Addresses an issue that may allow a user to continue logging on to an account using a smart card after disabling the account.
Addresses an issue that prevents access to enterprise resources when using Kerberos with Windows Hello for Business (WHfB) credentials. This causes users to receive multiple prompts to provide their credentials.
Addresses an issue that occasionally causes a PostScript printer to use the wrong font.
Addresses an issue that causes Lightweight Directory Access Protocol (LDAP) client applications to stop responding for at least 30 seconds when many LDAP queries are requested through multiple connections. This occurs because of a race condition in wldap32.dll. You must install this update on the LDAP client that calls wldap32.dll.
Addresses an issue that causes a roaming profile user to lose customized Start menu settings after upgrading the operating system (OS). After installing this update, administrators must enable the UseProfilePathMinorExtensionVersion registry setting described in KB4493782 for roaming user profiles (RUP). This key allows you to create a new RUP for an upgraded OS and prevents the loss of a custom Start menu. The RUP must be stored locally, and you must restart the device to enable the feature.
Addresses an issue that causes connection requests to the Remote Desktop Session Host (RDSH) servers in the deployment to fail. This issue occurs because of a deadlock in the Connection Broker.
Addresses an issue that may prevent Cluster Aware Update from restarting nodes when a cluster's credentials are reset. Cluster Aware Update must restart nodes after installing an update. The error is the following:
”Failed to restart "NODENAME": (ClusterUpdateException) Failed to restart "NODENAME": (Win32Exception) The user name or password is incorrect.”
Addresses a gradual memory leak in LSASS.exe on systems that have cached logon enabled. This issue mainly affects servers that process many interactive logon requests, such as web servers.
Addresses an issue that may cause a Lightweight Directory Access Protocol (LDAP) query to return incorrect results. This occurs if a filter clause contains an attribute that has a syntax of Large Integer type and the filter uses the rule, LDAP_MATCHING_RULE_BIT_AND. For example, a simple filter, such as “msExchRoleAssignmentFlags:1.2.840.113556.1.4.803:=51539607552” may return no matches when it should.
Addresses an issue that prevents Print Workflow Applications from launching for Point and Print.
Addresses an issue that may prevent Universal Windows Platform (UWP) apps from receiving keyboard input when its user interface thread becomes too busy. This issue occurs when the UWP app has an embedded WebView control.
There are also a bunch of known issues to be aware of:
| Symptom |
Workaround |
|---|---|
| After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension. |
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2:
Option 3: “HKLM\System\CurrentControlSet\Services\WDSServer\ Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release. |
| Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. |
Do one of the following:
|
| Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update. |
Microsoft has temporarily blocked devices from receiving this update if ArcaBit antivirus softwareis installed. ArcaBit has released an update to address this issue. For more information, see the Arcabit support article. |
| Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing this update. | Microsoft is working on a resolution and will provide an update in an upcoming release. |
| When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e." |
You can use another browser, such as Internet Explorer to print your documents. Microsoft is working on a resolution and will provide an update in an upcoming release. |
| After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND." |
Microsoft is working on a resolution and will provide an update in an upcoming release. |
Unlike the update that was made available earlier this week, this one is actually available through Windows Update. All you have to do is check for updates, as it won't install automatically.
4 Comments - Add comment