\n
Microsoft has just released another patch for Windows 10 version 1809, just two days after the release of a first cumulative to support the new Japanese era. If the latter wasn’t available to download via Windows update, the new patch (KB4495667) is and installing it will bump the build number to 17763.475
\n
It’s quite unusual for Microsoft to release two cumulative updates in a single week (especially on a Friday), but the new bits bring quite a long list of fixes, including all those related to the new Japanese era found in the previous patch. You can read all details below:
\n
\n
\n
- Allows the built-in Administrator account to run Microsoft Office setup after downloading the installer in Microsoft Edge.
\n
- Addresses an issue that causes Internet Explorer Automation to fail in certain instances.
\n
- 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.
\n
- Addresses an issue that prevents certain apps from launching when you set folder redirection for the Roaming AppData folder to a network path.
\n
- Addresses an issue in Gdi32full.dll that causes an application to stop responding.
\n
- Addresses an issue that may cause the UI to stop responding for several seconds when scrolling in windows that have many child windows.
\n
- Addresses an issue that may cause a touch screen to stop working after restart.
\n
- Enables a touch keyboard to support new Japanese Era characters. For more information, see KB4469068.
\n
- 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.
\n
- Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.
\n
- Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.
\n
- Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.
\n
- 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.
\n
- Updates fonts to support the new Japanese Era. For more information, see KB4469068.
\n
- Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.
\n
- 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.
\n
- Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.
\n
- Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.
\n
- 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).
\n
- 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.
\n
- Addresses an issue that may allow a user to continue logging on to an account using a smart card after disabling the account.
\n
- 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.
\n
- Addresses an issue that occasionally causes a PostScript printer to use the wrong font.
\n
- 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.
\n
- 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.
\n
- 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.
\n
- 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:
\n”Failed to restart “NODENAME”: (ClusterUpdateException) Failed to restart “NODENAME”: (Win32Exception) The user name or password is incorrect.”\n
- 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.
\n
- 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.
\n
- Addresses an issue that prevents Print Workflow Applications from launching for Point and Print.
\n
- 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.
\n
\n
\n
As a reminder, this new build is an optional update and it comes with a couple of minor issues that will be fixed in an upcoming release. If you opt to skip this new build, be aware that you will still get all these quality fixes in this month’s Patch Tuesday Update, to be released on May 14.
\n\nFurther reading: build 17763.475, cumulative update, Windows 10, Windows 10 October 2018 Update
