| 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 10240.18305 August 13, 2019 KB4512497 | Acknowledged | August 14, 2019 03:34 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 10240.18305 August 13, 2019 KB4512497 | Acknowledged | August 14, 2019 05:08 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 10240.18244 June 11, 2019 KB4503291 | Resolved External | August 09, 2019 07:03 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 10240.18094 January 08, 2019 KB4480962 | 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 KB4512497, 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 10240.18305 August 13, 2019 KB4512497 | Acknowledged | Last updated: August 14, 2019 03:34 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 KB4512497, 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 10240.18305 August 13, 2019 KB4512497 | Acknowledged | Last updated: August 14, 2019 05:08 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 (KB4503291) 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 10240.18244 June 11, 2019 KB4503291 | 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 |
| 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 | Acknowledged | August 14, 2019 03:34 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 | Acknowledged | August 14, 2019 05:08 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 |
| Some applications may fail to run as expected on clients of AD FS 2016 Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) See details > | OS Build 14393.2941 April 25, 2019 KB4493473 | 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 |
| Details | Originating update | Status | History |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512517, 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 14393.3144 August 13, 2019 KB4512517 | Acknowledged | Last updated: August 14, 2019 03:34 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 KB4512517, 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 14393.3144 August 13, 2019 KB4512517 | Acknowledged | Last updated: August 14, 2019 05:08 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 (KB4503267) 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 14393.3025 June 11, 2019 KB4503267 | Resolved External | Last updated: August 09, 2019 07:03 PM PT Opened: August 09, 2019 04:25 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, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.” Affected platforms:
Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 14393.3053 June 18, 2019 KB4503294 | Investigating | Last updated: August 01, 2019 05:00 PM PT Opened: August 01, 2019 05:00 PM PT |
| Details | Originating update | Status | History |
| Some applications may fail to run as expected on clients of AD FS 2016 Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of KB4493473 on the server. Applications that may exhibit this behavior use an IFRAME during non-interactive authentication requests and receive X-Frame Options set to DENY. Affected platforms:
Resolution: This issue was resolved in KB4507459. Back to top | OS Build 14393.2941 April 25, 2019 KB4493473 | Resolved KB4507459 | Resolved: July 16, 2019 10:00 AM PT Opened: June 04, 2019 05:55 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 15063.1988 August 13, 2019 KB4512507 | Acknowledged | August 14, 2019 03:34 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 15063.1988 August 13, 2019 KB4512507 | Acknowledged | August 14, 2019 05:08 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 15063.1955 July 16, 2019 KB4507467 | Resolved KB4512507 | 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 15063.1868 June 11, 2019 KB4503279 | Resolved External | August 09, 2019 07:03 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 15063.1563 January 08, 2019 KB4480973 | 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 KB4512507, 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 15063.1988 August 13, 2019 KB4512507 | Acknowledged | Last updated: August 14, 2019 03:34 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 KB4512507, 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 15063.1988 August 13, 2019 KB4512507 | Acknowledged | Last updated: August 14, 2019 05:08 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 (KB4503279) 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 15063.1868 June 11, 2019 KB4503279 | 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 |
| 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 | Acknowledged | August 14, 2019 03:34 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 | Acknowledged | August 14, 2019 05:08 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 |
| Details | Originating update | Status | History |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512516, 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 16299.1331 August 13, 2019 KB4512516 | Acknowledged | Last updated: August 14, 2019 03:34 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 KB4512516, 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 16299.1331 August 13, 2019 KB4512516 | Acknowledged | Last updated: August 14, 2019 05:08 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 (KB4503284) 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 16299.1217 June 11, 2019 KB4503284 | 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 |
| 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 | Acknowledged | August 14, 2019 03:34 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 | Acknowledged | August 14, 2019 05:08 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 |
| 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 17134.950 August 13, 2019 KB4512501 | Acknowledged | Last updated: August 14, 2019 03:34 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:
Next steps: Microsoft is presently investigating this issue and will provide an update when available. Back to top | OS Build 17134.950 August 13, 2019 KB4512501 | Acknowledged | Last updated: August 14, 2019 05:08 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 |
| 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 17763.678 August 13, 2019 KB4511553 | Acknowledged | August 14, 2019 03:34 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 | Acknowledged | August 14, 2019 05:08 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 |
| Details | Originating update | Status | History |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4511553, 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 17763.678 August 13, 2019 KB4511553 | Acknowledged | Last updated: August 14, 2019 03:34 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 KB4511553, 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 17763.678 August 13, 2019 KB4511553 | Acknowledged | Last updated: August 14, 2019 05:08 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 (KB4503327) 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 17763.557 June 11, 2019 KB4503327 | Resolved External | Last updated: August 09, 2019 07:03 PM PT Opened: August 09, 2019 04:25 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, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.” Affected platforms:
Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 17763.55 October 09, 2018 KB4464330 | Investigating | Last updated: August 01, 2019 05:00 PM PT Opened: August 01, 2019 05:00 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 | Acknowledged | August 14, 2019 03:34 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 | Acknowledged | August 14, 2019 05:08 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 |
| Issues updating when certain versions of Intel storage drivers are installed Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Mitigated 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 18362.295 August 13, 2019 KB4512508 | Acknowledged | Last updated: August 14, 2019 03:34 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 presently investigating this issue and will provide an update when available. Back to top | OS Build 18362.295 August 13, 2019 KB4512508 | Acknowledged | Last updated: August 14, 2019 05:08 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 (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 |
| 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 | Acknowledged | August 14, 2019 03:34 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 | Acknowledged | August 14, 2019 05:08 PM PT |
| IA64-based devices may fail to start after installing updates After installing updates released on or after August 13, 2019, IA64-based devices may fail to start. See details > | August 13, 2019 KB4512506 | Resolved KB4474419 | August 13, 2019 10:00 AM PT |
| Windows updates that are SHA-2 signed may not be offered Windows udates that are SHA-2 signed are not available with Symantec Endpoint Protection installed See details > | August 13, 2019 KB4512506 | Investigating | August 13, 2019 06:59 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 |
| Details | Originating update | Status | History |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512506, 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 presently investigating this issue and will provide an update when available. Back to top | August 13, 2019 KB4512506 | Acknowledged | Last updated: August 14, 2019 03:34 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 KB4512506, 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 presently investigating this issue and will provide an update when available. Back to top | August 13, 2019 KB4512506 | Acknowledged | Last updated: August 14, 2019 05:08 PM PT Opened: August 14, 2019 03:34 PM PT |
| IA64-based devices may fail to start after installing updates After installing KB4512506, IA64-based devices may fail to start with the following error: \"File: \\Windows\\system32\\winload.efi Status: 0xc0000428 Info: Windows cannot verify the digital signature for this file.\" Affected platforms:
Resolution: This issue has been resolved in the latest version of KB4474419 (released on or after August 13, 2019).Please verify that KB4474419 is installed and restart your machine before installing KB4512506 released August 13th, 2019 or later. Back to top | August 13, 2019 KB4512506 | Resolved KB4474419 | Resolved: August 13, 2019 10:00 AM PT Opened: August 13, 2019 08:34 AM PT |
| Windows updates that are SHA-2 signed may not be offered Symantec has identified an issue that occurs when a device is running any Symantec or Norton antivirus program and installs updates for Windows that are signed with SHA-2 certificates only. The Windows updates are blocked or deleted by the antivirus program during installation, which may then cause Windows to stop working or fail to start. Affected platforms:
Workaround: Guidance for Symantec customers can be found in the Symantec support article. Next steps: To safeguard your update experience, Microsoft and Symantec have partnered to place a safeguard hold on devices with an affected version of Symantec Antivirus or Norton Antivirus installed to prevent them from receiving this type of Windows update until a solution is available. We recommend that you do not manually install affected updates until a solution is available. Back to top | August 13, 2019 KB4512506 | Investigating | Last updated: August 13, 2019 06:59 PM PT Opened: August 13, 2019 10:05 AM 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 (KB4503292) 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 | June 11, 2019 KB4503292 | 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 |
| 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 | Acknowledged | August 14, 2019 03:34 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 | Acknowledged | August 14, 2019 05:08 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 |
| Details | Originating update | Status | History |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512488, 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 presently investigating this issue and will provide an update when available. Back to top | August 13, 2019 KB4512488 | Acknowledged | Last updated: August 14, 2019 03:34 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 KB4512488, 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 presently investigating this issue and will provide an update when available. Back to top | August 13, 2019 KB4512488 | Acknowledged | Last updated: August 14, 2019 05:08 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 (KB4503276) 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 | June 11, 2019 KB4503276 | 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 |
| 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 | Acknowledged | August 14, 2019 03:34 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 | Acknowledged | August 14, 2019 05:08 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 |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512476, 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 presently investigating this issue and will provide an update when available. Back to top | August 13, 2019 KB4512476 | Acknowledged | Last updated: August 14, 2019 03:34 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 KB4512476, 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 presently investigating this issue and will provide an update when available. Back to top | August 13, 2019 KB4512476 | Acknowledged | Last updated: August 14, 2019 05:08 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 (KB4503273) 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 | June 11, 2019 KB4503273 | 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 |
| 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 | Acknowledged | August 14, 2019 03:34 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 | Acknowledged | August 14, 2019 05:08 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 |
| Details | Originating update | Status | History |
| Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512518, 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 presently investigating this issue and will provide an update when available. Back to top | August 13, 2019 KB4512518 | Acknowledged | Last updated: August 14, 2019 03:34 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 KB4512518, 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 presently investigating this issue and will provide an update when available. Back to top | August 13, 2019 KB4512518 | Acknowledged | Last updated: August 14, 2019 05:08 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 (KB4503285) 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 | June 11, 2019 KB4503285 | Resolved External | Last updated: August 09, 2019 07:03 PM PT Opened: August 09, 2019 04:25 PM PT |
| Message | Date |
| August 2019 security update now available for Windows 10, version 1903 and all supported versions of Windows The August 2019 security update release, referred to as our “B” release, is now available for Windows 10, version 1903 and all supported versions of Windows. A “B” release is the primary, regular update event for each month and is the only regular release that contains security fixes. As a result, we recommend that you install these updates promptly. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. To be informed about the latest updates and releases, follow us on Twitter @WindowsUpdate. | August 13, 2019 10:00 AM PT |
| Advisory: Bluetooth encryption key size vulnerability disclosed (CVE-2019-9506) On August 13, 2019, Microsoft released security updates to address a Bluetooth key length encryption vulnerability. To exploit this vulnerability, an attacker would need specialized hardware and would be limited by the signal range of the Bluetooth devices in use. For more information about this industry-wide issue, see CVE-2019-9506 | Bluetooth Encryption Key Size Vulnerability in the Microsoft Security Update Guide and important guidance for IT pros in KB4514157. (Note: we are documenting this vulnerability together with guidance for IT admins as part of a coordinated industry disclosure effort.) | August 13, 2019 10:00 AM PT |
| Advisory: Windows Advanced Local Procedure Call Elevation of Privilege vulnerability disclosed (CVE-2019-1162) On August 13, 2019, Google Project Zero (GPZ) disclosed an Elevation of Privilege (EoP) vulnerability in the Windows Collaborative Translation Framework (CTF) service that affects Windows operating systems, versions 8.1 and higher. An attacker must already have code execution on the target system to leverage these vulnerabilities. Microsoft released security updates on August 13, 2019 that partially address this issue. Other items disclosed by GPZ require more time to address and we are working to release a resolution in mid-September. For more information, see CVE-2019-1162 | Windows ALPC Elevation of Privilege Vulnerability | August 13, 2019 10:00 AM PT |
| Advisory: Windows Advanced Local Procedure Call Elevation of Privilege vulnerability disclosed (CVE-2019-1162) On August 13, 2019, Google Project Zero (GPZ) disclosed an Elevation of Privilege (EoP) vulnerability in how Windows handles calls to Advanced Local Procedure Call (ALPC) that affects Windows operating systems, versions 8.1 and higher. An attacker must already have code execution on the target system to leverage these vulnerabilities. Microsoft released security updates on August 13, 2019 that partially address this issue. Other items disclosed by GPZ require more time to address and we are working to release a resolution in mid-September. For more information, see CVE-2019-1162 | Windows ALPC Elevation of Privilege Vulnerability | August 13, 2019 10:00 AM PT |
| Take action: Install required updates for Windows 7 SP1 and Windows Server 2008 RS2 SP1 for SHA-2 code sign support As of August 13, 2019, Windows 7 SP1 and Windows Server 2008 R2 SP1 updates signatures only support SHA-2 code signing. As outlined in 2019 SHA-2 Code Signing Support requirement for Windows and WSUS, we are requiring that SHA-2 code signing support be installed. If you have Windows Update enabled and have applied the security updates released in March 2019 (KB4490628) and August 2019 (KB4474419), you are protected automatically; no further configuration is necessary. If you have not installed the March 2019 updates, you will need to do so in order to continue to receive updates on devices running Windows 7 SP1 and Windows Server 2008 R2 SP1. | August 13, 2019 10:00 AM PT |
| Take action: Windows 10, version 1803 (the April 2018 Update) reaches end of service on November 12, 2019 Windows 10, version 1803 (the April 2018 Update) will reach end of service on November 12, 2019 for Home and Pro editions. We will begin updating devices running Windows 10, version 1803 to Windows 10, version 1903 (the May 2019 Update) starting July 16, 2019 to help ensure that these devices remain in a serviced and secure state. For more information, see the Windows 10, version 1903 section of the Windows release health dashboard. | August 13, 2019 10:00 AM PT |
| Advisory: Windows Kernel Information Disclosure Vulnerability (CVE-2019-1125) On July 9, 2019, Microsoft released a security update for a Windows kernel information disclosure vulnerability (CVE-2019-1125). Customers who have Windows Update enabled and have applied the security updates released on July 9, 2019 are protected automatically; no further configuration is necessary. For more information, see CVE-2019-1125 | Windows Kernel Information Disclosure Vulnerability in the Microsoft Security Update Guide. (Note: we are documenting this mitigation publicly today, instead of back in July, as part of a coordinated industry disclosure effort.) | August 06, 2019 10:00 AM PT |