Latest content is published (#371)

This commit is contained in:
DocsPreview 2019-06-06 12:21:23 -07:00 committed by Corrine Horvath
parent 6853e1aea5
commit cd819d71d3
12 changed files with 24 additions and 76 deletions

View File

@ -43,7 +43,6 @@ sections:
<tr><td><div id='186msg'></div><b>Applications using Microsoft Jet database fail to open</b><br>Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.<br><br><a href = '#186msgdesc'>See details ></a></td><td>OS Build 10240.18094<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480962' target='_blank'>KB4480962</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487018' target='_blank'>KB4487018</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr> <tr><td><div id='186msg'></div><b>Applications using Microsoft Jet database fail to open</b><br>Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.<br><br><a href = '#186msgdesc'>See details ></a></td><td>OS Build 10240.18094<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480962' target='_blank'>KB4480962</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487018' target='_blank'>KB4487018</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr>
<tr><td><div id='230msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#230msgdesc'>See details ></a></td><td>OS Build 10240.18094<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480962' target='_blank'>KB4480962</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487018' target='_blank'>KB4487018</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr> <tr><td><div id='230msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#230msgdesc'>See details ></a></td><td>OS Build 10240.18094<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480962' target='_blank'>KB4480962</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487018' target='_blank'>KB4487018</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr>
<tr><td><div id='212msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#212msgdesc'>See details ></a></td><td>OS Build 10240.18005<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462922' target='_blank'>KB4462922</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471323' target='_blank'>KB4471323</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr> <tr><td><div id='212msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#212msgdesc'>See details ></a></td><td>OS Build 10240.18005<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462922' target='_blank'>KB4462922</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471323' target='_blank'>KB4471323</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='133msg'></div><b>Guest VMs running Unicast NLB fail to respond after restart</b><br>All guest virtual machines running Unicast NLB fail to respond to NLB requests after the virtual machines restart.<br><br><a href = '#133msgdesc'>See details ></a></td><td>OS Build 10240.17976<br><br>September 11, 2018<br><a href ='https://support.microsoft.com/help/4457132' target='_blank'>KB4457132</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4462922' target='_blank'>KB4462922</a></td><td>October 09, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "
@ -104,12 +103,3 @@ sections:
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='212msgdesc'></div><b>Unable to use Seek bar in Windows Media Player</b><div>After installing <a href=\"https://support.microsoft.com/help/4462922\" target=\"_blank\">KB4462922</a>, users may not be able to use the <strong>Seek</strong> bar in Windows Media Player when playing specific files. This issue does not affect normal playback.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4471323\" target=\"_blank\">KB4471323</a>.</div><br><a href ='#212msg'>Back to top</a></td><td>OS Build 10240.18005<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462922' target='_blank'>KB4462922</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471323' target='_blank'>KB4471323</a></td><td>Resolved:<br>December 11, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='212msgdesc'></div><b>Unable to use Seek bar in Windows Media Player</b><div>After installing <a href=\"https://support.microsoft.com/help/4462922\" target=\"_blank\">KB4462922</a>, users may not be able to use the <strong>Seek</strong> bar in Windows Media Player when playing specific files. This issue does not affect normal playback.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4471323\" target=\"_blank\">KB4471323</a>.</div><br><a href ='#212msg'>Back to top</a></td><td>OS Build 10240.18005<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462922' target='_blank'>KB4462922</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471323' target='_blank'>KB4471323</a></td><td>Resolved:<br>December 11, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "
- title: September 2018
- items:
- type: markdown
text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='133msgdesc'></div><b>Guest VMs running Unicast NLB fail to respond after restart</b><div>All guest virtual machines running Unicast NLB fail to respond to NLB requests after the virtual machines restart.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015</li><li>Server: Windows Server, version 1803</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4462922\" target=\"_blank\">KB4462922</a>.</div><br><a href ='#133msg'>Back to top</a></td><td>OS Build 10240.17976<br><br>September 11, 2018<br><a href ='https://support.microsoft.com/help/4457132' target='_blank'>KB4457132</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4462922' target='_blank'>KB4462922</a></td><td>Resolved:<br>October 09, 2018 <br>10:00 AM PT<br><br>Opened:<br>September 11, 2018 <br>10:00 AM PT</td></tr>
</table>
"

View File

@ -52,8 +52,6 @@ sections:
<tr><td><div id='229msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#229msgdesc'>See details ></a></td><td>OS Build 14393.2724<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480961' target='_blank'>KB4480961</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480977' target='_blank'>KB4480977</a></td><td>January 17, 2019 <br>02:00 PM PT</td></tr> <tr><td><div id='229msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#229msgdesc'>See details ></a></td><td>OS Build 14393.2724<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480961' target='_blank'>KB4480961</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480977' target='_blank'>KB4480977</a></td><td>January 17, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='141msg'></div><b>System becomes unresponsive when end-user-defined characters (EUDC) are used</b><br>When features related to end-user-defined characters (EUDC) are used, the entire system may become unresponsive.<br><br><a href = '#141msgdesc'>See details ></a></td><td>OS Build 14393.2639<br><br>November 27, 2018<br><a href ='https://support.microsoft.com/help/4467684' target='_blank'>KB4467684</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471321' target='_blank'>KB4471321</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr> <tr><td><div id='141msg'></div><b>System becomes unresponsive when end-user-defined characters (EUDC) are used</b><br>When features related to end-user-defined characters (EUDC) are used, the entire system may become unresponsive.<br><br><a href = '#141msgdesc'>See details ></a></td><td>OS Build 14393.2639<br><br>November 27, 2018<br><a href ='https://support.microsoft.com/help/4467684' target='_blank'>KB4467684</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471321' target='_blank'>KB4471321</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='209msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#209msgdesc'>See details ></a></td><td>OS Build 14393.2551<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462917' target='_blank'>KB4462917</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471321' target='_blank'>KB4471321</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr> <tr><td><div id='209msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#209msgdesc'>See details ></a></td><td>OS Build 14393.2551<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462917' target='_blank'>KB4462917</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471321' target='_blank'>KB4471321</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='140msg'></div><b>Issues with install and activation of Key Management Service (KMS) (CSVLK) host keys</b><br>Installation and client activation of Windows Server 2019 and 1809 LTSC Key Management Service (KMS) (CSVLK) host keys do not work as expected.<br><br><a href = '#140msgdesc'>See details ></a></td><td>OS Build 14393.2457<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343884' target='_blank'>KB4343884</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4467684' target='_blank'>KB4467684</a></td><td>November 27, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='139msg'></div><b>Promotions that create non-root domains fail with optional features enabled</b><br>Windows Server 2016 promotions that create non-root domains fail in forests in which optional features like Active Directory recycle have been enabled.<br><br><a href = '#139msgdesc'>See details ></a></td><td>OS Build 14393.2515<br><br>September 20, 2018<br><a href ='https://support.microsoft.com/help/4457127' target='_blank'>KB4457127</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4467684' target='_blank'>KB4467684</a></td><td>November 27, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "
@ -139,21 +137,11 @@ sections:
</table> </table>
" "
- title: September 2018
- items:
- type: markdown
text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='139msgdesc'></div><b>Promotions that create non-root domains fail with optional features enabled</b><div>After installing <a href=\"https://support.microsoft.com/help/4457127\" target=\"_blank\">KB4457127</a>, Windows Server 2016 promotions that create non-root domains fail in forests in which optional features like Active Directory recycle have been enabled. The error is, “The replication operation encountered a database error.”</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Server: Windows Server 2016</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4467684\" target=\"_blank\">KB4467684</a>.</div><br><a href ='#139msg'>Back to top</a></td><td>OS Build 14393.2515<br><br>September 20, 2018<br><a href ='https://support.microsoft.com/help/4457127' target='_blank'>KB4457127</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4467684' target='_blank'>KB4467684</a></td><td>Resolved:<br>November 27, 2018 <br>10:00 AM PT<br><br>Opened:<br>September 20, 2018 <br>10:00 AM PT</td></tr>
</table>
"
- title: August 2018 - title: August 2018
- items: - items:
- type: markdown - type: markdown
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='132msgdesc'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><div>After you install the <a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/08/30/net-framework-august-2018-preview-of-quality-rollup/\" target=\"_blank\">August Preview of Quality Rollup</a> or<a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/09/11/net-framework-september-2018-security-and-quality-rollup\" target=\"_blank\"> September 11, 2018 .NET Framework update</a>, instantiation of SqlConnection can throw an exception.</div><div><br></div><div>For more information about this issue, see the following article in the Microsoft Knowledge Base: <a href=\"https://support.microsoft.com/help/4470809\" target=\"_blank\">4470809</a>, SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016</li><li>Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4480977\" target=\"_blank\">KB4480977</a>.</div><br><a href ='#132msg'>Back to top</a></td><td>OS Build 14393.2457<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343884' target='_blank'>KB4343884</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480977' target='_blank'>KB4480977</a></td><td>Resolved:<br>January 17, 2019 <br>02:00 PM PT<br><br>Opened:<br>August 30, 2018 <br>05:00 PM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='132msgdesc'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><div>After you install the <a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/08/30/net-framework-august-2018-preview-of-quality-rollup/\" target=\"_blank\">August Preview of Quality Rollup</a> or<a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/09/11/net-framework-september-2018-security-and-quality-rollup\" target=\"_blank\"> September 11, 2018 .NET Framework update</a>, instantiation of SqlConnection can throw an exception.</div><div><br></div><div>For more information about this issue, see the following article in the Microsoft Knowledge Base: <a href=\"https://support.microsoft.com/help/4470809\" target=\"_blank\">4470809</a>, SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016</li><li>Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4480977\" target=\"_blank\">KB4480977</a>.</div><br><a href ='#132msg'>Back to top</a></td><td>OS Build 14393.2457<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343884' target='_blank'>KB4343884</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480977' target='_blank'>KB4480977</a></td><td>Resolved:<br>January 17, 2019 <br>02:00 PM PT<br><br>Opened:<br>August 30, 2018 <br>05:00 PM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='140msgdesc'></div><b>Issues with install and activation of Key Management Service (KMS) (CSVLK) host keys</b><div>After installing <a href=\"https://support.microsoft.com/help/4343884\" target=\"_blank\">KB4343884</a>, installation and client activation of Windows Server 2019 and Windows 10 Enterprise 2019 LTSC Key Management Service (KMS) CSVLK host keys do not work as expected.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016</li><li>Server: Windows Server 2016</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4467684\" target=\"_blank\">KB4467684</a>.</div><br><a href ='#140msg'>Back to top</a></td><td>OS Build 14393.2457<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343884' target='_blank'>KB4343884</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4467684' target='_blank'>KB4467684</a></td><td>Resolved:<br>November 27, 2018 <br>10:00 AM PT<br><br>Opened:<br>August 30, 2018 <br>05:00 PM PT</td></tr>
</table> </table>
" "

View File

@ -47,8 +47,6 @@ sections:
<tr><td><div id='130msg'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><br>Instantiation of SqlConnection can throw an exception after certain updates have been installed.<br><br><a href = '#130msgdesc'>See details ></a></td><td>OS Build 15063.1292<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343889' target='_blank'>KB4343889</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480959' target='_blank'>KB4480959</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr> <tr><td><div id='130msg'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><br>Instantiation of SqlConnection can throw an exception after certain updates have been installed.<br><br><a href = '#130msgdesc'>See details ></a></td><td>OS Build 15063.1292<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343889' target='_blank'>KB4343889</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480959' target='_blank'>KB4480959</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr>
<tr><td><div id='228msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#228msgdesc'>See details ></a></td><td>OS Build 15063.1563<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480973' target='_blank'>KB4480973</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480959' target='_blank'>KB4480959</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr> <tr><td><div id='228msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#228msgdesc'>See details ></a></td><td>OS Build 15063.1563<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480973' target='_blank'>KB4480973</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480959' target='_blank'>KB4480959</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr>
<tr><td><div id='211msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#211msgdesc'>See details ></a></td><td>OS Build 15063.1387<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462937' target='_blank'>KB4462937</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471327' target='_blank'>KB4471327</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr> <tr><td><div id='211msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#211msgdesc'>See details ></a></td><td>OS Build 15063.1387<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462937' target='_blank'>KB4462937</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471327' target='_blank'>KB4471327</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='126msg'></div><b>LongonUI.exe stops working intermittently</b><br>LongonUI.exe stops working intermittently.<br><br><a href = '#126msgdesc'>See details ></a></td><td>OS Build 15063.1387<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462937' target='_blank'>KB4462937</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4467699' target='_blank'>KB4467699</a></td><td>November 27, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='128msg'></div><b>Error message beginning with “Hosted by…” when launching Microsoft Edge</b><br>Some users may encounter an error message beginning with “Hosted by…” when launching Microsoft Edge.<br><br><a href = '#128msgdesc'>See details ></a></td><td>OS Build 15063.1387<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462937' target='_blank'>KB4462937</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4462939' target='_blank'>KB4462939</a></td><td>October 18, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "
@ -110,8 +108,6 @@ sections:
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='211msgdesc'></div><b>Unable to use Seek bar in Windows Media Player</b><div>After installing <a href=\"https://support.microsoft.com/help/4462937\" target=\"_blank\">KB4462937</a>, users may not be able to use the <strong>Seek</strong> bar in Windows Media Player when playing specific files. This issue does not affect normal playback.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:&nbsp;</strong>This issue is resolved in <a href=\"https://support.microsoft.com/help/4471327\" target=\"_blank\">KB4471327</a>.</div><br><a href ='#211msg'>Back to top</a></td><td>OS Build 15063.1387<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462937' target='_blank'>KB4462937</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471327' target='_blank'>KB4471327</a></td><td>Resolved:<br>December 11, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='211msgdesc'></div><b>Unable to use Seek bar in Windows Media Player</b><div>After installing <a href=\"https://support.microsoft.com/help/4462937\" target=\"_blank\">KB4462937</a>, users may not be able to use the <strong>Seek</strong> bar in Windows Media Player when playing specific files. This issue does not affect normal playback.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:&nbsp;</strong>This issue is resolved in <a href=\"https://support.microsoft.com/help/4471327\" target=\"_blank\">KB4471327</a>.</div><br><a href ='#211msg'>Back to top</a></td><td>OS Build 15063.1387<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462937' target='_blank'>KB4462937</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471327' target='_blank'>KB4471327</a></td><td>Resolved:<br>December 11, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='126msgdesc'></div><b>LongonUI.exe stops working intermittently</b><div>After installing <a href=\"https://support.microsoft.com/help/4462937\" target=\"_blank\">KB4462937</a>, LogonUI.exe stops working intermittently.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Windows 10, version 1703</li></ul><div></div><div><strong>Resolution:</strong>&nbsp;This issue is resolved in <a href=\"https://support.microsoft.com/help/4467699\" target=\"_blank\">KB4467699</a>.</div><br><a href ='#126msg'>Back to top</a></td><td>OS Build 15063.1387<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462937' target='_blank'>KB4462937</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4467699' target='_blank'>KB4467699</a></td><td>Resolved:<br>November 27, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='128msgdesc'></div><b>Error message beginning with “Hosted by…” when launching Microsoft Edge</b><div>After installing <a href=\"https://support.microsoft.com/help/4462937\" target=\"_blank\">KB4462937</a>, some users may see a dialog box with a non-applicable message beginning with the words “Hosted by...” when first starting Microsoft Edge.</div><div><br></div><div>This dialog will only appear once if they have turned on “Block only third-party cookies” in Microsoft Edge and applied certain language packs before installing this update.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1709; Windows 10, version 1703</li><li>Server: Windows Server, version 1709</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4462939\" target=\"_blank\">KB4462939</a>.</div><br><a href ='#128msg'>Back to top</a></td><td>OS Build 15063.1387<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462937' target='_blank'>KB4462937</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4462939' target='_blank'>KB4462939</a></td><td>Resolved:<br>October 18, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "

View File

@ -49,7 +49,6 @@ sections:
<tr><td><div id='129msg'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><br>Instantiation of SqlConnection can throw an exception after certain updates have been installed.<br><br><a href = '#129msgdesc'>See details ></a></td><td>OS Build 16299.637<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343893' target='_blank'>KB4343893</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480967' target='_blank'>KB4480967</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr> <tr><td><div id='129msg'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><br>Instantiation of SqlConnection can throw an exception after certain updates have been installed.<br><br><a href = '#129msgdesc'>See details ></a></td><td>OS Build 16299.637<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343893' target='_blank'>KB4343893</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480967' target='_blank'>KB4480967</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr>
<tr><td><div id='227msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#227msgdesc'>See details ></a></td><td>OS Build 16299.904<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480978' target='_blank'>KB4480978</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480967' target='_blank'>KB4480967</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr> <tr><td><div id='227msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#227msgdesc'>See details ></a></td><td>OS Build 16299.904<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480978' target='_blank'>KB4480978</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480967' target='_blank'>KB4480967</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr>
<tr><td><div id='210msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#210msgdesc'>See details ></a></td><td>OS Build 16299.726<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462918' target='_blank'>KB4462918</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471329' target='_blank'>KB4471329</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr> <tr><td><div id='210msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#210msgdesc'>See details ></a></td><td>OS Build 16299.726<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462918' target='_blank'>KB4462918</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471329' target='_blank'>KB4471329</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='127msg'></div><b>Error message beginning with “Hosted by…” when launching Microsoft Edge</b><br>Some users may encounter an error message beginning with “Hosted by…” when launching Microsoft Edge.<br><br><a href = '#127msgdesc'>See details ></a></td><td>OS Build 16299.726<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462918' target='_blank'>KB4462918</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4462932' target='_blank'>KB4462932</a></td><td>October 18, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "
@ -121,7 +120,6 @@ sections:
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='210msgdesc'></div><b>Unable to use Seek bar in Windows Media Player</b><div>After installing <a href=\"https://support.microsoft.com/help/4462918\" target=\"_blank\">KB4462918</a>, users may not be able to use the <strong>Seek</strong> Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4471329\" target=\"_blank\">KB4471329</a>.</div><br><a href ='#210msg'>Back to top</a></td><td>OS Build 16299.726<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462918' target='_blank'>KB4462918</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471329' target='_blank'>KB4471329</a></td><td>Resolved:<br>December 11, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='210msgdesc'></div><b>Unable to use Seek bar in Windows Media Player</b><div>After installing <a href=\"https://support.microsoft.com/help/4462918\" target=\"_blank\">KB4462918</a>, users may not be able to use the <strong>Seek</strong> Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4471329\" target=\"_blank\">KB4471329</a>.</div><br><a href ='#210msg'>Back to top</a></td><td>OS Build 16299.726<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462918' target='_blank'>KB4462918</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471329' target='_blank'>KB4471329</a></td><td>Resolved:<br>December 11, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='127msgdesc'></div><b>Error message beginning with “Hosted by…” when launching Microsoft Edge</b><div>After installing <a href=\"https://support.microsoft.com/help/4462918\" target=\"_blank\">KB4462918</a>, some users may see a dialog box with a non-applicable message beginning with the words “Hosted by...” when first starting Microsoft Edge.</div><div><br></div><div>This dialog will only appear once if they have turned on “Block only third-party cookies” in Microsoft Edge and applied certain language packs before installing this update.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1709; Windows 10, version 1703</li><li>Server: Windows Server, version 1709</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4462932\" target=\"_blank\">KB4462932</a>.</div><br><a href ='#127msg'>Back to top</a></td><td>OS Build 16299.726<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462918' target='_blank'>KB4462918</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4462932' target='_blank'>KB4462932</a></td><td>Resolved:<br>October 18, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "

View File

@ -51,10 +51,6 @@ sections:
<tr><td><div id='150msg'></div><b>Blue or black screen with \"System thread exception not handled\" error</b><br>Some users may get a blue or black screen with the error code, “System thread exception not handled.”<br><br><a href = '#150msgdesc'>See details ></a></td><td>OS Build 17134.441<br><br>November 27, 2018<br><a href ='https://support.microsoft.com/help/4467682' target='_blank'>KB4467682</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471324' target='_blank'>KB4471324</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr> <tr><td><div id='150msg'></div><b>Blue or black screen with \"System thread exception not handled\" error</b><br>Some users may get a blue or black screen with the error code, “System thread exception not handled.”<br><br><a href = '#150msgdesc'>See details ></a></td><td>OS Build 17134.441<br><br>November 27, 2018<br><a href ='https://support.microsoft.com/help/4467682' target='_blank'>KB4467682</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471324' target='_blank'>KB4471324</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='152msg'></div><b>Custom Start menu layouts display incorrectly</b><br>Custom Start menu layouts may display incorrectly.<br><br><a href = '#152msgdesc'>See details ></a></td><td>OS Build 17134.441<br><br>November 27, 2018<br><a href ='https://support.microsoft.com/help/4467682' target='_blank'>KB4467682</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471324' target='_blank'>KB4471324</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr> <tr><td><div id='152msg'></div><b>Custom Start menu layouts display incorrectly</b><br>Custom Start menu layouts may display incorrectly.<br><br><a href = '#152msgdesc'>See details ></a></td><td>OS Build 17134.441<br><br>November 27, 2018<br><a href ='https://support.microsoft.com/help/4467682' target='_blank'>KB4467682</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471324' target='_blank'>KB4471324</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='205msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#205msgdesc'>See details ></a></td><td>OS Build 17134.345<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462919' target='_blank'>KB4462919</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471324' target='_blank'>KB4471324</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr> <tr><td><div id='205msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#205msgdesc'>See details ></a></td><td>OS Build 17134.345<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462919' target='_blank'>KB4462919</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471324' target='_blank'>KB4471324</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='155msg'></div><b>Users cannot set Win32 program defaults</b><br>Some users cannot set Win32 program defaults for certain app and file type combinations.<br><br><a href = '#155msgdesc'>See details ></a></td><td>OS Build 17134.320<br><br>September 26, 2018<br><a href ='https://support.microsoft.com/help/4458469' target='_blank'>KB4458469</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4467682' target='_blank'>KB4467682</a></td><td>November 27, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='153msg'></div><b>Developer Tools (F12) fail to start in Microsoft Edge</b><br>Developer Tools (F12) may fail to start in Microsoft Edge.<br><br><a href = '#153msgdesc'>See details ></a></td><td>OS Build 17134.376<br><br>October 24, 2018<br><a href ='https://support.microsoft.com/help/4462933' target='_blank'>KB4462933</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4467702' target='_blank'>KB4467702</a></td><td>November 13, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='134msg'></div><b>Guest VMs running Unicast NLB fail to respond after restart</b><br>All guest virtual machines running Unicast NLB fail to respond to NLB requests after the virtual machines restart.<br><br><a href = '#134msgdesc'>See details ></a></td><td>OS Build 17134.285<br><br>September 11, 2018<br><a href ='https://support.microsoft.com/help/4457128' target='_blank'>KB4457128</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4458469' target='_blank'>KB4458469</a></td><td>September 26, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='154msg'></div><b>Microsoft Intune takes a long time to deliver user profiles</b><br>Windows no longer recognizes the Personal Information exchange (PFX) certificate used for Wi-Fi or VPN authentication, causing delays in Microsoft Intune delivering user profiles.<br><br><a href = '#154msgdesc'>See details ></a></td><td>OS Build 17134.191<br><br>July 24, 2018<br><a href ='https://support.microsoft.com/help/4340917' target='_blank'>KB4340917</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4464218' target='_blank'>KB4464218</a></td><td>September 17, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "
@ -144,7 +140,6 @@ sections:
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='205msgdesc'></div><b>Unable to use Seek bar in Windows Media Player</b><div>After installing <a href=\"https://support.microsoft.com/help/4462919\" target=\"_blank\">KB4462919</a>, users may not be able to use the <strong>Seek </strong>bar in Windows Media Player when playing specific files. This issue does not affect normal playback.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution: </strong>This issue is resolved in <a href=\"https://support.microsoft.com/help/4471324\" target=\"_blank\">KB4471324</a>.&nbsp;</div><br><a href ='#205msg'>Back to top</a></td><td>OS Build 17134.345<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462919' target='_blank'>KB4462919</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471324' target='_blank'>KB4471324</a></td><td>Resolved:<br>December 11, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='205msgdesc'></div><b>Unable to use Seek bar in Windows Media Player</b><div>After installing <a href=\"https://support.microsoft.com/help/4462919\" target=\"_blank\">KB4462919</a>, users may not be able to use the <strong>Seek </strong>bar in Windows Media Player when playing specific files. This issue does not affect normal playback.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution: </strong>This issue is resolved in <a href=\"https://support.microsoft.com/help/4471324\" target=\"_blank\">KB4471324</a>.&nbsp;</div><br><a href ='#205msg'>Back to top</a></td><td>OS Build 17134.345<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4462919' target='_blank'>KB4462919</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471324' target='_blank'>KB4471324</a></td><td>Resolved:<br>December 11, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='153msgdesc'></div><b>Developer Tools (F12) fail to start in Microsoft Edge</b><div>Developer Tools (F12) may fail to start in Microsoft Edge.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803</li><li>Server: Windows Server, version 1803</li></ul><div></div><div><strong>Resolution</strong>: This issue is resolved in <a href=\"https://support.microsoft.com/help/4467702\" target=\"_blank\">KB4467702</a>.&nbsp;</div><br><a href ='#153msg'>Back to top</a></td><td>OS Build 17134.376<br><br>October 24, 2018<br><a href ='https://support.microsoft.com/help/4462933' target='_blank'>KB4462933</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4467702' target='_blank'>KB4467702</a></td><td>Resolved:<br>November 13, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 24, 2018 <br>02:00 PM PT</td></tr>
</table> </table>
" "
@ -154,16 +149,5 @@ sections:
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='131msgdesc'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><div>After you install the <a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/08/30/net-framework-august-2018-preview-of-quality-rollup/\" target=\"_blank\">August Preview of Quality Rollup</a> or<a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/09/11/net-framework-september-2018-security-and-quality-rollup\" target=\"_blank\">September 11,2018 .NET Framework update</a>, instantiation of SqlConnection can throw an exception.&nbsp;&nbsp;</div><div><br></div><div>For more information about this issue, see the following article in the Microsoft Knowledge Base: <a href=\"https://support.microsoft.com/help/4470809\" target=\"_blank\">4470809</a>,SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016</li><li>Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div></div><div><strong>Resolution: </strong>This issue is resolved in <a href=\"https://support.microsoft.com/help/4480976\" target=\"_blank\">KB4480976</a>.&nbsp;</div><br><a href ='#131msg'>Back to top</a></td><td>OS Build 17134.285<br><br>September 11, 2018<br><a href ='https://support.microsoft.com/help/4457128' target='_blank'>KB4457128</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480976' target='_blank'>KB4480976</a></td><td>Resolved:<br>January 15, 2019 <br>10:00 AM PT<br><br>Opened:<br>September 11, 2018 <br>10:00 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='131msgdesc'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><div>After you install the <a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/08/30/net-framework-august-2018-preview-of-quality-rollup/\" target=\"_blank\">August Preview of Quality Rollup</a> or<a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/09/11/net-framework-september-2018-security-and-quality-rollup\" target=\"_blank\">September 11,2018 .NET Framework update</a>, instantiation of SqlConnection can throw an exception.&nbsp;&nbsp;</div><div><br></div><div>For more information about this issue, see the following article in the Microsoft Knowledge Base: <a href=\"https://support.microsoft.com/help/4470809\" target=\"_blank\">4470809</a>,SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016</li><li>Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div></div><div><strong>Resolution: </strong>This issue is resolved in <a href=\"https://support.microsoft.com/help/4480976\" target=\"_blank\">KB4480976</a>.&nbsp;</div><br><a href ='#131msg'>Back to top</a></td><td>OS Build 17134.285<br><br>September 11, 2018<br><a href ='https://support.microsoft.com/help/4457128' target='_blank'>KB4457128</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480976' target='_blank'>KB4480976</a></td><td>Resolved:<br>January 15, 2019 <br>10:00 AM PT<br><br>Opened:<br>September 11, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='155msgdesc'></div><b>Users cannot set Win32 program defaults</b><div>After installing <a href=\"https://support.microsoft.com/help/4458469\" target=\"_blank\">KB4458469</a>, some users cannot set Win32 program defaults for certain app and file type combinations using the <strong>Open with...</strong> command or <strong>Settings</strong> &gt; <strong>Apps</strong> &gt; <strong>Default apps</strong>.&nbsp;</div><div>&nbsp;</div><div>In some cases, Microsoft Notepad or other Win32 programs cannot be set as the default.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803</li></ul><div></div><div><strong>Resolution</strong>: This issue is resolved in <a href=\"https://support.microsoft.com/help/4467682\" target=\"_blank\">KB4467682</a>.&nbsp;</div><br><a href ='#155msg'>Back to top</a></td><td>OS Build 17134.320<br><br>September 26, 2018<br><a href ='https://support.microsoft.com/help/4458469' target='_blank'>KB4458469</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4467682' target='_blank'>KB4467682</a></td><td>Resolved:<br>November 27, 2018 <br>10:00 AM PT<br><br>Opened:<br>September 26, 2018 <br>02:00 PM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='134msgdesc'></div><b>Guest VMs running Unicast NLB fail to respond after restart</b><div>All guest virtual machines running Unicast NLB fail to respond to NLB requests after the virtual machines restart.&nbsp;</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015</li><li>Server: Windows Server, version 1803</li></ul><div></div><div><strong>Resolution</strong>: This issue is resolved in <a href=\"https://support.microsoft.com/help/4458469\" target=\"_blank\">KB4458469</a>.&nbsp;</div><br><a href ='#134msg'>Back to top</a></td><td>OS Build 17134.285<br><br>September 11, 2018<br><a href ='https://support.microsoft.com/help/4457128' target='_blank'>KB4457128</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4458469' target='_blank'>KB4458469</a></td><td>Resolved:<br>September 26, 2018 <br>10:00 AM PT<br><br>Opened:<br>September 11, 2018 <br>10:00 AM PT</td></tr>
</table>
"
- title: July 2018
- items:
- type: markdown
text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='154msgdesc'></div><b>Microsoft Intune takes a long time to deliver user profiles</b><div>After installing <a href=\"https://support.microsoft.com/help/4457128\" target=\"_blank\">KB4457128</a>, Windows no longer recognizes the Personal Information exchange (PFX) certificate that's used for authenticating to a Wi-Fi or VPN connection. As a result, Microsoft Intune takes a long time to deliver user profiles because it doesn't recognize that the required certificate is on the device.&nbsp;</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803</li><li>Server: Windows Server, version 1803</li></ul><div></div><div><strong>Resolution</strong>: This issue is resolved in <a href=\"https://support.microsoft.com/help/4464218\" target=\"_blank\">KB4464218</a>.&nbsp;</div><br><a href ='#154msg'>Back to top</a></td><td>OS Build 17134.191<br><br>July 24, 2018<br><a href ='https://support.microsoft.com/help/4340917' target='_blank'>KB4340917</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4464218' target='_blank'>KB4464218</a></td><td>Resolved:<br>September 17, 2018 <br>10:00 AM PT<br><br>Opened:<br>July 24, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "

View File

@ -59,10 +59,6 @@ sections:
<tr><td><div id='225msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#225msgdesc'>See details ></a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4476976' target='_blank'>KB4476976</a></td><td>January 22, 2019 <br>02:00 PM PT</td></tr> <tr><td><div id='225msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#225msgdesc'>See details ></a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4476976' target='_blank'>KB4476976</a></td><td>January 22, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='206msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#206msgdesc'>See details ></a></td><td>OS Build 17763.55<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4464330' target='_blank'>KB4464330</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471332' target='_blank'>KB4471332</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr> <tr><td><div id='206msg'></div><b>Unable to use Seek bar in Windows Media Player</b><br>Users may not be able to use the Seek bar in Windows Media Player when playing specific files.<br><br><a href = '#206msgdesc'>See details ></a></td><td>OS Build 17763.55<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4464330' target='_blank'>KB4464330</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471332' target='_blank'>KB4471332</a></td><td>December 11, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='162msg'></div><b>Audio stops working after installing Intel audio driver</b><br>Upgrade block: Windows 10 audio stops working after installing Intel Smart Sound Technology driver (version 09.21.00.3755).<br><br><a href = '#162msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4468550' target='_blank'>KB4468550</a></td><td>December 07, 2018 <br>10:00 AM PT</td></tr> <tr><td><div id='162msg'></div><b>Audio stops working after installing Intel audio driver</b><br>Upgrade block: Windows 10 audio stops working after installing Intel Smart Sound Technology driver (version 09.21.00.3755).<br><br><a href = '#162msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4468550' target='_blank'>KB4468550</a></td><td>December 07, 2018 <br>10:00 AM PT</td></tr>
<tr><td><div id='165msg'></div><b>Office apps (32-bit) unable to use 'Save As…' function</b><br>Upgrade block: Devices using Morphisec Protector (or other application that uses the Morphisec SDK) may be unable to save documents when using 32-bit Microsoft Office apps.<br><br><a href = '#165msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>December 06, 2018 <br>12:00 PM PT</td></tr>
<tr><td><div id='156msg'></div><b>Users cannot set Win32 program defaults </b><br>Some users cannot set Win32 program defaults for certain app and file type combinations.<br><br><a href = '#156msgdesc'>See details ></a></td><td>OS Build 17763.55<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4464330' target='_blank'>KB4464330</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4469342' target='_blank'>KB4469342</a></td><td>December 05, 2018 <br>02:00 PM PT</td></tr>
<tr><td><div id='163msg'></div><b>Mapped drives fail to reconnect after login</b><br>Upgrade block: Mapped drives may fail to reconnect after booting and logging on to a Windows device.<br><br><a href = '#163msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4469342' target='_blank'>KB4469342</a></td><td>December 05, 2018 <br>02:00 PM PT</td></tr>
<tr><td><div id='157msg'></div><b>Microsoft Edge may crash or hang while playing video</b><br>Following an nVidia driver update, Microsoft Edge may crash or hang while playing video.<br><br><a href = '#157msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>December 05, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "
@ -144,9 +140,6 @@ sections:
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='168msgdesc'></div><b>Issues with lock screen and Microsoft Edge tabs for certain AMD Radeon video cards</b><div><strong>Note:</strong> AMD no longer supports Radeon HD2000 and HD4000 series graphic processor units (GPUs).</div><div>&nbsp;</div><div><strong>Upgrade block:</strong> After updating to Window 10, version 1809, Microsoft Edge tabs may stop working when a device is configured with AMD Radeon HD2000 or HD4000 series video cards. Customers may get the following error code: \"INVALID_POINTER_READ_c0000005_atidxx64.dll\".&nbsp;</div><div>&nbsp;</div><div>Some users may also experience performance issues with the lock screen or the ShellExperienceHost. (The lock screen hosts widgets, and the ShellExperienceHost is responsible for assorted shell functionality.)&nbsp;</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/help/4487044\" target=\"_blank\">KB4487044</a>, and the block was removed.</div><br><a href ='#168msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487044' target='_blank'>KB4487044</a></td><td>Resolved:<br>February 12, 2019 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='168msgdesc'></div><b>Issues with lock screen and Microsoft Edge tabs for certain AMD Radeon video cards</b><div><strong>Note:</strong> AMD no longer supports Radeon HD2000 and HD4000 series graphic processor units (GPUs).</div><div>&nbsp;</div><div><strong>Upgrade block:</strong> After updating to Window 10, version 1809, Microsoft Edge tabs may stop working when a device is configured with AMD Radeon HD2000 or HD4000 series video cards. Customers may get the following error code: \"INVALID_POINTER_READ_c0000005_atidxx64.dll\".&nbsp;</div><div>&nbsp;</div><div>Some users may also experience performance issues with the lock screen or the ShellExperienceHost. (The lock screen hosts widgets, and the ShellExperienceHost is responsible for assorted shell functionality.)&nbsp;</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/help/4487044\" target=\"_blank\">KB4487044</a>, and the block was removed.</div><br><a href ='#168msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487044' target='_blank'>KB4487044</a></td><td>Resolved:<br>February 12, 2019 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='166msgdesc'></div><b>Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible</b><div><strong>Upgrade block:</strong> Microsoft and Trend Micro have identified a compatibility issue with Trend Micro's OfficeScan and Worry-Free Business Security software when attempting to update to Windows 10, version 1809.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019&nbsp;</li></ul><div></div><div><strong>Resolution:</strong> Trend Micro has released a new version of these products that resolves the issue. To download them, please visit the <a href=\"https://success.trendmicro.com/solution/1121159\" target=\"_blank\">Trend Micro Business Support Portal</a>.</div><div><br></div><div>Once you have updated your version of Trend Micro's OfficeScan or Worry-Free Business Security software, you will be offered Windows 10, version 1809 automatically.&nbsp;</div><br><a href ='#166msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>Resolved:<br>February 01, 2019 <br>09:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='166msgdesc'></div><b>Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible</b><div><strong>Upgrade block:</strong> Microsoft and Trend Micro have identified a compatibility issue with Trend Micro's OfficeScan and Worry-Free Business Security software when attempting to update to Windows 10, version 1809.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019&nbsp;</li></ul><div></div><div><strong>Resolution:</strong> Trend Micro has released a new version of these products that resolves the issue. To download them, please visit the <a href=\"https://success.trendmicro.com/solution/1121159\" target=\"_blank\">Trend Micro Business Support Portal</a>.</div><div><br></div><div>Once you have updated your version of Trend Micro's OfficeScan or Worry-Free Business Security software, you will be offered Windows 10, version 1809 automatically.&nbsp;</div><br><a href ='#166msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>Resolved:<br>February 01, 2019 <br>09:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='162msgdesc'></div><b>Audio stops working after installing Intel audio driver</b><div><strong>Upgrade block:</strong> Intel unintentionally released version 9.21.00.3755 of the Intel Smart Sound Technology (ISST) Driver through Windows Update and inadvertently offered it to a range of devices running Window 10, version 1709, 1803, and 1809. If a device contained a compatible audio driver, the new driver overrode it and caused audio to stop working.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/help/4468550\" target=\"_blank\">KB4468550</a> and the upgrade block removed.&nbsp;</div><br><a href ='#162msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4468550' target='_blank'>KB4468550</a></td><td>Resolved:<br>December 07, 2018 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='162msgdesc'></div><b>Audio stops working after installing Intel audio driver</b><div><strong>Upgrade block:</strong> Intel unintentionally released version 9.21.00.3755 of the Intel Smart Sound Technology (ISST) Driver through Windows Update and inadvertently offered it to a range of devices running Window 10, version 1709, 1803, and 1809. If a device contained a compatible audio driver, the new driver overrode it and caused audio to stop working.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/help/4468550\" target=\"_blank\">KB4468550</a> and the upgrade block removed.&nbsp;</div><br><a href ='#162msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4468550' target='_blank'>KB4468550</a></td><td>Resolved:<br>December 07, 2018 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='165msgdesc'></div><b>Office apps (32-bit) unable to use 'Save As…' function</b><div><strong>Upgrade block:</strong> Microsoft and Morphisec have identified an issue on devices that have installed Morphisec Protector or another application that uses the Morphisec Software Development Kit (SDK) including Cisco AMP for Endpoints. These applications may impact customers' ability to use the 'Save As.'dialog when saving documents in 32-bit versions of Microsoft Office applications. Saving of files is not impacted.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> Morphisec and Cisco have released updated versions of their applications to address this issue. We recommend customers update to these minimum versions before attempting to attempting to upgrade to Windows 10, version 1809:</div><ul><li>Morphisec Protector version 2.4.8&nbsp;</li><li>Cisco AMP for Endpoints version 6.2.3.10814</li></ul><div></div><div>An upgrade block remains in place for earlier versions of the applications than those listed above.</div><br><a href ='#165msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>Resolved:<br>December 06, 2018 <br>12:00 PM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='163msgdesc'></div><b>Mapped drives fail to reconnect after login</b><div><strong>Upgrade block:</strong> Network drives may fail to reconnect after booting and logging on to a Windows device. Symptoms include:&nbsp;&nbsp;</div><ul><li>In Windows Explorer, a red X appears on the mapped network drives.&nbsp;</li><li>Mapped network drives show as <strong>Unavailable</strong> when you run the <strong>net use</strong> command from a command prompt.&nbsp;</li><li>In the notification area, a notification displays the following message, \"Could not reconnect all network drives.\"</li></ul><div></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/help/4469342\" target=\"_blank\">KB4469342</a> and the upgrade block removed.&nbsp;</div><br><a href ='#163msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4469342' target='_blank'>KB4469342</a></td><td>Resolved:<br>December 05, 2018 <br>02:00 PM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='157msgdesc'></div><b>Microsoft Edge may crash or hang while playing video</b><div>nVidia has notified Microsoft of an issue where Microsoft Edge may crash or hang while playing video. This issue occurs following an nVidia driver update.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> nVidia has released an updated driver to address this issue. Please follow the instructions found in <a href=\"https://nvidia.custhelp.com/app/answers/detail/a_id/4745\" target=\"_blank\">nVidia's support article</a>.&nbsp;</div><br><a href ='#157msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>Resolved:<br>December 05, 2018 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "
@ -156,6 +149,5 @@ sections:
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='206msgdesc'></div><b>Unable to use Seek bar in Windows Media Player</b><div>After installing <a href=\"https://support.microsoft.com/help/4464330\" target=\"_blank\">KB4464330</a>, users may not be able to use the <strong>Seek</strong> bar in Windows Media Player when playing specific files. This issue does not affect normal playback.&nbsp;</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4471332\" target=\"_blank\">KB4471332</a>.&nbsp;</div><br><a href ='#206msg'>Back to top</a></td><td>OS Build 17763.55<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4464330' target='_blank'>KB4464330</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471332' target='_blank'>KB4471332</a></td><td>Resolved:<br>December 11, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='206msgdesc'></div><b>Unable to use Seek bar in Windows Media Player</b><div>After installing <a href=\"https://support.microsoft.com/help/4464330\" target=\"_blank\">KB4464330</a>, users may not be able to use the <strong>Seek</strong> bar in Windows Media Player when playing specific files. This issue does not affect normal playback.&nbsp;</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4471332\" target=\"_blank\">KB4471332</a>.&nbsp;</div><br><a href ='#206msg'>Back to top</a></td><td>OS Build 17763.55<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4464330' target='_blank'>KB4464330</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4471332' target='_blank'>KB4471332</a></td><td>Resolved:<br>December 11, 2018 <br>10:00 AM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='156msgdesc'></div><b>Users cannot set Win32 program defaults </b><div>After installing <a href=\"https://support.microsoft.com/help/4464330\" target=\"_blank\">KB4464330</a>, some users cannot set Win32 program defaults for certain app and file type combinations using the <strong>Open with...</strong> command or <strong>Settings </strong>&gt;<strong> Apps </strong>&gt;<strong> Default apps</strong>.</div><div>&nbsp;</div><div>In some cases, Microsoft Notepad or other Win32 programs cannot be set as the default.&nbsp;</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4469342\" target=\"_blank\">KB4469342</a>.&nbsp;</div><br><a href ='#156msg'>Back to top</a></td><td>OS Build 17763.55<br><br>October 09, 2018<br><a href ='https://support.microsoft.com/help/4464330' target='_blank'>KB4464330</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4469342' target='_blank'>KB4469342</a></td><td>Resolved:<br>December 05, 2018 <br>02:00 PM PT<br><br>Opened:<br>October 09, 2018 <br>10:00 AM PT</td></tr>
</table> </table>
" "

View File

@ -60,7 +60,7 @@ sections:
- type: markdown - type: markdown
text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br> text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br>
<table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr> <table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr>
<tr><td><div id='461msg'></div><b>opening Internet Explorer 11 may fail</b><br>Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.<br><br><a href = '#461msgdesc'>See details ></a></td><td>OS Build 14393.2999<br><br>May 23, 2019<br><a href ='https://support.microsoft.com/help/4499177' target='_blank'>KB4499177</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 05, 2019 <br>05:54 PM PT</td></tr> <tr><td><div id='462msg'></div><b>Opening Internet Explorer 11 may fail</b><br>Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.<br><br><a href = '#462msgdesc'>See details ></a></td><td>OS Build 14393.2999<br><br>May 23, 2019<br><a href ='https://support.microsoft.com/help/4499177' target='_blank'>KB4499177</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 05, 2019 <br>07:51 PM PT</td></tr>
<tr><td><div id='459msg'></div><b>Some applications may fail to run as expected on clients of AD FS 2016</b><br>Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016)<br><br><a href = '#459msgdesc'>See details ></a></td><td>OS Build 14393.2941<br><br>April 25, 2019<br><a href ='https://support.microsoft.com/help/4493473' target='_blank'>KB4493473</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 04, 2019 <br>05:55 PM PT</td></tr> <tr><td><div id='459msg'></div><b>Some applications may fail to run as expected on clients of AD FS 2016</b><br>Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016)<br><br><a href = '#459msgdesc'>See details ></a></td><td>OS Build 14393.2941<br><br>April 25, 2019<br><a href ='https://support.microsoft.com/help/4493473' target='_blank'>KB4493473</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 04, 2019 <br>05:55 PM PT</td></tr>
<tr><td><div id='451msg'></div><b>Devices running Windows Server 2016 with Hyper-V seeing Bitlocker error 0xC0210000</b><br>Some devices running Windows Server with Hyper-V enabled may start into Bitlocker recovery with error 0xC0210000<br><br><a href = '#451msgdesc'>See details ></a></td><td>OS Build 14393.2969<br><br>May 14, 2019<br><a href ='https://support.microsoft.com/help/4494440' target='_blank'>KB4494440</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 23, 2019 <br>09:57 AM PT</td></tr> <tr><td><div id='451msg'></div><b>Devices running Windows Server 2016 with Hyper-V seeing Bitlocker error 0xC0210000</b><br>Some devices running Windows Server with Hyper-V enabled may start into Bitlocker recovery with error 0xC0210000<br><br><a href = '#451msgdesc'>See details ></a></td><td>OS Build 14393.2969<br><br>May 14, 2019<br><a href ='https://support.microsoft.com/help/4494440' target='_blank'>KB4494440</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 23, 2019 <br>09:57 AM PT</td></tr>
<tr><td><div id='135msg'></div><b>Cluster service may fail if the minimum password length is set to greater than 14</b><br>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.<br><br><a href = '#135msgdesc'>See details ></a></td><td>OS Build 14393.2639<br><br>November 27, 2018<br><a href ='https://support.microsoft.com/help/4467684' target='_blank'>KB4467684</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 25, 2019 <br>02:00 PM PT</td></tr> <tr><td><div id='135msg'></div><b>Cluster service may fail if the minimum password length is set to greater than 14</b><br>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.<br><br><a href = '#135msgdesc'>See details ></a></td><td>OS Build 14393.2639<br><br>November 27, 2018<br><a href ='https://support.microsoft.com/help/4467684' target='_blank'>KB4467684</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 25, 2019 <br>02:00 PM PT</td></tr>
@ -87,7 +87,7 @@ sections:
- type: markdown - type: markdown
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='461msgdesc'></div><b>opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>To set the <strong>Default Search Provider</strong>, use the following steps:</div><ol><li>Open an Administrator Command prompt and type the following: <strong>\"C:\\Program Files\\Internet Explorer\\iexplore.exe\"&nbsp;http://microsoft.com</strong></li><li>After Internet Explorer has opened, go to the <strong>Settings </strong>menu and select <strong>Manage add-ons</strong>.</li><li>Select <strong>Search Providers</strong> in left pane.</li><li>Select the link <strong>Find more search providers</strong> in the bottom left of the dialog.</li><li>A new Internet Explorer window should open, allowing you to select a search provider.</li><li>Select <strong>Add</strong> under the Search Provider you prefer.</li><li>The <strong>Add Search Provider</strong> dialog should open, select <strong>Add</strong>.</li><li>You should now be able to open Internet Explorer 11 normally.</li></ol><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and estimate a solution will be available in mid-June.</div><br><a href ='#461msg'>Back to top</a></td><td>OS Build 14393.2999<br><br>May 23, 2019<br><a href ='https://support.microsoft.com/help/4499177' target='_blank'>KB4499177</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 05, 2019 <br>05:54 PM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='462msgdesc'></div><b>Opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>To set the <strong>Default Search Provider</strong>, use the following steps:</div><ol><li>Open an Administrator Command prompt and type the following: <strong>\"C:\\Program Files\\Internet Explorer\\iexplore.exe\"&nbsp;http://microsoft.com</strong></li><li>After Internet Explorer has opened, go to the <strong>Settings </strong>menu and select <strong>Manage add-ons</strong>.</li><li>Select <strong>Search Providers</strong> in left pane.</li><li>Select the link <strong>Find more search providers</strong> in the bottom left of the dialog.</li><li>A new Internet Explorer window should open, allowing you to select a search provider.</li><li>Select <strong>Add</strong> under the Search Provider you prefer.</li><li>The <strong>Add Search Provider</strong> dialog should open, select <strong>Add</strong>.</li><li>You should now be able to open Internet Explorer 11 normally.</li></ol><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and estimate a solution will be available in mid-June.</div><br><a href ='#462msg'>Back to top</a></td><td>OS Build 14393.2999<br><br>May 23, 2019<br><a href ='https://support.microsoft.com/help/4499177' target='_blank'>KB4499177</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 05, 2019 <br>07:51 PM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='459msgdesc'></div><b>Some applications may fail to run as expected on clients of AD FS 2016</b><div>Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of <a href='https://support.microsoft.com/help/4493473' target='_blank'>KB4493473</a> on the server. Applications that may exhibit&nbsp;this behavior use an <strong>IFRAME </strong>during non-interactive authentication requests and receive <strong>X-Frame Options </strong>set to<strong> </strong>DENY.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Server: Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>You can use the Allow-From value of the header if the <strong>IFRAME</strong> 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: <strong>set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue \"allow-from </strong><a href=\"https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fexample.com&amp;data=02%7C01%7Cv-shros%40microsoft.com%7Cae8661902fd24427d3a208d6e946723c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636952886119832796&amp;sdata=PkA1pZtXvVBLCBjnOFg%2FvCSgtnMjO22cbSaztBer7%2Fg%3D&amp;reserved=0\" target=\"_blank\"><strong><u>https://example.com</u></strong></a><strong>\"</strong></div><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#459msg'>Back to top</a></td><td>OS Build 14393.2941<br><br>April 25, 2019<br><a href ='https://support.microsoft.com/help/4493473' target='_blank'>KB4493473</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 04, 2019 <br>05:55 PM PT<br><br>Opened:<br>June 04, 2019 <br>05:55 PM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='459msgdesc'></div><b>Some applications may fail to run as expected on clients of AD FS 2016</b><div>Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of <a href='https://support.microsoft.com/help/4493473' target='_blank'>KB4493473</a> on the server. Applications that may exhibit&nbsp;this behavior use an <strong>IFRAME </strong>during non-interactive authentication requests and receive <strong>X-Frame Options </strong>set to<strong> </strong>DENY.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Server: Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>You can use the Allow-From value of the header if the <strong>IFRAME</strong> 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: <strong>set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue \"allow-from </strong><a href=\"https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fexample.com&amp;data=02%7C01%7Cv-shros%40microsoft.com%7Cae8661902fd24427d3a208d6e946723c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636952886119832796&amp;sdata=PkA1pZtXvVBLCBjnOFg%2FvCSgtnMjO22cbSaztBer7%2Fg%3D&amp;reserved=0\" target=\"_blank\"><strong><u>https://example.com</u></strong></a><strong>\"</strong></div><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#459msg'>Back to top</a></td><td>OS Build 14393.2941<br><br>April 25, 2019<br><a href ='https://support.microsoft.com/help/4493473' target='_blank'>KB4493473</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 04, 2019 <br>05:55 PM PT<br><br>Opened:<br>June 04, 2019 <br>05:55 PM PT</td></tr>
</table> </table>
" "

