\n
Microsoft has just released a new optional patch for the Windows 10 October 2018 Update, just a week after it did the same for the April 2018 Update and other older versions of Windows 10. The new build 17763.652 includes a lot of quality fixes that will also be included in next month’s Patch Tuesday, and you can check the full list of improvements below:
\n
\n
\n
- Addresses a performance issue that may occur on some websites that use WebAssembly.
\n
- Addresses an issue that may cause Internet Explorer to stop working when you move a tab to create a new window.
\n
- Addresses an issue that may prevent the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer.
\n
- Updates time zone information for Brazil.
\n
- Addresses an issue that may cause Windows notifications to display nonsense characters instead of a single quote (‘).
\n
- Addresses an issue that prevents newly installed or updated applications from appearing in Windows search results.
\n
- Addresses an issue that prevents the Save and Save As options in Microsoft Office 2010 applications from working when high contrast mode is on.
\n
- Address an issue that prevents SharedPC policies from migrating properly during an upgrade.
\n
- Addresses an issue that prevents a Hardware Support application (HSA) from installing in a timely manner.
\n
- Addresses an issue that prevents the Windows Event Log service from processing notifications that the log is full. This causes issues with some Event Log behaviors such as archiving the log when it reaches a maximum file size and you’ve configured the “Archive the log when full, do not overwrite events” setting. Additionally, the Local Security Authority (LSA) cannot handle CrashOnAuditFail scenarios when the Security Log is full, and events cannot be written.
\n
- Addresses an issue that prevents a system from recognizing a Microsoft account or Azure Active Directory account until the user signs out and signs in again.
\n
- Addresses an issue that may prevent the Netlogon service from establishing a secure channel and reports the error, “0xC000007A – ERROR_PROC_NOT_FOUND.”
\n
- Addresses an issue that may cause authentication to fail when using Windows Hello for Business on a server running Windows Server 2016 with the Server Core option installed.
\n
- Addresses an issue that causes some processes running inside Windows Server containers and Hyper-V containers to have empty names.
\n
- Addresses an issue that causes input and output to fail when Multipath I/O (MPIO) failover occurs.
\n
- Addresses an issue that causes applications that use windows.storage.dll to stop working and displays ExceptionCode c0000005 (Access violation) when the process closes.
\n
- Reinforces the Certificate Revocation List (CRL) on Internet Key Exchange version 2 (IKEv2) machines for certificate-based virtual private network (VPN) connections, such as Device Tunnel, in an Always On VPN deployment.
\n
- Addresses an issue that intermittently prevents connections to a corporate network when using Always On VPN with the IKEv2 protocol. Connections are not always automatically established, and manual connections sometimes fail. In this scenario, when you call the RasDial function from the command line for the target VPN connection, you receive the error, “ERROR_PORT_NOT_AVAILABLE(633)”.
\n
- Addresses an issue that changes the status for Work Folders in File Explorer to 0x80C802A0 (ECS_E_SYNC_UPLOAD_PLACEHOLDER_FAILURE) after selecting Free up space.
\n
- Addresses an issue that may cause a Remote Desktop Server to stop responding when someone who is using drive redirection disconnects.
\n
- Addresses an issue that causes an error when using certain data persistence memory technologies.
\n
- Addresses an issue that prevents Microsoft Application Virtualization (App-V) scripting from working if you run it when you’re not connected to a domain controller (DC). App-V scripting also fails when you run it in an environment that only contains Microsoft Azure Active Directory.
\n
- Addresses an issue that damages the Microsoft Message Queuing (MSMQ) feature and prevents it from starting or installing again. This issue may occur after installing Windows updates or upgrading from Windows 10, versions 1607, 1703, and 1709 to Windows 10, version 1809.
\n
- Addresses an issue with opening or using the Window-Eyes screen reader application that may result in an error and prevent some features from functioning as expected.
\n
- Addresses an issue that may fail to keep App permissions settings when you select Keep my files after selecting Reset this PC.
\n
- Addresses an issue with system reliability in certain scenarios when upgrading from Windows 10, version 1703.
\n
- Addresses an issue with enrolling a device in the Windows enterprise commercial data pipeline.
\n
\n
\n
Be aware that this new build comes with four known issues that were already present in this month’s Patch Tuesday, including a bug causing some devices to startup to a black screen during the first logon after installing updates. Microsoft provided workarounds for all these issues on the release notes, and the company says that it will provide fixes in an upcoming release.
\n\nFurther reading: build 17763.652, cumulative updates, Windows 10, Windows 10 October 2018 Update
