A number of significant improvements and fixes are out for Windows 10, v 1809 with the release of KB4541331. Microsoft delivers updates for touch keyboard issues, the wrong appearance of calendar dates, printing to document share and more.
Just like other cumulative updates, KB4541331 for Windows 10, v1809 (OS Build 17763.1131) is not free from issues. Users can grab this patch through Windows Update Settings page. If some prefer manual installation, then the standalone packages are available at Microsoft Update Catalog.
KB4541331 Windows 10 1809 Changelog
Here is the list of enhancements and fixes that KB4541331 contains –
- Microsoft deals with an issue that throws up an error during printing to a document repository.
- Updates a drawing problem with Microsoft Foundation Class (MFC) toolbar. It happens to appear when users attempt to drag a multi-monitor environment.
- Suddenly the touch keyboard appears in the sign-in procedure when a user is providing a password. KB4541331 addresses this issue as well.
- A new child windows flicker and become visible as white squares on server devices. It occurs on the devices that are specially designed for stark visual contrast. However, the team resolves this complication.
- The team provides focus on the issue that incorrectly displays folder properties. When the path is longer than MAX_PATH, this problem is evident.
- In certain devices, calendar dates also appear on the wrong day of the week. This is noticeable in the clock and date region of the notification area. It happens when the user selects the Samoa time zone. Thankfully, Microsoft address this problem with the release of KB4541331.
- Updates for a complication with reading logs using the OpenEventLogA() function is out in this patch.
- Machines that have turned on “Credential Guard” from joining a domain are prevented by a problem. Microsoft addresses the error message “The server’s clock is not synchronized with the primary domain controller’s clock”.
- A slow down up to two minutes occurs when signing in or unlocking a session on Hybrid Azure Active Directory-joined machines. Fortunately, this problem got a fix in this cumulative update.
- Solution to the issue where authentication gets fail when using Azure Active Directory and the user’s security identifier (viz SID) has changed.
- There is a complication that might lead domain controllers (in short DC) to register a lowercase and a mixed or all uppercase Domain Name System (aka DNS) service (SRV) record in the _MSDCS.<forest root domain> DNS zone. KB4541331 deals with this that generally occurs when DC computer names contain one or more uppercase characters.
- An issue gets a solution that leads to authentication in an Azure Active Directory environment to fail without any error.
- Problem of high CPU utilization is apparent when retrieving a session object is over.
- High latency complication in Active Directory Federation Services (AD FS) gets a solution. The response times for all around circulated datacenters in which “SQL” might be on a remote datacenter become high.
- Improvisation is there in the performance for all token requests coming to AD FS, including OAuth, Security Assertion Markup Language (SAML), WS-Federation, and WS-Trust.
- Microsoft resolves another high latency problem that acquires OAuth tokens when AD FS front-end servers and back-end SQL servers are in different datacenters.
- The constructed attribute in Restoration of Active Directory and Active Directory Lightweight Directory Services (AD LDS) for msDS-parentdistname.
- Post-installation of KB4541331, SAML errors and the loss of access to third-party apps for users who do not have multi-factor authentication (aka MFA) enabled will be resolved.
- Evaluating the compatibility status of the Windows ecosystem to help ensure application in addition to device compatibility for all updates to Windows will be resolved.
- An issue that averts Microsoft User Experience Virtualization (UE-V) settings from roaming to enable the signature files that are used for new messages, forwarded messages, and replies is fixed.
- High CPU usage on AD FS servers that occurs when the backgroundCacheRefreshEnabled feature is enabled is taken care of by the team.
- A problem that generates the Storage Replica administrator group with the incorrect SAM-Account-Type and Group-Type respectively gets a solution. This eventually makes the Storage Replica administrator group inoperative when moving the primary domain controller (PDC) emulator.
- Some machines fail to automatically go into Sleep mode under certain circumstances because of Microsoft Defender Advanced Threat Protection (viz ATP) Auto Incident Response (IR). The issue gets a fix in this patch.
- Certain machines are prevented from functioning “Microsoft Defender ATP Threat & Vulnerability Management” successfully. This problem gets a resolution here.
- Enhances support for non-ASCII file paths for Microsoft Defender ATP Auto IR.
- In certain scenarios, a stop error 0xEF occurs while upgrading to Windows 10, v 1809. KB4541331 gets a fix for this also.
- Improvement in the performance of the Resilient File System (viz ReFS). It happens in certain scenarios that involve many operations on ReFS-cloned files.
Post-installation of KB4493509, certain devices with some Asian language packs installed may confront the following error –
"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
- First of all, Reinstall Windows 10 Language Pack that you have added not long ago.
- Navigate to Settings app and click Check for Updates in order to download install the April 2019 Cumulative Update.
Note – In case the reinstallation of the language pack does not resolve the above-mentioned problem, reset the PC by going through these steps –
- Open Windows Settings app and head to Update & Security.
- Choose Recovery subsection.
- Proceeding ahead, conduct a hit on Get Started button. It is visible under the Reset this PC section on the corresponding right pane.
- Select Keep my Files.
For the time being Microsoft is working on a resolution. The team will soon provide an update in the forthcoming release.
How to Get KB4541331
Installation of KB4541331 requires a specific condition for the device to meet. Users need to first successfully install the latest servicing stack update (SSU). This is important to perform because it mitigates the potential issues that might occur during installation of latest cumulative update (viz LCU). Furthermore, it also helps in managing Microsoft fixes.
By navigating to Windows Update settings page, users can grab the patch. To do so,
- Simply fire up Start Menu and click the cog icon to directly access Settings.
- Select Update & Security.
- Click Check for updates on the right pane.
- Wait for the system to download and install. Restart Windows 10 PC to successfully complete the installation process.
As an alternative, users can manually grab the standalone package as well. Just visit Microsoft Update Catalog and download the supportable architecture. Finally, complete the installation procedure manually.
Source – Release Note