Microsoft rolls KB4512941 cumulative update for Windows 10 19H1 users that, in turn, enhances the OS to build 18362.329. This is a non-security patch as contrary to KB4512508 that came on 13th Aug 2019. There are tons of new features and fixes introduced in this cumulative update. Besides, here is the complete catalog of Windows 10 cumulative updates.
The company addresses the remote desktop black screen, Windows Defender ATP, Universal WP apps, and several other bugs. KB4512941 improves the LdapPermissiveModify requests along with user experience and application compatibility on 19H1 OS. Let’s explore this patch update in somewhat more detail-
General Fixes and Improvements on KB4512941 19H1
Here are the key advancements that came along with this patch update for Windows 10 1903 users-
- KB4512941 resolves the black screen issue which occurs primarily when you use a Remote Desktop to connect with your 19H1 PC.
- Build 18362.329 addresses a bug that restricts Windows Sandbox from starting and rather pops the “ERROR_FILE_NOT_FOUND (0x80070002)”. This trouble appears when users change the default language while upgrading their 19H1 OS.
- They increase the total number of supported interrupts per device to 512. This is applicable to only those devices that have inbuilt x2APIC support.
- Works upon an anomaly that stops some Trusted Platform Module Machines from being accessed for the Next Generation credentials.
- Earlier when you sign in to use an updated principal name, a bug erupts the workstation thus restricting the access. For instance –
- changing UserN@contoso.com to User.Name@contoso.com
- KB4512941 addresses a bug that prevents Windows Defender Advanced Threat Protection (ATP) from running automated forensic data collection. This trouble arises while using a registry-based proxy configuration. They have fixed this issue on this build.
- The Company even modifies some configurations on Windows Defender ATP. This is why it won’t send any cyberspace events for paths beginning with \\tsclient.
- They resolve the compatibility issues of Windows Defender ATP. Hence, this can now access case-sensitive Server Messages Block i.e. SMB shares.
- The team resolves a bug that let mssecflt.sys consumes huge space on the kernel stack. As a result, there used to appear following error message-
- “STOP 0x7F: UNEXPECTED_KERNEL_MODE_TRAP”, where Parameter 1 is set to “EXCEPTION_DOUBLE_FAULT.”
- With Build 18362.329 onward, Windows Defender ATP won’t utilize excessive memory.
- The experts improve the detection accuracy of Microsoft Defender ATP threat as well as Vulnerability Management.
- KB4512941 patches an issue in which one can’t load third-party binaries from Universal WP apps. This restriction is applicable as long as Windows Defender is turned ON. In addition to this, there appears an event error 3033 which reads-
- “Code Integrity determined that a process (<process name>) attempted to load <binary name> that did not meet the Store signing level requirements.”
- The Company works upon a bug that leads some devices to have truncated names. This happens only when Autopilot provisioning assigns a name to them automatically.
- They address an anomaly that depicts the wrong product description of Windows Server 2019 when enquired using slmgr/dlv.
- Earlier, Windows Management Instrumentation (WMI) class Win32_PhysicalMemory reports an error. This reads “32 GB memory chips have a missing Capacity value”. Microsoft has worked on this issue.
- Windows 10 19H1 users can now easily copy or paste compound documents (previously OLE objects) between apps and host files. There is one necessity though, application, in concern, must support RichEdit control and other applications.
- Improves a bug that causes certain games leveraging Spatial Audio capabilities.
- Resolves an issue that fails to provide a cursor. This trouble arises primarily when you choose a text input element using the touchscreen.
- Improves an issue that may cause the following functionalities to stop responding-
- Apps that were developed in Visual Basic 6 (VB6).
- Macros that use Visual Basic for Applications (VBA).
- Scripts or apps that use Visual Basic Scripting Edition (VBScript).
Some Other Fixes
Addresses an issue that may cause the name of an unsupported application to appear as default text, such as “ms-resource:AppName/Text” in the Start menu after upgrading the operating system.
Addresses an issue that may prevent the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer.
Resolves an issue with downloading digital rights management (DRM) files from certain websites using Microsoft Edge and Internet Explorer.
Improves the user experience and app compatibility so that more Win32 apps will work with Windows Mixed Reality.
Addresses an issue with LdapPermissiveModify requests, which fail to make Active Directory (AD) group membership changes if the Lightweight Directory Access Protocol (LDAP) client uses the Security Identifier (SID) syntax. In this scenario, Active Directory returns a “SUCCESS” status even though the change did not occur.
Works upon an issue that may prevent devices from starting when they start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM). The error is, “Status: 0xc0000001, Info: A required device isn’t connected or can’t be accessed.”
Addresses an issue that may prevent devices from starting up or cause them to continue restarting if they are connected to a domain that is configured to use MIT Kerberos realms. This affects both domain controllers as well as domain members.
Windows 10 19H1 users may receive an “Invalid procedure call” error after updating to this patch update.
Known Issues on KB4512941 19H1
As per the company, there are no known issues on this cumulative update.
How to get this update
Before trying this cumulative update, make sure to download and install the latest servicing stack on your device. Microsoft releases SSU KB4515530 as the recent update for KB4512941. You will auto-receive a popup message regarding the same. If you don’t want to wait, go to this page to download this file manually.
You may download the patch update from Windows Update, Microsoft Update Catalog, and Windows Server Update Services too. You may visit the Update Catalog to download the .msi file from its official website.
Source – Update Catalog