Windows 10 v1809 KB4512534 Update released with VB Fix and more



[ad_1]

Windows Update

Microsoft is deploying KB4512534 for Windows 10 October 2018 Update and Windows Server 2019 with a long list of non-security bug fixes and enhancements. KB4512534 upgrades the system to Windows 10 version 17763.720 and fixes basic visual issues reported by Microsoft on August 15, shortly after the deployment of the patch security updates on Tuesday of August 2019.

The August 17 cumulative update for Windows 10 version 1809 also fixes a problem that prevented Windows Hello face recognition from working after the system reboot, and Microsoft had also resolved two issues with the classic Edge browser. This hotfix also improves the download of copyrighted digital media content from certain websites using Edge and Internet Explorer.

This is an optional update and if you want to install it on your PC, you will have to open settings and navigate to Update and security -> Windows Update and select Check for updates. The update is available through Windows Update, the Microsoft Update Catalog, and Windows Server Update Services (WSUS for business).

If you have multiple computers or want to manually fix computers, you can learn more about the process here.

Here is a complete list of fixes and enhancements included in the latest update:

  • Improves the reliability of push notifications for application deployments on Microsoft HoloLens 1 devices.
  • Resolves an issue that prevents Windows Hello Face authentication from running after a restart.
  • Resolves an issue with downloading digital rights management (DRM) files from certain Web sites using Microsoft Edge and Internet Explorer.
  • Resolves an issue that prevents the Universal C Runtime Library from returning the appropriate value for global timezone variables under certain conditions.
  • Resolves an issue causing DISM (Deployment Image Servicing and Management) intermittent shutdown when deprovisioning some preinstalled applications using Microsoft System Center Configuration Manager (SCCM).
  • Resolves an issue in which the default keyboard for the English (Cyprus) locale (en-CY) was not set correctly.
  • Resolves an issue that allowed Microsoft Edge to correctly print PDF documents containing landscape and portrait pages.
  • Fixes a problem with PDF files that are configured to open only once in Microsoft Edge.
  • Resolves performance issues for the Win32 subsystem and the Desktop Window Manager (DWM).
  • Resolves a problem with entering and displaying special characters when using an application. imm32.dll.
  • Resolves a composition descriptor leak in Universal Windows Platform (UWP) applications.
  • Address a memory leak in dwm.exe this could result in loss of functionality and prevent the unit from operating.
  • Resolves an issue that fails to skip automatic login (automatic login) when you hold down the Shift key at startup.
  • Resolves an issue that causes the Windows Management Instrumentation (WMI) class Win32_PhysicalMemory to report that 32GB memory chips have a missing capacity value.
  • Fixes a problem that prevents an App-V application from opening and displaying a network failure error. This problem occurs under certain circumstances, such as when the system's battery is low or unexpected power failure occurs.
  • Resolves an issue related to User Experience Virtualization (UE-V) that can sometimes prevent the operation of the exclusion paths.
  • Fixes a rare problem that makes Windows Defender Anti-Threat Protection (ATP) temporarily prevent other processes from accessing files.
  • Resolves an issue that prevents a workstation from functioning when you log in with the help of an updated Primary User Name (UPN) (for example, the change [email protected] at [email protected]).
  • Resolves an issue in which Windows Defender Application Control does not allow the loading of third party binary files from an application of the Universal Windows platform. The CodeIntegrity event error 3033 appears as, "The integrity of the code determined that an attempt to load by process () did not meet the requirements of the store's signature level." ".
  • Resolves an issue that prevents certain Secure Platform Module (TPM) devices from being used for next generation credentials.
  • Fixes a problem that causes a loss of intermittent connectivity of applications on a container host due to a port conflict with applications running on a container.
  • Resolves an issue that prevents some users from receiving a lifetime value when they are added as members of the Shadow Principals settings. This occurs for users whose distinguished name (DN) contains an escape character. The TTL value is now added as expected.
  • Fixes a problem with the disabled attribute of the contribution element, which does not allow to transmit a scope to the endpoint of authorization.
  • Fixes a problem with leaks in Windows notification sockets, which causes Windows to run out of ports.
  • Resolves an issue that prevents server edits from activating with a Multiple Activation Key (MAK) in the graphical user interface. The error is "0x80070490".
  • Resolves an issue that may break domain trust when the trash is configured on the trusted domain.
  • Increases the number of interrupts supported per device at 512 on systems where x2APIC is enabled.
  • Fixes an issue that may prevent devices from booting when they start using Windows Deployment Services (WDS) or System Center Configuration Manager (PXE) Preboot Execution Environment (PXE) images. SCCM). The error is, "Status: 0xc0000001, Info: a required device is not connected or is not accessible."
  • Resolves a problem that could cause the following response process to stop:
    • Applications created with the help of Visual Basic 6 (VB6).
    • Macros that use Visual Basic for Applications (VBA).
    • Scripts or applications using Visual Basic Scripting Edition (VBScript).

You may also receive an "Invalid procedure call" error.

Microsoft is aware of several known issues, including a bug that could generate a black screen when first starting the PC after the patch is installed. Here is a complete list of known issues and their solution:

Symptom Workaround
Some operations, such as reappoint, that you perform on files or folders that are on a clustered shared volume (CSV) may fail with the "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)" error. This occurs when you perform the operation on a CSV owner node from a process that does not have an administrator privilege.

Do one of the following:

  • Perform the operation from a process with administrator privileges.
  • Perform the operation from a node that does not own the CSV file.

Microsoft is working on a resolution and will provide an update in a future release.

After the installation of KB4493509, devices with some Asian language packs may receive the error message "0x800f0982 – PSFX_E_MATCHING_COMPONENT_NOT_FOUND".
  1. Uninstall and reinstall any newly added language packs. For instructions, see Manage Input and Display Language Settings in Windows 10.
  2. To select Check for updates and install the cumulative update for April 2019. For instructions, see Update Windows 10.

Note If reinstalling the language pack does not alleviate the problem, reset your PC as follows:

  1. Go to settings app> Recovery.
  2. To select To start under the Reset this PC recovery option.
  3. To select Keep my files.

Microsoft is working on a resolution and will provide an update in a future release.

We are studying information that a small number of devices might start on a black screen during the first login after the installation of the updates.

To resolve this problem, press Ctrl + Alt + Del, then select the Power button in the lower right corner of the screen and select To restart. Your device should now restart normally.

We are working on a resolution and will provide an update in a future release.

Applications and scripts that call the NetQueryDisplayInformation API or the WinNT equivalent may not return results after the first page of data, often 50 or 100 entries. When requesting additional pages, the error message "1359: an internal error has occurred" can be displayed. This problem occurs in this update and in all updates prior to June 18, 2019. We are working on a resolution and will provide an update in a future release.

[ad_2]

Source link