| Summary | Originating update | Status | Date resolved |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 14393.3025 June 11, 2019 KB4503267 | Resolved KB4512495 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 14393.3144 August 13, 2019 KB4512517 | Resolved KB4512495 | August 17, 2019 02:00 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 updating. See details > | OS Build 14393.3115 July 16, 2019 KB4507459 | Resolved KB4512517 | August 13, 2019 10:00 AM PT |
| Internet Explorer 11 and apps using the WebBrowser control may fail to render JavaScript may fail to render as expected in Internet Explorer 11 and in apps using JavaScript or the WebBrowser control. See details > | OS Build 14393.3085 July 09, 2019 KB4507460 | Resolved KB4512517 | August 13, 2019 10:00 AM PT |
| End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup. See details > | OS Build 14393.2879 March 19, 2019 KB4489889 | Resolved KB4493470 | April 09, 2019 10:00 AM PT |
| MSXML6 may cause applications to stop responding MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). See details > | OS Build 14393.2724 January 08, 2019 KB4480961 | Resolved KB4493470 | April 09, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files. See details > | OS Build 14393.2791 February 12, 2019 KB4487026 | Resolved KB4489882 | March 12, 2019 10:00 AM PT |
| Internet Explorer may fail to load images Internet Explorer may fail to load images with a backslash (\\) in their relative source path. See details > | OS Build 14393.2791 February 12, 2019 KB4487026 | Resolved KB4487006 | February 19, 2019 02:00 PM PT |
| First character of the Japanese era name not recognized as an abbreviation The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. See details > | OS Build 14393.2759 January 17, 2019 KB4480977 | Resolved KB4487006 | February 19, 2019 02:00 PM PT |
| Custom URI schemes may not start corresponding application Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer. See details > | OS Build 14393.2848 March 12, 2019 KB4489882 | Resolved KB4493473 | April 25, 2019 02:00 PM PT |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. See details > | OS Build 14393.2791 February 12, 2019 KB4487026 | Resolved KB4487006 | February 19, 2019 02:00 PM PT |
| Issue hosting multiple terminal server sessions and a user logs off on Windows Server In some cases, Windows Server will stop working and restart when hosting multiple terminal server sessions and a user logs off. See details > | OS Build 14393.2828 February 19, 2019 KB4487006 | Resolved KB4489882 | March 12, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503267 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512495. Back to top | OS Build 14393.3025 June 11, 2019 KB4503267 | Resolved KB4512495 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 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 KB4507459. 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 KB4512517. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 14393.3115 July 16, 2019 KB4507459 | Resolved KB4512517 | Resolved: August 13, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
| Internet Explorer 11 and apps using the WebBrowser control may fail to render Internet Explorer 11 may fail to render some JavaScript after installing KB4507460. You may also have issues with apps using JavaScript or the WebBrowser control, such as the present PowerPoint feature of Skype Meeting Broadcast. Affected platforms:
Resolution: This issue was resolved in KB4512517. Back to top | OS Build 14393.3085 July 09, 2019 KB4507460 | Resolved KB4512517 | Resolved: August 13, 2019 10:00 AM PT Opened: July 26, 2019 04:58 PM PT |
| Details | Originating update | Status | History |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. Affected platforms:
Resolution: This issue is resolved in KB4493470. Back to top | OS Build 14393.2791 February 12, 2019 KB4487026 | Resolved KB4493470 | Resolved: April 09, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files After installing KB4487026, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files. Affected platforms:
Resolution: This issue is resolved in KB4489882. Back to top | OS Build 14393.2791 February 12, 2019 KB4487026 | Resolved KB4489882 | Resolved: March 12, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Internet Explorer may fail to load images After installing KB4487026, Internet Explorer may fail to load images with a backslash (\\) in their relative source path. Affected platforms:
Resolution: This issue is resolved in KB4487006. Back to top | OS Build 14393.2791 February 12, 2019 KB4487026 | Resolved KB4487006 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. Affected platforms:
Resolution: This issue is resolved in KB4487006. Back to top | OS Build 14393.2791 February 12, 2019 KB4487026 | Resolved KB4487006 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Issue hosting multiple terminal server sessions and a user logs off on Windows Server In some cases, Windows Server will stop working and restart when hosting multiple terminal server sessions and a user logs off. The faulting driver is win32kbase.sys. Affected platforms:
Resolution: This issue is resolved in KB4489882. Back to top | OS Build 14393.2828 February 19, 2019 KB4487006 | Resolved KB4489882 | Resolved: March 12, 2019 10:00 AM PT Opened: February 19, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| Internet Explorer 11 authentication issue with multiple concurrent logons After installing KB4480961, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
Affected platforms:
Resolution: This issue was resolved in KB4493470. Back to top | OS Build 14393.2724 January 08, 2019 KB4480961 | Resolved KB4493470 | Resolved: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
| MSXML6 may cause applications to stop responding After installing KB4480961, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings. Affected platforms:
Resolution: This issue was resolved in KB4493470. Back to top | OS Build 14393.2724 January 08, 2019 KB4480961 | Resolved KB4493470 | Resolved: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
| First character of the Japanese era name not recognized as an abbreviation After installing KB4480977, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Affected platforms:
Resolution: This issue is resolved in KB4487006. Back to top | OS Build 14393.2759 January 17, 2019 KB4480977 | Resolved KB4487006 | Resolved: February 19, 2019 02:00 PM PT Opened: January 17, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. Affected platforms:
Resolution: This issue is resolved in KB4493474. Back to top | OS Build 15063.1631 February 12, 2019 KB4487020 | Resolved KB4493474 | Resolved: April 09, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files After installing KB4487011, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files. Affected platforms:
Resolution: This issue is resolved in KB4489871. Back to top | OS Build 15063.1659 February 19, 2019 KB4487011 | Resolved KB4489871 | Resolved: March 12, 2019 10:00 AM PT Opened: February 19, 2019 02:00 PM PT |
| Internet Explorer may fail to load images After installing KB4487020, Internet Explorer may fail to load images with a backslash (\\) in their relative source path. Affected platforms:
Resolution: This issue is resolved in KB4487011. Back to top | OS Build 15063.1631 February 12, 2019 KB4487020 | Resolved KB4487011 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. Affected platforms:
Resolution: This issue is resolved in KB4487011. Back to top | OS Build 15063.1631 February 12, 2019 KB4487020 | Resolved KB4487011 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| MSXML6 may cause applications to stop responding After installing KB4480973, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings. Affected platforms:
Resolution: This issue was resolved in KB4493474. Back to top | OS Build 15063.1563 January 08, 2019 KB4480973 | Resolved KB4493474 | Resolved: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
| First character of the Japanese era name not recognized as an abbreviation After installing KB4480959, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Affected platforms:
Resolution: This issue is resolved in KB4487011. Back to top | OS Build 15063.1596 January 15, 2019 KB4480959 | Resolved KB4487011 | Resolved: February 19, 2019 02:00 PM PT Opened: January 15, 2019 10:00 AM PT |
| Summary | Originating update | Status | Date resolved |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 16299.1217 June 11, 2019 KB4503284 | Resolved KB4512494 | August 16, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 16299.1331 August 13, 2019 KB4512516 | Resolved KB4512494 | August 16, 2019 02:00 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 updating. See details > | OS Build 16299.1296 July 16, 2019 KB4507465 | Resolved KB4512516 | August 13, 2019 10:00 AM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | OS Build 16299.1217 June 11, 2019 KB4503284 | Resolved External | August 09, 2019 07:03 PM PT |
| End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. See details > | OS Build 16299.1059 March 19, 2019 KB4489890 | Resolved KB4493441 | April 09, 2019 10:00 AM PT |
| MSXML6 causes applications to stop responding if an exception was thrown MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). See details > | OS Build 16299.904 January 08, 2019 KB4480978 | Resolved KB4493441 | April 09, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files. See details > | OS Build 16299.967 February 12, 2019 KB4486996 | Resolved KB4489886 | March 12, 2019 10:00 AM PT |
| Internet Explorer may fail to load images Internet Explorer may fail to load images with a backslash (\\) in their relative source path. See details > | OS Build 16299.967 February 12, 2019 KB4486996 | Resolved KB4487021 | February 19, 2019 02:00 PM PT |
| First character of the Japanese era name not recognized as an abbreviation The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. See details > | OS Build 16299.936 January 15, 2019 KB4480967 | Resolved KB4487021 | February 19, 2019 02:00 PM PT |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. See details > | OS Build 16299.967 February 12, 2019 KB4486996 | Resolved KB4487021 | February 19, 2019 02:00 PM PT |
| Stop error when attempting to start SSH from WSL A stop error occurs when attempting to start Secure Shell from Windows Subsystem for Linux with agent forwarding using a command line switch (ssh –A) or a configuration setting. See details > | OS Build 16299.1029 March 12, 2019 KB4489886 | Resolved KB4493441 | April 09, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503284 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512494. Back to top | OS Build 16299.1217 June 11, 2019 KB4503284 | Resolved KB4512494 | Resolved: August 16, 2019 02:00 PM PT Opened: July 10, 2019 02:51 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 KB4507465. 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 KB4512516. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 16299.1296 July 16, 2019 KB4507465 | Resolved KB4512516 | Resolved: August 13, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
| Details | Originating update | Status | History |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. Affected platforms:
Resolution: This issue is resolved in KB4493441. Back to top | OS Build 16299.967 February 12, 2019 KB4486996 | Resolved KB4493441 | Resolved: April 09, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files After installing KB4486996, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files. Affected platforms:
Resolution: This issue is resolved in KB4489886. Back to top | OS Build 16299.967 February 12, 2019 KB4486996 | Resolved KB4489886 | Resolved: March 12, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Internet Explorer may fail to load images After installing KB4486996, Internet Explorer may fail to load images with a backslash (\\) in their relative source path. Affected platforms:
Resolution: This issue is resolved in KB4487021. Back to top | OS Build 16299.967 February 12, 2019 KB4486996 | Resolved KB4487021 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. Affected platforms:
Resolution: This issue is resolved in KB4487021. Back to top | OS Build 16299.967 February 12, 2019 KB4486996 | Resolved KB4487021 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| MSXML6 causes applications to stop responding if an exception was thrown After installing KB4480978, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings. Affected platforms:
Resolution: This issue is resolved in KB4493441. Back to top | OS Build 16299.904 January 08, 2019 KB4480978 | Resolved KB4493441 | Resolved: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
| First character of the Japanese era name not recognized as an abbreviation After installing KB4480967, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Affected platforms:
Resolution: This issue is resolved in KB4487021. Back to top | OS Build 16299.936 January 15, 2019 KB4480967 | Resolved KB4487021 | Resolved: February 19, 2019 02:00 PM PT Opened: January 15, 2019 10:00 AM PT |
| Summary | Originating update | Status | Date resolved |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved KB4512509 | August 19, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 17134.950 August 13, 2019 KB4512501 | Resolved KB4512509 | August 19, 2019 02:00 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 updating. See details > | OS Build 17134.915 July 16, 2019 KB4507466 | Resolved KB4512501 | August 13, 2019 10:00 AM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved External | August 09, 2019 07:03 PM PT |
| Difficulty connecting to some iSCSI-based SANs Devices may have difficulty connecting to some Storage Area Network (SAN) devices that leverage iSCSI. See details > | OS Build 17134.799 May 21, 2019 KB4499183 | Resolved KB4509478 | June 26, 2019 04:00 PM PT |
| End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. See details > | OS Build 17134.677 March 19, 2019 KB4489894 | Resolved KB4493464 | April 09, 2019 10:00 AM PT |
| MSXML6 may cause applications to stop responding MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). See details > | OS Build 17134.523 January 08, 2019 KB4480966 | Resolved KB4493464 | April 09, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files Users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files. See details > | OS Build 17134.590 February 12, 2019 KB4487017 | Resolved KB4489868 | March 12, 2019 10:00 AM PT |
| Internet Explorer may fail to load images Internet Explorer may fail to load images with a backslash (\\) in their relative source path. See details > | OS Build 17134.590 February 12, 2019 KB4487017 | Resolved KB4487029 | February 19, 2019 02:00 PM PT |
| First character of the Japanese era name not recognized The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. See details > | OS Build 17134.556 January 15, 2019 KB4480976 | Resolved KB4487029 | February 19, 2019 02:00 PM PT |
| Custom URI schemes may not start corresponding application Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer. See details > | OS Build 17134.648 March 12, 2019 KB4489868 | Resolved KB4493437 | April 25, 2019 02:00 PM PT |
| Cannot pin a web link on the Start menu or the taskbar Some users cannot pin a web link on the Start menu or the taskbar. See details > | OS Build 17134.471 December 11, 2018 KB4471324 | Resolved KB4487029 | February 19, 2019 02:00 PM PT |
| Stop error when attempting to start SSH from WSL A stop error occurs when attempting to start Secure Shell from Windows Subsystem for Linux with agent forwarding using a command line switch (ssh –A) or a configuration setting. See details > | OS Build 17134.648 March 12, 2019 KB4489868 | Resolved KB4493464 | April 09, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512501, 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 KB4512509. The ‘optional’ update will be 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 KB4512509 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 17134.950 August 13, 2019 KB4512501 | Resolved KB4512509 | Resolved: August 19, 2019 02:00 PM PT Opened: August 14, 2019 03:34 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503286) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.” Affected platforms:
Resolution: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue. Back to top | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved External | Last updated: August 09, 2019 07:03 PM PT Opened: August 09, 2019 04:25 PM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503286 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512509. Back to top | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved KB4512509 | Resolved: August 19, 2019 02:00 PM PT Opened: July 10, 2019 02:51 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 KB4507466. 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 KB4512501. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 17134.915 July 16, 2019 KB4507466 | Resolved KB4512501 | Resolved: August 13, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
| Details | Originating update | Status | History |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. Affected platforms:
Resolution: This issue is resolved in KB4493464. Back to top | OS Build 17134.590 February 12, 2019 KB4487017 | Resolved KB4493464 | Resolved: April 09, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files After installing KB4487017, users may received \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files. Affected platforms:
Resolution: This issue is resolved in KB4489868. Back to top | OS Build 17134.590 February 12, 2019 KB4487017 | Resolved KB4489868 | Resolved: March 12, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Internet Explorer may fail to load images After installing KB4487017, Internet Explorer may fail to load images with a backslash (\\) in their relative source path. Affected platforms:
Resolution: This issue is resolved in KB4487029. Back to top | OS Build 17134.590 February 12, 2019 KB4487017 | Resolved KB4487029 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| MSXML6 may cause applications to stop responding After installing KB4480966, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings. Affected platforms:
Resolution: This issue was resolved in KB4493464. Back to top | OS Build 17134.523 January 08, 2019 KB4480966 | Resolved KB4493464 | Resolved: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
| First character of the Japanese era name not recognized After installing KB4480976, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Affected platforms:
Resolution: This issue is resolved in KB4487029. Back to top | OS Build 17134.556 January 15, 2019 KB4480976 | Resolved KB4487029 | Resolved: February 19, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Cannot pin a web link on the Start menu or the taskbar After installing KB4471324, some users cannot pin a web link on the Start menu or the taskbar. Affected platforms:
Resolution: This issue is resolved in KB4487029. Back to top | OS Build 17134.471 December 11, 2018 KB4471324 | Resolved KB4487029 | Resolved: February 19, 2019 02:00 PM PT Opened: December 11, 2018 10:00 AM PT |
| Summary | Originating update | Status | Date resolved |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 17763.557 June 11, 2019 KB4503327 | Resolved KB4512534 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 17763.678 August 13, 2019 KB4511553 | Resolved KB4512534 | August 17, 2019 02:00 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 updating. See details > | OS Build 17763.652 July 22, 2019 KB4505658 | Resolved KB4511553 | August 13, 2019 10:00 AM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | OS Build 17763.557 June 11, 2019 KB4503327 | Resolved External | August 09, 2019 07:03 PM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503327 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512534. Back to top | OS Build 17763.557 June 11, 2019 KB4503327 | Resolved KB4512534 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 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 KB4505658. 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 KB4511553. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 17763.652 July 22, 2019 KB4505658 | Resolved KB4511553 | Resolved: August 13, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
| Summary | Originating update | Status | Date resolved |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503292 | Resolved KB4512514 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | August 13, 2019 KB4512506 | Resolved KB4517297 | August 16, 2019 02:00 PM PT |
| System may be unresponsive after restart with certain McAfee antivirus products Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup. See details > | April 09, 2019 KB4493472 | Resolved External | August 13, 2019 06:59 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | June 11, 2019 KB4503292 | Resolved External | August 09, 2019 07:03 PM PT |
| Unable to access some gov.uk websites gov.uk websites that don’t support “HSTS” may not be accessible See details > | May 14, 2019 KB4499164 | Resolved KB4505050 | May 18, 2019 02:00 PM PT |
| System may be unresponsive after restart if ArcaBit antivirus software installed Devices with ArcaBit antivirus software installed may become unresponsive upon restart. See details > | April 09, 2019 KB4493472 | Resolved | May 14, 2019 01:23 PM PT |
| System unresponsive after restart if Sophos Endpoint Protection installed Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart. See details > | April 09, 2019 KB4493472 | Resolved | May 14, 2019 01:22 PM PT |
| System may be unresponsive after restart if Avira antivirus software installed Devices with Avira antivirus software installed may become unresponsive upon restart. See details > | April 09, 2019 KB4493472 | Resolved | May 14, 2019 01:21 PM PT |
| Authentication may fail for services after the Kerberos ticket expires Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires. See details > | March 12, 2019 KB4489878 | Resolved KB4499164 | May 14, 2019 10:00 AM PT |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. See details > | February 12, 2019 KB4486563 | Resolved KB4493472 | April 09, 2019 10:00 AM PT |
| Devices may not respond at login or Welcome screen if running certain Avast software Devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software may become unresponsive after restart. See details > | April 09, 2019 KB4493472 | Resolved | April 25, 2019 02:00 PM PT |
| NETDOM.EXE fails to run NETDOM.EXE fails to run and the error, “The command failed to complete successfully.” appears on screen. See details > | March 12, 2019 KB4489878 | Resolved KB4493472 | April 09, 2019 10:00 AM PT |
| Custom URI schemes may not start corresponding application Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer. See details > | March 12, 2019 KB4489878 | Resolved KB4493472 | April 09, 2019 10:00 AM PT |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. See details > | February 12, 2019 KB4486563 | Resolved KB4486565 | February 19, 2019 02:00 PM PT |
| Internet Explorer may fail to load images Internet Explorer may fail to load images with a backslash (\\) in their relative source path. See details > | February 12, 2019 KB4486563 | Resolved KB4486565 | February 19, 2019 02:00 PM PT |
| First character of the Japanese era name not recognized as an abbreviation The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. See details > | January 17, 2019 KB4480955 | Resolved KB4486565 | February 19, 2019 02:00 PM PT |
| Internet Explorer 11 authentication issue with multiple concurrent logons Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine. See details > | January 08, 2019 KB4480970 | Resolved KB4493472 | April 09, 2019 10:00 AM PT |
| Event Viewer may not show some event descriptions for network interface cards The Event Viewer may not show some event descriptions for network interface cards (NIC). See details > | October 18, 2018 KB4462927 | Resolved KB4489878 | March 12, 2019 10:00 AM PT |
| Virtual machines fail to restore Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before. See details > | January 08, 2019 KB4480970 | Resolved KB4490511 | February 19, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503292 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512514. Back to top | June 11, 2019 KB4503292 | Resolved KB4512514 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 PM PT |
| Details | Originating update | Status | History |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. Affected platforms:
Resolution: This issue is resolved in KB4493472. Back to top | February 12, 2019 KB4486563 | Resolved KB4493472 | Resolved: April 09, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. Affected platforms:
Resolution: This issue is resolved in KB4486565. Back to top | February 12, 2019 KB4486563 | Resolved KB4486565 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Internet Explorer may fail to load images After installing KB4486563, Internet Explorer may fail to load images with a backslash (\\) in their relative source path. Affected platforms:
Resolution: This issue is resolved in KB4486565. Back to top | February 12, 2019 KB4486563 | Resolved KB4486565 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| First character of the Japanese era name not recognized as an abbreviation After installing KB4480955, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Affected platforms:
Resolution: This issue is resolved in KB4486565. Back to top | January 17, 2019 KB4480955 | Resolved KB4486565 | Resolved: February 19, 2019 02:00 PM PT Opened: January 17, 2019 10:00 AM PT |
| Internet Explorer 11 authentication issue with multiple concurrent logons After installing KB4480970, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
Affected platforms:
Resolution: This issue is resolved in KB4493472. Back to top | January 08, 2019 KB4480970 | Resolved KB4493472 | Resolved: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
| Virtual machines fail to restore After installing KB4480970, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).” This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures. Affected platforms:
Resolution: This issue is resolved in KB4490511. Back to top | January 08, 2019 KB4480970 | Resolved KB4490511 | Resolved: February 19, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
| Summary | Originating update | Status | Date resolved |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503276 | Resolved KB4512478 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | August 13, 2019 KB4512488 | Resolved KB4517298 | August 16, 2019 02:00 PM PT |
| System may be unresponsive after restart with certain McAfee antivirus products Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup. See details > | April 09, 2019 KB4493446 | Resolved External | August 13, 2019 06:59 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | June 11, 2019 KB4503276 | Resolved External | August 09, 2019 07:03 PM PT |
| System may be unresponsive after restart if ArcaBit antivirus software installed Devices with ArcaBit antivirus software installed may become unresponsive upon restart. See details > | April 09, 2019 KB4493446 | Resolved | May 14, 2019 01:22 PM PT |
| System unresponsive after restart if Sophos Endpoint Protection installed Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart. See details > | April 09, 2019 KB4493446 | Resolved | May 14, 2019 01:22 PM PT |
| System may be unresponsive after restart if Avira antivirus software installed Devices with Avira antivirus software installed may become unresponsive upon restart. See details > | April 09, 2019 KB4493446 | Resolved | May 14, 2019 01:21 PM PT |
| Internet Explorer may fail to load images Internet Explorer may fail to load images with a backslash (\\) in their relative source path. See details > | February 12, 2019 KB4487000 | Resolved KB4487016 | February 19, 2019 02:00 PM PT |
| First character of the Japanese era name not recognized as an abbreviation The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. See details > | January 15, 2019 KB4480969 | Resolved KB4487016 | February 19, 2019 02:00 PM PT |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. See details > | February 12, 2019 KB4487000 | Resolved KB4493446 | April 09, 2019 10:00 AM PT |
| Devices may not respond at login or Welcome screen if running certain Avast software Devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software may become unresponsive after restart. See details > | April 09, 2019 KB4493446 | Resolved | April 25, 2019 02:00 PM PT |
| Devices with winsock kernel client may receive error Devices with a winsock kernel client may receive D1, FC, and other errors. See details > | March 12, 2019 KB4489881 | Resolved KB4489893 | March 19, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files. See details > | February 19, 2019 KB4487016 | Resolved KB4489881 | March 12, 2019 10:00 AM PT |
| MSXML6 may cause applications to stop responding. MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). See details > | January 08, 2019 KB4480963 | Resolved KB4493446 | April 09, 2019 10:00 AM PT |
| Internet Explorer 11 authentication issue with multiple concurrent logons Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine. See details > | January 08, 2019 KB4480963 | Resolved KB4493446 | April 09, 2019 10:00 AM PT |
| Virtual machines fail to restore Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before. See details > | January 08, 2019 KB4480963 | Resolved KB4490512 | February 19, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503276 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512478. Back to top | June 11, 2019 KB4503276 | Resolved KB4512478 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 PM PT |
| Details | Originating update | Status | History |
| Internet Explorer may fail to load images After installing KB4487000, Internet Explorer may fail to load images with a backslash (\\) in their relative source path. Affected platforms:
Resolution: This issue is resolved in KB4487016. Back to top | February 12, 2019 KB4487000 | Resolved KB4487016 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. Affected platforms
Resolution: This issue is resolved in KB4493446. Back to top | February 12, 2019 KB4487000 | Resolved KB4493446 | Resolved: April 09, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files After installing KB4487016, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files. Affected platforms:
Resolution: This issue is resolved in KB4489881. Back to top | February 19, 2019 KB4487016 | Resolved KB4489881 | Resolved: March 12, 2019 10:00 AM PT Opened: February 19, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| First character of the Japanese era name not recognized as an abbreviation After installing KB4480969, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Affected platforms:
Resolution: This issue is resolved in KB4487016. Back to top | January 15, 2019 KB4480969 | Resolved KB4487016 | Resolved: February 19, 2019 02:00 PM PT Opened: January 15, 2019 10:00 AM PT |
| MSXML6 may cause applications to stop responding. After installing KB4480963, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings. Affected platforms:
Resolution: This issue is resolved in KB4493446. Back to top | January 08, 2019 KB4480963 | Resolved KB4493446 | Resolved: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
| Internet Explorer 11 authentication issue with multiple concurrent logons After installing KB4480963, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
Affected platforms:
Resolution: This issue is resolved in KB4493446. Back to top | January 08, 2019 KB4480963 | Resolved KB4493446 | Resolved: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
| Virtual machines fail to restore After installing KB4480963, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).” This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures. Affected platforms:
Resolution: This issue is resolved in KB4490512. Back to top | January 08, 2019 KB4480963 | Resolved KB4490512 | Resolved: February 19, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
| Summary | Originating update | Status | Date resolved |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503273 | Resolved KB4512499 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | August 13, 2019 KB4512476 | Resolved KB4517301 | August 16, 2019 02:00 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | June 11, 2019 KB4503273 | Resolved External | August 09, 2019 07:03 PM PT |
| Event Viewer may close or you may receive an error when using Custom Views When trying to expand, view or create Custom Views in Event Viewer, you may receive an error and the app may stop responding or close. See details > | June 11, 2019 KB4503273 | Resolved KB4503271 | June 20, 2019 02:00 PM PT |
| System may be unresponsive after restart if Avira antivirus software installed Devices with Avira antivirus software installed may become unresponsive upon restart. See details > | April 09, 2019 KB4493471 | Resolved | May 14, 2019 01:19 PM PT |
| Authentication may fail for services after the Kerberos ticket expires Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires. See details > | March 12, 2019 KB4489880 | Resolved KB4499149 | May 14, 2019 10:00 AM PT |
| NETDOM.EXE fails to run NETDOM.EXE fails to run and the error, “The command failed to complete successfully.” appears on screen. See details > | March 12, 2019 KB4489880 | Resolved KB4493471 | April 09, 2019 10:00 AM PT |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. See details > | February 12, 2019 KB4487023 | Resolved KB4487022 | February 19, 2019 02:00 PM PT |
| First character of the Japanese era name not recognized as an abbreviation The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. See details > | January 17, 2019 KB4480974 | Resolved KB4489880 | March 12, 2019 10:00 AM PT |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. See details > | February 12, 2019 KB4487023 | Resolved KB4493471 | April 09, 2019 10:00 AM PT |
| Virtual machines fail to restore Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before. See details > | January 08, 2019 KB4480968 | Resolved KB4490514 | February 19, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503273 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512499. Back to top | June 11, 2019 KB4503273 | Resolved KB4512499 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 PM PT |
| Details | Originating update | Status | History |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. Affected platforms:
Resolution: This issue is resolved in KB4487022. Back to top | February 12, 2019 KB4487023 | Resolved KB4487022 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. Affected platforms
Resolution: This issue is resolved in KB4493471. Back to top | February 12, 2019 KB4487023 | Resolved KB4493471 | Resolved: April 09, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| First character of the Japanese era name not recognized as an abbreviation After installing KB4480974, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Affected platforms:
Resolution: This issue is resolved in KB4489880. Back to top | January 17, 2019 KB4480974 | Resolved KB4489880 | Resolved: March 12, 2019 10:00 AM PT Opened: January 17, 2019 10:00 AM PT |
| Virtual machines fail to restore After installing KB4480968, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).” This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures. Affected platforms:
Resolution: This issue is resolved in KB4490514. Back to top | January 08, 2019 KB4480968 | Resolved KB4490514 | Resolved: February 19, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
| Summary | Originating update | Status | Date resolved |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503285 | Resolved KB4512512 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | August 13, 2019 KB4512518 | Resolved KB4517302 | August 16, 2019 02:00 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | June 11, 2019 KB4503285 | Resolved External | August 09, 2019 07:03 PM PT |
| Some devices and generation 2 Hyper-V VMs may have issues installing updates Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing some updates when Secure Boot is enabled. See details > | June 11, 2019 KB4503285 | Resolved KB4503295 | June 21, 2019 02:00 PM PT |
| Layout and cell size of Excel sheets may change when using MS UI Gothic When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. See details > | April 25, 2019 KB4493462 | Resolved KB4499171 | May 14, 2019 10:00 AM PT |
| System unresponsive after restart if Sophos Endpoint Protection installed Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart. See details > | April 09, 2019 KB4493451 | Resolved | May 14, 2019 01:21 PM PT |
| System may be unresponsive after restart if Avira antivirus software installed Devices with Avira antivirus software installed may become unresponsive upon restart. See details > | April 09, 2019 KB4493451 | Resolved | May 14, 2019 01:19 PM PT |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. See details > | February 12, 2019 KB4487025 | Resolved KB4487024 | February 19, 2019 02:00 PM PT |
| First character of the Japanese era name not recognized as an abbreviation The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. See details > | January 15, 2019 KB4480971 | Resolved KB4487024 | February 19, 2019 02:00 PM PT |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. See details > | February 12, 2019 KB4487025 | Resolved KB4493451 | April 09, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files. See details > | February 12, 2019 KB4487025 | Resolved KB4489891 | March 12, 2019 10:00 AM PT |
| Internet Explorer 11 authentication issue with multiple concurrent logons Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine. See details > | January 08, 2019 KB4480975 | Resolved KB4493451 | April 09, 2019 10:00 AM PT |
| MSXML6 may cause applications to stop responding MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). See details > | January 08, 2019 KB4480975 | Resolved KB4493451 | April 09, 2019 10:00 AM PT |
| Virtual machines fail to restore Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before. See details > | January 08, 2019 KB4480975 | Resolved KB4490516 | February 19, 2019 02:00 PM PT |
| Event Viewer may not show some event descriptions for network interface cards The Event Viewer may not show some event descriptions for network interface cards (NIC). See details > | September 11, 2018 KB4457135 | Resolved KB4489891 | March 12, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503285 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512512. Back to top | June 11, 2019 KB4503285 | Resolved KB4512512 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 PM PT |
| Details | Originating update | Status | History |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. Affected platforms:
Resolution: This issue is resolved in KB4487024. Back to top | February 12, 2019 KB4487025 | Resolved KB4487024 | Resolved: February 19, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
| Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. Affected platforms
Resolution: This issue is resolved in KB4493451. Back to top | February 12, 2019 KB4487025 | Resolved KB4493451 | Resolved: April 09, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Error 1309 when installing/uninstalling MSI or MSP files After installing KB4487025, users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files. Affected platforms:
Resolution: This issue is resolved in KB4489891. Back to top | February 12, 2019 KB4487025 | Resolved KB4489891 | Resolved: March 12, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| First character of the Japanese era name not recognized as an abbreviation After installing KB4480971, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Affected platforms:
Resolution: This issue is resolved in KB4487024. Back to top | January 15, 2019 KB4480971 | Resolved KB4487024 | Resolved: February 19, 2019 02:00 PM PT Opened: January 15, 2019 10:00 AM PT |
| Internet Explorer 11 authentication issue with multiple concurrent logons After installing KB4480975, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
Affected platforms:
Resolution: This issue is resolved in KB4493451. Back to top | January 08, 2019 KB4480975 | Resolved KB4493451 | Resolved: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
| MSXML6 may cause applications to stop responding After installing KB4480975, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings. Affected platforms:
Resolution: This issue is resolved in KB4493451. Back to top | January 08, 2019 KB4480975 | Resolved KB4493451 | Resolved: April 09, 2019 10:00 AM PT Opened: January 08, 2019 10:00 AM PT |
| Virtual machines fail to restore After installing KB4480975, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, \"Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).\" This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures. Affected platforms:
Resolution: This issue is resolved in KB4490516. Back to top | January 08, 2019 KB4480975 | Resolved KB4490516 | Resolved: February 19, 2019 02:00 PM PT Opened: January 08, 2019 10:00 AM PT |
| Summary | Originating update | Status | Last updated |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 14393.3025 June 11, 2019 KB4503267 | Resolved KB4512495 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 14393.3144 August 13, 2019 KB4512517 | Resolved KB4512495 | August 17, 2019 02:00 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 updating. See details > | OS Build 14393.3115 July 16, 2019 KB4507459 | Resolved KB4512517 | August 13, 2019 10:00 AM PT |
| Internet Explorer 11 and apps using the WebBrowser control may fail to render JavaScript may fail to render as expected in Internet Explorer 11 and in apps using JavaScript or the WebBrowser control. See details > | OS Build 14393.3085 July 09, 2019 KB4507460 | Resolved KB4512517 | August 13, 2019 10:00 AM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | OS Build 14393.3025 June 11, 2019 KB4503267 | Resolved External | August 09, 2019 07:03 PM PT |
| 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. See details > | OS Build 14393.3053 June 18, 2019 KB4503294 | Investigating | August 01, 2019 05:00 PM PT |
| SCVMM cannot enumerate and manage logical switches deployed on the host For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host. See details > | OS Build 14393.2639 November 27, 2018 KB4467684 | Resolved KB4507459 | July 16, 2019 10:00 AM PT |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 14393.3025 June 11, 2019 KB4503267 | Mitigated | July 10, 2019 07:09 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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 |
| 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 | Mitigated | February 19, 2019 10:00 AM PT |
| Cluster service may fail if the minimum password length is set to greater than 14 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. See details > | OS Build 14393.2639 November 27, 2018 KB4467684 | Mitigated | April 25, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503267 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512495. Back to top | OS Build 14393.3025 June 11, 2019 KB4503267 | Resolved KB4512495 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 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 KB4507459. 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 KB4512517. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 14393.3115 July 16, 2019 KB4507459 | Resolved KB4512517 | Resolved: August 13, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
| Internet Explorer 11 and apps using the WebBrowser control may fail to render Internet Explorer 11 may fail to render some JavaScript after installing KB4507460. You may also have issues with apps using JavaScript or the WebBrowser control, such as the present PowerPoint feature of Skype Meeting Broadcast. Affected platforms:
Resolution: This issue was resolved in KB4512517. Back to top | OS Build 14393.3085 July 09, 2019 KB4507460 | Resolved KB4512517 | Resolved: August 13, 2019 10:00 AM PT Opened: July 26, 2019 04:58 PM PT |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503267 on a WDS server. Affected platforms:
Workaround: To mitigate this issue on an SCCM server:
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager. To mitigate this issue on a WDS server without SCCM:
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 14393.3025 June 11, 2019 KB4503267 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM PT |
| Summary | Originating update | Status | Last updated |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 16299.1217 June 11, 2019 KB4503284 | Resolved KB4512494 | August 16, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 16299.1331 August 13, 2019 KB4512516 | Resolved KB4512494 | August 16, 2019 02:00 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 updating. See details > | OS Build 16299.1296 July 16, 2019 KB4507465 | Resolved KB4512516 | August 13, 2019 10:00 AM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | OS Build 16299.1217 June 11, 2019 KB4503284 | Resolved External | August 09, 2019 07:03 PM PT |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 16299.1217 June 11, 2019 KB4503284 | Mitigated | July 10, 2019 07:09 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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 |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503284 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512494. Back to top | OS Build 16299.1217 June 11, 2019 KB4503284 | Resolved KB4512494 | Resolved: August 16, 2019 02:00 PM PT Opened: July 10, 2019 02:51 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 KB4507465. 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 KB4512516. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 16299.1296 July 16, 2019 KB4507465 | Resolved KB4512516 | Resolved: August 13, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503284 on a WDS server. Affected platforms:
Workaround: To mitigate this issue on an SCCM server:
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager. To mitigate this issue on a WDS server without SCCM:
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 16299.1217 June 11, 2019 KB4503284 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM PT |
| Summary | Originating update | Status | Last updated |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 17134.950 August 13, 2019 KB4512501 | Investigating | August 17, 2019 01:37 PM PT |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved KB4512509 | August 19, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 17134.950 August 13, 2019 KB4512501 | Resolved KB4512509 | August 19, 2019 02:00 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 updating. See details > | OS Build 17134.915 July 16, 2019 KB4507466 | Resolved KB4512501 | August 13, 2019 10:00 AM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved External | August 09, 2019 07:03 PM PT |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 17134.829 June 11, 2019 KB4503286 | Mitigated | July 10, 2019 07:09 PM 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 | Mitigated | June 14, 2019 04:41 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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 |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512501, 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:
Next steps: Microsoft is working on a resolution and estimates a solution will be available over the coming days. The ‘optional’ update will be 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 this update once it is released and install it. 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 17134.950 August 13, 2019 KB4512501 | Investigating | Last updated: August 17, 2019 01:37 PM PT Opened: August 14, 2019 03:34 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512501, 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 KB4512509. The ‘optional’ update will be 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 KB4512509 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 17134.950 August 13, 2019 KB4512501 | Resolved KB4512509 | Resolved: August 19, 2019 02:00 PM PT Opened: August 14, 2019 03:34 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503286) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.” Affected platforms:
Resolution: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue. Back to top | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved External | Last updated: August 09, 2019 07:03 PM PT Opened: August 09, 2019 04:25 PM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503286 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512509. Back to top | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved KB4512509 | Resolved: August 19, 2019 02:00 PM PT Opened: July 10, 2019 02:51 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 KB4507466. 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 KB4512501. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 17134.915 July 16, 2019 KB4507466 | Resolved KB4512501 | Resolved: August 13, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503286 on a WDS server. Affected platforms:
Workaround: To mitigate this issue on an SCCM server:
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager. To mitigate this issue on a WDS server without SCCM:
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 17134.829 June 11, 2019 KB4503286 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM PT |
| Summary | Originating update | Status | Last updated |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 17763.557 June 11, 2019 KB4503327 | Resolved KB4512534 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 17763.678 August 13, 2019 KB4511553 | Resolved KB4512534 | August 17, 2019 02:00 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 updating. See details > | OS Build 17763.652 July 22, 2019 KB4505658 | Resolved KB4511553 | August 13, 2019 10:00 AM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | OS Build 17763.557 June 11, 2019 KB4503327 | Resolved External | August 09, 2019 07:03 PM PT |
| 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. See details > | OS Build 17763.55 October 09, 2018 KB4464330 | Investigating | August 01, 2019 05:00 PM PT |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 17763.557 June 11, 2019 KB4503327 | Mitigated | July 10, 2019 07:09 PM 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 | Mitigated | June 14, 2019 04:41 PM PT |
| Devices with some Asian language packs installed may receive an error After installing the KB4493509 devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_F 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 Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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 |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503327 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512534. Back to top | OS Build 17763.557 June 11, 2019 KB4503327 | Resolved KB4512534 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 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 KB4505658. 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 KB4511553. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 17763.652 July 22, 2019 KB4505658 | Resolved KB4511553 | Resolved: August 13, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503327 on a WDS server. Affected platforms:
Workaround: To mitigate this issue on an SCCM server:
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager. To mitigate this issue on a WDS server without SCCM:
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 17763.557 June 11, 2019 KB4503327 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM PT |
| Summary | Originating update | Status | Last updated |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 18362.295 August 13, 2019 KB4512508 | Investigating | August 17, 2019 01:38 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 18362.295 August 13, 2019 KB4512508 | Investigating | August 17, 2019 01:49 PM PT |
| Updates may fail to install and you may receive Error 0x80073701 Installation of updates may fail and you may receive an error, \"Updates Failed, There were problems installing some updates, but we'll try again later\" and \"Error 0x80073701.\" See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | August 16, 2019 04:28 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 updating. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | August 13, 2019 06:59 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved External | August 09, 2019 07:03 PM PT |
| Details | Originating update | Status | History |
| 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:
Next steps: Microsoft is working on a resolution and estimates a solution will be available late August. The ‘optional’ update will be 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 the update once it is released. 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 | Investigating | Last updated: August 17, 2019 01:38 PM PT Opened: August 14, 2019 03:34 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:
Next steps: Microsoft is working on a resolution and estimates a solution will be available late August. The ‘optional’ update will be 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 the update once it is released. 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 | Investigating | Last updated: August 17, 2019 01:49 PM PT Opened: August 14, 2019 03:34 PM PT |
| 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:
Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | Last updated: August 16, 2019 04:28 PM PT Opened: August 16, 2019 01:41 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503293) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.” Affected platforms:
Resolution: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue. Back to top | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved External | Last updated: August 09, 2019 07:03 PM PT Opened: August 09, 2019 04:25 PM PT |
| Summary | Originating update | Status | Last updated |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503292 | Resolved KB4512514 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | August 13, 2019 KB4512506 | Resolved KB4517297 | August 16, 2019 02:00 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 |
| Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV Windows udates that are SHA-2 signed are not available with Symantec or Norton antivirus program installed See details > | August 13, 2019 KB4512506 | Investigating | August 16, 2019 04:28 PM PT |
| System may be unresponsive after restart with certain McAfee antivirus products Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup. See details > | April 09, 2019 KB4493472 | Resolved External | August 13, 2019 06:59 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | June 11, 2019 KB4503292 | Resolved External | August 09, 2019 07:03 PM PT |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503292 | Mitigated | July 10, 2019 02:59 PM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503292 on a WDS server. Affected platforms:
Workaround: To mitigate this issue on an SCCM server, set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points. Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager. To mitigate this issue on a WDS server without SCCM:
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | June 11, 2019 KB4503292 | Mitigated | Last updated: July 10, 2019 02:59 PM PT Opened: July 10, 2019 02:51 PM PT |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503292 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512514. Back to top | June 11, 2019 KB4503292 | Resolved KB4512514 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 PM PT |
| Summary | Originating update | Status | Last updated |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503276 | Resolved KB4512478 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | August 13, 2019 KB4512488 | Resolved KB4517298 | August 16, 2019 02:00 PM PT |
| System may be unresponsive after restart with certain McAfee antivirus products Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup. See details > | April 09, 2019 KB4493446 | Resolved External | August 13, 2019 06:59 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | June 11, 2019 KB4503276 | Resolved External | August 09, 2019 07:03 PM PT |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503276 | Mitigated | July 10, 2019 07:09 PM PT |
| 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. See details > | April 25, 2019 KB4493443 | Mitigated | May 15, 2019 05:53 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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 |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503276 on a WDS server. Affected platforms:
Workaround: To mitigate this issue on an SCCM server:
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager. To mitigate this issue on a WDS server without SCCM:
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | June 11, 2019 KB4503276 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM PT |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503276 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512478. Back to top | June 11, 2019 KB4503276 | Resolved KB4512478 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 PM PT |
| Summary | Originating update | Status | Last updated |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503273 | Resolved KB4512499 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | August 13, 2019 KB4512476 | Resolved KB4517301 | August 16, 2019 02:00 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | June 11, 2019 KB4503273 | Resolved External | August 09, 2019 07:03 PM PT |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503273 | Mitigated | July 10, 2019 02:59 PM PT |
| Details | Originating update | Status | History |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503273 on a WDS server. Affected platforms:
Workaround: To mitigate this issue on an SCCM server, set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points. Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager. To mitigate this issue on a WDS server without SCCM:
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | June 11, 2019 KB4503273 | Mitigated | Last updated: July 10, 2019 02:59 PM PT Opened: July 10, 2019 02:51 PM PT |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503273 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512499. Back to top | June 11, 2019 KB4503273 | Resolved KB4512499 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 PM PT |
| Summary | Originating update | Status | Last updated |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503285 | Resolved KB4512512 | August 17, 2019 02:00 PM PT |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | August 13, 2019 KB4512518 | Resolved KB4517302 | August 16, 2019 02:00 PM PT |
| MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | June 11, 2019 KB4503285 | Resolved External | August 09, 2019 07:03 PM PT |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503285 | Mitigated | July 10, 2019 07:09 PM PT |
| 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. See details > | April 25, 2019 KB4493462 | Mitigated | May 15, 2019 05:53 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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 |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503285 on a WDS server. Affected platforms:
Workaround: To mitigate this issue on an SCCM server:
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager. To mitigate this issue on a WDS server without SCCM:
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | June 11, 2019 KB4503285 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM PT |
| Devices starting using PXE from a WDS or SCCM 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 (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503285 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512512. Back to top | June 11, 2019 KB4503285 | Resolved KB4512512 | Resolved: August 17, 2019 02:00 PM PT Opened: July 10, 2019 02:51 PM PT |