Microsoft has issued a new Windows 10 update that solve plenty of issues on the platform. The company rolled the update out under the radar this past weekend.
It is worth noting the update is optional so it will not be coming to your machine automatically. Microsoft says the update is specifically for users running older versions of Windows 10, including the October 2018 Update.
The build in question is 17763.720 for the October 2018 Update and comes with numerous fixes. Among them is solving a problem where Windows Hello Face Authentication would stop working during a system restart.
Elsewhere, Microsoft says the update improved push notifications for HoloLens, making them more reliable.
Also included in the fix blitz, Microsoft addressed a problem with Deployment Image Servicing and Management (DISM), which was not responding under some conditions.
Changelog
- 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 [email protected] to [email protected]).
- 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 () attempted to load 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 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.
Other Windows 10 Versions
As mentioned, Microsoft rolled out updates for other previous Windows 10 versions, including 1709, 1703, 1607, and 1507. All the updates have known issues and are only available for Enterprise and Education edition users.
While these updates are all optional at the moment, they will be required when they are packaged into Patch Tuesday next month.