View File

@ -60,7 +60,7 @@ sections:
- type: markdown - type: markdown
text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br> text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br>
<table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr> <table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr>
<tr><td><div id='461msg'></div><b>opening Internet Explorer 11 may fail</b><br>Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.<br><br><a href = '#461msgdesc'>See details ></a></td><td>OS Build 15063.1839<br><br>May 28, 2019<br><a href ='https://support.microsoft.com/help/4499162' target='_blank'>KB4499162</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 05, 2019 <br>05:54 PM PT</td></tr> <tr><td><div id='462msg'></div><b>Opening Internet Explorer 11 may fail</b><br>Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.<br><br><a href = '#462msgdesc'>See details ></a></td><td>OS Build 15063.1839<br><br>May 28, 2019<br><a href ='https://support.microsoft.com/help/4499162' target='_blank'>KB4499162</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 05, 2019 <br>07:51 PM PT</td></tr>
<tr><td><div id='321msg'></div><b>Certain operations performed on a Cluster Shared Volume may fail</b><br>Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".<br><br><a href = '#321msgdesc'>See details ></a></td><td>OS Build 15063.1563<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480973' target='_blank'>KB4480973</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 25, 2019 <br>02:00 PM PT</td></tr> <tr><td><div id='321msg'></div><b>Certain operations performed on a Cluster Shared Volume may fail</b><br>Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".<br><br><a href = '#321msgdesc'>See details ></a></td><td>OS Build 15063.1563<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480973' target='_blank'>KB4480973</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 25, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='423msg'></div><b>Unable to access some gov.uk websites</b><br>gov.uk websites that dont support “HSTS” may not be accessible<br><br><a href = '#423msgdesc'>See details ></a></td><td>OS Build 15063.1805<br><br>May 14, 2019<br><a href ='https://support.microsoft.com/help/4499181' target='_blank'>KB4499181</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4505055' target='_blank'>KB4505055</a></td><td>May 19, 2019 <br>02:00 PM PT</td></tr> <tr><td><div id='423msg'></div><b>Unable to access some gov.uk websites</b><br>gov.uk websites that dont support “HSTS” may not be accessible<br><br><a href = '#423msgdesc'>See details ></a></td><td>OS Build 15063.1805<br><br>May 14, 2019<br><a href ='https://support.microsoft.com/help/4499181' target='_blank'>KB4499181</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4505055' target='_blank'>KB4505055</a></td><td>May 19, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='379msg'></div><b>Layout and cell size of Excel sheets may change when using MS UI Gothic </b><br>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. <br><br><a href = '#379msgdesc'>See details ></a></td><td>OS Build 15063.1784<br><br>April 25, 2019<br><a href ='https://support.microsoft.com/help/4493436' target='_blank'>KB4493436</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4499181' target='_blank'>KB4499181</a></td><td>May 14, 2019 <br>10:00 AM PT</td></tr> <tr><td><div id='379msg'></div><b>Layout and cell size of Excel sheets may change when using MS UI Gothic </b><br>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. <br><br><a href = '#379msgdesc'>See details ></a></td><td>OS Build 15063.1784<br><br>April 25, 2019<br><a href ='https://support.microsoft.com/help/4493436' target='_blank'>KB4493436</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4499181' target='_blank'>KB4499181</a></td><td>May 14, 2019 <br>10:00 AM PT</td></tr>
@ -79,7 +79,7 @@ sections:
- type: markdown - type: markdown
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='461msgdesc'></div><b>opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>To set the <strong>Default Search Provider</strong>, use the following steps:</div><ol><li>Open an Administrator Command prompt and type the following: <strong>\"C:\\Program Files\\Internet Explorer\\iexplore.exe\"&nbsp;http://microsoft.com</strong></li><li>After Internet Explorer has opened, go to the <strong>Settings </strong>menu and select <strong>Manage add-ons</strong>.</li><li>Select <strong>Search Providers</strong> in left pane.</li><li>Select the link <strong>Find more search providers</strong> in the bottom left of the dialog.</li><li>A new Internet Explorer window should open, allowing you to select a search provider.</li><li>Select <strong>Add</strong> under the Search Provider you prefer.</li><li>The <strong>Add Search Provider</strong> dialog should open, select <strong>Add</strong>.</li><li>You should now be able to open Internet Explorer 11 normally.</li></ol><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and estimate a solution will be available in mid-June.</div><br><a href ='#461msg'>Back to top</a></td><td>OS Build 15063.1839<br><br>May 28, 2019<br><a href ='https://support.microsoft.com/help/4499162' target='_blank'>KB4499162</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 05, 2019 <br>05:54 PM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='462msgdesc'></div><b>Opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>To set the <strong>Default Search Provider</strong>, use the following steps:</div><ol><li>Open an Administrator Command prompt and type the following: <strong>\"C:\\Program Files\\Internet Explorer\\iexplore.exe\"&nbsp;http://microsoft.com</strong></li><li>After Internet Explorer has opened, go to the <strong>Settings </strong>menu and select <strong>Manage add-ons</strong>.</li><li>Select <strong>Search Providers</strong> in left pane.</li><li>Select the link <strong>Find more search providers</strong> in the bottom left of the dialog.</li><li>A new Internet Explorer window should open, allowing you to select a search provider.</li><li>Select <strong>Add</strong> under the Search Provider you prefer.</li><li>The <strong>Add Search Provider</strong> dialog should open, select <strong>Add</strong>.</li><li>You should now be able to open Internet Explorer 11 normally.</li></ol><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and estimate a solution will be available in mid-June.</div><br><a href ='#462msg'>Back to top</a></td><td>OS Build 15063.1839<br><br>May 28, 2019<br><a href ='https://support.microsoft.com/help/4499162' target='_blank'>KB4499162</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 05, 2019 <br>07:51 PM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr>
</table> </table>
" "

