KB4512534 for Windows 10 version 1809 fixes VB bug and more

Martin Brinkmann
Aug 18, 2019
Windows, Windows 10, Windows Updates

Microsoft released the cumulative update KB4512534 for its Windows 10 version 1809 operating system on August 17, 2019.

The update follows the release of the updates KB4517297 for Windows 7 and Windows Server 2008 R2,
KB4517298 for Windows 8.1 and Windows Server 2012 R2, and KB4512494 for Windows 10 version 1709 which the company released on August 16, 2019.

KB4512534 is available on Windows Update, as a direct download on the Microsoft Update Catalog website, and on WSUS for organizations.

Note: We recommend that you back up the system partition before you install any updates on Windows machines. You may use free tools such as Macrium Reflect or Paragon Backup & Recovery Free for that.


KB4512534 windows 10 1809

Important links

The cumulative update fixes the VB bug that Microsoft acknowledged shortly after the release of the August 2019 Patch Day for Windows. The update addresses the long-standing Preboot Execution Environment issue as well.

Here is the list of fixes and changes in the release:

  • Fixed an issue with Windows Hello not working after restarts.
  • Improved reliability of push notifications about app deployments to Microsoft HoloLens 1 devices.
  • Fixed an issue with downloading DRM files from certain websites in Edge an IE.
  • Fixed an issue that prevented the Universal C Runtime Library from returning proper time zone global variables values.
  • Fixed a Deployment Image Servicing and Management (DISM) issue that caused it to stop responding under certain conditions.
  • Fixed a default keyboard issue that affected the English Cyprus (en-cy) locale.
  • Fixed a Microsoft Edge printing issue so that PDF documents with portrait and landscape pages print correctly.
  • Fixed another issue with PDF documents configured to be opened only once in Microsoft Edge.
  • Addressed performance issues for the Win32 subsystem and Desktop Window Manager.
  • Fixed an input and display of special characters issue when application used imm32.dll.
  • Addressed a composition leak in UWP apps.
  • Fixed a memory leak in dwm.exe that could lead to loss of functionality and cause a device to stop working.
  • Fixed an automatic sign-in issue that affected the bypass Shift-key.
  • Fixed a reporting issue in the Windows Management Instrumentation class Win32_PhysicalMemory.
  • Fixed an issue that prevented App-V applications from opening.
  • Fixed a User Experience Virtualization issue that prevented exclusion paths from working correctly.
  • Fixed a Windows Defender Advanced Threat Protection issue that caused the program to prevent others from accessing certain files.
  • Fixed an issue that caused workstations to stop working when users signed in using an updated user principal name.
  • Fixed a Windows Defender Application Control issue that prevented third-party binaries to be loaded from UWP applications.
  • Fixed a Trusted Platform Module issue that prevented TPM devices from being used for Next Generation Credentials.
  • Fixed an issue that caused applications on a container host to lose connectivity.
  • Fixed an issue that prevented some users from receiving a TTL value when being added as members of Shadow Principals.
  • Addressed an issue with the disabled attribute of the input element, which didn’t allow a scope to be passed to the authorization endpoint.
  • Fixed a leak issue in Windows notification sockets that caused the operating system to run out of ports.
  • Fixed a server edition authentication issue.
  • Fixed an issue that could break domain trust when the Recycle Bin was configured on the domain that carried the trust.
  • Increased the number of supported interrupts per device to 512 on systems that have x2APIC enabled.
  • Fixed the Preboot Execution Environment issue.
  • Fixed the VB issue.

Known Issues

Microsoft lists four known updates (down from six). All known issues are not new.

  • Certain operations on Cluster Shared Volumes may fail.
  • Errors on devices with certain Asian language packs installed.
  • Black screen on first logon after update installation issue.
  • Apps and scripts that use the NetQueryDisplayInformation API or the WinNT provider equivalent may only return 50 or 100 entries.

Now You: Have you installed the new update (updates) that Microsoft released in August? What is your experience so far?

KB4512534 for Windows 10 version 1809 fixes VB bug and more
Article Name
KB4512534 for Windows 10 version 1809 fixes VB bug and more
Microsoft released the cumulative update KB4512534 for its Windows 10 version 1809 operating system on August 17, 2019 that fixed the VB bug and other issues.
Ghacks Technology News

Tutorials & Tips

Previous Post: «
Next Post: «


  1. EP said on August 20, 2019 at 12:35 am

    looks like MS has posted the KB4512509 update for Win10 v1803 this Monday afternoon of 8/19, which includes the VB bug fixes. that leaves just the v1903 release withoug the VB fixes.

  2. EP said on August 19, 2019 at 4:12 am

    MS has also released VBA bug fixes for Win10 v1507/LTSB 2015, v1607/LTSB 2016 and v1703 as well. the 1803 and 1903 versions have not yet gotten their VBA fixes, Martin. woody has just mentioned them recently in his blog:


  3. ilev said on August 18, 2019 at 5:21 pm

    Gunter Born : But I received user feedback, that the issue isn’t completely fixed.

  4. Yuliya said on August 18, 2019 at 3:34 pm

    I’ve applied this one also on LTSC. Currently still cleaning the image via DISM. Everything went and works well.

    1. Anonymous said on August 18, 2019 at 4:54 pm

      Installed as well, did not run into any issues on a test system running Windows 10 version 1809. Still no sign of the 1903 update on that machine though.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.