mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 14:27:22 +00:00
Updates
This commit is contained in:
Nisha Mittal (Wipro Ltd.)
parent
a515154956
commit
5a13c4ea5e
@ -1,10 +1,10 @@
|
|||||||
### YamlMime:YamlDocument
|
### YamlMime:YamlDocument
|
||||||
|
|
||||||
documentType: LandingData
|
documentType: LandingData
|
||||||
title: Resolved issues in Windows 10, version 1709 and Windows Server 1709
|
title: Resolved issues in Windows 10, version 1709 and Windows Server, 1709
|
||||||
metadata:
|
metadata:
|
||||||
document_id:
|
document_id:
|
||||||
title: Resolved issues in Windows 10, version 1709 and Windows Server 1709
|
title: Resolved issues in Windows 10, version 1709 and Windows Server, 1709
|
||||||
description: Resolved issues in Windows 10, version 1709 and Windows Server 1709
|
description: Resolved issues in Windows 10, version 1709 and Windows Server 1709
|
||||||
keywords: ["Resolved issues in Windows 10", "Windows 10", "Windows 10, version 1709"]
|
keywords: ["Resolved issues in Windows 10", "Windows 10", "Windows 10, version 1709"]
|
||||||
ms.localizationpriority: high
|
ms.localizationpriority: high
|
||||||
@ -18,7 +18,7 @@ sections:
|
|||||||
- items:
|
- items:
|
||||||
- type: markdown
|
- type: markdown
|
||||||
text: "
|
text: "
|
||||||
See a list of known issues that have been resolved for Windows 10, version 1709 and Windows Server 1709 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
|
See a list of known issues that have been resolved for Windows 10, version 1709 and Windows Server, 1709 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
|
||||||
|
|
||||||
"
|
"
|
||||||
- items:
|
- items:
|
||||||
|
|||||||
@ -79,7 +79,6 @@ sections:
|
|||||||
text: "
|
text: "
|
||||||
<table border ='1'><tr bgcolor='#d4d7d8'><td width='55%'>Details</td><td width='15%'>Affected build</td><td width='15%'>Status</td><td width='15%'>History</td></tr>
|
<table border ='1'><tr bgcolor='#d4d7d8'><td width='55%'>Details</td><td width='15%'>Affected build</td><td width='15%'>Status</td><td width='15%'>History</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='158msgdesc'></div><b>Apps may stop working after selecting an audio output device other than the default</b><div>After installing <a href=\"https:\\\\support.microsoft.com\\en-us\\help\\4482887\" target=\"_blank\">KB4482887</a> on machines that have multiple audio devices, applications that provide advanced options for internal or external audio output devices may stop working unexpectedly. This issue occurs for users that select an audio output device different from the \"Default Audio Device\". Examples of applications that may stop working include: </div><div><br></div><ul><li>Windows Media Player </li><li>Realtek HD Audio Manager </li><li>Sound Blaster Control Panel </li></ul><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><br></div><div><strong>Workaround:</strong> As a temporary solution, select the \"Default Audio Device\" in the options provided by the application; please refer to the application's user manual for details. </div><div>For example, to set the <strong>Default Audio Device</strong> in Windows Media Player: </div><div><br></div><ol><li>Open Windows <strong>Media Player </strong>><strong> Tools </strong>><strong> Options </strong>><strong> Devices</strong>.</li><li>Select the device and choose <strong>Properties</strong>.</li><li>On the next dialog, from the drop-down menu under <strong>Select the Audio Device</strong>, choose <strong>Default Audio Device</strong> from the list.</li></ol><div> </div><div>You can then send audio from the application to the audio device you want in the per-application audio settings found under <strong>Settings </strong>><strong> System </strong>><strong> Sound </strong>><strong> App Volume and device preferences</strong>.</div><div><br></div><div><strong>Resolved:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/en-us/help/4490481\" target=\"_blank\">KB4490481</a>. </div><br><a href ='#158msg'>Back to top</a></td><td>OS Build 17763.348<br><br>March 01, 2019<br><a href ='https://support.microsoft.com/en-us/help/4482887' target='_blank'>KB4482887</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4490481' target='_blank'>KB4490481</a></td><td>Resolved:<br>April 02, 2019 10:00 AM PT<br><br>Opened:<br>March 01, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='158msgdesc'></div><b>Apps may stop working after selecting an audio output device other than the default</b><div>After installing <a href=\"https:\\\\support.microsoft.com\\en-us\\help\\4482887\" target=\"_blank\">KB4482887</a> on machines that have multiple audio devices, applications that provide advanced options for internal or external audio output devices may stop working unexpectedly. This issue occurs for users that select an audio output device different from the \"Default Audio Device\". Examples of applications that may stop working include: </div><div><br></div><ul><li>Windows Media Player </li><li>Realtek HD Audio Manager </li><li>Sound Blaster Control Panel </li></ul><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><br></div><div><strong>Workaround:</strong> As a temporary solution, select the \"Default Audio Device\" in the options provided by the application; please refer to the application's user manual for details. </div><div>For example, to set the <strong>Default Audio Device</strong> in Windows Media Player: </div><div><br></div><ol><li>Open Windows <strong>Media Player </strong>><strong> Tools </strong>><strong> Options </strong>><strong> Devices</strong>.</li><li>Select the device and choose <strong>Properties</strong>.</li><li>On the next dialog, from the drop-down menu under <strong>Select the Audio Device</strong>, choose <strong>Default Audio Device</strong> from the list.</li></ol><div> </div><div>You can then send audio from the application to the audio device you want in the per-application audio settings found under <strong>Settings </strong>><strong> System </strong>><strong> Sound </strong>><strong> App Volume and device preferences</strong>.</div><div><br></div><div><strong>Resolved:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/en-us/help/4490481\" target=\"_blank\">KB4490481</a>. </div><br><a href ='#158msg'>Back to top</a></td><td>OS Build 17763.348<br><br>March 01, 2019<br><a href ='https://support.microsoft.com/en-us/help/4482887' target='_blank'>KB4482887</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4490481' target='_blank'>KB4490481</a></td><td>Resolved:<br>April 02, 2019 10:00 AM PT<br><br>Opened:<br>March 01, 2019 10:00 AM PT</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='159msgdesc'></div><b>Global DNS outage affects Windows Update customers</b><div>Windows Update customers were affected by a network infrastructure event on January 29, 2019 (21:00 UTC), caused by an external DNS service provider's global outage. A software update to the external provider's DNS servers resulted in the distribution of corrupted DNS records that affected connectivity to the Windows Update service. The DNS records were restored by January 30, 2019 (00:10 UTC), and the majority of local Internet Service Providers (ISP) have refreshed their DNS servers and customer services have been restored. </div><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><br></div><div>While this was not an issue with Microsoft's services, we take any service disruption for our customers seriously. We will work with partners to better understand this so we can provide higher quality service in the future even across diverse global network providers. </div><div> </div><div>If you are still unable to connect to Windows Update services due to this problem, please contact your local ISP or network administrator. You can also refer to our new <a href=\"https://support.microsoft.com/en-us/help/4493784\" target=\"_blank\">KB4493784</a> for more information to determine if your network is affected, and to provide your local ISP or network administrator with additional information to assist you. </div><br><a href ='#159msg'>Back to top</a></td><td><br><br><br><a href ='' target='_blank'></a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>Resolved:<br>March 08, 2019 11:15 AM PT<br><br>Opened:<br>March 08, 2019 10:00 AM PT</td></tr>
|
|
||||||
</table>
|
</table>
|
||||||
"
|
"
|
||||||
|
|
||||||
@ -102,6 +101,7 @@ sections:
|
|||||||
<table border ='1'><tr bgcolor='#d4d7d8'><td width='55%'>Details</td><td width='15%'>Affected build</td><td width='15%'>Status</td><td width='15%'>History</td></tr>
|
<table border ='1'><tr bgcolor='#d4d7d8'><td width='55%'>Details</td><td width='15%'>Affected build</td><td width='15%'>Status</td><td width='15%'>History</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='240msgdesc'></div><b>Internet Explorer 11 authentication issue with multiple concurrent logons</b><div>After installing the February 12, 2019 update (<a href=\"https://support.microsoft.com/en-us/help/4487044\" target=\"_blank\">KB4487044</a>), Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to: </div><div> </div><ul><li>Cache size and location show zero or empty. </li><li>Keyboard shortcuts may not work properly. </li><li>Webpages may intermittently fail to load or render correctly. </li><li>Issues with credential prompts. </li><li>Issues when downloading files. </li></ul><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1</li></ul><div> </div><div><strong>Resolved</strong>: This issue was resolved in <a href=\"https://support.microsoft.com/en-us/help/4493509\" target=\"_blank\">KB4493509</a>. </div><br><a href ='#240msg'>Back to top</a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/en-us/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493509' target='_blank'>KB4493509</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>January 08, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='240msgdesc'></div><b>Internet Explorer 11 authentication issue with multiple concurrent logons</b><div>After installing the February 12, 2019 update (<a href=\"https://support.microsoft.com/en-us/help/4487044\" target=\"_blank\">KB4487044</a>), Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to: </div><div> </div><ul><li>Cache size and location show zero or empty. </li><li>Keyboard shortcuts may not work properly. </li><li>Webpages may intermittently fail to load or render correctly. </li><li>Issues with credential prompts. </li><li>Issues when downloading files. </li></ul><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1</li></ul><div> </div><div><strong>Resolved</strong>: This issue was resolved in <a href=\"https://support.microsoft.com/en-us/help/4493509\" target=\"_blank\">KB4493509</a>. </div><br><a href ='#240msg'>Back to top</a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/en-us/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493509' target='_blank'>KB4493509</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>January 08, 2019 10:00 AM PT</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='219msgdesc'></div><b>MSXML6 may cause applications to stop responding </b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4480116\" target=\"_blank\">KB4480116</a>, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as <strong>appendChild()</strong>, <strong>insertBefore()</strong>, and <strong>moveNode()</strong>.</div><div> </div><div>The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings. </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 1507; Windows 8.1</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</li></ul><div><br></div><div><strong>Resolved:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/en-us/help/4493509\" target=\"_blank\">KB4493509</a>. </div><br><a href ='#219msg'>Back to top</a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/en-us/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493509' target='_blank'>KB4493509</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>January 08, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='219msgdesc'></div><b>MSXML6 may cause applications to stop responding </b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4480116\" target=\"_blank\">KB4480116</a>, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as <strong>appendChild()</strong>, <strong>insertBefore()</strong>, and <strong>moveNode()</strong>.</div><div> </div><div>The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings. </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 1507; Windows 8.1</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</li></ul><div><br></div><div><strong>Resolved:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/en-us/help/4493509\" target=\"_blank\">KB4493509</a>. </div><br><a href ='#219msg'>Back to top</a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/en-us/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493509' target='_blank'>KB4493509</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>January 08, 2019 10:00 AM PT</td></tr>
|
||||||
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='159msgdesc'></div><b>Global DNS outage affects Windows Update customers</b><div>Windows Update customers were affected by a network infrastructure event on January 29, 2019 (21:00 UTC), caused by an external DNS service provider's global outage. A software update to the external provider's DNS servers resulted in the distribution of corrupted DNS records that affected connectivity to the Windows Update service. The DNS records were restored by January 30, 2019 (00:10 UTC), and the majority of local Internet Service Providers (ISP) have refreshed their DNS servers and customer services have been restored. </div><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><br></div><div>While this was not an issue with Microsoft's services, we take any service disruption for our customers seriously. We will work with partners to better understand this so we can provide higher quality service in the future even across diverse global network providers. </div><div> </div><div>If you are still unable to connect to Windows Update services due to this problem, please contact your local ISP or network administrator. You can also refer to our new <a href=\"https://support.microsoft.com/en-us/help/4493784\" target=\"_blank\">KB4493784</a> for more information to determine if your network is affected, and to provide your local ISP or network administrator with additional information to assist you. </div><br><a href ='#159msg'>Back to top</a></td><td><br><br><br><a href ='' target='_blank'></a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>Resolved:<br>March 08, 2019 11:15 AM PT<br><br>Opened:<br>January 29, 2019 02:00 PM PT</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='147msgdesc'></div><b>Webpages become unresponsive in Microsoft Edge</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4480116\" target=\"_blank\">KB4480116</a>, some Microsoft Edge users report that they:</div><div><br></div><ul><li>Cannot load webpages using a local IP address. </li><li>Cannot load webpages on the Internet using a VPN connection.</li></ul><div><br></div><div>Browsing fails or the webpage may become unresponsive.</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</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709</li></ul><div><br></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/en-us/help/4487044\" target=\"_blank\">KB4487044</a>. </div><br><a href ='#147msg'>Back to top</a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/en-us/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4487044' target='_blank'>KB4487044</a></td><td>Resolved:<br>February 12, 2019 10:00 AM PT<br><br>Opened:<br>January 08, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='147msgdesc'></div><b>Webpages become unresponsive in Microsoft Edge</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4480116\" target=\"_blank\">KB4480116</a>, some Microsoft Edge users report that they:</div><div><br></div><ul><li>Cannot load webpages using a local IP address. </li><li>Cannot load webpages on the Internet using a VPN connection.</li></ul><div><br></div><div>Browsing fails or the webpage may become unresponsive.</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</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709</li></ul><div><br></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/en-us/help/4487044\" target=\"_blank\">KB4487044</a>. </div><br><a href ='#147msg'>Back to top</a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/en-us/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4487044' target='_blank'>KB4487044</a></td><td>Resolved:<br>February 12, 2019 10:00 AM PT<br><br>Opened:<br>January 08, 2019 10:00 AM PT</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='225msgdesc'></div><b>Unable to access hotspots with third-party applications</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4480116\" target=\"_blank\">KB4480116</a>, third-party applications may have difficulty authenticating hotspots. </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 1507; Windows 8.1</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</li></ul><div><br></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/en-us/help/4476976\" target=\"_blank\">KB4476976</a>. </div><br><a href ='#225msg'>Back to top</a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/en-us/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4476976' target='_blank'>KB4476976</a></td><td>Resolved:<br>January 22, 2019 02:00 PM PT<br><br>Opened:<br>January 08, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='225msgdesc'></div><b>Unable to access hotspots with third-party applications</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4480116\" target=\"_blank\">KB4480116</a>, third-party applications may have difficulty authenticating hotspots. </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 1507; Windows 8.1</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</li></ul><div><br></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/en-us/help/4476976\" target=\"_blank\">KB4476976</a>. </div><br><a href ='#225msg'>Back to top</a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/en-us/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4476976' target='_blank'>KB4476976</a></td><td>Resolved:<br>January 22, 2019 02:00 PM PT<br><br>Opened:<br>January 08, 2019 10:00 AM PT</td></tr>
|
||||||
</table>
|
</table>
|
||||||
|
|||||||
@ -85,7 +85,7 @@ sections:
|
|||||||
<table border ='1'><tr bgcolor='#d4d7d8'><td width='55%'>Details</td><td width='15%'>Affected build</td><td width='15%'>Status</td><td width='15%'>History</td></tr>
|
<table border ='1'><tr bgcolor='#d4d7d8'><td width='55%'>Details</td><td width='15%'>Affected build</td><td width='15%'>Status</td><td width='15%'>History</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='235msgdesc'></div><b>End-user-defined characters (EUDC) cause blue screen at startup</b><div>If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.</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</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div><br></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/en-us/help/4493470\" target=\"_blank\">KB4493470</a>.</div><br><a href ='#235msg'>Back to top</a></td><td>OS Build 14393.2879<br><br>March 19, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489889' target='_blank'>KB4489889</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493470' target='_blank'>KB4493470</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>March 19, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='235msgdesc'></div><b>End-user-defined characters (EUDC) cause blue screen at startup</b><div>If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.</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</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div><br></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/en-us/help/4493470\" target=\"_blank\">KB4493470</a>.</div><br><a href ='#235msg'>Back to top</a></td><td>OS Build 14393.2879<br><br>March 19, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489889' target='_blank'>KB4489889</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493470' target='_blank'>KB4493470</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>March 19, 2019 10:00 AM PT</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='191msgdesc'></div><b>Custom URI schemes may not start corresponding application</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4489882\" target=\"_blank\">KB4489882</a>, Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer.</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 1507; Windows 8.1; Windows 7, Service Pack 1 </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 2008 R2 SP1</li></ul><div><br></div><div><strong>Workaround:</strong> Right-click the URL link to open it in a new window or tab, or enable Protected Mode in Internet Explorer for local intranet and trusted sites</div><div><br></div><ol><li>Go to <strong>Tools</strong> > <strong>Internet options</strong> > <strong>Security</strong>.</li><li>Within <strong>Select a zone to view or change security settings</strong>, select <strong>Local intranet</strong> and then select <strong>Enable Protected Mode</strong>.</li><li>Select <strong>Trusted sites</strong> and then select <strong>Enable Protected Mode</strong>.</li><li>Select <strong>OK</strong>.</li></ol><div><br></div><div>You must restart the browser after making these changes.</div><div><br></div><div><strong>Next steps:</strong> Microsoft is working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#191msg'>Back to top</a></td><td>OS Build 14393.2848<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489882' target='_blank'>KB4489882</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>March 19, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='191msgdesc'></div><b>Custom URI schemes may not start corresponding application</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4489882\" target=\"_blank\">KB4489882</a>, Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer.</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 1507; Windows 8.1; Windows 7, Service Pack 1 </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 2008 R2 SP1</li></ul><div><br></div><div><strong>Workaround:</strong> Right-click the URL link to open it in a new window or tab, or enable Protected Mode in Internet Explorer for local intranet and trusted sites</div><div><br></div><ol><li>Go to <strong>Tools</strong> > <strong>Internet options</strong> > <strong>Security</strong>.</li><li>Within <strong>Select a zone to view or change security settings</strong>, select <strong>Local intranet</strong> and then select <strong>Enable Protected Mode</strong>.</li><li>Select <strong>Trusted sites</strong> and then select <strong>Enable Protected Mode</strong>.</li><li>Select <strong>OK</strong>.</li></ol><div><br></div><div>You must restart the browser after making these changes.</div><div><br></div><div><strong>Next steps:</strong> Microsoft is working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#191msg'>Back to top</a></td><td>OS Build 14393.2848<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489882' target='_blank'>KB4489882</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>March 19, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='238msgdesc'></div><b>Issue using PXE to start a device from WDS</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4489882\" target=\"_blank\">KB4489882</a>, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.</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 Enterprise LTSC 2016; Windows 8.1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2</li></ul><div><br></div><div><strong>Workaround:</strong> To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:</div><div><br></div><div><strong>Option 1:</strong></div><div>Open an Administrator Command prompt and type the following:</div><div><br></div><div>Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No</div><div><br></div><div><strong>Option 2:</strong></div><div>Use the Windows Deployment Services UI to make the following adjustment:</div><div><br></div><div>1. Open Windows Deployment Services from Windows Administrative Tools.</div><div>2. Expand Servers and right-click a WDS server.</div><div>3. Open its properties and clear the <strong>Enable Variable Window Extension</strong> box on the TFTP tab.</div><div><br></div><div><strong>Option 3:</strong></div><div>Set the following registry value to 0:</div><div><br></div><div>HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension</div><div><br></div><div>Restart the WDSServer service after disabling the Variable Window Extension.</div><div><br></div><div><strong>Next steps:</strong> Microsoft is working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#238msg'>Back to top</a></td><td>OS Build 14393.2848<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489882' target='_blank'>KB4489882</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>March 19, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='238msgdesc'></div><b>Issue using PXE to start a device from WDS</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4489882\" target=\"_blank\">KB4489882</a>, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.</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 Enterprise LTSC 2016; Windows 8.1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2</li></ul><div><br></div><div><strong>Workaround:</strong> To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:</div><div><br></div><div><strong>Option 1:</strong></div><div>Open an Administrator Command prompt and type the following:</div><div><br></div><div><pre class=\"ql-syntax\" spellcheck=\"false\">Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No</pre></div><div><br></div><div><strong>Option 2:</strong></div><div>Use the Windows Deployment Services UI to make the following adjustment:</div><div><br></div><div>1. Open Windows Deployment Services from Windows Administrative Tools.</div><div>2. Expand Servers and right-click a WDS server.</div><div>3. Open its properties and clear the <strong>Enable Variable Window Extension</strong> box on the TFTP tab.</div><div><br></div><div><strong>Option 3:</strong></div><div>Set the following registry value to 0:</div><div><br></div><div>HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension</div><div><br></div><div>Restart the WDSServer service after disabling the Variable Window Extension.</div><div><br></div><div><strong>Next steps:</strong> Microsoft is working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#238msg'>Back to top</a></td><td>OS Build 14393.2848<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489882' target='_blank'>KB4489882</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>March 19, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
||||||
</table>
|
</table>
|
||||||
"
|
"
|
||||||
|
|
||||||
|
|||||||
@ -1,10 +1,10 @@
|
|||||||
### YamlMime:YamlDocument
|
### YamlMime:YamlDocument
|
||||||
|
|
||||||
documentType: LandingData
|
documentType: LandingData
|
||||||
title: Windows 10, version 1709 and Windows Server 1709
|
title: Windows 10, version 1709 and Windows Server, 1709
|
||||||
metadata:
|
metadata:
|
||||||
document_id:
|
document_id:
|
||||||
title: Windows 10, version 1709 and Windows Server 1709
|
title: Windows 10, version 1709 and Windows Server, 1709
|
||||||
description: View annoucements and review known issues and fixes for Windows 10 version 1709 and Windows Server 1709
|
description: View annoucements and review known issues and fixes for Windows 10 version 1709 and Windows Server 1709
|
||||||
keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
|
keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
|
||||||
ms.localizationpriority: high
|
ms.localizationpriority: high
|
||||||
@ -18,7 +18,7 @@ sections:
|
|||||||
- items:
|
- items:
|
||||||
- type: markdown
|
- type: markdown
|
||||||
text: "
|
text: "
|
||||||
Find information on known issues for Windows 10, version 1709 and Windows Server 1709. 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 1709 and Windows Server, 1709. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
|
||||||
|
|
||||||
"
|
"
|
||||||
|
|
||||||
|
|||||||
@ -83,7 +83,7 @@ sections:
|
|||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='232msgdesc'></div><b>End-user-defined characters (EUDC) may cause blue screen at startup</b><div>If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions. </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</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div> </div><div><strong>Resolution</strong>: This issue was resolved in <a href=\"https://support.microsoft.com/help/4493464\" target=\"_blank\">KB4493464</a>. </div><br><a href ='#232msg'>Back to top</a></td><td>OS Build 17134.677<br><br>March 19, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489894' target='_blank'>KB4489894</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493464' target='_blank'>KB4493464</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>March 19, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='232msgdesc'></div><b>End-user-defined characters (EUDC) may cause blue screen at startup</b><div>If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions. </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</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div> </div><div><strong>Resolution</strong>: This issue was resolved in <a href=\"https://support.microsoft.com/help/4493464\" target=\"_blank\">KB4493464</a>. </div><br><a href ='#232msg'>Back to top</a></td><td>OS Build 17134.677<br><br>March 19, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489894' target='_blank'>KB4489894</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493464' target='_blank'>KB4493464</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>March 19, 2019 10:00 AM PT</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='144msgdesc'></div><b>Stop error when attempting to start SSH from WSL</b><div>After applying <a href=\"https://support.microsoft.com/help/4489868\" target=\"_blank\">KB4489868</a>, a stop error occurs when attempting to start the Secure Shell (SSH) client program from Windows Subsystem for Linux (WSL) with agent forwarding enabled using a command line switch (ssh -A) or a configuration setting.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1709</li><li>Server: Windows Server, version 1803; Windows Server, version 1709</li></ul><div><br></div><div><strong>Resolution</strong>: This issue was resolved in <a href=\"https://support.microsoft.com/help/4493464\" target=\"_blank\">KB4493464</a>.</div><br><a href ='#144msg'>Back to top</a></td><td>OS Build 17134.648<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489868' target='_blank'>KB4489868</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493464' target='_blank'>KB4493464</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='144msgdesc'></div><b>Stop error when attempting to start SSH from WSL</b><div>After applying <a href=\"https://support.microsoft.com/help/4489868\" target=\"_blank\">KB4489868</a>, a stop error occurs when attempting to start the Secure Shell (SSH) client program from Windows Subsystem for Linux (WSL) with agent forwarding enabled using a command line switch (ssh -A) or a configuration setting.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1709</li><li>Server: Windows Server, version 1803; Windows Server, version 1709</li></ul><div><br></div><div><strong>Resolution</strong>: This issue was resolved in <a href=\"https://support.microsoft.com/help/4493464\" target=\"_blank\">KB4493464</a>.</div><br><a href ='#144msg'>Back to top</a></td><td>OS Build 17134.648<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489868' target='_blank'>KB4489868</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493464' target='_blank'>KB4493464</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='188msgdesc'></div><b>Custom URI schemes may not start corresponding application</b><div>After installing <a href=\"https://support.microsoft.com/help/4489868\" target=\"_blank\">KB4489868</a>, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer. </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 1507; Windows 8.1; Windows 7, Service Pack 1 </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 2008 R2 SP1</li></ul><div><br></div><div><strong>Workaround:</strong> Right-click the URL link to open it in a new window or tab, or enable Protected Mode in Internet Explorer for local intranet and trusted sites </div><div> </div><ol><li>Go to <strong>Tools </strong>> <strong>Internet options </strong>> <strong>Security</strong> </li><li>Within <strong>Select a zone to view or change security settings</strong>, select <strong>Local intranet </strong>and then select <strong>Enable Protected Mode.</strong></li><li>Select <strong>Trusted sites </strong>and then select <strong>Enable Protected Mode</strong>. </li><li>Select <strong>OK</strong>. </li></ol><div> </div><div>You must restart the browser after making these changes. </div><div> </div><div><strong>Next steps:</strong> Microsoft is working on a resolution and will provide an update in an upcoming release. </div><br><a href ='#188msg'>Back to top</a></td><td>OS Build 17134.648<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489868' target='_blank'>KB4489868</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>March 19, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='188msgdesc'></div><b>Custom URI schemes may not start corresponding application</b><div>After installing <a href=\"https://support.microsoft.com/help/4489868\" target=\"_blank\">KB4489868</a>, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer. </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 1507; Windows 8.1; Windows 7, Service Pack 1 </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 2008 R2 SP1</li></ul><div><br></div><div><strong>Workaround:</strong> Right-click the URL link to open it in a new window or tab, or enable Protected Mode in Internet Explorer for local intranet and trusted sites </div><div> </div><ol><li>Go to <strong>Tools </strong>> <strong>Internet options </strong>> <strong>Security</strong> </li><li>Within <strong>Select a zone to view or change security settings</strong>, select <strong>Local intranet </strong>and then select <strong>Enable Protected Mode.</strong></li><li>Select <strong>Trusted sites </strong>and then select <strong>Enable Protected Mode</strong>. </li><li>Select <strong>OK</strong>. </li></ol><div> </div><div>You must restart the browser after making these changes. </div><div> </div><div><strong>Next steps:</strong> Microsoft is working on a resolution and will provide an update in an upcoming release. </div><br><a href ='#188msg'>Back to top</a></td><td>OS Build 17134.648<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489868' target='_blank'>KB4489868</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>March 19, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='237msgdesc'></div><b>Issue using PXE to start a device from WDS</b><div>After installing <a href=\"https://support.microsoft.com/help/4489868\" target=\"_blank\">KB4489868</a>, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension. </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 Enterprise LTSC 2016; Windows 8.1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2</li></ul><div><br></div><div><strong>Workaround:</strong> To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: </div><div> </div><div><strong>Option 1:</strong> </div><div>Open an Administrator Command prompt and type the following: </div><div> </div><div>Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No </div><div> </div><div><strong>Option 2:</strong> </div><div>Use the Windows Deployment Services UI to make the following adjustment: </div><div> </div><ol><li>Open Windows Deployment Services from Windows Administrative Tools. </li><li>Expand Servers and right-click a WDS server. </li><li>Open its properties and clear the <strong>Enable Variable Window Extension </strong>box on the TFTP tab. </li></ol><div> </div><div><strong>Option 3:</strong> </div><div>Set the following registry value to 0: </div><div> </div><div>HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension </div><div> </div><div>Restart the WDSServer service after disabling the Variable Window Extension. </div><div> </div><div><strong>Next steps:</strong> Microsoft is working on a resolution and will provide an update in an upcoming release. </div><br><a href ='#237msg'>Back to top</a></td><td>OS Build 17134.648<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489868' target='_blank'>KB4489868</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>March 19, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='237msgdesc'></div><b>Issue using PXE to start a device from WDS</b><div>After installing <a href=\"https://support.microsoft.com/help/4489868\" target=\"_blank\">KB4489868</a>, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension. </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 Enterprise LTSC 2016; Windows 8.1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2</li></ul><div><br></div><div><strong>Workaround:</strong> To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: </div><div> </div><div><strong>Option 1:</strong> </div><div>Open an Administrator Command prompt and type the following: </div><div> </div><div><pre class=\"ql-syntax\" spellcheck=\"false\">Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No</pre></div><div> </div><div><strong>Option 2:</strong> </div><div>Use the Windows Deployment Services UI to make the following adjustment: </div><div> </div><ol><li>Open Windows Deployment Services from Windows Administrative Tools. </li><li>Expand Servers and right-click a WDS server. </li><li>Open its properties and clear the?<strong>Enable Variable Window Extension?</strong>box on the TFTP tab. </li></ol><div> </div><div><strong>Option 3:</strong> </div><div>Set the following registry value to 0: </div><div> </div><div>HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension </div><div> </div><div>Restart the WDSServer service after disabling the Variable Window Extension. </div><div> </div><div><strong>Next steps:</strong> Microsoft is working on a resolution and will provide an update in an upcoming release. </div><br><a href ='#237msg'>Back to top</a></td><td>OS Build 17134.648<br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489868' target='_blank'>KB4489868</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>March 19, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
||||||
</table>
|
</table>
|
||||||
"
|
"
|
||||||
|
|
||||||
|
|||||||
@ -99,7 +99,7 @@ sections:
|
|||||||
text: "
|
text: "
|
||||||
<table border ='1'><tr bgcolor='#d4d7d8'><td width='55%'>Details</td><td width='15%'>Affected build</td><td width='15%'>Status</td><td width='15%'>History</td></tr>
|
<table border ='1'><tr bgcolor='#d4d7d8'><td width='55%'>Details</td><td width='15%'>Affected build</td><td width='15%'>Status</td><td width='15%'>History</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='276msgdesc'></div><b>Custom URI schemes may not start corresponding application</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4489881\" target=\"_blank\">KB4489881</a>, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer.</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 1507; Windows 8.1; Windows 7, Service Pack 1 </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 2008 R2 SP1 </li></ul><div><br></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/en-us/help/4493446\" target=\"_blank\">KB4493446</a>.</div><br><a href ='#276msg'>Back to top</a></td><td><br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489881' target='_blank'>KB4489881</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493446' target='_blank'>KB4493446</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='276msgdesc'></div><b>Custom URI schemes may not start corresponding application</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4489881\" target=\"_blank\">KB4489881</a>, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer.</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 1507; Windows 8.1; Windows 7, Service Pack 1 </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 2008 R2 SP1 </li></ul><div><br></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/en-us/help/4493446\" target=\"_blank\">KB4493446</a>.</div><br><a href ='#276msg'>Back to top</a></td><td><br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489881' target='_blank'>KB4489881</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/en-us/help/4493446' target='_blank'>KB4493446</a></td><td>Resolved:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
||||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='279msgdesc'></div><b>Issue using PXE to start a device from WDS</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4489881\" target=\"_blank\">KB4489881</a>, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.</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 Enterprise LTSC 2016; Windows 8.1 </li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2 </li></ul><div><br></div><div><strong>Workaround:</strong> To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:</div><div><br></div><div><strong>Option 1:</strong></div><div>Open an Administrator Command prompt and type the following:</div><div><br></div><div>Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No</div><div><br></div><div><strong>Option 2:</strong></div><div>Use the Windows Deployment Services UI to make the following adjustment:</div><div><br></div><div>1. Open Windows Deployment Services from Windows Administrative Tools.</div><div>2. Expand Servers and right-click a WDS server.</div><div>3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.</div><div><br></div><div><strong>Option 3:</strong></div><div>Set the following registry value to 0:</div><div><br></div><div>HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension</div><div><br></div><div>Restart the WDSServer service after disabling the Variable Window Extension.</div><div><br></div><div><strong>Next steps:</strong> Microsoft is working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#279msg'>Back to top</a></td><td><br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489881' target='_blank'>KB4489881</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='279msgdesc'></div><b>Issue using PXE to start a device from WDS</b><div>After installing <a href=\"https://support.microsoft.com/en-us/help/4489881\" target=\"_blank\">KB4489881</a>, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.</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 Enterprise LTSC 2016; Windows 8.1 </li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2 </li></ul><div><br></div><div><strong>Workaround:</strong> To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:</div><div><br></div><div><strong>Option 1:</strong></div><div>Open an Administrator Command prompt and type the following:</div><div><br></div><div><pre class=\"ql-syntax\" spellcheck=\"false\">Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No</pre></div><div><br></div><div><strong>Option 2:</strong></div><div>Use the Windows Deployment Services UI to make the following adjustment:</div><div><br></div><div>1. Open Windows Deployment Services from Windows Administrative Tools.</div><div>2. Expand Servers and right-click a WDS server.</div><div>3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.</div><div><br></div><div><strong>Option 3:</strong></div><div>Set the following registry value to 0:</div><div><br></div><div>HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension</div><div><br></div><div>Restart the WDSServer service after disabling the Variable Window Extension.</div><div><br></div><div><strong>Next steps:</strong> Microsoft is working on a resolution and will provide an update in an upcoming release.</div><br><a href ='#279msg'>Back to top</a></td><td><br><br>March 12, 2019<br><a href ='https://support.microsoft.com/en-us/help/4489881' target='_blank'>KB4489881</a></td><td>Mitigated<br><a href = '' target='_blank'></a></td><td>Last updated:<br>April 09, 2019 10:00 AM PT<br><br>Opened:<br>March 12, 2019 10:00 AM PT</td></tr>
|
||||||
</table>
|
</table>
|
||||||
"
|
"
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user