View File

@ -60,7 +60,7 @@ sections:
- type: markdown - type: markdown
text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br> text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br>
<table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr> <table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr>
<tr><td><div id='461msg'></div><b>opening Internet Explorer 11 may fail</b><br>Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.<br><br><a href = '#461msgdesc'>See details ></a></td><td>OS Build 16299.1182<br><br>May 28, 2019<br><a href ='https://support.microsoft.com/help/4499147' target='_blank'>KB4499147</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 05, 2019 <br>05:54 PM PT</td></tr> <tr><td><div id='462msg'></div><b>Opening Internet Explorer 11 may fail</b><br>Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.<br><br><a href = '#462msgdesc'>See details ></a></td><td>OS Build 16299.1182<br><br>May 28, 2019<br><a href ='https://support.microsoft.com/help/4499147' target='_blank'>KB4499147</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 05, 2019 <br>07:51 PM PT</td></tr>
<tr><td><div id='320msg'></div><b>Certain operations performed on a Cluster Shared Volume may fail</b><br>Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".<br><br><a href = '#320msgdesc'>See details ></a></td><td>OS Build 16299.904<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480978' target='_blank'>KB4480978</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 25, 2019 <br>02:00 PM PT</td></tr> <tr><td><div id='320msg'></div><b>Certain operations performed on a Cluster Shared Volume may fail</b><br>Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".<br><br><a href = '#320msgdesc'>See details ></a></td><td>OS Build 16299.904<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480978' target='_blank'>KB4480978</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 25, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='422msg'></div><b>Unable to access some gov.uk websites</b><br>gov.uk websites that dont support “HSTS” may not be accessible<br><br><a href = '#422msgdesc'>See details ></a></td><td>OS Build 16299.1143<br><br>May 14, 2019<br><a href ='https://support.microsoft.com/help/4498946' target='_blank'>KB4498946</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4505062' target='_blank'>KB4505062</a></td><td>May 19, 2019 <br>02:00 PM PT</td></tr> <tr><td><div id='422msg'></div><b>Unable to access some gov.uk websites</b><br>gov.uk websites that dont support “HSTS” may not be accessible<br><br><a href = '#422msgdesc'>See details ></a></td><td>OS Build 16299.1143<br><br>May 14, 2019<br><a href ='https://support.microsoft.com/help/4498946' target='_blank'>KB4498946</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4505062' target='_blank'>KB4505062</a></td><td>May 19, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='379msg'></div><b>Layout and cell size of Excel sheets may change when using MS UI Gothic </b><br>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. <br><br><a href = '#379msgdesc'>See details ></a></td><td>OS Build 16299.1127<br><br>April 25, 2019<br><a href ='https://support.microsoft.com/help/4493440' target='_blank'>KB4493440</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4499179' target='_blank'>KB4499179</a></td><td>May 14, 2019 <br>10:00 AM PT</td></tr> <tr><td><div id='379msg'></div><b>Layout and cell size of Excel sheets may change when using MS UI Gothic </b><br>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. <br><br><a href = '#379msgdesc'>See details ></a></td><td>OS Build 16299.1127<br><br>April 25, 2019<br><a href ='https://support.microsoft.com/help/4493440' target='_blank'>KB4493440</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4499179' target='_blank'>KB4499179</a></td><td>May 14, 2019 <br>10:00 AM PT</td></tr>
@ -80,7 +80,7 @@ sections:
- type: markdown - type: markdown
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='461msgdesc'></div><b>opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>To set the <strong>Default Search Provider</strong>, use the following steps:</div><ol><li>Open an Administrator Command prompt and type the following: <strong>\"C:\\Program Files\\Internet Explorer\\iexplore.exe\"&nbsp;http://microsoft.com</strong></li><li>After Internet Explorer has opened, go to the <strong>Settings </strong>menu and select <strong>Manage add-ons</strong>.</li><li>Select <strong>Search Providers</strong> in left pane.</li><li>Select the link <strong>Find more search providers</strong> in the bottom left of the dialog.</li><li>A new Internet Explorer window should open, allowing you to select a search provider.</li><li>Select <strong>Add</strong> under the Search Provider you prefer.</li><li>The <strong>Add Search Provider</strong> dialog should open, select <strong>Add</strong>.</li><li>You should now be able to open Internet Explorer 11 normally.</li></ol><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and estimate a solution will be available in mid-June.</div><br><a href ='#461msg'>Back to top</a></td><td>OS Build 16299.1182<br><br>May 28, 2019<br><a href ='https://support.microsoft.com/help/4499147' target='_blank'>KB4499147</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 05, 2019 <br>05:54 PM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='462msgdesc'></div><b>Opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>To set the <strong>Default Search Provider</strong>, use the following steps:</div><ol><li>Open an Administrator Command prompt and type the following: <strong>\"C:\\Program Files\\Internet Explorer\\iexplore.exe\"&nbsp;http://microsoft.com</strong></li><li>After Internet Explorer has opened, go to the <strong>Settings </strong>menu and select <strong>Manage add-ons</strong>.</li><li>Select <strong>Search Providers</strong> in left pane.</li><li>Select the link <strong>Find more search providers</strong> in the bottom left of the dialog.</li><li>A new Internet Explorer window should open, allowing you to select a search provider.</li><li>Select <strong>Add</strong> under the Search Provider you prefer.</li><li>The <strong>Add Search Provider</strong> dialog should open, select <strong>Add</strong>.</li><li>You should now be able to open Internet Explorer 11 normally.</li></ol><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and estimate a solution will be available in mid-June.</div><br><a href ='#462msg'>Back to top</a></td><td>OS Build 16299.1182<br><br>May 28, 2019<br><a href ='https://support.microsoft.com/help/4499147' target='_blank'>KB4499147</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 05, 2019 <br>07:51 PM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr>
</table> </table>
" "

