diff --git a/windows/release-information/resolved-issues-windows-10-1709.yml b/windows/release-information/resolved-issues-windows-10-1709.yml
index dfd804d65b..1fbb647b06 100644
--- a/windows/release-information/resolved-issues-windows-10-1709.yml
+++ b/windows/release-information/resolved-issues-windows-10-1709.yml
@@ -1,10 +1,10 @@
### YamlMime:YamlDocument
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:
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
keywords: ["Resolved issues in Windows 10", "Windows 10", "Windows 10, version 1709"]
ms.localizationpriority: high
@@ -18,7 +18,7 @@ sections:
- items:
- type: markdown
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:
diff --git a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml
index e289521015..98a4a59bda 100644
--- a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml
+++ b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml
@@ -79,7 +79,6 @@ sections:
text: "
| Details | Affected build | Status | History |
Apps may stop working after selecting an audio output device other than the defaultAfter installing KB4482887 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:
- Windows Media Player
- Realtek HD Audio Manager
- Sound Blaster Control Panel
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Workaround: 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. For example, to set the Default Audio Device in Windows Media Player:
- Open Windows Media Player > Tools > Options > Devices.
- Select the device and choose Properties.
- On the next dialog, from the drop-down menu under Select the Audio Device, choose Default Audio Device from the list.
You can then send audio from the application to the audio device you want in the per-application audio settings found under Settings > System > Sound > App Volume and device preferences.
Resolved: This issue was resolved in KB4490481.
Back to top | OS Build 17763.348
March 01, 2019
KB4482887 | Resolved
KB4490481 | Resolved:
April 02, 2019 10:00 AM PT
Opened:
March 01, 2019 10:00 AM PT |
- | Global DNS outage affects Windows Update customers 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. Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
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. 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 KB4493784 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.
Back to top |
| Resolved
| Resolved:
March 08, 2019 11:15 AM PT
Opened:
March 08, 2019 10:00 AM PT |
"
@@ -102,6 +101,7 @@ sections:
| Details | Affected build | Status | History |
Internet Explorer 11 authentication issue with multiple concurrent logonsAfter installing the February 12, 2019 update ( KB4487044), 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: - Cache size and location show zero or empty.
- Keyboard shortcuts may not work properly.
- Webpages may intermittently fail to load or render correctly.
- Issues with credential prompts.
- Issues when downloading files.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7, Service Pack 1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolved: This issue was resolved in KB4493509.
Back to top | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4493509 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
MSXML6 may cause applications to stop responding After installing KB4480116, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Affected platforms: - 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
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolved: This issue was resolved in KB4493509.
Back to top | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4493509 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
+ | Global DNS outage affects Windows Update customers 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. Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
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. 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 KB4493784 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.
Back to top |
| Resolved
| Resolved:
March 08, 2019 11:15 AM PT
Opened:
January 29, 2019 02:00 PM PT |
Webpages become unresponsive in Microsoft EdgeAfter installing KB4480116, some Microsoft Edge users report that they:
- Cannot load webpages using a local IP address.
- Cannot load webpages on the Internet using a VPN connection.
Browsing fails or the webpage may become unresponsive.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue is resolved in KB4487044.
Back to top | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4487044 | Resolved:
February 12, 2019 10:00 AM PT
Opened:
January 08, 2019 10:00 AM PT |
Unable to access hotspots with third-party applicationsAfter installing KB4480116, third-party applications may have difficulty authenticating hotspots.
Affected platforms: - 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
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2
Resolution: This issue is resolved in KB4476976.
Back to top | OS Build 17763.253
January 08, 2019
KB4480116 | Resolved
KB4476976 | Resolved:
January 22, 2019 02:00 PM PT
Opened:
January 08, 2019 10:00 AM PT |
diff --git a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml
index aede053e66..dd674ef62c 100644
--- a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml
+++ b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml
@@ -85,7 +85,7 @@ sections:
| Details | Affected build | Status | History |
| End-user-defined characters (EUDC) cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - 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
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue was resolved in KB4493470.
Back to top | OS Build 14393.2879
March 19, 2019
KB4489889 | Resolved
KB4493470 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 19, 2019 10:00 AM PT |
Custom URI schemes may not start corresponding applicationAfter installing KB4489882, Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer.
Affected platforms: - 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
- 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
Workaround: 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
- Go to Tools > Internet options > Security.
- Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
- Select Trusted sites and then select Enable Protected Mode.
- Select OK.
You must restart the browser after making these changes.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | OS Build 14393.2848
March 12, 2019
KB4489882 | Mitigated
| Last updated:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
- Issue using PXE to start a device from WDSAfter installing KB4489882, 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.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2
Workaround: To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:
Option 1: Open an Administrator Command prompt and type the following:
Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No
Option 2: Use the Windows Deployment Services UI to make the following adjustment:
1. Open Windows Deployment Services from Windows Administrative Tools. 2. Expand Servers and right-click a WDS server. 3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.
Option 3: Set the following registry value to 0:
HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension
Restart the WDSServer service after disabling the Variable Window Extension.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | OS Build 14393.2848
March 12, 2019
KB4489882 | Mitigated
| Last updated:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDSAfter installing KB4489882, 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.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2
Workaround: To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:
Option 1: Open an Administrator Command prompt and type the following:
Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No
Option 2: Use the Windows Deployment Services UI to make the following adjustment:
1. Open Windows Deployment Services from Windows Administrative Tools. 2. Expand Servers and right-click a WDS server. 3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.
Option 3: Set the following registry value to 0:
HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension
Restart the WDSServer service after disabling the Variable Window Extension.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | OS Build 14393.2848
March 12, 2019
KB4489882 | Mitigated
| Last updated:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
"
diff --git a/windows/release-information/status-windows-10-1709.yml b/windows/release-information/status-windows-10-1709.yml
index a9e04fff1a..45156027be 100644
--- a/windows/release-information/status-windows-10-1709.yml
+++ b/windows/release-information/status-windows-10-1709.yml
@@ -1,10 +1,10 @@
### YamlMime:YamlDocument
documentType: LandingData
-title: Windows 10, version 1709 and Windows Server 1709
+title: Windows 10, version 1709 and Windows Server, 1709
metadata:
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
keywords: Windows 10, issues, fixes, announcements, Windows Server, advisories
ms.localizationpriority: high
@@ -18,7 +18,7 @@ sections:
- items:
- type: markdown
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).
"
diff --git a/windows/release-information/status-windows-10-1803.yml b/windows/release-information/status-windows-10-1803.yml
index 6ccbb189e7..0fbe6c4c1d 100644
--- a/windows/release-information/status-windows-10-1803.yml
+++ b/windows/release-information/status-windows-10-1803.yml
@@ -83,7 +83,7 @@ sections:
| End-user-defined characters (EUDC) may cause blue screen at startup If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup. This is not a common setting in non-Asian regions.
Affected platforms: - 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
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue was resolved in KB4493464.
Back to top | OS Build 17134.677
March 19, 2019
KB4489894 | Resolved
KB4493464 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 19, 2019 10:00 AM PT |
Stop error when attempting to start SSH from WSLAfter applying KB4489868, 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.
Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1709
- Server: Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue was resolved in KB4493464.
Back to top | OS Build 17134.648
March 12, 2019
KB4489868 | Resolved
KB4493464 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
Custom URI schemes may not start corresponding applicationAfter installing KB4489868, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer.
Affected platforms: - 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
- 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
Workaround: 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 - Go to Tools > Internet options > Security
- Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
- Select Trusted sites and then select Enable Protected Mode.
- Select OK.
You must restart the browser after making these changes. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | OS Build 17134.648
March 12, 2019
KB4489868 | Mitigated
| Last updated:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
- Issue using PXE to start a device from WDSAfter installing KB4489868, 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.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2
Workaround: To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI to make the following adjustment: - Open Windows Deployment Services from Windows Administrative Tools.
- Expand Servers and right-click a WDS server.
- Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.
Option 3: Set the following registry value to 0: HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension Restart the WDSServer service after disabling the Variable Window Extension. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | OS Build 17134.648
March 12, 2019
KB4489868 | Mitigated
| Last updated:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDSAfter installing KB4489868, 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.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2
Workaround: To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options: Option 1: Open an Administrator Command prompt and type the following: Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No Option 2: Use the Windows Deployment Services UI to make the following adjustment: - Open Windows Deployment Services from Windows Administrative Tools.
- Expand Servers and right-click a WDS server.
- Open its properties and clear the?Enable Variable Window Extension?box on the TFTP tab.
Option 3: Set the following registry value to 0: HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension Restart the WDSServer service after disabling the Variable Window Extension. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top | OS Build 17134.648
March 12, 2019
KB4489868 | Mitigated
| Last updated:
March 19, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
"
diff --git a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml
index d72f50f64c..da35d46652 100644
--- a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml
+++ b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml
@@ -99,7 +99,7 @@ sections:
text: "
| Details | Affected build | Status | History |
Custom URI schemes may not start corresponding applicationAfter installing KB4489881, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer.
Affected platforms: - 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
- 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
Resolution: This issue is resolved in KB4493446.
Back to top |
March 12, 2019
KB4489881 | Resolved
KB4493446 | Resolved:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
- Issue using PXE to start a device from WDSAfter installing KB4489881, 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.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2
Workaround: To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:
Option 1: Open an Administrator Command prompt and type the following:
Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No
Option 2: Use the Windows Deployment Services UI to make the following adjustment:
1. Open Windows Deployment Services from Windows Administrative Tools. 2. Expand Servers and right-click a WDS server. 3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.
Option 3: Set the following registry value to 0:
HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension
Restart the WDSServer service after disabling the Variable Window Extension.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top |
March 12, 2019
KB4489881 | Mitigated
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
+ Issue using PXE to start a device from WDSAfter installing KB4489881, 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.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 8.1
- Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2
Workaround: To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:
Option 1: Open an Administrator Command prompt and type the following:
Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No
Option 2: Use the Windows Deployment Services UI to make the following adjustment:
1. Open Windows Deployment Services from Windows Administrative Tools. 2. Expand Servers and right-click a WDS server. 3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.
Option 3: Set the following registry value to 0:
HKLM\\System\\CurrentControlSet\\Services\\WDSServer\\Providers\\WDSTFTP\\EnableVariableWindowExtension
Restart the WDSServer service after disabling the Variable Window Extension.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Back to top |
March 12, 2019
KB4489881 | Mitigated
| Last updated:
April 09, 2019 10:00 AM PT
Opened:
March 12, 2019 10:00 AM PT |
"