For v1809 users, Microsoft just released the august cumulative update. You can find the KB4512534 update offline installer download links down below.
Unlike other updates, this is an optional and non-security update that is mainly aimed at fixing some bugs in apps that are designed with Visual Basic Scripting Edition. In addition to that, the update also brings in some much-required fixes and improvements Windows Hello Face Authentication, DISM, Windows Defender, Win32 subsystem and Desktop Window Manager (DWM), etc.
Even though the update is considered optional, installing it can help fix any bugs in your system.
You can install the KB4512534 directly from the PC Settings app. Open the PC Settings app, go to “Update & Security -> Windows Update” and click on the “Check for updates” buttons. If the update is available for your machine, the system will automatically download and install the update for you.
Direct Download KB4512534 Offline Installer
To make things easier for you, I found the direct download links for KB4512534 for both Windows 10 32-bit and 64-bit systems. Depending on your system type, download the update using below links and install it like any other Windows software. After installing, restart the system and you are good to go.
- KB4512534 x86 (32-bit) offline installer (download size: 125.6 MB)
- KB4512534 x64 (64-bit) offline installer (download size: 271.1 MB)
If you want KB4512534 download links for Windows Server or ARM64 based systems, go to the Microsoft update catalog website to find the appropriate links. All you have to do is click on the Download button next to the appropriate version.
KB4512534 Change Log
This non-security update includes quality improvements. Key changes include:
- Improves the reliability of push notifications about app deployments to Microsoft HoloLens 1 devices.
- Addresses an issue that prevents Windows Hello Face Authentication from working after a restart.
- Addresses an issue with downloading digital rights management (DRM) files from certain websites using Microsoft Edge and Internet Explorer.
- Addresses an issue that prevents the Universal C Runtime Library from returning the proper value for time zone global variables in certain conditions.
- Addresses an issue that causes Deployment Image Servicing and Management (DISM) to intermittently stop responding while deprovisioning some preinstalled apps using the Microsoft System Center Configuration Manager (SCCM).
- Addresses an issue in which the default keyboard for the English (Cyprus) (en-CY) locale was not set properly.
- Addresses an issue to enable Microsoft Edge to print PDF documents that contain landscape and portrait-oriented pages correctly.
- Addresses an issue with PDFs that are configured to be opened only once in Microsoft Edge.
- Addresses performance issues for the Win32 subsystem and Desktop Window Manager (DWM).
- Addresses an issue with the input and display of special characters that occurs when an app uses imm32.dll.
- Addresses a composition handle leak in Universal Windows Platform (UWP) apps.
- Addresses a memory leak in dwm.exe that may lead to a loss of functionality and cause a device to stop working.
- Addresses an issue that fails to bypass automatic sign in (Autologon) when you press and hold the Shift key during startup.
- 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 an App-V application from opening and displays a network failure error. This issue occurs under certain circumstances, such as when a system’s battery is low or there is an unexpected power failure.
- Addresses an issue with User Experience Virtualization (UE-V) that may sometimes prevent exclusion paths from working.
- Addresses a rare issue that causes Windows Defender Advanced Threat Protection (ATP) to temporarily prevent other processes from accessing files.
- 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 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 prevents some Trusted Platform Module (TPM) devices from being used for Next-Generation Credentials.
- Addresses an issue that causes applications on a container host to intermittently lose connectivity because of a port conflict with applications running on a container.
- Addresses an issue that prevents some users from receiving a TTL value when they are added as members of Shadow Principals. This occurs for users who have distinguished names (DN) that contain an escape character. The TTL value is now added as expected.
- Addresses an issue with the disabled attribute of the input element, which doesn’t allow a scope to be passed to the authorization endpoint.
- Addresses an issue with leaks in Windows notification sockets that causes Windows to run out of ports.
- Addresses an issue that prevents server editions from activating with a Multiple Activation Key (MAK) in the graphical user interface (GUI). The error is, “0x80070490”.
- Addresses an issue that may break the domain trust when the Recycle Bin is configured on the domain that carries the trust.
- Increases the number of supported interrupts per device to 512 on systems that have x2APIC enabled.
- Addresses an issue that may prevent devices from starting when they start up using the 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 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).
You may also receive an “Invalid procedure call” error.
That is all.