View File

@ -60,7 +60,7 @@ sections:
- type: markdown - type: markdown
text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br> text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br>
<table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr> <table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr>
<tr><td><div id='461msg'></div><b>opening Internet Explorer 11 may fail</b><br>Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.<br><br><a href = '#461msgdesc'>See details ></a></td><td>OS Build 17134.799<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4499183' target='_blank'>KB4499183</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 05, 2019 <br>05:54 PM PT</td></tr> <tr><td><div id='462msg'></div><b>Opening Internet Explorer 11 may fail</b><br>Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.<br><br><a href = '#462msgdesc'>See details ></a></td><td>OS Build 17134.799<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4499183' target='_blank'>KB4499183</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 05, 2019 <br>07:51 PM PT</td></tr>
<tr><td><div id='237msg'></div><b>Issue using PXE to start a device from WDS</b><br>Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.<br><br><a href = '#237msgdesc'>See details ></a></td><td>OS Build 17134.648<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/help/4489868' target='_blank'>KB4489868</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 25, 2019 <br>02:00 PM PT</td></tr> <tr><td><div id='237msg'></div><b>Issue using PXE to start a device from WDS</b><br>Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.<br><br><a href = '#237msgdesc'>See details ></a></td><td>OS Build 17134.648<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/help/4489868' target='_blank'>KB4489868</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 25, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='319msg'></div><b>Certain operations performed on a Cluster Shared Volume may fail</b><br>Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".<br><br><a href = '#319msgdesc'>See details ></a></td><td>OS Build 17134.523<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480966' target='_blank'>KB4480966</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 25, 2019 <br>02:00 PM PT</td></tr> <tr><td><div id='319msg'></div><b>Certain operations performed on a Cluster Shared Volume may fail</b><br>Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".<br><br><a href = '#319msgdesc'>See details ></a></td><td>OS Build 17134.523<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480966' target='_blank'>KB4480966</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 25, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='422msg'></div><b>Unable to access some gov.uk websites</b><br>gov.uk websites that dont support “HSTS” may not be accessible<br><br><a href = '#422msgdesc'>See details ></a></td><td>OS Build 17134.765<br><br>May 14, 2019<br><a href ='https://support.microsoft.com/help/4499167' target='_blank'>KB4499167</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4505064' target='_blank'>KB4505064</a></td><td>May 19, 2019 <br>02:00 PM PT</td></tr> <tr><td><div id='422msg'></div><b>Unable to access some gov.uk websites</b><br>gov.uk websites that dont support “HSTS” may not be accessible<br><br><a href = '#422msgdesc'>See details ></a></td><td>OS Build 17134.765<br><br>May 14, 2019<br><a href ='https://support.microsoft.com/help/4499167' target='_blank'>KB4499167</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4505064' target='_blank'>KB4505064</a></td><td>May 19, 2019 <br>02:00 PM PT</td></tr>
@ -81,7 +81,7 @@ sections:
- type: markdown - type: markdown
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='461msgdesc'></div><b>opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>To set the <strong>Default Search Provider</strong>, use the following steps:</div><ol><li>Open an Administrator Command prompt and type the following: <strong>\"C:\\Program Files\\Internet Explorer\\iexplore.exe\"&nbsp;http://microsoft.com</strong></li><li>After Internet Explorer has opened, go to the <strong>Settings </strong>menu and select <strong>Manage add-ons</strong>.</li><li>Select <strong>Search Providers</strong> in left pane.</li><li>Select the link <strong>Find more search providers</strong> in the bottom left of the dialog.</li><li>A new Internet Explorer window should open, allowing you to select a search provider.</li><li>Select <strong>Add</strong> under the Search Provider you prefer.</li><li>The <strong>Add Search Provider</strong> dialog should open, select <strong>Add</strong>.</li><li>You should now be able to open Internet Explorer 11 normally.</li></ol><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and estimate a solution will be available in mid-June.</div><br><a href ='#461msg'>Back to top</a></td><td>OS Build 17134.799<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4499183' target='_blank'>KB4499183</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 05, 2019 <br>05:54 PM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='462msgdesc'></div><b>Opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>To set the <strong>Default Search Provider</strong>, use the following steps:</div><ol><li>Open an Administrator Command prompt and type the following: <strong>\"C:\\Program Files\\Internet Explorer\\iexplore.exe\"&nbsp;http://microsoft.com</strong></li><li>After Internet Explorer has opened, go to the <strong>Settings </strong>menu and select <strong>Manage add-ons</strong>.</li><li>Select <strong>Search Providers</strong> in left pane.</li><li>Select the link <strong>Find more search providers</strong> in the bottom left of the dialog.</li><li>A new Internet Explorer window should open, allowing you to select a search provider.</li><li>Select <strong>Add</strong> under the Search Provider you prefer.</li><li>The <strong>Add Search Provider</strong> dialog should open, select <strong>Add</strong>.</li><li>You should now be able to open Internet Explorer 11 normally.</li></ol><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and estimate a solution will be available in mid-June.</div><br><a href ='#462msg'>Back to top</a></td><td>OS Build 17134.799<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4499183' target='_blank'>KB4499183</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 05, 2019 <br>07:51 PM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr>
</table> </table>
" "

