Microsoft Known Issue

Known issues in Microsoft Patches:
 
Microsoft often releases patches to address security and reliability issues. Sometimes, patches itself will introduce unprecedented issues after installing them. Here's the updated list of all the known issues in Microsoft patches and possible workaround for them.

Oops! No results for your search.

workaround
Jul 12, 2019
KB4507461
2019-07 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB4507461) (CVE-2019-1132)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4507452
2019-07 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4507452) (CVE-2019-1132)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4503271
2019-06 Preview of Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4503271)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4503287
2019-06 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB4503287)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4503273
2019-06 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4503273)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4505057
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4505057) Insider Preview
After installing this update, users may experience error “0x800705b4” when launching Windows Defender Application Guard or Windows Sandbox.
Use the credentials of a local admin to create and set the following registry keys on the Host OS then restart the Host: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Containers\CmService\Policy] "DisableClone"=dword:00000001 "DisableSnapshot"=dword:00000001
workaround
Jul 12, 2019
KB4497936
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4497936)
After installing this update, users may experience error “0x800705b4” when launching Windows Defender Application Guard or Windows Sandbox.
Use the credentials of a local admin to create and set the following registry keys on the Host OS then restart the Host: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Containers\CmService\Policy] "DisableClone"=dword:00000001 "DisableSnapshot"=dword:00000001 Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4088881
2018-03 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4088881)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
The issue is resolved in KB4093113. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088882
2018-03 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4088882)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093121. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088883
2018-03 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4088883)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093116. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088876
2018-03 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4088876)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093114. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088880
2018-03 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4088880)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093122. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088877
2018-03 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4088877)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093123. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088878
2018-03 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4088878)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093108. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088875
2018-03 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4088875)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093118. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088879
2018-03 Security Only Quality Update for Windows 8.1 for x64-based Systems (KB4088879)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093115. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4075212
2018-02 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4075212)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093121. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4075211
2018-02 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4075211)
Because of an issue that affects some versions of antivirus software, this fix is being applied only to the computers on which the antivirus ISV have updated the ALLOW REGKEY.
The issue is resolved in KB4093113. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4074598
2018-02 Security Monthly Quality Rollup for Windows 7 for x64-based Systems - Meltdown and Spectre(KB4074598)
Because of an issue that affects some versions of antivirus software, this fix is being applied only to the computers on which the antivirus ISV have updated the ALLOW REGKEY.
This issue is resolved in KB4093118. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4074587
2018-02 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems - Meltdown and Spectre(KB4074587)
Because of an issue that affects some versions of antivirus software, this fix is being applied only to the computers on which the antivirus ISV have updated the ALLOW REGKEY.
This issue is resolved in KB4093108. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4074597
2018-02 Security Only Quality Update for Windows 8.1 for x64-based Systems - Meltdown and SpectreKB4074597)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093115. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4074594
2018-02 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems - Meltdown and Spectre(KB4074594)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093114. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4057400
2018-01 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems - Meltdown and Spectre (KB4057400)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
The issue is resolved in KB4093113. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4057401
2018-01 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems - Meltdown and Spectre(KB4057401)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093121. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4056895
2018-01 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems - Meltdown and Spectre (KB4056895)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093114. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4056894
2018-01 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems - Meltdown and Spectre (KB4056894)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093118. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4056898
2018-01 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems - Meltdown and Spectre (KB4056898)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093115. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4056897
2018-01 Security Only Quality Update for Windows 7 for x64-based Systems - Meltdown and Spectre (KB4056897)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093108. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 11, 2019
KB4507464
2019-07 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4507464) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507448
2019-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4507448) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507456
2019-07 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4507456) (CVE-2019-1132)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507462
2019-07 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4507462) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507449
2019-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4507449) (CVE-2019-1132)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507457
2019-07 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4507457) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503295
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503295)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503283
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503283)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming releas
workaround
Jul 11, 2019
KB4503277
2019-06 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503277)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503285
2019-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503285)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503269
2019-06 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4503269)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503292
2019-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503292)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503290
2019-06 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4503290)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503276
2019-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503276)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503263
2019-06 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4503263)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507435
2019-07 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4507435) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507469
2019-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4507469) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release
workaround
Jul 11, 2019
KB4507455
2019-07 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4507455) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507453
2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4507453) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4501375
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4501375)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4509479
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4509479)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4509478
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4509478)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4509477
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4509477)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4501371
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501371)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503288
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503288)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503281
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503281)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503286
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503286)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503284
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503284)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503293
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4503293)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507455
2019-07 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4507455) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507455
2019-07 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4507455) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507449
2019-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4507449) (CVE-2019-1132)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jul 10, 2019
KB4507453
2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4507453) (CVE-2019-0880)
Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.
Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507453
2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4507453) (CVE-2019-0880)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note If the Remote Access Connection Manager service is not running after setting the Group Policy or registry key, you will need to manually start the service or restart the device. We are working on a resolution and estimate a solution will be available in late July.
workaround
Jul 10, 2019
KB4507453
2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4507453) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507450
2019-07 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4507450) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507450
2019-07 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4507450) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507435
2019-07 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4507435) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507435
2019-07 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4507435) (CVE-2019-0880)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507435
2019-07 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4507435) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507469
2019-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4507469) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507469
2019-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4507469) (CVE-2019-0880)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507469
2019-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4507469) (CVE-2019-0880)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507469
2019-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4507469) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
Run mofcomp on the following mof files on the affected host: Scvmmswitchportsettings.mof VMMDHCPSvr.mof Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
workaround
Jul 10, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507448
2019-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4507448) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507448
2019-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4507448) (CVE-2019-0880)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jul 10, 2019
KB4507448
2019-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4507448) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507458
2019-07 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB4507458) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507458
2019-07 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB4507458) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507462
2019-07 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4507462) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 9, 2019
KB4507464
2019-07 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4507464)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 9, 2019
KB4507457
2019-07 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4507457)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 9, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 9, 2019
KB4509476
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4509476)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4503289
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503289)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 9, 2019
KB4503279
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503279)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 9, 2019
KB4503291
2019-06 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB4503291)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4507458.
workaround
Jul 9, 2019
KB4499162
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4499162)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4499177
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499177)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 9, 2019
KB4505055
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4505055)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4505052
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4505052)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 9, 2019
KB4499181
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4499181)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4494440
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4494440)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 2, 2019
KB4501375
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4501375)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note If the Remote Access Connection Manager service is not running after setting the Group Policy or registry key, you will need to manually start the service or restart the device. We are working on a resolution and estimate a solution will be available in late July.
workaround
Jul 2, 2019
KB4503293
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4503293)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note If the Remote Access Connection Manager service is not running after setting the Group Policy or registry key, you will need to manually start the service or restart the device. We are working on a resolution and estimate a solution will be available in late July.
workaround
Jul 2, 2019
KB4497935
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4497935)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note If the Remote Access Connection Manager service is not running after setting the Group Policy or registry key, you will need to manually start the service or restart the device.We are working on a resolution and estimate a solution will be available in late July.
workaround
Jun 29, 2019
KB4501375
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4501375)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” when devices are manually configured to the non-default telemetry setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with or without device
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note You may need to restart the Remote Access Connection Manager service after setting the Group Policy or registry key.We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 29, 2019
KB4503293
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4503293)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” when devices are manually configured to the non-default telemetry setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with or without device
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note You may need to restart the Remote Access Connection Manager service after setting the Group Policy or registry key.We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 29, 2019
KB4497935
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4497935)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” when devices are manually configured to the non-default telemetry setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with or without device
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note You may need to restart the Remote Access Connection Manager service after setting the Group Policy or registry key.We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 28, 2019
KB4501375
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4501375)
Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.
Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 28, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
Run mofcomp on the following mof files on the affected host: Scvmmswitchportsettings.mof VMMDHCPSvr.mof Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
workaround
Jun 28, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 28, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 28, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 28, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509475.
workaround
Jun 28, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509475.
workaround
Jun 28, 2019
KB4499177
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499177)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509475.
workaround
Jun 27, 2019
KB4509479
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4509479)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509479
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4509479)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509479
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4509479)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509478
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4509478)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509478
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4509478)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509477
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4509477)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509476
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4509476)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4503293
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4503293)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4501375.
workaround
Jun 27, 2019
KB4501371
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501371)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509479.
workaround
Jun 27, 2019
KB4503288
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503288)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509478.
workaround
Jun 27, 2019
KB4503281
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503281)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509477.
workaround
Jun 27, 2019
KB4503289
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503289)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509476.
workaround
Jun 27, 2019
KB4503279
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503279)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509476.
workaround
Jun 27, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509479.
workaround
Jun 27, 2019
KB4503286
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503286)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509478.
workaround
Jun 27, 2019
KB4503284
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503284)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509477.
workaround
Jun 27, 2019
KB4499147
2019-05 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4499147)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509477.
workaround
Jun 27, 2019
KB4499162
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4499162)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509476.
workaround
Jun 27, 2019
KB4499183
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4499183)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509478.
workaround
Jun 27, 2019
KB4497934
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509479.
workaround
Jun 22, 2019
KB4503263
2019-06 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4503263)
Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing this update when Secure Boot is enabled.
This issue is resolved in KB4508776.
workaround
Jun 22, 2019
KB4503263
2019-06 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4503263)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4508776.
workaround
Jun 22, 2019
KB4503285
2019-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503285)
Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing this update when Secure Boot is enabled.
This issue is resolved in KB4503295.
workaround
Jun 22, 2019
KB4499177
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499177)
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
This issue is resolved in KB4503267.
workaround
Jun 21, 2019
KB4508776
2019-06 Update for Windows Server 2012 for x64-based Systems (KB4508776)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4508776
2019-06 Update for Windows Server 2012 for x64-based Systems (KB4508776)
Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing this update when Secure Boot is enabled.
Disabling Secure Boot should allow the update to install as expected. You can enable Secure Boot again after installation is complete.We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4508773
2019-06 Update for Windows Server 2012 R2 for x64-based Systems (KB4508773)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4503295
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503295)
Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing this update when Secure Boot is enabled.
Disabling Secure Boot should allow the update to install as expected. You can enable Secure Boot again after installation is complete.We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4503295
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503295)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4503283
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503283)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4503283
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503283)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jun 21, 2019
KB4503277
2019-06 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503277)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jun 21, 2019
KB4503273
2019-06 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4503273)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503271.
workaround
Jun 21, 2019
KB4503273
2019-06 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4503273)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503271.
workaround
Jun 21, 2019
KB4503290
2019-06 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4503290)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4508773.
workaround
Jun 21, 2019
KB4503276
2019-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503276)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503283.
workaround
Jun 21, 2019
KB4503276
2019-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503276)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503283.
workaround
Jun 21, 2019
KB4503285
2019-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503285)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503295.
workaround
Jun 21, 2019
KB4503285
2019-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503285)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503295.
workaround
Jun 21, 2019
KB4503269
2019-06 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4503269)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4508772.
workaround
Jun 21, 2019
KB4503292
2019-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503292)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503277.
workaround
Jun 21, 2019
KB4503292
2019-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503292)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503277.
workaround
Jun 21, 2019
KB4503287
2019-06 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB4503287)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4508774.
workaround
Jun 21, 2019
KB4499184
2019-05 Preview of Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4499184)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503271.
workaround
Jun 21, 2019
KB4499145
2019-05 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499145)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503295.
workaround
Jun 21, 2019
KB4499182
2019-05 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499182)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503283.
workaround
Jun 21, 2019
KB4499178
2019-05 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4499178)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503277.
workaround
Jun 21, 2019
KB4499151
2019-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499151)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503283.
workaround
Jun 21, 2019
KB4499171
2019-05 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499171)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503295.
workaround
Jun 21, 2019
KB4499164
2019-05 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4499164)(CVE-2019-0708)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503277.
workaround
Jun 21, 2019
KB4499149
2019-05 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4499149)(CVE-2019-0708)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503271.
workaround
Jun 20, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4497934
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4505056
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4505056)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4494441
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4494441)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4501835
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501835)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4493509
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4493509)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4490481
2019-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4490481)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4489899
2019-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4489899)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 19, 2019
KB4501371
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501371)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4501371
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501371)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4501371
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501371)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503288
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503288)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503288
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503288)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503281
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503281)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503289
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503289)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
After installing this update and restarting, some devices running Windows Server 2016 with Hyper-V enabled may enter Bitlocker recovery mode and receive an error, "0xC0210000".Note Windows 10, version 1607 may also be affected when Bitlocker and Hyper-V are enabled.
For a workaround for this issue, please see KB4505821. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
Run mofcomp on the following mof files on the affected host: Scvmmswitchportsettings.mof VMMDHCPSvr.mof Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
workaround
Jun 19, 2019
KB4503286
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503286)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503288.
workaround
Jun 19, 2019
KB4503284
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503284)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503281.
workaround
Jun 19, 2019
KB4503279
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503279)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503289.
workaround
Jun 19, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503294.
workaround
Jun 19, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4501371.
workaround
Jun 15, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 15, 2019
KB4503286
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503286)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503284
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503284)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503279
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503279)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
After installing this update and restarting, some devices running Windows Server 2016 with Hyper-V enabled may enter Bitlocker recovery mode and receive an error, "0xC0210000".Note Windows 10, version 1607 may also be affected when Bitlocker and Hyper-V are enabled.
For a workaround for this issue, please see KB4505821. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
Run mofcomp on the following mof files on the affected host: Scvmmswitchportsettings.mof VMMDHCPSvr.mof Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
workaround
Jun 12, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503290
2019-06 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4503290)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503293
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4503293)
Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.
Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503276
2019-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503276)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jun 12, 2019
KB4503276
2019-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503276)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503263
2019-06 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4503263)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503291
2019-06 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB4503291)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503285
2019-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503285)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503286
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503286)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503292
2019-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503292)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jun 12, 2019
KB4499147
2019-05 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4499147)
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
This issue is resolved in KB4503284.
workaround
Jun 12, 2019
KB4499162
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4499162)
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
This issue is resolved in KB4503279.
workaround
Jun 12, 2019
KB4499177
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499177)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4497934
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4497934
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934)
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4499183
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4499183)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4499183
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4499183)
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4505056
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4505056)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4505064
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4505064)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4505052
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4505052)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4499167
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4499167)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4494441
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4494441)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4494440
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4494440)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4501835
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501835)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4493437
2019-04 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4493437)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4499418
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499418)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4493473
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4493473)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4493464
2019-04 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4493464)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4493509
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4493509)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4493470
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4493470)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4490481
2019-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4490481)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4489894
2019-03 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4489894)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4489889
2019-03 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4489889)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4489899
2019-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4489899)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4489868
2019-03 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4489868)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4489882
2019-03 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4489882)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 11, 2019
KB4499145
2019-05 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499145)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4499182
2019-05 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499182)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4499165
2019-05 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4499165)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503290.
workaround
Jun 11, 2019
KB4499151
2019-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499151)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4499158
2019-05 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4499158)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503263.
workaround
Jun 11, 2019
KB4499171
2019-05 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499171)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4493462
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4493462)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4493443
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493443)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4493450
2019-04 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4493450)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503263.
workaround
Jun 11, 2019
KB4493446
2019-04 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493446)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4493451
2019-04 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4493451)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4493467
2019-04 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4493467)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503290.
workaround
Jun 11, 2019
KB4489920
2019-03 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4489920)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4489893
2019-03 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4489893)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4489891
2019-03 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4489891)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4489881
2019-03 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4489881)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4489884
2019-03 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4489884)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503263.
workaround
Jun 11, 2019
KB4489883
2019-03 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4489883)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503290.
workaround
Jun 5, 2019
KB4499177
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499177)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 5, 2019
KB4505052
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4505052)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 5, 2019
KB4494440
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4494440)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 5, 2019
KB4499418
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499418)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 5, 2019
KB4493473
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4493473)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 30, 2019
KB4497935
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4497935)
When opening games that utilize BattlEye anti-cheat software, the BattlEye UI or game may display one of the following errors: “Failed to start BattlEye Service.” “Failed to initialize BattlEye Service.” Some games that use older BattlEye versions are not compatible with Windows 10, version 1903. BattlEye has provided an updated patch for games we know are affected. For a list of recent games that use BattlEye, go to www.battleye.com/.
Do one or more of the following: Verify that your game is up to date with the latest available version. Some game platforms allow you to validate your game files, which can confirm that your installation is fully up to date. Restart your system and open the game again. Uninstall BattlEye using UninstallBE.exe, and then reopen your game. Uninstall and reinstall your game. For more troubleshooting options, go to www.battleye.com/support/faq/.
workaround
Jul 12, 2019
KB4507461
2019-07 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB4507461) (CVE-2019-1132)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4507452
2019-07 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4507452) (CVE-2019-1132)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4503271
2019-06 Preview of Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4503271)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4503287
2019-06 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB4503287)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4503273
2019-06 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4503273)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4505057
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4505057) Insider Preview
After installing this update, users may experience error “0x800705b4” when launching Windows Defender Application Guard or Windows Sandbox.
Use the credentials of a local admin to create and set the following registry keys on the Host OS then restart the Host: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Containers\CmService\Policy] "DisableClone"=dword:00000001 "DisableSnapshot"=dword:00000001
workaround
Jul 12, 2019
KB4497936
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4497936)
After installing this update, users may experience error “0x800705b4” when launching Windows Defender Application Guard or Windows Sandbox.
Use the credentials of a local admin to create and set the following registry keys on the Host OS then restart the Host: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Containers\CmService\Policy] "DisableClone"=dword:00000001 "DisableSnapshot"=dword:00000001 Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 12, 2019
KB4088881
2018-03 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4088881)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
The issue is resolved in KB4093113. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088882
2018-03 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4088882)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093121. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088883
2018-03 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4088883)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093116. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088876
2018-03 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4088876)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093114. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088880
2018-03 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4088880)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093122. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088877
2018-03 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4088877)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093123. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088878
2018-03 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4088878)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093108. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088875
2018-03 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4088875)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093118. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4088879
2018-03 Security Only Quality Update for Windows 8.1 for x64-based Systems (KB4088879)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093115. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4075212
2018-02 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4075212)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093121. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4075211
2018-02 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4075211)
Because of an issue that affects some versions of antivirus software, this fix is being applied only to the computers on which the antivirus ISV have updated the ALLOW REGKEY.
The issue is resolved in KB4093113. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4074598
2018-02 Security Monthly Quality Rollup for Windows 7 for x64-based Systems - Meltdown and Spectre(KB4074598)
Because of an issue that affects some versions of antivirus software, this fix is being applied only to the computers on which the antivirus ISV have updated the ALLOW REGKEY.
This issue is resolved in KB4093118. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4074587
2018-02 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems - Meltdown and Spectre(KB4074587)
Because of an issue that affects some versions of antivirus software, this fix is being applied only to the computers on which the antivirus ISV have updated the ALLOW REGKEY.
This issue is resolved in KB4093108. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4074597
2018-02 Security Only Quality Update for Windows 8.1 for x64-based Systems - Meltdown and SpectreKB4074597)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093115. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4074594
2018-02 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems - Meltdown and Spectre(KB4074594)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093114. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4057400
2018-01 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems - Meltdown and Spectre (KB4057400)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
The issue is resolved in KB4093113. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4057401
2018-01 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems - Meltdown and Spectre(KB4057401)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093121. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4056895
2018-01 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems - Meltdown and Spectre (KB4056895)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093114. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4056894
2018-01 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems - Meltdown and Spectre (KB4056894)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093118. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4056898
2018-01 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems - Meltdown and Spectre (KB4056898)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093115. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 12, 2019
KB4056897
2018-01 Security Only Quality Update for Windows 7 for x64-based Systems - Meltdown and Spectre (KB4056897)
Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.
This issue is resolved in KB4093108. You no longer need the following ALLOW REGKEY to detect and be offered this update: HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat\cadca5fe-87d3-4b96-b7fb-a231484277cc
workaround
Jul 11, 2019
KB4507464
2019-07 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4507464) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507448
2019-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4507448) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507456
2019-07 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4507456) (CVE-2019-1132)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507462
2019-07 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4507462) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507449
2019-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4507449) (CVE-2019-1132)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507457
2019-07 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4507457) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503295
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503295)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503283
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503283)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming releas
workaround
Jul 11, 2019
KB4503277
2019-06 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503277)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503285
2019-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503285)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503269
2019-06 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4503269)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503292
2019-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503292)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503290
2019-06 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4503290)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503276
2019-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503276)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503263
2019-06 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4503263)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507435
2019-07 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4507435) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507469
2019-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4507469) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release
workaround
Jul 11, 2019
KB4507455
2019-07 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4507455) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4507453
2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4507453) (CVE-2019-0880)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4501375
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4501375)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4509479
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4509479)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4509478
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4509478)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4509477
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4509477)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4501371
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501371)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503288
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503288)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503281
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503281)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503286
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503286)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503284
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503284)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 11, 2019
KB4503293
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4503293)
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 isnt connected or cant be accessed" after installing this update on a WDS server.
For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507455
2019-07 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4507455) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507455
2019-07 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4507455) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507449
2019-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4507449) (CVE-2019-1132)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jul 10, 2019
KB4507453
2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4507453) (CVE-2019-0880)
Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.
Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507453
2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4507453) (CVE-2019-0880)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note If the Remote Access Connection Manager service is not running after setting the Group Policy or registry key, you will need to manually start the service or restart the device. We are working on a resolution and estimate a solution will be available in late July.
workaround
Jul 10, 2019
KB4507453
2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4507453) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507450
2019-07 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4507450) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507450
2019-07 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4507450) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507435
2019-07 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4507435) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507435
2019-07 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4507435) (CVE-2019-0880)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507435
2019-07 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4507435) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507469
2019-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4507469) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507469
2019-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4507469) (CVE-2019-0880)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507469
2019-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4507469) (CVE-2019-0880)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507469
2019-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4507469) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
Run mofcomp on the following mof files on the affected host: Scvmmswitchportsettings.mof VMMDHCPSvr.mof Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
workaround
Jul 10, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507460
2019-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4507460) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507448
2019-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4507448) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507448
2019-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4507448) (CVE-2019-0880)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jul 10, 2019
KB4507448
2019-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4507448) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507458
2019-07 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB4507458) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507458
2019-07 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB4507458) (CVE-2019-0880)
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.Note Users who have already migrated from Window-Eyes to Freedom Scientifics other screen reader, JAWS, should not be affected by this issue.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 10, 2019
KB4507462
2019-07 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4507462) (CVE-2019-0880)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 9, 2019
KB4507464
2019-07 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4507464)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 9, 2019
KB4507457
2019-07 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4507457)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 9, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 9, 2019
KB4509476
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4509476)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4503289
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503289)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 9, 2019
KB4503279
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503279)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 9, 2019
KB4503291
2019-06 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB4503291)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4507458.
workaround
Jul 9, 2019
KB4499162
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4499162)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4499177
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499177)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 9, 2019
KB4505055
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4505055)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4505052
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4505052)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 9, 2019
KB4499181
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4499181)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507450.
workaround
Jul 9, 2019
KB4494440
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4494440)
After installing this update and restarting, some devices with Hyper-V enabled may enter BitLocker recovery mode and receive an error, "0xC0210000".
This issue is resolved in KB4507460.
workaround
Jul 2, 2019
KB4501375
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4501375)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note If the Remote Access Connection Manager service is not running after setting the Group Policy or registry key, you will need to manually start the service or restart the device. We are working on a resolution and estimate a solution will be available in late July.
workaround
Jul 2, 2019
KB4503293
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4503293)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note If the Remote Access Connection Manager service is not running after setting the Group Policy or registry key, you will need to manually start the service or restart the device. We are working on a resolution and estimate a solution will be available in late July.
workaround
Jul 2, 2019
KB4497935
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4497935)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note If the Remote Access Connection Manager service is not running after setting the Group Policy or registry key, you will need to manually start the service or restart the device.We are working on a resolution and estimate a solution will be available in late July.
workaround
Jun 29, 2019
KB4501375
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4501375)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” when devices are manually configured to the non-default telemetry setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with or without device
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note You may need to restart the Remote Access Connection Manager service after setting the Group Policy or registry key.We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 29, 2019
KB4503293
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4503293)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” when devices are manually configured to the non-default telemetry setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with or without device
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note You may need to restart the Remote Access Connection Manager service after setting the Group Policy or registry key.We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 29, 2019
KB4497935
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4497935)
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” when devices are manually configured to the non-default telemetry setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with or without device
To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note You may need to restart the Remote Access Connection Manager service after setting the Group Policy or registry key.We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 28, 2019
KB4501375
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4501375)
Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.
Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 28, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
Run mofcomp on the following mof files on the affected host: Scvmmswitchportsettings.mof VMMDHCPSvr.mof Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
workaround
Jun 28, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 28, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 28, 2019
KB4509475
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4509475)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 28, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509475.
workaround
Jun 28, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509475.
workaround
Jun 28, 2019
KB4499177
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499177)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509475.
workaround
Jun 27, 2019
KB4509479
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4509479)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509479
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4509479)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509479
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4509479)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509478
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4509478)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509478
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4509478)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509477
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4509477)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4509476
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4509476)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 27, 2019
KB4503293
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4503293)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4501375.
workaround
Jun 27, 2019
KB4501371
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501371)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509479.
workaround
Jun 27, 2019
KB4503288
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503288)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509478.
workaround
Jun 27, 2019
KB4503281
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503281)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509477.
workaround
Jun 27, 2019
KB4503289
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503289)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509476.
workaround
Jun 27, 2019
KB4503279
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503279)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509476.
workaround
Jun 27, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509479.
workaround
Jun 27, 2019
KB4503286
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503286)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509478.
workaround
Jun 27, 2019
KB4503284
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503284)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509477.
workaround
Jun 27, 2019
KB4499147
2019-05 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4499147)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509477.
workaround
Jun 27, 2019
KB4499162
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4499162)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509476.
workaround
Jun 27, 2019
KB4499183
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4499183)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509478.
workaround
Jun 27, 2019
KB4497934
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934)
Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing this update. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”
This issue is resolved in KB4509479.
workaround
Jun 22, 2019
KB4503263
2019-06 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4503263)
Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing this update when Secure Boot is enabled.
This issue is resolved in KB4508776.
workaround
Jun 22, 2019
KB4503263
2019-06 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4503263)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4508776.
workaround
Jun 22, 2019
KB4503285
2019-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503285)
Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing this update when Secure Boot is enabled.
This issue is resolved in KB4503295.
workaround
Jun 22, 2019
KB4499177
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499177)
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
This issue is resolved in KB4503267.
workaround
Jun 21, 2019
KB4508776
2019-06 Update for Windows Server 2012 for x64-based Systems (KB4508776)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4508776
2019-06 Update for Windows Server 2012 for x64-based Systems (KB4508776)
Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing this update when Secure Boot is enabled.
Disabling Secure Boot should allow the update to install as expected. You can enable Secure Boot again after installation is complete.We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4508773
2019-06 Update for Windows Server 2012 R2 for x64-based Systems (KB4508773)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4503295
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503295)
Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing this update when Secure Boot is enabled.
Disabling Secure Boot should allow the update to install as expected. You can enable Secure Boot again after installation is complete.We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4503295
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503295)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4503283
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503283)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 21, 2019
KB4503283
2019-06 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503283)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jun 21, 2019
KB4503277
2019-06 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503277)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jun 21, 2019
KB4503273
2019-06 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4503273)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503271.
workaround
Jun 21, 2019
KB4503273
2019-06 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4503273)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503271.
workaround
Jun 21, 2019
KB4503290
2019-06 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4503290)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4508773.
workaround
Jun 21, 2019
KB4503276
2019-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503276)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503283.
workaround
Jun 21, 2019
KB4503276
2019-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503276)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503283.
workaround
Jun 21, 2019
KB4503285
2019-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503285)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503295.
workaround
Jun 21, 2019
KB4503285
2019-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503285)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503295.
workaround
Jun 21, 2019
KB4503269
2019-06 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4503269)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4508772.
workaround
Jun 21, 2019
KB4503292
2019-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503292)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503277.
workaround
Jun 21, 2019
KB4503292
2019-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503292)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503277.
workaround
Jun 21, 2019
KB4503287
2019-06 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB4503287)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4508774.
workaround
Jun 21, 2019
KB4499184
2019-05 Preview of Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4499184)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503271.
workaround
Jun 21, 2019
KB4499145
2019-05 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499145)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503295.
workaround
Jun 21, 2019
KB4499182
2019-05 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499182)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503283.
workaround
Jun 21, 2019
KB4499178
2019-05 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4499178)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503277.
workaround
Jun 21, 2019
KB4499151
2019-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499151)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503283.
workaround
Jun 21, 2019
KB4499171
2019-05 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499171)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503295.
workaround
Jun 21, 2019
KB4499164
2019-05 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4499164)(CVE-2019-0708)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503277.
workaround
Jun 21, 2019
KB4499149
2019-05 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4499149)(CVE-2019-0708)
Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
This issue is resolved in KB4503271.
workaround
Jun 20, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4497934
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4505056
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4505056)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4494441
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4494441)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4501835
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501835)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4493509
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4493509)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4490481
2019-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4490481)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 20, 2019
KB4489899
2019-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4489899)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
This issue is resolved in KB4501371.
workaround
Jun 19, 2019
KB4501371
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501371)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4501371
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501371)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4501371
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501371)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503288
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503288)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503288
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503288)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503281
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503281)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503289
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503289)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
After installing this update and restarting, some devices running Windows Server 2016 with Hyper-V enabled may enter Bitlocker recovery mode and receive an error, "0xC0210000".Note Windows 10, version 1607 may also be affected when Bitlocker and Hyper-V are enabled.
For a workaround for this issue, please see KB4505821. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 19, 2019
KB4503294
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503294)
For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
Run mofcomp on the following mof files on the affected host: Scvmmswitchportsettings.mof VMMDHCPSvr.mof Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
workaround
Jun 19, 2019
KB4503286
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503286)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503288.
workaround
Jun 19, 2019
KB4503284
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503284)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503281.
workaround
Jun 19, 2019
KB4503279
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503279)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503289.
workaround
Jun 19, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4503294.
workaround
Jun 19, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, "MMC has detected an error in a snap-in and will unload it." and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.
This issue is resolved in KB4501371.
workaround
Jun 15, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 15, 2019
KB4503286
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503286)
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503284
2019-06 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4503284)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503279
2019-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4503279)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
After installing this update and restarting, some devices running Windows Server 2016 with Hyper-V enabled may enter Bitlocker recovery mode and receive an error, "0xC0210000".Note Windows 10, version 1607 may also be affected when Bitlocker and Hyper-V are enabled.
For a workaround for this issue, please see KB4505821. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
Run mofcomp on the following mof files on the affected host: Scvmmswitchportsettings.mof VMMDHCPSvr.mof Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
workaround
Jun 12, 2019
KB4503267
2019-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4503267)
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503327
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503290
2019-06 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4503290)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503293
2019-06 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4503293)
Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.
Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503276
2019-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503276)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jun 12, 2019
KB4503276
2019-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4503276)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503263
2019-06 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4503263)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503291
2019-06 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB4503291)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503285
2019-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4503285)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503286
2019-06 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4503286)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 12, 2019
KB4503292
2019-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4503292)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
Jun 12, 2019
KB4499147
2019-05 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4499147)
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
This issue is resolved in KB4503284.
workaround
Jun 12, 2019
KB4499162
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4499162)
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
This issue is resolved in KB4503279.
workaround
Jun 12, 2019
KB4499177
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499177)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4497934
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4497934
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934)
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4499183
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4499183)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4499183
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4499183)
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4505056
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4505056)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4505064
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4505064)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4505052
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4505052)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4499167
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4499167)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4494441
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4494441)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4494440
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4494440)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4501835
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501835)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4493437
2019-04 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4493437)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4499418
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499418)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4493473
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4493473)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4493464
2019-04 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4493464)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4493509
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4493509)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4493470
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4493470)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4490481
2019-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4490481)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4489894
2019-03 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4489894)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4489889
2019-03 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4489889)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 12, 2019
KB4489899
2019-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4489899)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503327.
workaround
Jun 12, 2019
KB4489868
2019-03 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4489868)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503286.
workaround
Jun 12, 2019
KB4489882
2019-03 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4489882)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503267.
workaround
Jun 11, 2019
KB4499145
2019-05 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499145)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4499182
2019-05 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499182)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4499165
2019-05 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4499165)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503290.
workaround
Jun 11, 2019
KB4499151
2019-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499151)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4499158
2019-05 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4499158)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503263.
workaround
Jun 11, 2019
KB4499171
2019-05 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499171)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4493462
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4493462)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4493443
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493443)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4493450
2019-04 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4493450)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503263.
workaround
Jun 11, 2019
KB4493446
2019-04 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493446)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4493451
2019-04 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4493451)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4493467
2019-04 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4493467)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503290.
workaround
Jun 11, 2019
KB4489920
2019-03 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4489920)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4489893
2019-03 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4489893)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4489891
2019-03 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4489891)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503285.
workaround
Jun 11, 2019
KB4489881
2019-03 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4489881)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503276.
workaround
Jun 11, 2019
KB4489884
2019-03 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4489884)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved KB4503263.
workaround
Jun 11, 2019
KB4489883
2019-03 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4489883)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
This issue is resolved in KB4503290.
workaround
Jun 5, 2019
KB4499177
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499177)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 5, 2019
KB4505052
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4505052)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 5, 2019
KB4494440
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4494440)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 5, 2019
KB4499418
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499418)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 5, 2019
KB4493473
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4493473)
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update 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.
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 30, 2019
KB4497935
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4497935)
When opening games that utilize BattlEye anti-cheat software, the BattlEye UI or game may display one of the following errors: “Failed to start BattlEye Service.” “Failed to initialize BattlEye Service.” Some games that use older BattlEye versions are not compatible with Windows 10, version 1903. BattlEye has provided an updated patch for games we know are affected. For a list of recent games that use BattlEye, go to www.battleye.com/.
Do one or more of the following: Verify that your game is up to date with the latest available version. Some game platforms allow you to validate your game files, which can confirm that your installation is fully up to date. Restart your system and open the game again. Uninstall BattlEye using UninstallBE.exe, and then reopen your game. Uninstall and reinstall your game. For more troubleshooting options, go to www.battleye.com/support/faq/.
workaround
May 16, 2019
KB4499151
2019-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499151)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4499167
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4499167)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4499171
2019-05 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499171)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4494440
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4494440)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4499165
2019-05 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4499165)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4497936
2019-05 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4497936)
After installing this update, users may experience error “0x800705b4” when launching Windows Defender Application Guard or Windows Sandbox.
Use the credentials of a local admin to create and set the following registry keys on the Host OS then restart the Host: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Containers\CmService\Policy] "DisableClone"=dword:00000001 "DisableSnapshot"=dword:00000001 Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4499158
2019-05 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4499158)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4494441
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4494441)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4501835
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501835)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493462
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4493462)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493443
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493443)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493437
2019-04 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4493437)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4499418
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499418)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493473
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4493473)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493464
2019-04 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4493464)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493467
2019-04 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4493467)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493509
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4493509)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493450
2019-04 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4493450)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493446
2019-04 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493446)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493451
2019-04 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4493451)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4493470
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4493470)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4490481
2019-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4490481)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489920
2019-03 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4489920)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489893
2019-03 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4489893)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489894
2019-03 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4489894)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489889
2019-03 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4489889)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489899
2019-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4489899)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489868
2019-03 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4489868)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489882
2019-03 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4489882)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489891
2019-03 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4489891)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489881
2019-03 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4489881)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489884
2019-03 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4489884)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4489883
2019-03 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4489883)
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI. Open Windows Deployment Services from Windows Administrative Tools. Expand Servers and right-click a WDS server. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. Option 3: Set the following registry value to 0: “HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”. Restart the WDSServer service after disabling the Variable Window Extension. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 16, 2019
KB4494441
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4494441)
Some customers report that KB4494441 installed twice on their device. In certain situations, installing an update requires multiple download and restart steps. If two intermediate steps of the installation complete successfully, the View your Update history page will report that installation completed successfully twice.
No action is required on your part. The update installation may take longer and may require more than one restart, but will install successfully after all intermediate installation steps have completed. We are working on improving this update experience to ensure the Update history correctly reflects the installation of the latest cumulative update (LCU).
workaround
May 16, 2019
KB4499151
2019-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499151)
If previous dictionary updates are installed, the Japanese input method editor (IME) doesnt show the new Japanese Era name as a text input option.
If you see any of the previous dictionary updates listed below, uninstall it from Programs and features > Uninstall or change a program. New words that were in previous dictionary updates are also in this update. Update for Japanese Microsoft IME Standard Dictionary (15.0.2013) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.2013) Update for Japanese Microsoft IME Standard Dictionary (15.0.1215) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.1215) Update for Japanese Microsoft IME Standard Dictionary (15.0.1080) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.1080)
workaround
May 16, 2019
KB4499171
2019-05 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499171)
If previous dictionary updates are installed, the Japanese input method editor (IME) doesnt show the new Japanese Era name as a text input option.
If you see any of the previous dictionary updates listed below, uninstall it from Programs and features > Uninstall or change a program. New words that were in previous dictionary updates are also in this update. Update for Japanese Microsoft IME Standard Dictionary (15.0.2013) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.2013) Update for Japanese Microsoft IME Standard Dictionary (15.0.1215) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.1215) Update for Japanese Microsoft IME Standard Dictionary (15.0.1080) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.1080)
workaround
May 16, 2019
KB4493462
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4493462)
If previous dictionary updates are installed, the Japanese input method editor (IME) doesnt show the new Japanese Era name as a text input option.
If you see any of the previous dictionary updates listed below, uninstall it from Programs and features > Uninstall or change a program. New words that were in previous dictionary updates are also in this update. Update for Japanese Microsoft IME Standard Dictionary (15.0.2013) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.2013) Update for Japanese Microsoft IME Standard Dictionary (15.0.1215) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.1215) Update for Japanese Microsoft IME Standard Dictionary (15.0.1080) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.1080)
workaround
May 16, 2019
KB4493443
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493443)
If previous dictionary updates are installed, the Japanese input method editor (IME) doesnt show the new Japanese Era name as a text input option.
If you see any of the previous dictionary updates listed below, uninstall it from Programs and features > Uninstall or change a program. New words that were in previous dictionary updates are also in this update. Update for Japanese Microsoft IME Standard Dictionary (15.0.2013) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.2013) Update for Japanese Microsoft IME Standard Dictionary (15.0.1215) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.1215) Update for Japanese Microsoft IME Standard Dictionary (15.0.1080) Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.1080)
workaround
May 15, 2019
KB4499164
2019-05 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4499164)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
May 15, 2019
KB4494440
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4494440)
For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
Run mofcomp on the following mof files on the affected host: Scvmmswitchportsettings.mof VMMDHCPSvr.mof Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
workaround
May 15, 2019
KB4494440
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4494440)
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4494440
2019-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4494440)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4494441
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4494441)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4494441
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4494441)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
You can use another browser, such as Internet Explorer to print your documents. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4494441
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4494441)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4499165
2019-05 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4499165)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4499181
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4499181)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4499158
2019-05 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4499158)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4499179
2019-05 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4499179)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4499151
2019-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499151)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4499151
2019-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4499151)
Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update.
We are presently investigating this issue with McAfee. Guidance for McAfee customers can be found in the following McAfee support articles: McAfee Security (ENS) Threat Prevention 10.x McAfee Host Intrusion Prevention (Host IPS) 8.0 McAfee VirusScan Enterprise (VSE) 8.8
workaround
May 15, 2019
KB4499167
2019-05 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4499167)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4499171
2019-05 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4499171)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4499154
2019-05 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB4499154)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 15, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing this update.
This issue is resolved in KB4494441.
workaround
May 15, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4494441.
workaround
May 15, 2019
KB4502112
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4502112)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4499181.
workaround
May 15, 2019
KB4493462
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4493462)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4499171.
workaround
May 15, 2019
KB4493453
2019-04 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493453)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499164.
workaround
May 15, 2019
KB4493453
2019-04 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493453)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates.Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article
workaround
May 15, 2019
KB4493453
2019-04 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493453)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates.Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.
workaround
May 15, 2019
KB4493453
2019-04 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493453)
Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates.ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.
workaround
May 15, 2019
KB4493453
2019-04 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493453)
Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install this update and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.
This issue has been resolved. Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.
workaround
May 15, 2019
KB4493453
2019-04 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493453)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4499164.
workaround
May 15, 2019
KB4493443
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493443)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates.Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article
workaround
May 15, 2019
KB4493443
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493443)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates.Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.
workaround
May 15, 2019
KB4493443
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493443)
Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates.ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.
workaround
May 15, 2019
KB4493443
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493443)
Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install this update and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.
This issue has been resolved. Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.
workaround
May 15, 2019
KB4493443
2019-04 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493443)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4499151.
workaround
May 15, 2019
KB4493460
2019-04 Preview of Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4493460)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499149.
workaround
May 15, 2019
KB4493460
2019-04 Preview of Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4493460)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article
workaround
May 15, 2019
KB4493460
2019-04 Preview of Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4493460)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.
workaround
May 15, 2019
KB4493460
2019-04 Preview of Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4493460)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4499149.
workaround
May 15, 2019
KB4493437
2019-04 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4493437)
Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing this update.
This issue is resolved in KB4499167.
workaround
May 15, 2019
KB4493437
2019-04 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4493437)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4499167.
workaround
May 15, 2019
KB4493440
2019-04 Cumulative Update for Windows Server 2016 (1709) for x64-based Systems (KB4493440)
Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing this update.
This issue is resolved in KB4499179.
workaround
May 15, 2019
KB4493436
2019-04 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4493436)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4499181.
workaround
May 15, 2019
KB4493440
2019-04 Cumulative Update for Windows Server 2016 (1709) for x64-based Systems (KB4493440)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4499179.
workaround
May 15, 2019
KB4493473
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4493473)
Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) protocol may fail after installing this update.
This issue is resolved in KB4494440.
workaround
May 15, 2019
KB4493473
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4493473)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4494440.
workaround
May 15, 2019
KB4499418
2019-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4499418)
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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4494440.
workaround
May 15, 2019
KB4493467
2019-04 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4493467)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
workaround
May 15, 2019
KB4493467
2019-04 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4493467)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. We are presently investigating this issue with Avira and will provide an update when available.
workaround
May 15, 2019
KB4493467
2019-04 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4493467)
Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install this update and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.
This issue has been resolved. Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.
workaround
May 15, 2019
KB4493450
2019-04 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4493450)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
workaround
May 15, 2019
KB4493450
2019-04 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB4493450)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.
workaround
May 15, 2019
KB4493448
2019-04 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4493448)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499175.
workaround
May 15, 2019
KB4493448
2019-04 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4493448)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
workaround
May 15, 2019
KB4493448
2019-04 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4493448)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. We are presently investigating this issue with Avira and will provide an update when available.
workaround
May 15, 2019
KB4493448
2019-04 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4493448)
Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install this update and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.
This issue has been resolved. Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.
workaround
May 15, 2019
KB4493446
2019-04 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493446)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
workaround
May 15, 2019
KB4493446
2019-04 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493446)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.
workaround
May 15, 2019
KB4493446
2019-04 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493446)
Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.
workaround
May 15, 2019
KB4493446
2019-04 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493446)
Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install this update and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.
This issue has been resolved. Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.
workaround
May 15, 2019
KB4493451
2019-04 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4493451)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
workaround
May 15, 2019
KB4493451
2019-04 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4493451)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.
workaround
May 15, 2019
KB4493458
2019-04 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB4493458)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499180.
workaround
May 15, 2019
KB4493458
2019-04 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB4493458)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
workaround
May 15, 2019
KB4493458
2019-04 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB4493458)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.
workaround
May 15, 2019
KB4493472
2019-04 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493472)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499164.
workaround
May 15, 2019
KB4493472
2019-04 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493472)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
workaround
May 15, 2019
KB4493472
2019-04 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493472)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.
workaround
May 15, 2019
KB4493472
2019-04 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493472)
Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.
workaround
May 15, 2019
KB4493472
2019-04 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493472)
Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install this update and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.
This issue has been resolved. Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.
workaround
May 15, 2019
KB4493471
2019-04 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4493471)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499149.
workaround
May 15, 2019
KB4493471
2019-04 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4493471)
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.
workaround
May 15, 2019
KB4493471
2019-04 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4493471)
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.
workaround
May 15, 2019
KB4489887
2019-03 Preview of Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4489887)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499149.
workaround
May 15, 2019
KB4489892
2019-03 Preview of Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4489892)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499164.
workaround
May 15, 2019
KB4489878
2019-03 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4489878)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499164.
workaround
May 15, 2019
KB4489880
2019-03 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB4489880)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499149.
workaround
May 15, 2019
KB4489885
2019-03 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4489885)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499175.
workaround
May 15, 2019
KB4489876
2019-03 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB4489876)
After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.
This issue is resolved in KB4499180.
workaround
May 9, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Arcabit has confirmed this issue is not applicable to Window 10, version 1809.
workaround
May 9, 2019
KB4501835
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501835)
Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Arcabit has confirmed this issue is not applicable to Window 10, version 1809.
workaround
May 9, 2019
KB4493509
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4493509)
Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update.
This issue has been resolved. Arcabit has confirmed this issue is not applicable to Window 10, version 1809.
workaround
May 5, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 5, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
You can use another browser, such as Internet Explorer to print your documents. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 5, 2019
KB4495667
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see "Manage the input and display language settings in Windows 10". Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see "Update Windows 10". Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 3, 2019
KB4501835
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501835)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 3, 2019
KB4501835
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501835)
After installing this update, Custom URI Schemes for Application Protocol handlers may not start the corresponding application for local intranet and trusted sites on Internet Explorer.
This issue is resolved in KB4495667.
workaround
May 3, 2019
KB4501835
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501835)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
You can use another browser, such as Internet Explorer to print your documents. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 3, 2019
KB4501835
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4501835)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see "Manage the input and display language settings in Windows 10". Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see "Update Windows 10". Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 3, 2019
KB4502112
2019-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4502112)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership.Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 3, 2019
KB4493509
2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4493509)
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, "Your printer has experienced an unexpected configuration problem. 0x80070007e."
You can use another browser, such as Internet Explorer to print your documents. Microsoft is working on a resolution and will provide an update in an upcoming release.

Disclaimer:This webpage is intended to provide you information about patch announcement for certain specific software products. The information is provided "As Is" without warranty of any kind. The links provided point to pages on the vendors websites. You can get more information by clicking the links to visit the relevant pages on the vendors website.