Microsoft Reports a New Windows 10 Bug – Affects Last Year’s v1903 and v1909

Microsoft Reports a New Windows 10 Bug – Affects Last Year’s v1903 and v1909

4 years ago
Anonymous $rxtAWepgzY

https://wccftech.com/microsoft-reports-a-new-windows-10-bug-affects-v1903-and-v1909/

Microsoft has added a new bug in the list of known issues affecting Windows 10 November 2019 Update (version 1909) and Windows 10 May 2019 Update (version 1903). This is the first bug that the Windows maker has added in the list since February. The issue impacts both these feature updates since they share a common core operating system and an identical set of system files, and receive similar cumulative updates.

The company writes that some users might receive a compatibility report dialog warning that the "installation of Windows will remove some optional features." Microsoft explained that "you might receive this compatibility warning when LOCAL SYSTEM accounts are blocked in a firewall from accessing the internet via HTTP." The problem apparently arrived with August's Patch Tuesday update (KB4565351 - Builds 18362.1016 and 18363.1016).

Microsoft Reports a New Windows 10 Bug – Affects Last Year’s v1903 and v1909

Sep 22, 2020, 10:16pm UTC
https://wccftech.com/microsoft-reports-a-new-windows-10-bug-affects-v1903-and-v1909/ > Microsoft has added a new bug in the list of known issues affecting Windows 10 November 2019 Update (version 1909) and Windows 10 May 2019 Update (version 1903). This is the first bug that the Windows maker has added in the list since February. The issue impacts both these feature updates since they share a common core operating system and an identical set of system files, and receive similar cumulative updates. > The company writes that some users might receive a compatibility report dialog warning that the "installation of Windows will remove some optional features." Microsoft explained that "you might receive this compatibility warning when LOCAL SYSTEM accounts are blocked in a firewall from accessing the internet via HTTP." The problem apparently arrived with August's Patch Tuesday update (KB4565351 - Builds 18362.1016 and 18363.1016).