View File

@ -65,7 +65,7 @@ sections:
- type: markdown - type: markdown
text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br> text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br>
<table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr> <table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr>
<tr><td><div id='461msg'></div><b>opening Internet Explorer 11 may fail</b><br>Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.<br><br><a href = '#461msgdesc'>See details ></a></td><td>OS Build 17763.529<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4497934' target='_blank'>KB4497934</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 05, 2019 <br>05:54 PM PT</td></tr> <tr><td><div id='462msg'></div><b>Opening Internet Explorer 11 may fail</b><br>Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.<br><br><a href = '#462msgdesc'>See details ></a></td><td>OS Build 17763.529<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4497934' target='_blank'>KB4497934</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>June 05, 2019 <br>07:51 PM PT</td></tr>
<tr><td><div id='346msg'></div><b>Devices with some Asian language packs installed may receive an error</b><br>After installing the KB4493509 devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_F<br><br><a href = '#346msgdesc'>See details ></a></td><td>OS Build 17763.437<br><br>April 09, 2019<br><a href ='https://support.microsoft.com/help/4493509' target='_blank'>KB4493509</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 03, 2019 <br>10:59 AM PT</td></tr> <tr><td><div id='346msg'></div><b>Devices with some Asian language packs installed may receive an error</b><br>After installing the KB4493509 devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_F<br><br><a href = '#346msgdesc'>See details ></a></td><td>OS Build 17763.437<br><br>April 09, 2019<br><a href ='https://support.microsoft.com/help/4493509' target='_blank'>KB4493509</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 03, 2019 <br>10:59 AM PT</td></tr>
<tr><td><div id='341msg'></div><b>Printing from Microsoft Edge or other UWP apps, you may receive the error 0x80070007</b><br>Attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive an error.<br><br><a href = '#341msgdesc'>See details ></a></td><td>OS Build 17763.379<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/help/4489899' target='_blank'>KB4489899</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 02, 2019 <br>04:47 PM PT</td></tr> <tr><td><div id='341msg'></div><b>Printing from Microsoft Edge or other UWP apps, you may receive the error 0x80070007</b><br>Attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive an error.<br><br><a href = '#341msgdesc'>See details ></a></td><td>OS Build 17763.379<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/help/4489899' target='_blank'>KB4489899</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 02, 2019 <br>04:47 PM PT</td></tr>
<tr><td><div id='239msg'></div><b>Issue using PXE to start a device from WDS</b><br>Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.<br><br><a href = '#239msgdesc'>See details ></a></td><td>OS Build 17763.379<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/help/4489899' target='_blank'>KB4489899</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 09, 2019 <br>10:00 AM PT</td></tr> <tr><td><div id='239msg'></div><b>Issue using PXE to start a device from WDS</b><br>Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.<br><br><a href = '#239msgdesc'>See details ></a></td><td>OS Build 17763.379<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/help/4489899' target='_blank'>KB4489899</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>April 09, 2019 <br>10:00 AM PT</td></tr>
@ -92,7 +92,7 @@ sections:
- type: markdown - type: markdown
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='461msgdesc'></div><b>opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>To set the <strong>Default Search Provider</strong>, use the following steps:</div><ol><li>Open an Administrator Command prompt and type the following: <strong>\"C:\\Program Files\\Internet Explorer\\iexplore.exe\"&nbsp;http://microsoft.com</strong></li><li>After Internet Explorer has opened, go to the <strong>Settings </strong>menu and select <strong>Manage add-ons</strong>.</li><li>Select <strong>Search Providers</strong> in left pane.</li><li>Select the link <strong>Find more search providers</strong> in the bottom left of the dialog.</li><li>A new Internet Explorer window should open, allowing you to select a search provider.</li><li>Select <strong>Add</strong> under the Search Provider you prefer.</li><li>The <strong>Add Search Provider</strong> dialog should open, select <strong>Add</strong>.</li><li>You should now be able to open Internet Explorer 11 normally.</li></ol><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and estimate a solution will be available in mid-June.</div><br><a href ='#461msg'>Back to top</a></td><td>OS Build 17763.529<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4497934' target='_blank'>KB4497934</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 05, 2019 <br>05:54 PM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='462msgdesc'></div><b>Opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Workaround: </strong>To set the <strong>Default Search Provider</strong>, use the following steps:</div><ol><li>Open an Administrator Command prompt and type the following: <strong>\"C:\\Program Files\\Internet Explorer\\iexplore.exe\"&nbsp;http://microsoft.com</strong></li><li>After Internet Explorer has opened, go to the <strong>Settings </strong>menu and select <strong>Manage add-ons</strong>.</li><li>Select <strong>Search Providers</strong> in left pane.</li><li>Select the link <strong>Find more search providers</strong> in the bottom left of the dialog.</li><li>A new Internet Explorer window should open, allowing you to select a search provider.</li><li>Select <strong>Add</strong> under the Search Provider you prefer.</li><li>The <strong>Add Search Provider</strong> dialog should open, select <strong>Add</strong>.</li><li>You should now be able to open Internet Explorer 11 normally.</li></ol><div><br></div><div><strong>Next steps:</strong>&nbsp;We are working on a resolution and estimate a solution will be available in mid-June.</div><br><a href ='#462msg'>Back to top</a></td><td>OS Build 17763.529<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4497934' target='_blank'>KB4497934</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 05, 2019 <br>07:51 PM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr>
</table> </table>
" "

