Windows 10 update settings

Windows 10 update KB4541331 (build 17763.1131) releases for version 1809

Microsoft pushes update KB4541331 to fix a bunch of problems with PCs running Windows 10 version 1809, and here's all you need to know.

Outside of the regular schedule, Microsoft is now rolling out update KB4541331 to address a slew of issues with Windows 10 version 1809 (October 2018 Update).

KB4541331 bumps the version number to build 17763.1131, and according to the company fixes error when printing to a document share, touch keyboard during sign in, date and time settings, and improves app and devices compatibility with Windows updates.

In addition, older versions of Windows 10, including version 1803, 1709, and 1607 also received several fixes.

Update KB4541331 for Windows 10 version 1809

Microsoft has announced KB4541331 in the Windows support site, and it’s referred as “March 17, 2020—KB4541331 (OS Build 17763.1131).” If you’re already running the Windows 10 October 2019 Update on your device, this update will address these issues:

  • Addresses an issue that causes an error when printing to a document repository.
  • Addresses a drawing issue with the Microsoft Foundation Class (MFC) toolbar that occurs when dragging in a multi-monitor environment.
  • Fixes a problem that prevents the touch keyboard from appearing during sign in when the user is prompted for the password.
  • Addresses an issue that causes new child windows to flicker and appear as white squares on server devices that are configured for stark visual contrast.
  • Fixes a problem that displays incorrect folder properties in File Explorer when the path is longer than MAX_PATH.
  • Addresses an issue that causes calendar dates to appear on the wrong day of the week in the clock and date region of the notification area when you select the Samoa time zone.
  • Fixes a problem with reading logs using the OpenEventLogA() function.
  • Addresses an issue that prevents machines that have enabled Credential Guard from joining a domain. The error message is “The server’s clock is not synchronized with the primary domain controller’s clock.”
  • Fixes a problem that might cause a delay of up to two minutes when signing in or unlocking a session on Hybrid Azure Active Directory-joined machines.
  • Addresses an issue that causes authentication to fail when using Azure Active Directory and the user’s security identifier (SID) has changed.
  • Fixes a problem that might cause domain controllers (DC) to register a lowercase and a mixed or all uppercase Domain Name System (DNS) service (SRV) record in the _MSDCS.<forest root domain> DNS zone. 
  • Addresses an issue that causes authentication in an Azure Active Directory environment to fail and no error appears.
  • Fixes a problem that causes high CPU utilization when retrieving a session object.
  • Addresses high latency in Active Directory Federation Services (AD FS) response times for globally distributed datacenters in which SQL might be on a remote datacenter.
  • Addresses a high latency issue in acquiring OAuth tokens when AD FS front-end servers and back-end SQL servers are in different datacenters.
  • Addresses an issue to prevent SAML errors and the loss of access to third-party apps for users who do not have multi-factor authentication (MFA) enabled.
  • Fixes a problem with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  • Addresses an issue that prevents Microsoft User Experience Virtualization (UE-V) settings from roaming to enable the signature files that are used for new messages, forwarded messages, and replies.
  • Fixes a problem with high CPU usage on AD FS servers that occurs when the backgroundCacheRefreshEnabled feature is enabled. 
  • Addresses an issue that creates the Storage Replica administrator group with the incorrect SAM-Account-Type and Group-Type. 
  • Fixes a problem that prevents some machines from automatically going into Sleep mode under certain circumstances because of Microsoft Defender Advanced Threat Protection (ATP) Auto Incident Response (IR).
  • Addresses an issue that prevents some machines from running Microsoft Defender ATP Threat & Vulnerability Management successfully.
  • Fixes a problem that, in some scenarios, causes stop error 0xEF while upgrading to Windows 10, version 1809.
  • Improves support for non-ASCII file paths for Microsoft Defender ATP Auto IR.
  • Improves the performance for all token requests coming to AD FS, including OAuth, Security Assertion Markup Language (SAML), WS-Federation, and WS-Trust.
  • Restores the constructed attribute in Active Directory and Active Directory Lightweight Directory Services (AD LDS) for msDS-parentdistname.

You can download the updates to install them manually for version 1809 with the links below:

Update for older versions of Windows 10

The April 2018 Update, version 1803, has reached the end of support on November 12, 2019, but the company has released update KB4541333 to fix several problems while bumping the version number to build 17134.1399.

Although version 1709 (Fall Creators Update) is no longer supported, organizations running the Enterprise or Education edition of Windows 10 are getting update KB4541330 to address a security problem and bumps the version number to 16299.1775.

Also, the Windows 10 Anniversary Update, version 1607, is getting update KB4541329 to address some issues with the no longer supported operating system bumping the version number to build 14393.3595.

Uninstall update KB4541331 from Windows 10

If the KB4541331 update is causing issues on your device, you can always uninstall it to revert the changes.

To uninstall KB4541331 or any other quality update on Windows 10, use these steps:

  1. Open Start.

  2. Search for Command Prompt and click the top result to open the app.

  3. Type the following command to view the update history and press Enter:

    wmic qfe list brief /format:table
  4. Check the Windows Update history of your device, and identify the update by its HotFixID and InstalledOn information.

  5. Type the following command to uninstall the update from your computer and press Enter:

    wusa /uninstall /kb:4541331

    In the command, replace “4541331” for KB number that correspond to the update that you’re trying to remove. For instance, if you’re trying to uninstall update KB4541331, then the number that you can have to use in the command is “4541331.”

  6. Click the Yes button.

  7. Continue with the on-screen directions (if applicable).

Once you complete the steps, the recently installed update will be removed from your computer fixing any issues as a result of the release.

Download March 2020 update for Windows 10

These updates are available immediately, they’ll download and install automatically, but you can always force the update from Settings > Update & Security > Windows Update and clicking the Check for updates button. You can find more details about the most recent updates in the Windows 10 update history tracker guide.

About the author

Mauro Huculak is a Windows How-To Expert who started Pureinfotech in 2010 as an independent online publication. He has also been a Windows Central contributor for nearly a decade. Mauro has over 14 years of experience writing comprehensive guides and creating professional videos about Windows and software, including Android and Linux. Before becoming a technology writer, he was an IT administrator for seven years. In total, Mauro has over 20 years of combined experience in technology. Throughout his career, he achieved different professional certifications from Microsoft (MSCA), Cisco (CCNP), VMware (VCP), and CompTIA (A+ and Network+), and he has been recognized as a Microsoft MVP for many years. You can follow him on X (Twitter), YouTube, LinkedIn and Email him at [email protected].