| Summary | Originating update | Status | Date resolved |
| Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | OS Build 10240.18334 September 23, 2019 KB4522009 | Resolved KB4520011 | October 08, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Intermittent issues when printing Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
Affected platforms:
Resolution: This issue was resolved in KB4520011. Back to top | OS Build 10240.18334 September 23, 2019 KB4522009 | Resolved KB4520011 | Resolved: October 08, 2019 10:00 AM PT Opened: September 30, 2019 06:26 PM PT |
| Summary | Originating update | Status | Date resolved |
| Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. See details > | OS Build 14393.2608 November 13, 2018 KB4467691 | Resolved External | January 23, 2020 02:08 PM PT |
| Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | OS Build 14393.3206 September 23, 2019 KB4522010 | Resolved KB4519998 | October 08, 2019 10:00 AM PT |
| IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage. See details > | OS Build 14393.3204 September 10, 2019 KB4516044 | Resolved | September 17, 2019 04:47 PM PT |
| Apps and scripts using the NetQueryDisplayInformation API may fail with error Applications and scripts that call NetQueryDisplayInformation may fail to return results after the first page of data. See details > | OS Build 14393.3053 June 18, 2019 KB4503294 | Resolved KB4516044 | September 10, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Intermittent issues when printing Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
Affected platforms:
Resolution: This issue was resolved in KB4519998. Back to top | OS Build 14393.3206 September 23, 2019 KB4522010 | Resolved KB4519998 | Resolved: October 08, 2019 10:00 AM PT Opened: September 30, 2019 06:26 PM PT |
| IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) may become unresponsive or may have high CPU usage. Affected IMEs include Chinese Simplified (ChsIME.EXE) and Chinese Traditional (ChtIME.EXE) with Changjie/Quick keyboard. Affected platforms:
Resolution: After investigation, we have found that this issue does not affect this version of Windows. Back to top | OS Build 14393.3204 September 10, 2019 KB4516044 | Resolved | Resolved: September 17, 2019 04:47 PM PT Opened: September 13, 2019 05:25 PM PT |
| Details | Originating update | Status | History |
| Apps and scripts using the NetQueryDisplayInformation API may fail with error Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.” Affected platforms:
Resolution: This issue was resolved in KB4516044. Back to top | OS Build 14393.3053 June 18, 2019 KB4503294 | Resolved KB4516044 | Resolved: September 10, 2019 10:00 AM PT Opened: August 01, 2019 05:00 PM PT |
| Details | Originating update | Status | History |
| Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. Affected platforms:
Workaround: Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart. If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled. Resolution: Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device. Back to top | OS Build 14393.2608 November 13, 2018 KB4467691 | Resolved External | Last updated: January 23, 2020 02:08 PM PT Opened: November 13, 2018 10:00 AM PT |
| Summary | Originating update | Status | Date resolved |
| Unable to create local users in Chinese, Japanese and Korean during device setup You might be unable to create users in Chinese, Japanese and Korean using Input Method Editor (IME) during OOBE. See details > | OS Build 16299.1387 September 10, 2019 KB4516066 | Resolved KB4534318 | January 23, 2020 02:00 PM PT |
| Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | OS Build 16299.1392 September 23, 2019 KB4522012 | Resolved KB4520004 | October 08, 2019 10:00 AM PT |
| IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage. See details > | OS Build 16299.1387 September 10, 2019 KB4516066 | Resolved | September 19, 2019 04:08 PM PT |
| Details | Originating update | Status | History |
| Unable to create local users in Chinese, Japanese and Korean during device setup When setting up a new Windows device using the Out of Box Experience (OOBE), you might be unable to create a local user when using Input Method Editor (IME). This issue might affect you if you are using the IME for Chinese, Japanese, or Korean languages. Note This issue does not affect using a Microsoft Account during OOBE. Affected platforms:
Resolution: This issue was resolved in KB4534318. Back to top | OS Build 16299.1387 September 10, 2019 KB4516066 | Resolved KB4534318 | Resolved: January 23, 2020 02:00 PM PT Opened: October 29, 2019 05:15 PM PT |
| Details | Originating update | Status | History |
| Intermittent issues when printing Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
Affected platforms:
Resolution: This issue was resolved in KB4520004. Back to top | OS Build 16299.1392 September 23, 2019 KB4522012 | Resolved KB4520004 | Resolved: October 08, 2019 10:00 AM PT Opened: September 30, 2019 06:26 PM PT |
| IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) may become unresponsive or may have high CPU usage. Affected IMEs include Chinese Simplified (ChsIME.EXE) and Chinese Traditional (ChtIME.EXE) with Changjie/Quick keyboard. Affected platforms:
Resolution: Due to security related changes in KB4516066, this issue may occur when Touch Keyboard and Handwriting Panel Service is not configured to its default startup type of Manual. To resolve the issue, perform the following steps:
Back to top | OS Build 16299.1387 September 10, 2019 KB4516066 | Resolved | Resolved: September 19, 2019 04:08 PM PT Opened: September 13, 2019 05:25 PM PT |
| Summary | Originating update | Status | Date resolved |
| Unable to create local users in Chinese, Japanese and Korean during device setup You might be unable to create users in Chinese, Japanese and Korean using Input Method Editor (IME) during OOBE. See details > | OS Build 17134.1006 September 10, 2019 KB4516058 | Resolved KB4534308 | January 23, 2020 02:00 PM PT |
| Windows Mixed Reality Portal users may intermittently receive a 15-5 error code You may receive a 15-5 error code in Windows Mixed Reality Portal and your headset may not wake up from sleep. See details > | OS Build 17134.950 August 13, 2019 KB4512501 | Resolved KB4519978 | October 15, 2019 10:00 AM PT |
| Startup to a black screen after installing updates Your device may startup to a black screen during the first logon after installing updates. See details > | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved KB4519978 | October 15, 2019 10:00 AM PT |
| Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | OS Build 17134.1009 September 23, 2019 KB4522014 | Resolved KB4520008 | October 08, 2019 10:00 AM PT |
| IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage. See details > | OS Build 17134.1006 September 10, 2019 KB4516058 | Resolved | September 19, 2019 04:08 PM PT |
| Notification issue: \"Your device is missing important security and quality fixes.\" Some users may have incorrectly received the notification \"Your device is missing important security and quality fixes.\" See details > | N/A | Resolved | September 03, 2019 12:32 PM PT |
| Details | Originating update | Status | History |
| Unable to create local users in Chinese, Japanese and Korean during device setup When setting up a new Windows device using the Out of Box Experience (OOBE), you might be unable to create a local user when using Input Method Editor (IME). This issue might affect you if you are using the IME for Chinese, Japanese, or Korean languages. Note This issue does not affect using a Microsoft Account during OOBE. Affected platforms:
Resolution: This issue was resolved in KB4534308. Back to top | OS Build 17134.1006 September 10, 2019 KB4516058 | Resolved KB4534308 | Resolved: January 23, 2020 02:00 PM PT Opened: October 29, 2019 05:15 PM PT |
| Details | Originating update | Status | History |
| Windows Mixed Reality Portal users may intermittently receive a 15-5 error code After installing KB4512501, Windows Mixed Reality Portal users may intermittently receive a 15-5 error code. In some cases, Windows Mixed Reality Portal may report that the headset is sleeping and pressing “Wake up” may appear to produce no action. Affected platforms:
Resolution: This issue was resolved in KB4519978. Back to top | OS Build 17134.950 August 13, 2019 KB4512501 | Resolved KB4519978 | Resolved: October 15, 2019 10:00 AM PT Opened: September 11, 2019 05:32 PM PT |
| Intermittent issues when printing Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
Affected platforms:
Resolution: This issue was resolved in KB4520008. Back to top | OS Build 17134.1009 September 23, 2019 KB4522014 | Resolved KB4520008 | Resolved: October 08, 2019 10:00 AM PT Opened: September 30, 2019 06:26 PM PT |
| IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) may become unresponsive or may have high CPU usage. Affected IMEs include Chinese Simplified (ChsIME.EXE) and Chinese Traditional (ChtIME.EXE) with Changjie/Quick keyboard. Affected platforms:
Resolution: Due to security related changes in KB4516058, this issue may occur when Touch Keyboard and Handwriting Panel Service is not configured to its default startup type of Manual. To resolve the issue, perform the following steps:
Back to top | OS Build 17134.1006 September 10, 2019 KB4516058 | Resolved | Resolved: September 19, 2019 04:08 PM PT Opened: September 13, 2019 05:25 PM PT |
| Notification issue: \"Your device is missing important security and quality fixes.\" Some users may have incorrectly received the notification \"Your device is missing important security and quality fixes\" in the Windows Update dialog and a red \"!\" in the task tray on the Windows Update tray icon. This notification is intended for devices that are 90 days or more out of date, but some users with installed updates released in June or July also saw this notification. Affected platforms:
Resolution: This issue was resolved on the server side on August 30, 2019. Only devices that are out of date by 90 days or more should now see the notification. No action is required by the user to resolve this issue. If you are still seeing the \"Your device is missing important security and quality fixes\" notification, we recommend selecting Check for Updates in the Windows Update dialog. For instructions, see Update Windows 10. Microsoft always recommends trying to keep your devices up to date, as the monthly updates contain important security fixes. Back to top | N/A | Resolved | Resolved: September 03, 2019 12:32 PM PT Opened: September 03, 2019 12:32 PM PT |
| Details | Originating update | Status | History |
| Startup to a black screen after installing updates We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates. Affected platforms:
Resolution: This issue was resolved in KB4519978. Back to top | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved KB4519978 | Resolved: October 15, 2019 10:00 AM PT Opened: June 14, 2019 04:41 PM PT |
| Summary | Originating update | Status | Date resolved |
| Unable to create local users in Chinese, Japanese and Korean during device setup You might be unable to create users in Chinese, Japanese and Korean using Input Method Editor (IME) during OOBE. See details > | OS Build 17763.737 September 10, 2019 KB4512578 | Resolved KB4534321 | January 23, 2020 02:00 PM PT |
| Microsoft Defender Advanced Threat Protection might stop running The Microsoft Defender ATP service might stop running and might fail to send reporting data. See details > | OS Build 17763.832 October 15, 2019 KB4520062 | Resolved KB4523205 | November 12, 2019 10:00 AM PT |
| Windows Mixed Reality Portal users may intermittently receive a 15-5 error code You may receive a 15-5 error code in Windows Mixed Reality Portal and your headset may not wake up from sleep. See details > | OS Build 17763.678 August 13, 2019 KB4511553 | Resolved KB4520062 | October 15, 2019 10:00 AM PT |
| Startup to a black screen after installing updates Your device may startup to a black screen during the first logon after installing updates. See details > | OS Build 17763.557 June 11, 2019 KB4503327 | Resolved KB4520062 | October 15, 2019 10:00 AM PT |
| Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | OS Build 17763.740 September 23, 2019 KB4522015 | Resolved KB4519338 | October 08, 2019 10:00 AM PT |
| Apps and scripts using the NetQueryDisplayInformation API may fail with error Applications and scripts that call NetQueryDisplayInformation may fail to return results after the first page of data. See details > | OS Build 17763.55 October 09, 2018 KB4464330 | Resolved KB4516077 | September 24, 2019 10:00 AM PT |
| IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage. See details > | OS Build 17763.737 September 10, 2019 KB4512578 | Resolved | September 19, 2019 04:08 PM PT |
| Details | Originating update | Status | History |
| Unable to create local users in Chinese, Japanese and Korean during device setup When setting up a new Windows device using the Out of Box Experience (OOBE), you might be unable to create a local user when using Input Method Editor (IME). This issue might affect you if you are using the IME for Chinese, Japanese, or Korean languages. Note This issue does not affect using a Microsoft Account during OOBE. Affected platforms:
Resolution: This issue was resolved in KB4534321. Back to top | OS Build 17763.737 September 10, 2019 KB4512578 | Resolved KB4534321 | Resolved: January 23, 2020 02:00 PM PT Opened: October 29, 2019 05:15 PM PT |
| Microsoft Defender Advanced Threat Protection might stop running After installing the optional non-security update (KB4520062), the Microsoft Defender Advanced Threat Protection (ATP) service might stop running and might fail to send reporting data. You might also receive a 0xc0000409 error in Event Viewer on MsSense.exe. Note Microsoft Microsoft Defender Antivirus is not affected by this issue. Affected platforms:
Resolution: This issue was resolved in KB4523205. Back to top | OS Build 17763.832 October 15, 2019 KB4520062 | Resolved KB4523205 | Resolved: November 12, 2019 10:00 AM PT Opened: October 17, 2019 05:14 PM PT |
| Details | Originating update | Status | History |
| Windows Mixed Reality Portal users may intermittently receive a 15-5 error code After installing KB4511553, Windows Mixed Reality Portal users may intermittently receive a 15-5 error code. In some cases, Windows Mixed Reality Portal may report that the headset is sleeping and pressing “Wake up” may appear to produce no action. Affected platforms:
Resolution: This issue was resolved in KB4520062. Back to top | OS Build 17763.678 August 13, 2019 KB4511553 | Resolved KB4520062 | Resolved: October 15, 2019 10:00 AM PT Opened: September 11, 2019 05:32 PM PT |
| Intermittent issues when printing Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
Affected platforms:
Resolution: This issue was resolved in KB4519338. Back to top | OS Build 17763.740 September 23, 2019 KB4522015 | Resolved KB4519338 | Resolved: October 08, 2019 10:00 AM PT Opened: September 30, 2019 06:26 PM PT |
| IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) may become unresponsive or may have high CPU usage. Affected IMEs include Chinese Simplified (ChsIME.EXE) and Chinese Traditional (ChtIME.EXE) with Changjie/Quick keyboard. Affected platforms:
Resolution: Due to security related changes in KB4512578, this issue may occur when Touch Keyboard and Handwriting Panel Service is not configured to its default startup type of Manual. To resolve the issue, perform the following steps:
Back to top | OS Build 17763.737 September 10, 2019 KB4512578 | Resolved | Resolved: September 19, 2019 04:08 PM PT Opened: September 13, 2019 05:25 PM PT |
| Details | Originating update | Status | History |
| Apps and scripts using the NetQueryDisplayInformation API may fail with error Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.” Affected platforms:
Resolution: This issue was resolved in KB4516077. Back to top | OS Build 17763.55 October 09, 2018 KB4464330 | Resolved KB4516077 | Resolved: September 24, 2019 10:00 AM PT Opened: August 01, 2019 05:00 PM PT |
| Details | Originating update | Status | History |
| Startup to a black screen after installing updates We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates. Affected platforms:
Resolution: This issue was resolved in KB4520062. Back to top | OS Build 17763.557 June 11, 2019 KB4503327 | Resolved KB4520062 | Resolved: October 15, 2019 10:00 AM PT Opened: June 14, 2019 04:41 PM PT |
| Summary | Originating update | Status | Date resolved |
| Unable to create local users in Chinese, Japanese and Korean during device setup You might be unable to create users in Chinese, Japanese and Korean using Input Method Editor (IME) during OOBE. See details > | OS Build 18362.356 September 10, 2019 KB4515384 | Resolved KB4530684 | December 10, 2019 10:00 AM PT |
| Intermittent loss of Wi-Fi connectivity Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved External | November 22, 2019 04:10 PM PT |
| Unable to discover or connect to Bluetooth devices using some Realtek adapters Microsoft has identified compatibility issues with some versions of Realtek Bluetooth radio drivers. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved External | November 15, 2019 05:59 PM PT |
| Updates may fail to install and you may receive Error 0x80073701 Installation of updates may fail and you may receive error code 0x80073701. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved | November 12, 2019 08:11 AM PT |
| Intel Audio displays an intcdaud.sys notification Devices with a range of Intel Display Audio device drivers may experience battery drain. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved External | November 12, 2019 08:04 AM PT |
| Unable to discover or connect to Bluetooth devices using some Qualcomm adapters Microsoft has identified compatibility issues with some versions of Qualcomm Bluetooth radio drivers. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved KB4517389 | October 08, 2019 10:00 AM PT |
| Safeguard on certain devices with some Intel and Broadcom Wi-Fi adapters Some devices with Intel Centrino 6205/6235 and Broadcom 802.11ac Wi-Fi cards may experience compatibility issues. See details > | N/A | Resolved KB4522355 | October 24, 2019 10:00 AM PT |
| dGPU occasionally disappear from device manager on Surface Book 2 Some apps or games may close or fail to open on Surface Book 2 devices with Nvidia dGPU. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved | October 18, 2019 04:33 PM PT |
| Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | OS Build 18362.357 September 23, 2019 KB4522016 | Resolved KB4517389 | October 08, 2019 10:00 AM PT |
| Audio in games is quiet or different than expected Microsoft has received reports that audio in certain games is quieter or different than expected. See details > | OS Build 18362.356 September 10, 2019 KB4515384 | Resolved KB4517211 | September 26, 2019 02:00 PM PT |
| IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage. See details > | OS Build 18362.356 September 10, 2019 KB4515384 | Resolved | September 19, 2019 04:08 PM PT |
| Some users report issues related to the Start menu and Windows Desktop Search A small number of users have reported issues related to the Start menu and Windows Desktop Search. See details > | OS Build 18362.356 September 10, 2019 KB4515384 | Resolved | September 19, 2019 04:58 PM PT |
| Screenshots and Snips have an unnatural orange tint Users have reported an orange tint on Screenshots and Snips with the Lenovo Vantage app installed See details > | OS Build 18362.356 September 10, 2019 KB4516115 | Resolved External | September 11, 2019 08:54 PM PT |
| Windows Desktop Search may not return any results and may have high CPU usage Windows Desktop Search may not return any results and SearchUI.exe may have high CPU usage after installing KB4512941. See details > | OS Build 18362.329 August 30, 2019 KB4512941 | Resolved KB4515384 | September 10, 2019 10:00 AM PT |
| Domain connected devices that use MIT Kerberos realms will not start up Devices may not start after updating when connected to a domain that is configured to use MIT Kerberos realms. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
| Issues updating when certain versions of Intel storage drivers are installed Windows 10, version 1903 update may fail with certain versions of Intel Rapid Storage Technology (Intel RST) drivers. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications made using VB6, macros using VBA, and VBScript may stop responding and you may receive an error. See details > | OS Build 18362.295 August 13, 2019 KB4512508 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
| Initiating a Remote Desktop connection may result in black screen When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
| Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start on devices in which the operating system language was changed between updates. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
| Devices starting using PXE from a WDS or Configuration Manager servers may fail to start Devices that start up using PXE images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Unable to create local users in Chinese, Japanese and Korean during device setup When setting up a new Windows device using the Out of Box Experience (OOBE), you might be unable to create a local user when using Input Method Editor (IME). This issue might affect you if you are using the IME for Chinese, Japanese, or Korean languages. Note This issue does not affect using a Microsoft Account during OOBE. Affected platforms:
Resolution: This issue was resolved in KB4530684. Back to top | OS Build 18362.356 September 10, 2019 KB4515384 | Resolved KB4530684 | Resolved: December 10, 2019 10:00 AM PT Opened: October 29, 2019 05:15 PM PT |
| Unable to discover or connect to Bluetooth devices using some Qualcomm adapters Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Qualcomm. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Qualcomm Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated. Affected platforms:
Resolution: This issue was resolved in KB4517389 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved KB4517389 | Resolved: October 08, 2019 10:00 AM PT Opened: October 25, 2019 04:21 PM PT |
| Details | Originating update | Status | History |
| Safeguard on certain devices with some Intel and Broadcom Wi-Fi adapters Microsoft and NEC have found incompatibility issues with Intel Centrino 6205/6235 and Broadcom 802.11ac Wi-Fi cards when running Windows 10, version 1903 on specific models of NEC devices. If these devices are updated to Windows 10, version 1903, they will no longer be able to use any Wi-Fi connections. The Wi-Fi driver may have a yellow exclamation point in device manager. The task tray icon for networking may show the icon for no internet and Network & Internet settings may not show any Wi-Fi networks. To safeguard your update experience, we have applied a compatibility hold on the affected devices from being offered Windows 10, version 1903. Affected platforms:
Resolution: This issue was resolved in KB4522355. The safeguard hold is estimated to be removed in mid-November. Back to top | N/A | Resolved KB4522355 | Resolved: October 24, 2019 10:00 AM PT Opened: September 13, 2019 05:25 PM PT |
| Intermittent issues when printing Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
Affected platforms:
Resolution: This issue was resolved in KB4517389. Back to top | OS Build 18362.357 September 23, 2019 KB4522016 | Resolved KB4517389 | Resolved: October 08, 2019 10:00 AM PT Opened: September 30, 2019 06:26 PM PT |
| Audio in games is quiet or different than expected Microsoft has received reports that audio in certain games is quieter or different than expected. At the request of some of our audio partners, we implemented a compatibility change that enabled certain games to query support and render multi-channel audio. Due to customer feedback, we are reverting this change as some games and some devices are not rendering multi-channel audio as expected. This may result in games sounding different than customers are used to and may have missing channels. Affected platforms:
Resolution: This issue was resolved in KB4517211. Back to top | OS Build 18362.356 September 10, 2019 KB4515384 | Resolved KB4517211 | Resolved: September 26, 2019 02:00 PM PT Opened: September 13, 2019 05:25 PM PT |
| IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) may become unresponsive or may have high CPU usage. Affected IMEs include Chinese Simplified (ChsIME.EXE) and Chinese Traditional (ChtIME.EXE) with Changjie/Quick keyboard. Affected platforms:
Resolution: Due to security related changes in KB4515384, this issue may occur when Touch Keyboard and Handwriting Panel Service is not configured to its default startup type of Manual. To resolve the issue, perform the following steps:
Back to top | OS Build 18362.356 September 10, 2019 KB4515384 | Resolved | Resolved: September 19, 2019 04:08 PM PT Opened: September 13, 2019 05:25 PM PT |
| Some users report issues related to the Start menu and Windows Desktop Search Microsoft has received reports that a small number of users are having issues related to the Start menu and Windows Desktop Search. Affected platforms:
Resolution: At this time, Microsoft has not found a Search or Start issue significantly impacting users originating from KB4515384. We will continue monitoring to ensure users have a high-quality experience when interacting with these areas. If you are currently having issues, we recommend you to take a moment to report it in via the Feedback Hub (Windows + F) then try the Windows 10 Troubleshoot settings (found in Settings). If you are having an issue with search, see Fix problems in Windows Search. Back to top | OS Build 18362.356 September 10, 2019 KB4515384 | Resolved | Resolved: September 19, 2019 04:58 PM PT Opened: September 11, 2019 05:18 PM PT |
| Screenshots and Snips have an unnatural orange tint When creating screenshots or using similar tools (such as Snipping Tool or Snip & Sketch), the resulting images may have an unnatural orange tint. This issue is caused by the Eye Care mode feature of Lenovo Vantage. This issue started on or around September 5, 2019. Affected platforms:
Resolution: For guidance on this issue, see the Lenovo support article Screenshots and Snips have an unnatural orange tint. There is no update for Windows needed for this issue. Back to top | OS Build 18362.356 September 10, 2019 KB4516115 | Resolved External | Last updated: September 11, 2019 08:54 PM PT Opened: September 11, 2019 08:54 PM PT |
| Windows Desktop Search may not return any results and may have high CPU usage Microsoft is getting reports that a small number of users may not receive results when using Windows Desktop Search and may see high CPU usage from SearchUI.exe when searching after installing KB4512941. This issue is only encountered on devices in which searching the web from Windows Desktop Search has been disabled. Affected platforms:
Resolution: This issue was resolved in KB4515384. Back to top | OS Build 18362.329 August 30, 2019 KB4512941 | Resolved KB4515384 | Resolved: September 10, 2019 10:00 AM PT Opened: September 04, 2019 02:25 PM PT |
| Details | Originating update | Status | History |
| Updates may fail to install and you may receive Error 0x80073701 Installation of updates may fail and you may receive the error message, \"Updates Failed, There were problems installing some updates, but we'll try again later\" or \"Error 0x80073701\" on the Windows Update dialog or within Update history. Affected platforms:
Resolution: This issue has been resolved for most users. If you are still having issues, please see KB4528159. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved | Resolved: November 12, 2019 08:11 AM PT Opened: August 16, 2019 01:41 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512508, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an \"invalid procedure call error.\" Affected platforms:
Resolution: This issue was resolved in KB4512941. The ‘optional’ update is available on Microsoft Update Catalog, Windows Update, Microsoft Update and Windows Server Update Services (WSUS). As with any 'optional' update, you will need to Check for updates to receive KB4512941 and install. For instructions, see Update Windows 10. Note Windows Update for Business customers should apply the update via Microsoft Update Catalog or Windows Server Update Services (WSUS). Back to top | OS Build 18362.295 August 13, 2019 KB4512508 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: August 14, 2019 03:34 PM PT |
| Details | Originating update | Status | History |
| dGPU occasionally disappear from device manager on Surface Book 2 Microsoft has identified a compatibility issue on some Surface Book 2 devices configured with Nvidia discrete graphics processing units (dGPUs). After updating to Windows 10, version 1903 (the May 2019 Update), some apps or games that needs to perform graphics intensive operations may close or fail to open. To safeguard your update experience, we have applied a compatibility hold on Surface Book 2 devices with Nvidia dGPU from being offered Windows 10, version 1903 until this issue is resolved. Affected platforms:
Resolved: To resolve this issue, you will need to update the firmware of your Surface Book 2 device. Please see the Surface Book 2 update history page for instructions on how to install the October 2019 updates on your device. There is no update for Windows needed for this issue. The safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved | Resolved: October 18, 2019 04:33 PM PT Opened: July 12, 2019 04:20 PM PT |
| Domain connected devices that use MIT Kerberos realms will not start up Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected. To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903. Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists: HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms - Affected platforms:
Resolution: This issue was resolved in KB4512941 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
| Issues updating when certain versions of Intel storage drivers are installed Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903). To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated. Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050. Affected platforms:
Resolution: This issue was resolved in KB4512941 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
| Initiating a Remote Desktop connection may result in black screen When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU). Affected platforms:
Resolution: This issue was resolved in KB4512941. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 12, 2019 04:42 PM PT |
| Devices starting using PXE from a WDS or Configuration Manager servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager might fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503293 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512941. Back to top | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 10, 2019 02:51 PM PT |
| Details | Originating update | Status | History |
| Intermittent loss of Wi-Fi connectivity Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM). To safeguard your upgrade experience, we have applied a hold on devices with affected Qualcomm driver from being offered Windows 10, version 1903 or Windows 10, version 1909, until the updated driver is installed. Affected platforms:
Resolution: This issue was resolved with an updated Qualcomm Wifi driver and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1909 or Windows 10, version 1903. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved External | Last updated: November 22, 2019 04:10 PM PT Opened: May 21, 2019 07:13 AM PT |
| Unable to discover or connect to Bluetooth devices using some Realtek adapters Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Realtek. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Realtek Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated. Affected platforms:
Resolution: This issue was resolved with an updated driver for the affected Realtek Bluetooth radio and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1909 or Windows 10, version 1903. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved External | Last updated: November 15, 2019 05:59 PM PT Opened: May 21, 2019 07:29 AM PT |
| Intel Audio displays an intcdaud.sys notification Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in higher than normal battery drain. If you see an intcdaud.sys notification or “What needs your attention” notification when trying to update to Windows 10, version 1903, you have an affected Intel Audio Display device driver installed on your machine (intcdaud.sys, versions 10.25.0.3 through 10.25.0.8). To safeguard your update experience, we have applied a compatibility hold on devices with drivers from being offered Windows 10, version 1903 until updated device drivers have been installed. Affected platforms:
Resolution: This issue was resolved with updated drivers from your device manufacturer (OEM) or Intel. The safeguard hold has been removed. Note If you are still experiencing the issue described, please contact your device manufacturer (OEM). Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved External | Last updated: November 12, 2019 08:04 AM PT Opened: May 21, 2019 07:22 AM PT |
| Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903. Affected platforms:
Resolution: This issue was resolved in KB4512941. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: May 24, 2019 04:20 PM PT |
| Summary | Originating update | Status | Date resolved |
| Unable to create local users in Chinese, Japanese and Korean during device setup You might be unable to create users in Chinese, Japanese and Korean using Input Method Editor (IME) during OOBE. See details > | OS Build 18363.476 November 12, 2019 KB4524570 | Resolved KB4530684 | December 10, 2019 10:00 AM PT |
| Intermittent loss of Wi-Fi connectivity Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. See details > | OS Build 18363.476 November 12, 2019 KB4524570 | Resolved External | November 22, 2019 04:10 PM PT |
| Unable to discover or connect to Bluetooth devices using some Realtek adapters Microsoft has identified compatibility issues with some versions of Realtek Bluetooth radio drivers. See details > | OS Build 18363.476 November 12, 2019 KB4524570 | Resolved External | November 15, 2019 05:59 PM PT |
| Details | Originating update | Status | History |
| Unable to create local users in Chinese, Japanese and Korean during device setup When setting up a new Windows device using the Out of Box Experience (OOBE), you might be unable to create a local user when using Input Method Editor (IME). This issue might affect you if you are using the IME for Chinese, Japanese, or Korean languages. Note This issue does not affect using a Microsoft Account during OOBE. Affected platforms:
Resolution: This issue was resolved in KB4530684. Back to top | OS Build 18363.476 November 12, 2019 KB4524570 | Resolved KB4530684 | Resolved: December 10, 2019 10:00 AM PT Opened: October 29, 2019 05:15 PM PT |
| Details | Originating update | Status | History |
| Intermittent loss of Wi-Fi connectivity Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM). To safeguard your upgrade experience, we have applied a hold on devices with affected Qualcomm driver from being offered Windows 10, version 1903 or Windows 10, version 1909, until the updated driver is installed. Affected platforms:
Resolution: This issue was resolved with an updated Qualcomm Wifi driver and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1909 or Windows 10, version 1903. Back to top | OS Build 18363.476 November 12, 2019 KB4524570 | Resolved External | Last updated: November 22, 2019 04:10 PM PT Opened: May 21, 2019 07:13 AM PT |
| Unable to discover or connect to Bluetooth devices using some Realtek adapters Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Realtek. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Realtek Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated. Affected platforms:
Resolution: This issue was resolved with an updated driver for the affected Realtek Bluetooth radio and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1909 or Windows 10, version 1903. Back to top | OS Build 18363.476 November 12, 2019 KB4524570 | Resolved External | Last updated: November 15, 2019 05:59 PM PT Opened: May 21, 2019 07:29 AM PT |
| Summary | Originating update | Status | Date resolved |
| After installing an update and restarting, you might receive an error You might receive the error, “Failure to configure Windows updates. Reverting Changes.” or \"Failed\" in Update History. See details > | February 11, 2020 KB4537820 | Resolved | February 12, 2020 05:37 PM PT |
| Custom wallpaper displays as black Using a custom image set to \"Stretch\" might not display as expected. See details > | January 14, 2020 KB4534310 | Resolved KB4539601 | February 07, 2020 10:00 AM PT |
| MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from WU/WSUS. See details > | Resolved | January 23, 2020 02:08 PM PT | |
| Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | September 24, 2019 KB4516048 | Resolved KB4519976 | October 08, 2019 10:00 AM PT |
| You may receive an error when opening or using the Toshiba Qosmio AV Center Toshiba Qosmio AV Center may error when opening and you may also receive an error in Event Log related to cryptnet.dll. See details > | August 13, 2019 KB4512506 | Resolved KB4516048 | September 24, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| After installing an update and restarting, you might receive an error After installing KB4537820 and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History. Affected platforms:
Resolution: This is expected in the following circumstances:
If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the \"How to get this update\" section of this article. Back to top | February 11, 2020 KB4537820 | Resolved | Resolved: February 12, 2020 05:37 PM PT Opened: February 12, 2020 03:47 PM PT |
| Details | Originating update | Status | History |
| Custom wallpaper displays as black After installing KB4534310, your desktop wallpaper when set to \"Stretch\" might display as black. Affected platforms:
Resolution: This issue was resolved in KB4539601, if you are using Monthly Rollups. If you are using Security Only updates, see KB4539602. These updates are available for all customers running Windows 7 SP1 and Windows Server 2008 R2 SP1. Back to top | January 14, 2020 KB4534310 | Resolved KB4539601 | Resolved: February 07, 2020 10:00 AM PT Opened: January 24, 2020 09:15 AM PT |
| Details | Originating update | Status | History |
| MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from Windows Update (WU), Windows Server Update Services (WSUS) or Configuration Manager and might be re-offered. If you use WU or WSUS, you might also receive the following error in the WindowsUpdate.log, “Misc WARNING: Digital Signatures on file C:\\Windows\\SoftwareDistribution\\Download\\XXXX are not trusted: Error 0x800b0109”. If you use Configuration Manager, you might also receive the following error in the WUAHandler.log, \"Failed to download updates to the WUAgent datastore. Error = 0x800b0109. WUAHandler 14/11/2019 16:33:23 980 (0x03D4)\". Note All Configuration Manager information also applies to System Center Configuration Manager and Microsoft Endpoint Configuration Manager. Affected platforms:
Resolution: This issue was resolved in the December 2019 release of Windows Malicious Software Removal Tool (MSRT). Back to top | Resolved | Resolved: January 23, 2020 02:08 PM PT Opened: November 15, 2019 05:59 PM PT |
| Details | Originating update | Status | History |
| Intermittent issues when printing Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
Note This issue also affects the Internet Explorer Cumulative Update KB4522007, release September 23, 2019. Affected platforms:
Resolution: This issue was resolved in KB4519976. If you are using Security Only updates, see KB4519974 for resolving KB for your platform. Back to top | September 24, 2019 KB4516048 | Resolved KB4519976 | Resolved: October 08, 2019 10:00 AM PT Opened: September 30, 2019 06:26 PM PT |
| You may receive an error when opening or using the Toshiba Qosmio AV Center After installing KB4512506, you may receive an error when opening or using the Toshiba Qosmio AV Center. You may also receive an error in Event Log related to cryptnet.dll. Affected platforms:
Resolution: This issue was resolved in KB4516048. Back to top | August 13, 2019 KB4512506 | Resolved KB4516048 | Resolved: September 24, 2019 10:00 AM PT Opened: September 10, 2019 09:48 AM PT |
| Summary | Originating update | Status | Date resolved |
| Printing from 32-bit apps might fail on a 64-bit OS When attempting to print, you may receive an error or the application may stop responding or close. See details > | August 13, 2019 KB4512489 | Resolved KB4525250 | November 12, 2019 10:00 AM PT |
| Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | September 24, 2019 KB4516041 | Resolved KB4520005 | October 08, 2019 10:00 AM PT |
| Windows RT 8.1 devices may have issues opening Internet Explorer 11 On Windows RT 8.1 devices, Internet Explorer 11 may not open and you may receive an error. See details > | September 10, 2019 KB4516067 | Resolved KB4516041 | September 24, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Printing from 32-bit apps might fail on a 64-bit OS When attempting to print from a 32-bit app on a 64-bit operating system (OS), you may receive an error, or the application may stop responding or close. Note This issue only affects the 64-bit Security Only updates listed and does not affect any Monthly Rollup. Affected platforms:
Resolution: This issue is resolved in KB4525250. However, the issue occurs when you install only KB4512489 (released on August 13, 2019) without installing KB4507457, the previous Security Only update (released July 9, 2019). Reminder When using the Security Only updates, you must install the latest and all previous Security Only updates to ensure that the device contains all resolved security vulnerabilities. Back to top | August 13, 2019 KB4512489 | Resolved KB4525250 | Resolved: November 12, 2019 10:00 AM PT Opened: November 27, 2019 04:02 PM PT |
| Details | Originating update | Status | History |
| Intermittent issues when printing Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
Note This issue also affects the Internet Explorer Cumulative Update KB4522007, release September 23, 2019. Affected platforms:
Resolution: This issue was resolved in KB4520005. If you are using Security Only updates, see KB4519974 for resolving KB for your platform. Back to top | September 24, 2019 KB4516041 | Resolved KB4520005 | Resolved: October 08, 2019 10:00 AM PT Opened: September 30, 2019 06:26 PM PT |
| Windows RT 8.1 devices may have issues opening Internet Explorer 11 On Windows 8.1 RT devices, Internet Explorer 11 may not open and you may receive the error, \"C:\\Program Files\\Internet Explorer\\iexplore.exe: A certificate was explicitly revoked by its issuer.\" Affected platforms:
Resolution: This issue was resolved in KB4516041. Back to top | September 10, 2019 KB4516067 | Resolved KB4516041 | Resolved: September 24, 2019 10:00 AM PT Opened: September 13, 2019 05:25 PM PT |
| Summary | Originating update | Status | Date resolved |
| After installing an update and restarting, you might receive an error You might receive the error, “Failure to configure Windows updates. Reverting Changes.” or \"Failed\" in Update History. See details > | February 11, 2020 KB4537810 | Resolved | February 12, 2020 05:37 PM PT |
| MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from WU/WSUS. See details > | Resolved | January 23, 2020 02:08 PM PT | |
| Issues manually installing updates by double-clicking the .msu file You may encounter issues manually installing updates by double-clicking the .msu file and may receive an error. See details > | September 10, 2019 KB4474419 | Resolved KB4474419 | September 23, 2019 10:00 AM PT |
| Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | September 24, 2019 KB4516030 | Resolved KB4520002 | October 08, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| After installing an update and restarting, you might receive an error After installing KB4537810 and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History. Affected platforms:
Resolution: This is expected in the following circumstances:
If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the \"How to get this update\" section of this article. Back to top | February 11, 2020 KB4537810 | Resolved | Resolved: February 12, 2020 05:37 PM PT Opened: February 12, 2020 03:47 PM PT |
| Details | Originating update | Status | History |
| MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from Windows Update (WU), Windows Server Update Services (WSUS) or Configuration Manager and might be re-offered. If you use WU or WSUS, you might also receive the following error in the WindowsUpdate.log, “Misc WARNING: Digital Signatures on file C:\\Windows\\SoftwareDistribution\\Download\\XXXX are not trusted: Error 0x800b0109”. If you use Configuration Manager, you might also receive the following error in the WUAHandler.log, \"Failed to download updates to the WUAgent datastore. Error = 0x800b0109. WUAHandler 14/11/2019 16:33:23 980 (0x03D4)\". Note All Configuration Manager information also applies to System Center Configuration Manager and Microsoft Endpoint Configuration Manager. Affected platforms:
Resolution: This issue was resolved in the December 2019 release of Windows Malicious Software Removal Tool (MSRT). Back to top | Resolved | Resolved: January 23, 2020 02:08 PM PT Opened: November 15, 2019 05:59 PM PT |
| Details | Originating update | Status | History |
| Issues manually installing updates by double-clicking the .msu file After installing the SHA-2 update (KB4474419) released on September 10, 2019, you may encounter issues manually installing updates by double-clicking on the .msu file and may receive the error, \"Installer encountered an error: 0x80073afc. The resource loader failed to find MUI file.\" Affected platforms:
Workaround: Open a command prompt and use the following command (replacing <msu location> with the actual location and filename of the update): wusa.exe <msu location> /quiet Resolution: This issue is resolved in KB4474419 released October 8, 2019. It will install automatically from Windows Update and Windows Server Update Services (WSUS). If you need to install this update manually, you will need to use the workaround above. Note If you previously installed KB4474419 released September 23, 2019, then you already have the latest version of this update and do not need to reinstall. Back to top | September 10, 2019 KB4474419 | Resolved KB4474419 | Resolved: September 23, 2019 10:00 AM PT Opened: September 20, 2019 04:57 PM PT |
| Intermittent issues when printing Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
Note This issue also affects the Internet Explorer Cumulative Update KB4522007, release September 23, 2019. Affected platforms:
Resolution: This issue was resolved in KB4520002. If you are using Security Only updates, see KB4519974 for resolving KB for your platform. Back to top | September 24, 2019 KB4516030 | Resolved KB4520002 | Resolved: October 08, 2019 10:00 AM PT Opened: September 30, 2019 06:26 PM PT |
| Summary | Originating update | Status | Date resolved |
| Printing from 32-bit apps might fail on a 64-bit OS When attempting to print, you may receive an error or the application may stop responding or close. See details > | August 13, 2019 KB4512482 | Resolved KB4525253 | November 12, 2019 10:00 AM PT |
| Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | September 24, 2019 KB4516069 | Resolved KB4520007 | October 08, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Printing from 32-bit apps might fail on a 64-bit OS When attempting to print from a 32-bit app on a 64-bit operating system (OS), you may receive an error, or the application may stop responding or close. Note This issue only affects the 64-bit Security Only updates listed and does not affect any Monthly Rollup. Affected platforms:
Resolution: This issue is resolved in KB4525253. However, the issue occurs when you install only KB4512482 (released on August 13, 2019) without installing KB4507447, the previous Security Only update (released July 9, 2019). Reminder When using the Security Only updates, you must install the latest and all previous Security Only updates to ensure that the device contains all resolved security vulnerabilities. Back to top | August 13, 2019 KB4512482 | Resolved KB4525253 | Resolved: November 12, 2019 10:00 AM PT Opened: November 27, 2019 04:02 PM PT |
| Details | Originating update | Status | History |
| Intermittent issues when printing Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
Note This issue also affects the Internet Explorer Cumulative Update KB4522007, release September 23, 2019. Affected platforms:
Resolution: This issue was resolved in KB4520007. If you are using Security Only updates, see KB4519974 for resolving KB for your platform. Back to top | September 24, 2019 KB4516069 | Resolved KB4520007 | Resolved: October 08, 2019 10:00 AM PT Opened: September 30, 2019 06:26 PM PT |
| Summary | Originating update | Status | Last updated |
| You might encounter issues with KB4502496 You might encounter issues trying to install or after installing KB4502496 See details > | N/A February 11, 2020 KB4502496 | Mitigated | February 15, 2020 01:22 AM PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | OS Build 10240.18368 October 08, 2019 KB4520011 | Mitigated External | November 05, 2019 03:36 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). See details > | OS Build 10240.18094 January 08, 2019 KB4480962 | Mitigated | April 25, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| You might encounter issues with KB4502496 You might encounter issues trying to install or after installing KB4502496. Affected platforms:
Workaround: To help a sub-set of affected devices, the standalone security update (KB4502496) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates. If this update is installed and you are experiencing issues, you can uninstall this update.
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4502496 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| Details | Originating update | Status | History |
| TLS connections might fail or timeout Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Next Steps: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. Back to top | OS Build 10240.18368 October 08, 2019 KB4520011 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
| Details | Originating update | Status | History |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Affected platforms:
Workaround: Do one of the following:
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 10240.18094 January 08, 2019 KB4480962 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
| Summary | Originating update | Status | Last updated |
| “Reset this PC” feature might fail “Reset this PC” feature is also called “Push Button Reset” or PBR. See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244 See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | OS Build 14393.3274 October 08, 2019 KB4519998 | Mitigated External | November 05, 2019 03:36 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). See details > | OS Build 14393.2724 January 08, 2019 KB4480961 | Mitigated | April 25, 2019 02:00 PM PT |
| Cluster service may fail if the minimum password length is set to greater than 14 The cluster service may fail to start if “Minimum Password Length” is configured with greater than 14 characters. See details > | OS Build 14393.2639 November 27, 2018 KB4467684 | Mitigated | April 25, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| “Reset this PC” feature might fail Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”. Affected platforms:
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update. If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244. Affected platforms:
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates. If this update is installed and you are experiencing issues, you can uninstall this update.
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| Details | Originating update | Status | History |
| TLS connections might fail or timeout Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Next Steps: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. Back to top | OS Build 14393.3274 October 08, 2019 KB4519998 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
| Details | Originating update | Status | History |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Affected platforms:
Workaround: Do one of the following:
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 14393.2724 January 08, 2019 KB4480961 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Cluster service may fail if the minimum password length is set to greater than 14 After installing KB4467684, the cluster service may fail to start with the error \"2245 (NERR_PasswordTooShort)\" if the Group Policy \"Minimum Password Length\" is configured with greater than 14 characters. Affected platforms:
Workaround: Set the domain default \"Minimum Password Length\" policy to less than or equal to 14 characters. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 14393.2639 November 27, 2018 KB4467684 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: November 27, 2018 10:00 AM PT |
| Summary | Originating update | Status | Last updated |
| “Reset this PC” feature might fail “Reset this PC” feature is also called “Push Button Reset” or PBR. See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244 See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | OS Build 16299.1451 October 08, 2019 KB4520004 | Mitigated External | November 05, 2019 03:36 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). See details > | OS Build 16299.904 January 08, 2019 KB4480978 | Mitigated | April 25, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| “Reset this PC” feature might fail Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”. Affected platforms:
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update. If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244. Affected platforms:
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates. If this update is installed and you are experiencing issues, you can uninstall this update.
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| Details | Originating update | Status | History |
| TLS connections might fail or timeout Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Next Steps: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. Back to top | OS Build 16299.1451 October 08, 2019 KB4520004 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
| Details | Originating update | Status | History |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Affected platforms:
Workaround: Do one of the following:
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 16299.904 January 08, 2019 KB4480978 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
Current status as of November 12, 2019: Windows 10, version 1803 (the April 2018 Update) Home and Pro editions have reached end of service. For Windows 10 devices that are at, or within several months of reaching end of service, Windows Update will automatically initiate a feature update (with users having the ability to choose a convenient time); keeping those devices supported and receiving the monthly updates that are critical to device security and ecosystem health.
- |
| Summary | Originating update | Status | Last updated |
| “Reset this PC” feature might fail “Reset this PC” feature is also called “Push Button Reset” or PBR. See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244 See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | OS Build 17134.1069 October 08, 2019 KB4520008 | Mitigated External | November 05, 2019 03:36 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). See details > | OS Build 17134.523 January 08, 2019 KB4480966 | Mitigated | April 25, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| “Reset this PC” feature might fail Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”. Affected platforms:
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update. If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244. Affected platforms:
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates. If this update is installed and you are experiencing issues, you can uninstall this update.
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| Details | Originating update | Status | History |
| TLS connections might fail or timeout Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Next Steps: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. Back to top | OS Build 17134.1069 October 08, 2019 KB4520008 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
| Details | Originating update | Status | History |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Affected platforms:
Workaround: Do one of the following:
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 17134.523 January 08, 2019 KB4480966 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
Current status as of November 12, 2019: Windows 10, version 1809 is designated for broad deployment. The recommended servicing status is Semi-Annual Channel.
- |
| Summary | Originating update | Status | Last updated |
| “Reset this PC” feature might fail “Reset this PC” feature is also called “Push Button Reset” or PBR. See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244 See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | OS Build 17763.805 October 08, 2019 KB4519338 | Mitigated External | November 05, 2019 03:36 PM PT |
| Devices with some Asian language packs installed may receive an error Devices with Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.\" See details > | OS Build 17763.437 April 09, 2019 KB4493509 | Mitigated | May 03, 2019 10:59 AM PT |
| Certain operations performed on a Cluster Shared Volume may fail Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). See details > | OS Build 17763.253 January 08, 2019 KB4480116 | Mitigated | April 09, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| “Reset this PC” feature might fail Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”. Affected platforms:
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update. If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244. Affected platforms:
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates. If this update is installed and you are experiencing issues, you can uninstall this update.
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| Details | Originating update | Status | History |
| TLS connections might fail or timeout Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Next Steps: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. Back to top | OS Build 17763.805 October 08, 2019 KB4519338 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
| Details | Originating update | Status | History |
| Devices with some Asian language packs installed may receive an error After installing the April 2019 Cumulative Update (KB4493509), devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.\" Affected platforms:
Workaround:
Note: If reinstalling the language pack does not mitigate the issue, reset your PC as follows:
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 17763.437 April 09, 2019 KB4493509 | Mitigated | Last updated: May 03, 2019 10:59 AM PT Opened: May 02, 2019 04:36 PM PT |
| Details | Originating update | Status | History |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Affected platforms:
Workaround: Do one of the following:
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 17763.253 January 08, 2019 KB4480116 | Mitigated | Last updated: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
Current status as of November 12, 2019: Windows 10, version 1903 (the May 2019 Update) is designated ready for broad deployment for all users via Windows Update. We recommend commercial customers running earlier versions of Windows 10 begin broad deployments of Windows 10, version 1903 in their organizations. Note Follow @WindowsUpdate to find out when new content is published to the release information dashboard.
- |
| Summary | Originating update | Status | Last updated |
| “Reset this PC” feature might fail “Reset this PC” feature is also called “Push Button Reset” or PBR. See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244 See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| Issues with some older versions of Avast and AVG anti-virus products Microsoft and Avast has identified compatibility issues with some versions of Avast and AVG Antivirus. See details > | N/A | Mitigated External | November 25, 2019 05:25 PM PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | OS Build 18362.418 October 08, 2019 KB4517389 | Mitigated External | November 05, 2019 03:36 PM PT |
| Details | Originating update | Status | History |
| “Reset this PC” feature might fail Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”. Affected platforms:
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update. If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244. Affected platforms:
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates. If this update is installed and you are experiencing issues, you can uninstall this update.
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| Details | Originating update | Status | History |
| Issues with some older versions of Avast and AVG anti-virus products Microsoft and Avast has identified compatibility issues with some older versions of Avast Antivirus and AVG Antivirus that might still be installed by a small number of users. Any application from Avast or AVG that contains Antivirus version 19.5.4444.567 or earlier is affected. To safeguard your upgrade experience, we have applied a hold on devices with affected Avast and AVG Antivirus from being offered or installing Windows 10, version 1903 or Windows 10, version 1909, until the application is updated. Affected platforms:
Workaround: Before updating to Windows 10, version 1903 or Windows 10, version 1909, you will need to download and install an updated version of your Avast or AVG application. Guidance for Avast and AVG customers can be found in the following support articles: Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new version of your Avast or AVG application has been installed and the Windows 10, version 1903 or Windows 10, version 1909 feature update has been automatically offered to you. Back to top | N/A | Mitigated External | Last updated: November 25, 2019 05:25 PM PT Opened: November 22, 2019 04:10 PM PT |
| TLS connections might fail or timeout Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Next Steps: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. Back to top | OS Build 18362.418 October 08, 2019 KB4517389 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
Current status as of January 21, 2020: Windows 10, version 1909 is available for any user on a recent version of Windows 10 who manually selects “Check for updates” via Windows Update. The recommended servicing status is Semi-Annual Channel. We are starting the next phase in our controlled approach to automatically initiate a feature update for an increased number of devices running the October 2018 Update (Windows 10, version 1809) Home and Pro editions, keeping those devices supported and receiving the monthly updates that are critical to device security and ecosystem health. Our rollout process starts several months in advance of the end of service date to provide adequate time for a smooth update process. For information on how users running Windows 10, version 1903 can update to Windows 10, version 1909 in a new, streamlined way, see this post. Note follow @WindowsUpdate on Twitter to find out when new content is published to the release information dashboard.
- |
| Summary | Originating update | Status | Last updated |
| “Reset this PC” feature might fail “Reset this PC” feature is also called “Push Button Reset” or PBR. See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244 See details > | N/A February 11, 2020 KB4524244 | Mitigated | February 15, 2020 01:22 AM PT |
| Issues with some older versions of Avast and AVG anti-virus products Microsoft and Avast has identified compatibility issues with some versions of Avast and AVG Antivirus. See details > | N/A | Mitigated External | November 25, 2019 05:25 PM PT |
| Details | Originating update | Status | History |
| “Reset this PC” feature might fail Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”. Affected platforms:
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update. If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| You might encounter issues with KB4524244 You might encounter issues trying to install or after installing KB4524244. Affected platforms:
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates. If this update is installed and you are experiencing issues, you can uninstall this update.
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | N/A February 11, 2020 KB4524244 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| Details | Originating update | Status | History |
| Issues with some older versions of Avast and AVG anti-virus products Microsoft and Avast has identified compatibility issues with some older versions of Avast Antivirus and AVG Antivirus that might still be installed by a small number of users. Any application from Avast or AVG that contains Antivirus version 19.5.4444.567 or earlier is affected. To safeguard your upgrade experience, we have applied a hold on devices with affected Avast and AVG Antivirus from being offered or installing Windows 10, version 1903 or Windows 10, version 1909, until the application is updated. Affected platforms:
Workaround: Before updating to Windows 10, version 1903 or Windows 10, version 1909, you will need to download and install an updated version of your Avast or AVG application. Guidance for Avast and AVG customers can be found in the following support articles: Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new version of your Avast or AVG application has been installed and the Windows 10, version 1903 or Windows 10, version 1909 feature update has been automatically offered to you. Back to top | N/A | Mitigated External | Last updated: November 25, 2019 05:25 PM PT Opened: November 22, 2019 04:10 PM PT |
| Summary | Originating update | Status | Last updated |
| After installing an update and restarting, you might receive an error You might receive the error, “Failure to configure Windows updates. Reverting Changes.” or \"Failed\" in Update History. See details > | February 11, 2020 KB4537820 | Resolved | February 12, 2020 05:37 PM PT |
| Custom wallpaper displays as black Using a custom image set to \"Stretch\" might not display as expected. See details > | January 14, 2020 KB4534310 | Resolved KB4539601 | February 07, 2020 10:00 AM PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | October 08, 2019 KB4519976 | Mitigated External | November 05, 2019 03:36 PM PT |
| IA64 and x64 devices may fail to start after installing updates After installing updates released on or after August 13, 2019, IA64 and x64 devices using EFI Boot may fail to start. See details > | August 13, 2019 KB4512506 | Mitigated | August 17, 2019 12:59 PM PT |
| Details | Originating update | Status | History |
| After installing an update and restarting, you might receive an error After installing KB4537820 and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History. Affected platforms:
Resolution: This is expected in the following circumstances:
If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the \"How to get this update\" section of this article. Back to top | February 11, 2020 KB4537820 | Resolved | Resolved: February 12, 2020 05:37 PM PT Opened: February 12, 2020 03:47 PM PT |
| Details | Originating update | Status | History |
| Custom wallpaper displays as black After installing KB4534310, your desktop wallpaper when set to \"Stretch\" might display as black. Affected platforms:
Resolution: This issue was resolved in KB4539601, if you are using Monthly Rollups. If you are using Security Only updates, see KB4539602. These updates are available for all customers running Windows 7 SP1 and Windows Server 2008 R2 SP1. Back to top | January 14, 2020 KB4534310 | Resolved KB4539601 | Resolved: February 07, 2020 10:00 AM PT Opened: January 24, 2020 09:15 AM PT |
| Details | Originating update | Status | History |
| TLS connections might fail or timeout Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Next Steps: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. Back to top | October 08, 2019 KB4519976 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
| Details | Originating update | Status | History |
| IA64 and x64 devices may fail to start after installing updates IA64 devices (in any configuration) and x64 devices using EFI boot that were provisioned after the July 9th updates and/or skipped the recommended update (KB3133977), may fail to start with the following error: \"File: \\Windows\\system32\\winload.efi Status: 0xc0000428 Info: Windows cannot verify the digital signature for this file.\" Affected platforms:
Take Action: To resolve this issue please follow the steps outlined in the SHA-2 support FAQ article for error code 0xc0000428. Back to top | August 13, 2019 KB4512506 | Mitigated | Last updated: August 17, 2019 12:59 PM PT Opened: August 13, 2019 08:34 AM PT |
| Summary | Originating update | Status | Last updated |
| You might encounter issues with KB4502496 You might encounter issues trying to install or after installing KB4502496 See details > | February 11, 2020 KB4502496 | Mitigated | February 15, 2020 01:22 AM PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | October 08, 2019 KB4520005 | Mitigated External | November 05, 2019 03:36 PM PT |
| Japanese IME doesn't show the new Japanese Era name as a text input option With previous dictionary updates installed, the Japanese IME doesn't show the new Japanese Era name as an input option. See details > | April 25, 2019 KB4493443 | Mitigated | May 15, 2019 05:53 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). See details > | January 08, 2019 KB4480963 | Mitigated | April 25, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| You might encounter issues with KB4502496 You might encounter issues trying to install or after installing KB4502496. Affected platforms:
Workaround: To help a sub-set of affected devices, the standalone security update (KB4502496) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates. If this update is installed and you are experiencing issues, you can uninstall this update.
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | February 11, 2020 KB4502496 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| Details | Originating update | Status | History |
| TLS connections might fail or timeout Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Next Steps: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. Back to top | October 08, 2019 KB4520005 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
| Details | Originating update | Status | History |
| Japanese IME doesn't show the new Japanese Era name as a text input option If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option. Affected platforms:
Workaround: If you see any of the previous dictionary updates listed below, uninstall it from Programs and features > Uninstall or change a program. New words that were in previous dictionary updates are also in this update.
Back to top | April 25, 2019 KB4493443 | Mitigated | Last updated: May 15, 2019 05:53 PM PT Opened: May 15, 2019 05:53 PM PT |
| Details | Originating update | Status | History |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Affected platforms:
Workaround: Do one of the following:
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | January 08, 2019 KB4480963 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
| Summary | Originating update | Status | Last updated |
| After installing an update and restarting, you might receive an error You might receive the error, “Failure to configure Windows updates. Reverting Changes.” or \"Failed\" in Update History. See details > | February 11, 2020 KB4537810 | Resolved | February 12, 2020 05:37 PM PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | October 08, 2019 KB4520002 | Mitigated External | November 05, 2019 03:36 PM PT |
| Details | Originating update | Status | History |
| After installing an update and restarting, you might receive an error After installing KB4537810 and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History. Affected platforms:
Resolution: This is expected in the following circumstances:
If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the \"How to get this update\" section of this article. Back to top | February 11, 2020 KB4537810 | Resolved | Resolved: February 12, 2020 05:37 PM PT Opened: February 12, 2020 03:47 PM PT |
| Details | Originating update | Status | History |
| TLS connections might fail or timeout Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Next Steps: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. Back to top | October 08, 2019 KB4520002 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
| Summary | Originating update | Status | Last updated |
| You might encounter issues with KB4502496 You might encounter issues trying to install or after installing KB4502496 See details > | February 11, 2020 KB4502496 | Mitigated | February 15, 2020 01:22 AM PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | October 08, 2019 KB4520007 | Mitigated External | November 05, 2019 03:36 PM PT |
| Japanese IME doesn't show the new Japanese Era name as a text input option With previous dictionary updates installed, the Japanese IME doesn't show the new Japanese Era name as an input option. See details > | April 25, 2019 KB4493462 | Mitigated | May 15, 2019 05:53 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). See details > | January 08, 2019 KB4480975 | Mitigated | April 25, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| You might encounter issues with KB4502496 You might encounter issues trying to install or after installing KB4502496. Affected platforms:
Workaround: To help a sub-set of affected devices, the standalone security update (KB4502496) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates. If this update is installed and you are experiencing issues, you can uninstall this update.
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update. Back to top | February 11, 2020 KB4502496 | Mitigated | Last updated: February 15, 2020 01:22 AM PT Opened: February 15, 2020 12:02 AM PT |
| Details | Originating update | Status | History |
| TLS connections might fail or timeout Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Next Steps: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. Back to top | October 08, 2019 KB4520007 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
| Details | Originating update | Status | History |
| Japanese IME doesn't show the new Japanese Era name as a text input option If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option. Affected platforms:
Workaround: If you see any of the previous dictionary updates listed below, uninstall it from Programs and features > Uninstall or change a program. New words that were in previous dictionary updates are also in this update.
Back to top | April 25, 2019 KB4493462 | Mitigated | Last updated: May 15, 2019 05:53 PM PT Opened: May 15, 2019 05:53 PM PT |
| Details | Originating update | Status | History |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Affected platforms:
Workaround: Do one of the following:
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | January 08, 2019 KB4480975 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
| Message | Date |
| February 2020 Windows 10, version 1909 and Windows 10, version 1903 \"D\" optional release is available The February 2020 optional monthly “D” release for Windows 10, version 1909 and Windows 10, version 1903 is now available. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. Follow @WindowsUpdate for the latest on the availability of this release. | February 27, 2020 01:30 PM PT |
| February 2020 Windows \"C\" optional release is available. The February 2020 optional monthly “C” release for all supported versions of Windows prior to Windows 10, version 1903 is now available. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. Follow @WindowsUpdate for the latest on the availability of this release. | February 25, 2020 08:00 AM PT |
| Status of February 2020 “C” release The optional monthly “C” release for February 2020 for all supported versions of Windows and Windows Server prior to Windows 10, version 1903 and Windows Server, version 1903 will be available in the near term. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. Follow @WindowsUpdate for the latest on the availability of this release. | February 21, 2020 12:00 PM PT |
| Compatibility issue with some Windows Server container images If you are encountering issues with Windows Server container images, please see KB4542617. | February 13, 2020 03:21 PM PT |
| Take action: February 2020 security update available for all supported versions of Windows The February 2020 security update release, referred to as our “B” release, is now available for Windows 10, version 1909 and all supported versions of Windows. We recommend that you install these updates promptly. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. To be informed about the latest updates and releases, follow us on Twitter @WindowsUpdate. | February 11, 2020 08:00 AM PT |
| Take action: ESU security updates available for Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Server 2008 SP2 Windows 7 SP1, Windows Server 2008 R2 SP1, and Windows Server 2008 SP2 reached end of support on January 14, 2020. For customers who have purchased Extended Security Updates (ESU), the first monthly ESU security updates are now available. If your organization has not yet been able to complete your transition to Windows 10, Windows Server 2016, or Windows Server 2019 and want to continue to receive security updates for your current version of Windows, you will need to purchase Extended Security Updates. For information on how to do so, please see How to get Extended Security Updates for eligible Windows devices, Windows 7 ESU frequently ask questions, and Windows Server 2008 R2 SP1 and Windows Server 2008 SP2 ESU frequently asked questions. We recommend ESU customers review the applicable KB article below for prerequisites and other important information you will need to deploy these updates. The following updates were released today for Windows Server 2008 SP2:
The following updates were released today for Windows 7 SP1 and Windows Server 2008 R2 SP1: | February 11, 2020 08:00 AM PT |
| Resolved: Windows Search shows blank box We are aware of a temporary server-side issue causing Windows search to show a blank box. This issue has been resolved for most users and in some cases, you might need to restart your device. We are working diligently to fully resolve the issue and will provide an update once resolved. This issue was resolved at 12:00 PM PST. If you are still experiencing issues, please restart your device. In rare cases, to mitigate this issue you may need to manually end the SearchUI.exe or SearchApp.exe process via Task Manager. (To locate these processes, select CTRL + Shift + Esc then select the Details tab.) If you have restarted and tried the previous mitigations and are still encountering issues with Windows Search, you are not experiencing the issue described here. Please see Fix problems in Windows Search for other mitigations. | February 05, 2020 12:00 PM PT |
| January 2020 Windows 10, version 1909 \"D\" optional release is available. The January 2020 optional monthly “D” release for Windows 10, version 1909 and Windows 10, version 1903 is now available. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. Follow @WindowsUpdate for the latest on the availability of this release. | January 28, 2020 08:00 AM PT |
| January 2020 Windows \"C\" optional release is available. The January 2020 optional monthly “C” release for all supported versions of Windows is now available. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. Follow @WindowsUpdate for the latest on the availability of this release. | January 23, 2020 12:00 PM PT |
| Windows 7 has reached end of support Windows 7 reached end of support on January 14, 2020. If your organization has not yet been able to complete your transition from Windows 7 to Windows 10, and want to continue to receive security updates while you complete your upgrade projects, please read How to get Extended Security Updates for eligible Windows devices. For more information on end of service dates for currently supported versions of Windows 10, see the Windows lifecycle fact sheet. | January 15, 2020 10:00 AM PT |
| Take action: January 2020 security update available for all supported versions of Windows The January 2020 security update release, referred to as our “B” release, is now available for Windows 10, version 1909 and all supported versions of Windows. We recommend that you install these updates promptly. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. To be informed about the latest updates and releases, follow us on Twitter @WindowsUpdate. | January 14, 2020 08:00 AM PT |
| Advisory: Windows CryptoAPI certificate validation vulnerability On January 14, 2020, Microsoft released security updates to address an elliptic-curve cryptography (ECC) certificate validation issue in the Windows CryptoAPI. This vulnerability applies to all versions of the Windows 10 operating system, client and server. While we have not observed an attack exploiting this vulnerability, we recommend that you apply this update to all of your Windows 10 devices with priority. Here is what you need to know:
If you are running an unsupported version of Windows 10, we recommend that you upgrade to the current version of Windows 10 to benefit from the latest security protections. For more information about this vulnerability, see the Microsoft Security Guidance for CVE-2020-0601 and the Microsoft Security Response Center blog, January 2020 Security Updates: CVE-2020-0601. | January 14, 2020 08:00 AM PT |
| Take action: December 2019 security update available for all supported versions of Windows The December 2019 security update release, referred to as our “B” release, is now available for Windows 10, version 1909 and all supported versions of Windows. We recommend that you install these updates promptly. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. To be informed about the latest updates and releases, follow us on Twitter @WindowsUpdate. | December 10, 2019 08:00 AM PT |
| Timing of Windows 10 optional update releases (December 2019) For the balance of this calendar year, there will be no optional non-security “C” and “D” releases for Windows 10. The \"C\" releases normally target the third week of the month, with \"D\" releases targeting the fourth week. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. | December 10, 2019 08:00 AM PT |
| Windows 10, version 1909 now available Learn how to get Windows 10, version 1909 (the November 2019 Update), and explore how we’ve worked to make this a great experience for all devices, including a new, streamlined (and fast) update experience for devices updating directly from the May 2019 Update. | November 12, 2019 10:00 AM PT |
| Windows 10, version 1909 delivery options Learn how devices running Windows 10, version 1903 can update to Windows 10, version 1909 using the same servicing technology used to deliver monthly quality updates, resulting in a single restart and reducing update-related downtime. | November 12, 2019 10:00 AM PT |
| What’s new for IT pros in Windows 10, version 1909 Explore the latest features for IT, get information about media availability and related tools, and find answers to frequently asked questions. | November 12, 2019 10:00 AM PT |
| Take action: November 2019 security update available for all supported versions of Windows The November 2019 security update release, referred to as our “B” release, is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. To be informed about the latest updates and releases, follow us on Twitter @WindowsUpdate. | November 12, 2019 10:00 AM PT |
| Timing of Windows 10 optional update releases (November/December 2019) For the balance of this calendar year, there will be no optional non-security “C” and “D” releases for Windows 10. The \"C\" releases normally target the third week of the month, with \"D\" releases targeting the fourth week. Note There will be a December Security Update Tuesday release, as usual. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer | November 12, 2019 10:00 AM PT |
| Windows 10, version 1803 Home and Pro editions have reached end of service Windows 10, version 1803 (the April 2018 Update) Home and Pro editions have reached end of service. For Windows 10 devices that are at, or within several months of reaching end of service, Windows Update will automatically initiate a feature update (with users having the ability to choose a convenient time); keeping those devices supported and receiving the monthly updates that are critical to device security and ecosystem health. For more information on end of service dates for currently supported versions of Windows 10, see the Windows lifecycle fact sheet. | November 12, 2019 10:00 AM PT |
| October 2019 Windows 10, version 1903 \"D\" optional release is available. The October 2019 optional monthly “D” release for Windows 10, version 1903 is now available. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. Follow @WindowsUpdate for the latest on the availability of this release. | October 24, 2019 08:00 AM PT |
| October 2019 Windows \"C\" optional release is available. The October 2019 optional monthly “C” release for all supported versions of Windows is now available. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. Follow @WindowsUpdate for the latest on the availability of this release. | October 15, 2019 09:59 AM PT |
| Windows 10, version 1703 has reached end of service Consumer and commercial editions of Windows 10, version 1703 have reached end of service. As devices running these editions are no longer receiving monthly security and quality updates containing protections from the latest security threats, we recommend that you update these devices to the latest version of Windows 10 immediately. For more information on end of service dates for currently supported versions of Windows 10, see the Windows lifecycle fact sheet. Note The Windows 10, version 1703 section will be removed from this dashboard on November 12, 2019. | October 09, 2019 12:00 PM PT |
| Take Action: October 2019 security update available for all supported versions of Windows The October 2019 security update release, referred to as our “B” release, is now available for Windows 10, version 1903 and all supported versions of Windows. We recommend that you install these updates promptly. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. To be informed about the latest updates and releases, follow us on Twitter @WindowsUpdate. | October 08, 2019 08:00 AM PT |
| Take action: Security update available for all supported versions of Windows On October 3, 2019, Microsoft expanded delivery of the out-of-band Internet Explorer scripting engine security vulnerability (CVE-2019-1367) update released on September 23, 2019 to Windows Update and Windows Server Update Services (WSUS). This is now a required security update for all supported versions of Windows as it includes the Internet Explorer scripting engine vulnerability mitigation and corrects a recent printing issue some users have experienced. All customers using Windows Update or WSUS will be offered this update automatically. We recommend that you install this update as soon as a possible, then restart your PC to fully apply the mitigations and help secure your devices. As with all cumulative updates, this update supersedes any preceding update. Note: This update does not replace the standard October 2019 monthly security update release, which is scheduled for October 8, 2019. | October 03, 2019 08:00 AM PT |
| September 2019 Windows 10, version 1903 \"D\" optional release is available The September 2019 optional monthly “D” release for Windows 10, version 1903 is now available. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. Follow @WindowsUpdate for the latest on the availability of this release. | September 26, 2019 02:00 PM PT |
| Status update: September 2019 Windows \"C\" optional release available The September 2019 optional monthly “C” release for all supported versions of Windows is now available. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. Follow @WindowsUpdate for the latest on the availability of this release. | September 24, 2019 08:10 AM PT |
| Plan for change: Windows Media Center Electronic Program Guide retiring in January 2020 Starting in January 2020, Microsoft is retiring its Electronic Program Guide (EPG) service for all versions of Windows Media Center. To continue receiving TV Program Guide information on your Windows Media Center, you’ll need to configure an alternate TV listing provider. | September 24, 2019 08:00 AM PT |
| Status of September 2019 “C” release The optional monthly “C” release for September 2019 for all supported versions of Windows and Windows Server prior to Windows 10, version 1903 and Windows Server, version 1903 will be available in the near term. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. Follow @WindowsUpdate for the latest on the availability of this release. | September 19, 2019 04:11 PM PT |
| Plan for change: End of service reminders for Windows 10, versions 1703 and 1803 The Enterprise and Education editions of Windows 10, version 1703 (the Creators Update) will reach end of service on October 8, 2019. The Home, Pro, Pro for Workstations, and IoT Core editions of Windows 10, version 1803 (the April 2018 Update) will reach end of service on November 12, 2019. We recommend that you update devices running these versions and editions to the latest version of Windows 10—Windows 10, version 1903—as soon as possible to help keep them protected and your environments secure. | September 13, 2019 03:23 PM PT |
| September 2019 security update available for all supported versions of Windows The September 2019 security update release, referred to as our “B” release, is now available for Windows 10, version 1903 and all supported versions of Windows. We recommend that you install these updates promptly. To be informed about the latest updates and releases, follow us on Twitter @WindowsUpdate. | September 10, 2019 09:34 AM PT |
| Status update: Windows 10, version 1903 \"D\" optional release available August 30th The August optional monthly “D” release for Windows 10, version 1903 is now available. Follow @WindowsUpdate for the latest on the availability of this release. | August 30, 2019 08:00 AM PT |
| Feature update install notification on Windows 10, version 1809 (the October 2018 Update) We've had reports on August 29th that some customers running Windows 10, version 1809 (the October 2018 Update) have received notification to install the latest feature update (version 1903) early. Updating remains in your control. To install the update, you must select one of the following options: \"Pick a Time\", \"Restart Tonight,\" or \"Restart Now\". If you are not ready to update at this time, simply dismiss the notification by clicking the arrow in the top right corner. If you have updated to Windows 10, version 1903 and would like to go back to your previous version, see the instructions here. | August 29, 2019 04:39 PM PT |
| Take Action: Internet Explorer 11 now available on Windows Update/WSUS for Windows Server 2012 and Windows Embedded 8 Standard Internet Explorer 11 (KB 4492872) is now available via Windows Update (WU) and Windows Server Update Services (WSUS) for commercial customers running Windows Server 2012 and Windows Embedded 8 Standard. For details about these changes and end of support for IE10, please refer to the IT Pro blog. | August 29, 2019 08:00 AM PT |
| Windows 10, version 1903 rollout begins The Windows 10 May 2019 Update (Windows 10, version 1903) is available today to commercial customers via Windows Server Update Services (WSUS), Windows Update for Business, and the Volume Licensing Service Center (VLSC)—and to end users who manually select “Check for updates.” We are slowly throttling up availability while we carefully monitor data and feedback. | May 21, 2019 10:00 AM PT |