View File

@ -21,8 +21,8 @@ sections:
Find information on known issues for Windows 10, version 1903 and Windows Server, version 1903. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Find information on known issues for Windows 10, version 1903 and Windows Server, version 1903. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
<table border = '0' class='box-info'><tr> <table border = '0' class='box-info'><tr>
<td bgcolor='#d3f1fb' class='alert is-primary'><b>Current status</b>:<br> <td bgcolor='#d3f1fb' class='alert is-primary'><b>Current status as of June 6, 2019:</b><br>
<div>Windows 10, version 1903 is available by manually selecting “Check for updates” via Windows Update. (<b>Note</b> We are slowly throttling up this availability while we carefully monitor data and feedback.) The recommended servicing status is Semi-Annual Channel.</div> <div>Windows 10, version 1903 is available for any user who manually selects “Check for updates” via Windows Update. The recommended servicing status is Semi-Annual Channel. <br><b>Note</b> follow @WindowsUpdate to find out when new content is published to the release information dashboard.</div>
</td></tr></table> </td></tr></table>
" "
@ -65,20 +65,20 @@ sections:
- type: markdown - type: markdown
text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br> text: "<div>This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.</div><br>
<table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr> <table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Last updated</td></tr>
<tr><td><div id='456msg'></div><b>Windows Sandbox may fail to start with error code “0x80070002”</b><br>Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates<br><br><a href = '#456msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 20, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Acknowledged<br><a href = '' target='_blank'></a></td><td>May 24, 2019 <br>04:20 PM PT</td></tr> <tr><td><div id='463msg'></div><b>Windows Sandbox may fail to start with error code “0x80070002”</b><br>Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates<br><br><a href = '#463msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 20, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>June 06, 2019 <br>11:05 AM PT</td></tr>
<tr><td><div id='455msg'></div><b>Loss of functionality in Dynabook Smartphone Link app</b><br>After updating to Windows 10, version 1903, you may experience a loss of functionality when using the Dynabook Smartphone Link application.<br><br><a href = '#455msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 20, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>May 24, 2019 <br>03:10 PM PT</td></tr> <tr><td><div id='455msg'></div><b>Loss of functionality in Dynabook Smartphone Link app</b><br>After updating to Windows 10, version 1903, you may experience a loss of functionality when using the Dynabook Smartphone Link application.<br><br><a href = '#455msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 20, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>May 24, 2019 <br>03:10 PM PT</td></tr>
<tr><td><div id='448msg'></div><b>Display brightness may not respond to adjustments</b><br>Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers.<br><br><a href = '#448msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:47 PM PT</td></tr> <tr><td><div id='448msg'></div><b>Display brightness may not respond to adjustments</b><br>Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers.<br><br><a href = '#448msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:47 PM PT</td></tr>
<tr><td><div id='433msg'></div><b>Audio not working with Dolby Atmos headphones and home theater </b><br>Users may experience audio loss with Dolby Atmos headphones or Dolby Atmos home theater.<br><br><a href = '#433msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>07:17 AM PT</td></tr> <tr><td><div id='433msg'></div><b>Audio not working with Dolby Atmos headphones and home theater </b><br>Users may experience audio loss with Dolby Atmos headphones or Dolby Atmos home theater.<br><br><a href = '#433msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>07:17 AM PT</td></tr>
<tr><td><div id='426msg'></div><b>Duplicate folders and documents showing in user profile directory</b><br>If known folders (e.g. Desktop, Documents, or Pictures folders) are redirected, an empty folder with that same name may be created.<br><br><a href = '#426msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>07:16 AM PT</td></tr>
<tr><td><div id='454msg'></div><b>Gamma ramps, color profiles, and night light settings do not apply in some cases</b><br>Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.<br><br><a href = '#454msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 24, 2019 <br>11:02 AM PT</td></tr> <tr><td><div id='454msg'></div><b>Gamma ramps, color profiles, and night light settings do not apply in some cases</b><br>Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.<br><br><a href = '#454msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 24, 2019 <br>11:02 AM PT</td></tr>
<tr><td><div id='452msg'></div><b>AMD RAID driver incompatibility </b><br>Installation process may stop when trying to install Windows 10, version 1903 update on computers that run certain versions of AMD RAID drivers.<br><br><a href = '#452msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 23, 2019 <br>09:28 AM PT</td></tr>
<tr><td><div id='442msg'></div><b>Error attempting to update with external USB device or memory card attached </b><br>PCs with an external USB device or SD memory card attached may get error: \"This PC can't be upgraded to Windows 10.\"<br><br><a href = '#442msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:49 PM PT</td></tr>
<tr><td><div id='450msg'></div><b>Unable to discover or connect to Bluetooth devices</b><br>Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers.<br><br><a href = '#450msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:48 PM PT</td></tr> <tr><td><div id='450msg'></div><b>Unable to discover or connect to Bluetooth devices</b><br>Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers.<br><br><a href = '#450msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:48 PM PT</td></tr>
<tr><td><div id='447msg'></div><b>Intel Audio displays an intcdaud.sys notification</b><br>Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain. <br><br><a href = '#447msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:47 PM PT</td></tr> <tr><td><div id='447msg'></div><b>Intel Audio displays an intcdaud.sys notification</b><br>Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain. <br><br><a href = '#447msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:47 PM PT</td></tr>
<tr><td><div id='446msg'></div><b>Cannot launch Camera app </b><br>Microsoft and Intel have identified an issue affecting Intel RealSense SR300 or Intel RealSense S200 camera apps.<br><br><a href = '#446msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:47 PM PT</td></tr> <tr><td><div id='446msg'></div><b>Cannot launch Camera app </b><br>Microsoft and Intel have identified an issue affecting Intel RealSense SR300 or Intel RealSense S200 camera apps.<br><br><a href = '#446msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:47 PM PT</td></tr>
<tr><td><div id='445msg'></div><b>Intermittent loss of Wi-Fi connectivity</b><br>Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. <br><br><a href = '#445msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:46 PM PT</td></tr> <tr><td><div id='445msg'></div><b>Intermittent loss of Wi-Fi connectivity</b><br>Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. <br><br><a href = '#445msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:46 PM PT</td></tr>
<tr><td><div id='444msg'></div><b>D3D applications and games may fail to enter full-screen mode on rotated displays</b><br>Some Direct3D (D3D) applications and games may fail to enter full-screen mode on rotated displays.<br><br><a href = '#444msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>04:45 PM PT</td></tr> <tr><td><div id='464msg'></div><b>Duplicate folders and documents showing in user profile directory</b><br>If known folders (e.g. Desktop, Documents, or Pictures folders) are redirected, an empty folder with that same name may be created.<br><br><a href = '#464msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4497935' target='_blank'>KB4497935</a></td><td>May 29, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='427msg'></div><b>Older versions of BattlEye anti-cheat software incompatible</b><br>Microsoft and BattlEye have identified a compatibility issue with some games that use older versions of BattlEye anti-cheat software.<br><br><a href = '#427msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>May 21, 2019 <br>07:34 AM PT</td></tr> <tr><td><div id='466msg'></div><b>AMD RAID driver incompatibility </b><br>Installation process may stop when trying to install Windows 10, version 1903 update on computers that run certain versions of AMD RAID drivers.<br><br><a href = '#466msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>June 06, 2019 <br>11:06 AM PT</td></tr>
<tr><td><div id='467msg'></div><b>Error attempting to update with external USB device or memory card attached </b><br>PCs with an external USB device or SD memory card attached may get error: \"This PC can't be upgraded to Windows 10.\"<br><br><a href = '#467msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4497935' target='_blank'>KB4497935</a></td><td>May 29, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='469msg'></div><b>D3D applications and games may fail to enter full-screen mode on rotated displays</b><br>Some Direct3D (D3D) applications and games may fail to enter full-screen mode on rotated displays.<br><br><a href = '#469msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4497935' target='_blank'>KB4497935</a></td><td>May 29, 2019 <br>02:00 PM PT</td></tr>
<tr><td><div id='468msg'></div><b>Older versions of BattlEye anti-cheat software incompatible</b><br>Microsoft and BattlEye have identified a compatibility issue with some games that use older versions of BattlEye anti-cheat software.<br><br><a href = '#468msgdesc'>See details ></a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>June 06, 2019 <br>11:04 AM PT</td></tr>
</table> </table>
" "
@ -94,19 +94,19 @@ sections:
- type: markdown - type: markdown
text: " text: "
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr> <table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='456msgdesc'></div><b>Windows Sandbox may fail to start with error code “0x80070002”</b><div>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.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Next steps: </strong>We are working on a resolution and estimate a solution will be available in late June.</div><br><a href ='#456msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 20, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Acknowledged<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 24, 2019 <br>04:20 PM PT<br><br>Opened:<br>May 24, 2019 <br>04:20 PM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='463msgdesc'></div><b>Windows Sandbox may fail to start with error code “0x80070002”</b><div>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.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Next steps: </strong>We are working on a resolution and estimate a solution will be available mid-to-late June.</div><br><a href ='#463msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 20, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>Last updated:<br>June 06, 2019 <br>11:05 AM PT<br><br>Opened:<br>May 24, 2019 <br>04:20 PM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='455msgdesc'></div><b>Loss of functionality in Dynabook Smartphone Link app</b><div>Some users may experience a loss of functionality after updating to Windows 10, version 1903 when using the Dynabook Smartphone Link application on Windows devices. Loss of functionality may affect the display of phone numbers in the Call menu and the ability to answer phone calls on the Windows PC.</div><div><br></div><div>To safeguard your update experience, we have applied a compatibility hold on devices with Dynabook Smartphone Link from being offered Windows 10, version 1903, until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Next steps: </strong>Microsoft and Dynabook are working on a resolution; the Dynabook Smartphone Link application may have a loss of functionality until this issue is resolved.</div><div><br></div><div><strong>Note&nbsp;</strong>We recommend that you do not attempt to manually update using the&nbsp;<strong>Update now</strong>&nbsp;button or the Media Creation Tool until this issue has been resolved.</div><br><a href ='#455msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 20, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 24, 2019 <br>03:10 PM PT<br><br>Opened:<br>May 24, 2019 <br>03:10 PM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='455msgdesc'></div><b>Loss of functionality in Dynabook Smartphone Link app</b><div>Some users may experience a loss of functionality after updating to Windows 10, version 1903 when using the Dynabook Smartphone Link application on Windows devices. Loss of functionality may affect the display of phone numbers in the Call menu and the ability to answer phone calls on the Windows PC.</div><div><br></div><div>To safeguard your update experience, we have applied a compatibility hold on devices with Dynabook Smartphone Link from being offered Windows 10, version 1903, until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Next steps: </strong>Microsoft and Dynabook are working on a resolution; the Dynabook Smartphone Link application may have a loss of functionality until this issue is resolved.</div><div><br></div><div><strong>Note&nbsp;</strong>We recommend that you do not attempt to manually update using the&nbsp;<strong>Update now</strong>&nbsp;button or the Media Creation Tool until this issue has been resolved.</div><br><a href ='#455msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 20, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 24, 2019 <br>03:10 PM PT<br><br>Opened:<br>May 24, 2019 <br>03:10 PM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='448msgdesc'></div><b>Display brightness may not respond to adjustments</b><div>Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Window 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change.</div><div><br></div><div>To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>Restart your device to apply changes to brightness.</div><div><br></div><div><strong>Note</strong> We recommend that you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until this issue has been resolved.</div><div><br></div><div><strong>Next steps: </strong>We are working on a resolution that will be made available in upcoming release.</div><br><a href ='#448msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:47 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:56 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='448msgdesc'></div><b>Display brightness may not respond to adjustments</b><div>Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Window 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change.</div><div><br></div><div>To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>Restart your device to apply changes to brightness.</div><div><br></div><div><strong>Note</strong> We recommend that you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until this issue has been resolved.</div><div><br></div><div><strong>Next steps: </strong>We are working on a resolution that will be made available in upcoming release.</div><br><a href ='#448msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:47 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:56 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='433msgdesc'></div><b>Audio not working with Dolby Atmos headphones and home theater </b><div>After updating to Windows 10, version 1903, you may experience loss of audio with Dolby Atmos for home theater (free extension) or Dolby Atmos for headphones (paid extension) acquired through the Microsoft Store due to a licensing configuration error.</div><div>&nbsp;</div><div>This occurs due to an issue with a Microsoft Store licensing component, where license holders are not able to connect to the Dolby Access app and enable Dolby Atmos extensions.</div><div>&nbsp;</div><div>To safeguard your update experience, we have applied protective hold on devices from being offered Windows 10, version 1903 until&nbsp;this issue is resolved. This configuration error will not result in loss of access for the acquired license once the problem is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Next steps: </strong>We are working on a resolution for Microsoft Store and estimate a solution will be available in mid-June.</div><div><strong>Note</strong> We recommend you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until this issue has been resolved.&nbsp;</div><br><a href ='#433msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>07:17 AM PT<br><br>Opened:<br>May 21, 2019 <br>07:16 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='433msgdesc'></div><b>Audio not working with Dolby Atmos headphones and home theater </b><div>After updating to Windows 10, version 1903, you may experience loss of audio with Dolby Atmos for home theater (free extension) or Dolby Atmos for headphones (paid extension) acquired through the Microsoft Store due to a licensing configuration error.</div><div>&nbsp;</div><div>This occurs due to an issue with a Microsoft Store licensing component, where license holders are not able to connect to the Dolby Access app and enable Dolby Atmos extensions.</div><div>&nbsp;</div><div>To safeguard your update experience, we have applied protective hold on devices from being offered Windows 10, version 1903 until&nbsp;this issue is resolved. This configuration error will not result in loss of access for the acquired license once the problem is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Next steps: </strong>We are working on a resolution for Microsoft Store and estimate a solution will be available in mid-June.</div><div><strong>Note</strong> We recommend you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until this issue has been resolved.&nbsp;</div><br><a href ='#433msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>07:17 AM PT<br><br>Opened:<br>May 21, 2019 <br>07:16 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='426msgdesc'></div><b>Duplicate folders and documents showing in user profile directory</b><div>If you have redirected known folders (e.g. Desktop, Documents, or Pictures folders) you may see an empty folder with the same name in your %userprofile% directories after updating to Windows 10, version 1903. This may occur if known folders were redirected when you chose to back up your content to OneDrive using the OneDrive wizard, or if you chose to back up your content during the Windows Out-of-Box-Experience (OOBE). This may also occur if you redirected your known folders manually through the Properties dialog box in File Explorer. This issue does not cause any user files to be deleted and a solution is in progress.</div><div><br></div><div>To safeguard your update experience, we have applied a quality hold on devices with redirected known folders from being offered Windows 10, version 1903, until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Next steps: </strong>Microsoft is working on a resolution and estimates a solution will be available in late May.</div><div><strong>Note </strong>We recommend that you do not attempt to manually update to Windows 10, version 1903 using the <strong>Update now</strong> button or the Media Creation Tool until this issue has been resolved.</div><br><a href ='#426msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Investigating<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>07:16 AM PT<br><br>Opened:<br>May 21, 2019 <br>07:16 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='454msgdesc'></div><b>Gamma ramps, color profiles, and night light settings do not apply in some cases</b><div>Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.</div><div><br></div><div>Microsoft has identified some scenarios where night light settings may stop working, for example:</div><ul><li>Connecting to (or disconnecting from) an external monitor, dock, or projector</li><li>Rotating the screen</li><li>Updating display drivers or making other display mode changes</li><li>Closing full screen applications</li><li>Applying custom color profiles</li><li>Running applications that rely on custom gamma ramps</li></ul><div></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer.&nbsp;For other color setting issues, restart your computer to correct the issue.</div><div><br></div><div><strong>Note </strong>We recommend that you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until this issue has been resolved.</div><div><br></div><div><strong>Next steps: </strong>We are working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#454msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 24, 2019 <br>11:02 AM PT<br><br>Opened:<br>May 21, 2019 <br>07:28 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='454msgdesc'></div><b>Gamma ramps, color profiles, and night light settings do not apply in some cases</b><div>Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.</div><div><br></div><div>Microsoft has identified some scenarios where night light settings may stop working, for example:</div><ul><li>Connecting to (or disconnecting from) an external monitor, dock, or projector</li><li>Rotating the screen</li><li>Updating display drivers or making other display mode changes</li><li>Closing full screen applications</li><li>Applying custom color profiles</li><li>Running applications that rely on custom gamma ramps</li></ul><div></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer.&nbsp;For other color setting issues, restart your computer to correct the issue.</div><div><br></div><div><strong>Note </strong>We recommend that you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until this issue has been resolved.</div><div><br></div><div><strong>Next steps: </strong>We are working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#454msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 24, 2019 <br>11:02 AM PT<br><br>Opened:<br>May 21, 2019 <br>07:28 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='452msgdesc'></div><b>AMD RAID driver incompatibility </b><div>Microsoft and AMD have identified an incompatibility with AMD RAID driver versions earlier than 9.2.0.105. When you attempt to install&nbsp;the Windows 10, version 1903 update on a Windows 10-based computer with an affected driver version, the installation process stops and you get a message like the following:</div><p class=\"ql-indent-1\">AMD Ryzen™ or AMD Ryzen™ Threadripper™ configured in SATA or NVMe RAID mode.</div><p class=\"ql-indent-1\">“A driver is installed that causes stability problems on Windows. This driver will be disabled. Check with your software/driver provider for an updated version that runs on this version of Windows.”</div><div><strong>&nbsp;</strong></div><div>To safeguard your update experience, we have applied a compatibility hold on devices with these AMD drivers from being offered Windows 10, version 1903, until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>To resolve this issue, download the latest AMD RAID drivers directly from AMD at&nbsp;<a href=\"https://www.amd.com/en/support/chipsets/amd-socket-tr4/x399\" target=\"_blank\">https://www.amd.com/en/support/chipsets/amd-socket-tr4/x399</a>. The drivers must be version&nbsp;9.2.0.105 or later. Install the drivers on the affected computer, and then restart the installation process for the Windows 10, version 1903 feature update.</div><div>&nbsp;</div><div><strong>Note</strong> We recommend that you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.</div><div>&nbsp;</div><br><a href ='#452msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 23, 2019 <br>09:28 AM PT<br><br>Opened:<br>May 21, 2019 <br>07:12 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='442msgdesc'></div><b>Error attempting to update with external USB device or memory card attached </b><div>If you have an external USB device or SD memory card attached when installing Windows 10, version 1903, you may get an error message stating \"This PC can't be upgraded to Windows 10.\" This is caused by inappropriate drive reassignment during installation.</div><div><br></div><div>Sample scenario: An update to Windows 10, version 1903 is attempted on a computer that has a thumb drive inserted into its USB port. Before the update, the thumb drive is mounted in the system as drive G based on the existing drive configuration. After the feature update is installed; however, the device is&nbsp;reassigned a different drive letter (e.g., drive H).</div><div><br></div><div><strong>Note</strong> The drive reassignment is not limited to removable drives. Internal hard drives may also be affected.</div><div><br></div><div>To safeguard your update experience, we have applied a hold on devices with an external USB device or SD memory card attached from being offered Windows 10, version 1903 until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>To work around this issue, remove&nbsp;all external media, such as USB devices and SD cards, from your computer and restart installation of the Windows 10, version 1903 feature update. The update should then proceed normally.</div><div><strong>Note </strong>If you need to keep your external device, SD memory card, or other devices attached to your computer while updating, we recommend that you do not attempt to manually update to Windows 10, version 1903 using the <strong>Update now </strong>button or the Media Creation Tool until this issue has been resolved.</div><div><br></div><div><strong>Next steps: </strong>Microsoft is working on a resolution and estimate a solution will be available in late May.</div><br><a href ='#442msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:49 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:38 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='450msgdesc'></div><b>Unable to discover or connect to Bluetooth devices</b><div>Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Realtek and Qualcomm. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Realtek or Qualcomm Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li><li>Server: Windows Server, version 1903</li></ul><div></div><div><strong>Workaround: </strong>Check with your device manufacturer (OEM) to see if an updated driver is available and install it.</div><div><br></div><ul><li>For Qualcomm drivers, you will need to install a driver version greater than 10.0.1.11.</li><li>For Realtek drivers, you will need to install a driver version greater than 1.5.1011.0.</li></ul><div></div><div><strong>Note</strong> Until an updated driver has been installed, we recommend you do not attempt to manually update using the<strong> Update now </strong>button or the Media Creation Tool.&nbsp;</div><div><br></div><div><strong>Next steps:&nbsp;</strong>Microsoft is working with Realtek and Qualcomm to release new drivers for all affected system via Windows Update.<strong>&nbsp;</strong>&nbsp;</div><div><br></div><br><a href ='#450msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:48 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:29 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='450msgdesc'></div><b>Unable to discover or connect to Bluetooth devices</b><div>Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Realtek and Qualcomm. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Realtek or Qualcomm Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li><li>Server: Windows Server, version 1903</li></ul><div></div><div><strong>Workaround: </strong>Check with your device manufacturer (OEM) to see if an updated driver is available and install it.</div><div><br></div><ul><li>For Qualcomm drivers, you will need to install a driver version greater than 10.0.1.11.</li><li>For Realtek drivers, you will need to install a driver version greater than 1.5.1011.0.</li></ul><div></div><div><strong>Note</strong> Until an updated driver has been installed, we recommend you do not attempt to manually update using the<strong> Update now </strong>button or the Media Creation Tool.&nbsp;</div><div><br></div><div><strong>Next steps:&nbsp;</strong>Microsoft is working with Realtek and Qualcomm to release new drivers for all affected system via Windows Update.<strong>&nbsp;</strong>&nbsp;</div><div><br></div><br><a href ='#450msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:48 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:29 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='447msgdesc'></div><b>Intel Audio displays an intcdaud.sys notification</b><div>Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in higher than normal battery drain.&nbsp;If you see an <strong>intcdaud.sys</strong> notification or “What needs your attention” notification when trying to update to Windows 10, version 1903, you have an affected Intel Audio Display device driver installed on your machine (intcdaud.sys, versions 10.25.0.3 through 10.25.0.8).</div><div>&nbsp;&nbsp;</div><div>To safeguard your update experience, we have applied a compatibility hold on devices with drivers from being offered Windows 10, version 1903 until&nbsp;updated device drivers have been installed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903; Windows 10, version 1809</li></ul><div></div><div><strong>Workaround:</strong></div><div>On the “What needs your attention\" notification, click the <strong>Back </strong>button to remain on your current version of Windows 10. (Do not click <strong>Confirm</strong> as this will proceed with the update and you may experience compatibility issues.)&nbsp;Affected devices will automatically revert to the previous working configuration.</div><div><br></div><div>For more information, see <a href=\"https://www.intel.com/content/www/us/en/support/articles/000030792/graphics-drivers.html\" target=\"_blank\" style=\"\">Intel's customer support guidance</a> and the Microsoft knowledge base article <a href=\"https://support.microsoft.com/help/4465877\" target=\"_blank\" style=\"\">KB4465877</a>.</div><div><br></div><div><strong>Note</strong> We recommend you do not attempt to update your devices until newer device drivers are installed.</div><div><br></div><div><strong>Next steps: </strong>You can opt to wait for newer drivers to be installed automatically through Windows Update or check with the computer manufacturer for the latest device driver software availability and installation procedures.</div><br><a href ='#447msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:47 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:22 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='447msgdesc'></div><b>Intel Audio displays an intcdaud.sys notification</b><div>Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in higher than normal battery drain.&nbsp;If you see an <strong>intcdaud.sys</strong> notification or “What needs your attention” notification when trying to update to Windows 10, version 1903, you have an affected Intel Audio Display device driver installed on your machine (intcdaud.sys, versions 10.25.0.3 through 10.25.0.8).</div><div>&nbsp;&nbsp;</div><div>To safeguard your update experience, we have applied a compatibility hold on devices with drivers from being offered Windows 10, version 1903 until&nbsp;updated device drivers have been installed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903; Windows 10, version 1809</li></ul><div></div><div><strong>Workaround:</strong></div><div>On the “What needs your attention\" notification, click the <strong>Back </strong>button to remain on your current version of Windows 10. (Do not click <strong>Confirm</strong> as this will proceed with the update and you may experience compatibility issues.)&nbsp;Affected devices will automatically revert to the previous working configuration.</div><div><br></div><div>For more information, see <a href=\"https://www.intel.com/content/www/us/en/support/articles/000030792/graphics-drivers.html\" target=\"_blank\" style=\"\">Intel's customer support guidance</a> and the Microsoft knowledge base article <a href=\"https://support.microsoft.com/help/4465877\" target=\"_blank\" style=\"\">KB4465877</a>.</div><div><br></div><div><strong>Note</strong> We recommend you do not attempt to update your devices until newer device drivers are installed.</div><div><br></div><div><strong>Next steps: </strong>You can opt to wait for newer drivers to be installed automatically through Windows Update or check with the computer manufacturer for the latest device driver software availability and installation procedures.</div><br><a href ='#447msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:47 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:22 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='446msgdesc'></div><b>Cannot launch Camera app </b><div>Microsoft and Intel have identified an issue affecting Intel RealSense SR300 and Intel RealSense S200 cameras when using the Camera app. After updating to the Windows 10 May 2019 Update and launching the Camera app, you may get an error message stating:</div><p class=\"ql-indent-1\">\"Close other apps, error code: 0XA00F4243.”</div><div><br></div><div>To safeguard your update experience, we have applied a protective hold on machines with Intel RealSense SR300 or Intel RealSense S200 cameras installed from being offered Windows 10, version 1903, until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>To temporarily resolve this issue, perform one of the following:</div><div><br></div><ul><li>Unplug your camera and plug it back in.</li></ul><p class=\"ql-indent-1\">or</div><ul><li>Disable and re-enable the driver in Device Manager. In the Search box, type \"Device Manager\" and press <strong>Enter</strong>. In the Device Manager dialog box, expand <strong>Cameras</strong>, then right-click on any <strong>RealSense</strong> driver listed and select <strong>Disable device</strong>. Right click on the driver again and select <strong>Enable device</strong>.</li></ul><p class=\"ql-indent-1\">or</div><ul><li>Restart the <strong>RealSense </strong>service. In the Search box, type \"Task Manager\" and hit <strong>Enter</strong>. In the Task Manager dialog box, click on the <strong>Services </strong>tab, right-click on <strong>RealSense</strong>, and select <strong>Restart</strong>.&nbsp;</li></ul><div></div><div><strong>Note </strong>This workaround will only resolve the issue until your next system restart.</div><div><br></div><div><strong>Note </strong>We recommend that you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until this issue has been resolved.</div><div><br></div><div><strong>Next steps: </strong>We are working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#446msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:47 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:20 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='446msgdesc'></div><b>Cannot launch Camera app </b><div>Microsoft and Intel have identified an issue affecting Intel RealSense SR300 and Intel RealSense S200 cameras when using the Camera app. After updating to the Windows 10 May 2019 Update and launching the Camera app, you may get an error message stating:</div><p class=\"ql-indent-1\">\"Close other apps, error code: 0XA00F4243.”</div><div><br></div><div>To safeguard your update experience, we have applied a protective hold on machines with Intel RealSense SR300 or Intel RealSense S200 cameras installed from being offered Windows 10, version 1903, until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>To temporarily resolve this issue, perform one of the following:</div><div><br></div><ul><li>Unplug your camera and plug it back in.</li></ul><p class=\"ql-indent-1\">or</div><ul><li>Disable and re-enable the driver in Device Manager. In the Search box, type \"Device Manager\" and press <strong>Enter</strong>. In the Device Manager dialog box, expand <strong>Cameras</strong>, then right-click on any <strong>RealSense</strong> driver listed and select <strong>Disable device</strong>. Right click on the driver again and select <strong>Enable device</strong>.</li></ul><p class=\"ql-indent-1\">or</div><ul><li>Restart the <strong>RealSense </strong>service. In the Search box, type \"Task Manager\" and hit <strong>Enter</strong>. In the Task Manager dialog box, click on the <strong>Services </strong>tab, right-click on <strong>RealSense</strong>, and select <strong>Restart</strong>.&nbsp;</li></ul><div></div><div><strong>Note </strong>This workaround will only resolve the issue until your next system restart.</div><div><br></div><div><strong>Note </strong>We recommend that you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until this issue has been resolved.</div><div><br></div><div><strong>Next steps: </strong>We are working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#446msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:47 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:20 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='445msgdesc'></div><b>Intermittent loss of Wi-Fi connectivity</b><div>Some older computers may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM).</div><div><br></div><div>To safeguard your upgrade experience, we have applied a hold on devices with this Qualcomm driver from being offered Windows 10, version 1903, until&nbsp;the updated driver is installed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>Download<strong> </strong>and install an updated Wi-Fi driver from your device manufacturer (OEM).</div><div>&nbsp;</div><div><strong>Note</strong> We recommend that you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.</div><br><a href ='#445msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:46 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:13 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='445msgdesc'></div><b>Intermittent loss of Wi-Fi connectivity</b><div>Some older computers may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM).</div><div><br></div><div>To safeguard your upgrade experience, we have applied a hold on devices with this Qualcomm driver from being offered Windows 10, version 1903, until&nbsp;the updated driver is installed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>Download<strong> </strong>and install an updated Wi-Fi driver from your device manufacturer (OEM).</div><div>&nbsp;</div><div><strong>Note</strong> We recommend that you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.</div><br><a href ='#445msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:46 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:13 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='444msgdesc'></div><b>D3D applications and games may fail to enter full-screen mode on rotated displays</b><div>Some Direct3D&nbsp;(D3D) applications and games (e.g., 3DMark) may fail to enter full-screen mode on displays where the display orientation has been changed from the default (e.g., a landscape display in portrait mode).</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li><li>Server: Windows Server, version 1903</li></ul><div></div><div><strong>Workaround: </strong>To work around this issue, do one of the following:</div><ul><li>Run applications in windowed mode or, if available, on a secondary non-rotated display.&nbsp;</li><li>Change compatibility settings for the applications to “Disable Full Screen Optimizations.”</li></ul><div></div><div><strong>Next steps: </strong>Microsoft is working on a resolution and estimates a solution will be available in late May.</div><br><a href ='#444msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>04:45 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:05 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='464msgdesc'></div><b>Duplicate folders and documents showing in user profile directory</b><div>If you have redirected known folders (e.g. Desktop, Documents, or Pictures folders) you may see an empty folder with the same name in your %userprofile% directories after updating to Windows 10, version 1903. This may occur if known folders were redirected when you chose to back up your content to OneDrive using the OneDrive wizard, or if you chose to back up your content during the Windows Out-of-Box-Experience (OOBE). This may also occur if you redirected your known folders manually through the Properties dialog box in File Explorer. This issue does not cause any user files to be deleted and a solution is in progress.</div><div><br></div><div>To safeguard your update experience, we have applied a quality hold on devices with redirected known folders from being offered Windows 10, version 1903, until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Resolution: </strong>This issue was resolved in <a href='https://support.microsoft.com/help/4497935' target='_blank'>KB4497935</a>. The safeguard hold will be removed following the June Update Tuesday release.</div><div><strong>Note </strong>We recommend that you do not attempt to manually update to Windows 10, version 1903 using the <strong>Update now</strong> button or the Media Creation Tool until this issue has been resolved.</div><br><a href ='#464msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4497935' target='_blank'>KB4497935</a></td><td>Resolved:<br>May 29, 2019 <br>02:00 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:16 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='427msgdesc'></div><b>Older versions of BattlEye anti-cheat software incompatible</b><div>Microsoft and BattlEye have identified a compatibility issue with some games that use older versions of BattlEye anti-cheat software. When launching a game that uses an older, impacted version of BattlEye anti-cheat software on a device running Windows 10, version 1903, the device may experience a system crash.</div><div><br></div><div>To safeguard your gaming experience, we have applied a compatibility hold on devices with the impacted versions of BattlEye software used by games installed on your PC. This will prevent Windows 10, version 1903 from being offered until the incompatible version of BattlEye software is no longer installed on the device.&nbsp;</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Mitigated: </strong>BattlEye has provided an updated patch to known impacted games. For a list of recent games that use BattlEye, go to&nbsp;<a href=\"https://www.battleye.com/\" target=\"_blank\">https://www.battleye.com/</a>.</div><div><br></div><div><strong>Workaround: </strong>Before updating your machine, we recommend you do one or more of the following:</div><div><br></div><ul><li>Verify that your game is up to date with the latest available version of BattlEye software. Some game platforms allow you to validate your game files, which can confirm that your installation is fully up to date.</li><li>Restart your system and open the game again.</li><li>Uninstall BattlEye using <a href=\"https://www.battleye.com/downloads/UninstallBE.exe\" target=\"_blank\">https://www.battleye.com/downloads/UninstallBE.exe</a>, and then reopen your game.</li><li>Uninstall and reinstall your game.</li></ul><div></div><div>For more troubleshooting options, see <a href=\"https://www.battleye.com/support/faq/\" target=\"_blank\">https://www.battleye.com/support/faq/</a>.</div><div><br></div><div><strong>Next steps: </strong>We are working with BattlEye and gaming partners to ensure games are automatically updated with the latest BattlEye software. We have confirmed the latest version of impacted games do not exhibit this issue. To minimize the chance of hitting this upgrade compatibility hold, please make sure you are running the latest version of your games before attempting to update the operating system.&nbsp;&nbsp;</div><div><strong>Note </strong>We recommend that you do not attempt to manually update using the <strong>Update now </strong>button or the Media Creation Tool until you have installed an updated version of BattlEye software that resolves this issue.</div><br><a href ='#427msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>May 21, 2019 <br>07:34 AM PT<br><br>Opened:<br>May 21, 2019 <br>07:34 AM PT</td></tr> <tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='466msgdesc'></div><b>AMD RAID driver incompatibility </b><div>Microsoft and AMD have identified an incompatibility with AMD RAID driver versions earlier than 9.2.0.105. When you attempt to install&nbsp;the Windows 10, version 1903 update on a Windows 10-based computer with an affected driver version, the installation process stops and you get a message like the following:</div><p class=\"ql-indent-1\">AMD Ryzen™ or AMD Ryzen™ Threadripper™ configured in SATA or NVMe RAID mode.</div><p class=\"ql-indent-1\">“A driver is installed that causes stability problems on Windows. This driver will be disabled. Check with your software/driver provider for an updated version that runs on this version of Windows.”</div><div><strong>&nbsp;</strong></div><div>To safeguard your update experience, we have applied a compatibility hold on devices with these AMD drivers from being offered Windows 10, version 1903, until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Resolution: </strong>This issue has been resolved externally by AMD. To resolve this issue, you will need to download the latest AMD RAID drivers directly from AMD at&nbsp;<a href=\"https://www.amd.com/en/support/chipsets/amd-socket-tr4/x399\" target=\"_blank\">https://www.amd.com/en/support/chipsets/amd-socket-tr4/x399</a>. The drivers must be version&nbsp;9.2.0.105 or later. Install the drivers on the affected computer, and then restart the installation process for the Windows 10, version 1903 feature update.</div><div>&nbsp;</div><div><strong>Note</strong> The safeguard hold will remain in place on machines with the older AMD RAID drivers. We recommend that you do not attempt to manually update using the <strong>Update now</strong> button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.</div><br><a href ='#466msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>Resolved:<br>June 06, 2019 <br>11:06 AM PT<br><br>Opened:<br>May 21, 2019 <br>07:12 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='467msgdesc'></div><b>Error attempting to update with external USB device or memory card attached </b><div>If you have an external USB device or SD memory card attached when installing Windows 10, version 1903, you may get an error message stating \"This PC can't be upgraded to Windows 10.\" This is caused by inappropriate drive reassignment during installation.</div><div><br></div><div>Sample scenario: An update to Windows 10, version 1903 is attempted on a computer that has a thumb drive inserted into its USB port. Before the update, the thumb drive is mounted in the system as drive G based on the existing drive configuration. After the feature update is installed; however, the device is&nbsp;reassigned a different drive letter (e.g., drive H).</div><div><br></div><div><strong>Note</strong> The drive reassignment is not limited to removable drives. Internal hard drives may also be affected.</div><div><br></div><div>To safeguard your update experience, we have applied a hold on devices with an external USB device or SD memory card attached from being offered Windows 10, version 1903 until&nbsp;this issue is resolved.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Resolution: </strong>This issue was resolved in <a href='https://support.microsoft.com/help/4497935' target='_blank'>KB4497935</a>. The safeguard hold will be removed following the June Update Tuesday release.</div><br><a href ='#467msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4497935' target='_blank'>KB4497935</a></td><td>Resolved:<br>May 29, 2019 <br>02:00 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:38 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='469msgdesc'></div><b>D3D applications and games may fail to enter full-screen mode on rotated displays</b><div>Some Direct3D&nbsp;(D3D) applications and games (e.g., 3DMark) may fail to enter full-screen mode on displays where the display orientation has been changed from the default (e.g., a landscape display in portrait mode).</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li><li>Server: Windows Server, version 1903</li></ul><div></div><div><strong>Resolution: </strong>This issue was resolved in <a href='https://support.microsoft.com/help/4497935' target='_blank'>KB4497935</a>.&nbsp;</div><br><a href ='#469msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4497935' target='_blank'>KB4497935</a></td><td>Resolved:<br>May 29, 2019 <br>02:00 PM PT<br><br>Opened:<br>May 21, 2019 <br>07:05 AM PT</td></tr>
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='468msgdesc'></div><b>Older versions of BattlEye anti-cheat software incompatible</b><div>Microsoft and BattlEye have identified a compatibility issue with some games that use older versions of BattlEye anti-cheat software. When launching a game that uses an older, impacted version of BattlEye anti-cheat software on a device running Windows 10, version 1903, the device may experience a system crash.</div><div><br></div><div>To safeguard your gaming experience, we have applied a compatibility hold on devices with the impacted versions of BattlEye software used by games installed on your PC. This will prevent Windows 10, version 1903 from being offered until the incompatible version of BattlEye software is no longer installed on the device.&nbsp;</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903</li></ul><div></div><div><strong>Workaround: </strong>Before updating your machine, we recommend you do one or more of the following:</div><div><br></div><ul><li>Verify that your game is up to date with the latest available version of BattlEye software. Some game platforms allow you to validate your game files, which can confirm that your installation is fully up to date.</li><li>Restart your system and open the game again.</li><li>Uninstall BattlEye using <a href=\"https://www.battleye.com/downloads/UninstallBE.exe\" target=\"_blank\">https://www.battleye.com/downloads/UninstallBE.exe</a>, and then reopen your game.</li><li>Uninstall and reinstall your game.</li></ul><div></div><div>For more troubleshooting options, see <a href=\"https://www.battleye.com/support/faq/\" target=\"_blank\">https://www.battleye.com/support/faq/</a>.</div><div><br></div><div>We are working with BattlEye and gaming partners to ensure games are automatically updated with the latest BattlEye software. We have confirmed the latest version of impacted games do not exhibit this issue. To minimize the chance of hitting this upgrade compatibility hold, please make sure you are running the latest version of your games before attempting to update the operating system.&nbsp;&nbsp;</div><div><br></div><div><strong>Resolution: </strong>This issue was resolved externally by BattlEye. You will need to update the BattlEye service for impacted games. For a list of recent games that use BattlEye, go to&nbsp;<a href=\"https://www.battleye.com/\" target=\"_blank\">https://www.battleye.com/</a>. The safeguard hold will remain in place on older version of the BattlEye service. We recommend that you do not attempt to manually update using the <strong>Update now </strong>button or the Media Creation Tool until you have installed an updated version of BattlEye software that resolves this issue.</div><br><a href ='#468msg'>Back to top</a></td><td>OS Build 18362.116<br><br>May 21, 2019<br><a href ='https://support.microsoft.com/help/4505057' target='_blank'>KB4505057</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>Resolved:<br>June 06, 2019 <br>11:04 AM PT<br><br>Opened:<br>May 21, 2019 <br>07:34 AM PT</td></tr>
</table> </table>
" "