New
#1
also KB4511555 Cumulative Update for .NET Framework 3.5, 4.8 for Windows 10, version 1903 released.
Cumulative Update KB4511555 .NET Framework 3.5, 4.8 Windows 10 Aug. 30
UPDATE 9/10: Cumulative Update KB4515384 Windows 10 v1903 build 18362.356 Sept. 10
August 30, 2019 - KB4512941 (OS Build 18362.329)
Applies to: Windows 10 version 1903, Windows Server version 1903
Note Follow @WindowsUpdate to find out when new content is published to the release information dashboard.
For more information about the various types of Windows updates, such as critical, security, driver, service packs, and so on, please see the following article.
ePub support ending in Microsoft Edge
Microsoft Edge will end support for e-books that use the .epub file extension over the next several months. For more information, see Download an ePub app to keep reading e-books.
Highlights
- Updates an issue that prevents certain games from leveraging Spatial Audio capabilities.
- Updates an issue that fails to provide a cursor when you select a text input box using touch.
- Updates 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.
- Updates an issue with downloading copyrighted digital media (music, TV shows, movies, and so on) 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.
- [ADDED 9/6] Updates an issue that causes excessive CPU usage when users switch applications or hover over the Taskbar.
Improvements and fixes
This non-security update includes quality improvements. Key changes include:
- Addresses an issue that displays a black screen when you use Remote Desktop to connect to a machine running Windows 10, version 1903.
- Addresses an issue that may prevent the Windows Sandbox from starting with the error, "ERROR_FILE_NOT_FOUND (0x80070002)." This occurs on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.
- Increases the number of supported interrupts per device to 512 on systems that have x2APIC enabled.
- Addresses an issue that prevents some Trusted Platform Module (TPM) devices from being used for Next Generation Credentials.
- Addresses an issue that causes a workstation to stop working when you sign in using an updated user principal name (UPN) (for example, changing UserN@contoso.com to User.Name@contoso.com).
- Addresses an issue that prevents Windows Defender Advanced Threat Protection (ATP) from running automated forensic data collection when using registry-based proxy configuration.
- Addresses an issue that prevents Windows Defender Advanced Threat Protection (ATP) from sending cyberspace events for paths beginning with \\tsclient.
- Addresses a possible compatibility issue when Windows Defender Advanced Threat Protection (ATP) accesses case-sensitive Server Message Block (SMB) shares.
- Addresses a rare issue that occurs when the mssecflt.sys driver takes too much space on the kernel stack. This results in the error, "STOP 0x7F: UNEXPECTED_KERNEL_MODE_TRAP", and Parameter 1 is set to “EXCEPTION_DOUBLE_FAULT.”
- Addresses an issue that leads to excessive memory utilization in Windows Defender Advanced Threat Protection (ATP).
- Improves the detection accuracy of Microsoft Defender ATP Threat & Vulnerability Management.
- Addresses an issue in which Windows Defender Application Control will not allow third-party binaries to be loaded from a Universal Windows Platform application. CodeIntegrity event error 3033 appears as, “Code Integrity determined that a process (<process name>) attempted to load <binary name> that did not meet the Store signing level requirements.”
- Addresses an issue that causes devices to have truncated device names when Autopilot provisioning automatically assigns a name to them.
- Addresses an issue in which the product description of Windows Server 2019 was incorrect when queried using slmgr /dlv.
- Addresses an issue that causes the Windows Management Instrumentation (WMI) class Win32_PhysicalMemory to report that 32 GB memory chips have a missing Capacity value.
- Addresses an issue that prevents you from copying and pasting compound documents (formerly OLE objects) between an application that hosts the RichEdit control and other applications.
- Addresses an issue that prevents certain games from leveraging Spatial Audio capabilities.
- Addresses an issue that fails to provide a cursor when you select a text input element using touch.
- 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.
- Addresses 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.
- Addresses 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. Domain controllers and domain members are both affected.
- Addresses an issue that may cause the following to stop responding:
- Applications that were made using Visual Basic 6 (VB6).
- Macros that use Visual Basic for Applications (VBA).
- Scripts or apps that use Visual Basic Scripting Edition (VBScript).
- [ADDED 9/6] Addresses an issue that causes excessive central processing unit (CPU) usage when users switch applications or hover over the Taskbar.
You may also receive an "Invalid procedure call” error.
If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.
Windows Update Improvements
Microsoft has released an update directly to the Windows Update client to improve reliability. Any device running Windows 10 configured to receive updates automatically from Windows Update, including Enterprise and Pro editions, will be offered the latest Windows 10 feature update based on device compatibility and Windows Update for Business deferral policy. This doesn't apply to long-term servicing editions.
Known issues in this update
Symptom Workaround [ADDED 9/4] Microsoft is getting reports that a small number of users may not receive results when using Windows Desktop Search and may see high CPU usage from SearchUI.exe. This issue only occurs on devices that have disabled searching the web using Windows Desktop Search. We are working on a resolution and estimate a solution will be available in mid-September.
Tweet
— Twitter API (@user) View on Twitter
How to get this update
Before installing this update
Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU. For more information, see Servicing stack updates.
If you are using Windows Update, the latest SSU (KB4515530) will be offered to you automatically. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog.
Install this update
Release Channel Available Next Step Windows Update or Microsoft Update Yes Go to Settings > Update & Security > Windows Update and select Check for updates. Microsoft Update Catalog Yes To get the standalone package for this update, go to the Microsoft Update Catalog. Windows Server Update Services (WSUS) Yes This update will automatically synchronize with WSUS if you configure Products and Classifications as follows:
Product: Product: Windows 10, version 1903 and later
Classification: Update
Source: https://support.microsoft.com/en-us/help/4512941
Direct download links for KB4512941 MSU file from Microsoft Update Catalog:
Download KB4512941 MSU for Windows 10 v1903 32-bit (x86) - 114.6 MB
Download KB4512941 MSU for Windows 10 v1903 64-bit (x64) - 262.5 MB
Download KB4512941 MSU for Windows 10 v1903 ARM64 - 287.5 MB
also KB4511555 Cumulative Update for .NET Framework 3.5, 4.8 for Windows 10, version 1903 released.
Cumulative Update KB4511555 .NET Framework 3.5, 4.8 Windows 10 Aug. 30
a bit slow to apply the update, anyway no problem to report so far![]()
Just un-paused updates, which merely resulted in KB4512508 being reapplied and reinstalled on my PC - and with the same as before result:
As you can see from the above it's the same result with the new Servicing Stack released also today (KB4515530).
With that in mind I am now skipping to this very update (KB4512941):
and am installing it manually out of sheer boredom:
But frankly can't see this issue on the fixes list being reported as resolved:
https://docs.microsoft.com/en-us/win...903#634msgdesc
Will let you know the result shortly.
It took 1/2 hour and three starts and stops to complete the upgrade to .329. All seems fine now.
WEK
First WU only presented the net update and once I rebooted the CU appeared. I'm going to stay normal and leave the insiders stuff alone since I've performed a clean install and everything is running good.
Ah yes, .NET thingy has actually installed fine and on the first go.
Which obviously indicates even stronger that it's not the update mechanism on my end that it's the problem here...