From 56f35abcbef06b3ebe52e50295e34aab5fa14c3b Mon Sep 17 00:00:00 2001 From: "Nisha Mittal (Wipro Ltd.)" Date: Mon, 22 Apr 2019 16:24:09 -0700 Subject: [PATCH] Updates --- .../resolved-issues-windows-10-1703.yml | 4 ++-- .../resolved-issues-windows-10-1803.yml | 4 ++-- ...s-windows-10-1809-and-windows-server-2019.yml | 14 ++++++++++++++ ...s-windows-10-1607-and-windows-server-2016.yml | 16 ++++++++-------- .../status-windows-10-1703.yml | 4 ++-- .../status-windows-10-1803.yml | 4 ++-- ...s-windows-10-1809-and-windows-server-2019.yml | 16 +++++----------- 7 files changed, 35 insertions(+), 27 deletions(-) diff --git a/windows/release-information/resolved-issues-windows-10-1703.yml b/windows/release-information/resolved-issues-windows-10-1703.yml index 85791909af..6537ecddd7 100644 --- a/windows/release-information/resolved-issues-windows-10-1703.yml +++ b/windows/release-information/resolved-issues-windows-10-1703.yml @@ -35,7 +35,7 @@ sections:
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

See details >OS Build 15063.1659

February 19, 2019
KB4487011Resolved
KB4489871March 12, 2019 10:00 AM PT
First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >OS Build 15063.1596

January 15, 2019
KB4480959Resolved
KB4487011February 19, 2019 02:00 PM PT
Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

See details >OS Build 15063.1631

February 12, 2019
KB4487020Resolved
KB4487011February 19, 2019 02:00 PM PT -
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

See details >OS Build 15063.1631

February 12, 2019
KB4487020Resolved
KB4487020February 12, 2019 10:00 AM PT +
Applications using Microsoft Jet database and Microsoft Access 95 file format stop wo
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

See details >OS Build 15063.1631

February 12, 2019
KB4487020Resolved
KB4487020February 12, 2019 10:00 AM PT
Applications using Microsoft Jet database fail to open
Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.

See details >OS Build 15063.1563

January 08, 2019
KB4480973Resolved
KB4487020February 12, 2019 10:00 AM PT
Webpages become unresponsive in Microsoft Edge
Microsoft Edge users report difficulty browsing and loading webpages.

See details >OS Build 15063.1563

January 08, 2019
KB4480973Resolved
KB4487020February 12, 2019 10:00 AM PT
SqlConnection instantiation exception on .NET 4.6 and later
Instantiation of SqlConnection can throw an exception after certain updates have been installed.

See details >OS Build 15063.1292

August 30, 2018
KB4343889Resolved
KB4480959January 15, 2019 10:00 AM PT @@ -59,7 +59,7 @@ sections: - +
DetailsAffected buildStatusHistory
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487011, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

Resolution: This issue is resolved in KB4489871.

Back to top		OS Build 15063.1659

February 19, 2019
KB4487011		Resolved
KB4489871		Resolved:
March 12, 2019 10:00 AM PT

Opened:
February 19, 2019 02:00 PM PT
Internet Explorer may fail to load images
After installing KB4487020, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

Resolution: This issue is resolved in KB4487011.

Back to top		OS Build 15063.1631

February 12, 2019
KB4487020		Resolved
KB4487011		Resolved:
February 19, 2019 02:00 PM PT

Opened:
February 12, 2019 10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

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 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 2008 R2 SP1

Resolution: This issue is resolved in KB4487011.

Back to top		OS Build 15063.1631

February 12, 2019
KB4487020		Resolved
KB4487020		Resolved:
February 12, 2019 10:00 AM PT

Opened:
February 12, 2019 10:00 AM PT
Applications using Microsoft Jet database and Microsoft Access 95 file format stop wo
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

Resolution: This issue is resolved in KB4487011.

Back to top		OS Build 15063.1631

February 12, 2019
KB4487020		Resolved
KB4487020		Resolved:
February 12, 2019 10:00 AM PT

Opened:
February 12, 2019 10:00 AM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1803.yml b/windows/release-information/resolved-issues-windows-10-1803.yml index 60405b2a35..2573c8440a 100644 --- a/windows/release-information/resolved-issues-windows-10-1803.yml +++ b/windows/release-information/resolved-issues-windows-10-1803.yml @@ -41,7 +41,7 @@ sections:
SqlConnection instantiation exception on .NET 4.6 and later
After you install the August Preview of Quality Rollup or the September 11, 2018 .NET Framework update, instantiation of SqlConnection can throw an exception.

See details >OS Build 17134.285

September 11, 2018
KB4457128Resolved
KB4480976January 15, 2019 10:00 AM PT
Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.

See details >OS Build 17134.523

January 08, 2019
KB4480966Resolved
KB4480976January 15, 2019 10:00 AM PT
Blue or black screen with \"System thread exception not handled\" error
Some users may get a blue or black screen with the error code, “System thread exception not handled.”

See details >OS Build 17134.441

November 27, 2018
KB4467682Resolved
KB4471324December 11, 2018 10:00 AM PT -
Custom Start menu layouts display incorrectly
Custom Start menu layouts may display incorrectly.

See details >OS Build 17134.441

November 27, 2018
KB4467682Resolved
KB4471324December 11, 2018 10:00 AM PT +
Custom Start menu layouts display incorrectly
Custom Start menu layouts may display incorrectly.

See details >OS Build 17134.441

November 27, 2018
KB4467682Resolved
KB4471324December 11, 2018 10:00 AM PT
Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek Bar in Windows Media Player when playing specific files.

See details >OS Build 17134.345

October 09, 2018
KB4462919Resolved
KB4471324December 11, 2018 10:00 AM PT
Users cannot set Win32 program defaults
Some users cannot set Win32 program defaults for certain app and file type combinations.

See details >OS Build 17134.320

September 26, 2018
KB4458469Resolved
KB4467682November 27, 2018 10:00 AM PT
Developer Tools (F12) fail to start in Microsoft Edge
Developer Tools (F12) may fail to start in Microsoft Edge.

See details >OS Build 17134.376

October 24, 2018
KB4462933Resolved
KB4467702November 13, 2018 10:00 AM PT @@ -94,7 +94,7 @@ sections: text: " - +
DetailsAffected buildStatusHistory
Blue or black screen with \"System thread exception not handled\" error
After installing KB4467682, an optional update, some users may get a blue or black screen with the error code, \"System thread exception not handled.\"
 
Resolution: This issue is resolved in KB4471324. 

Back to top		OS Build 17134.441

November 27, 2018
KB4467682		Resolved
KB4471324		Resolved:
December 11, 2018 10:00 AM PT

Opened:
November 27, 2018 10:00 AM PT
Custom Start menu layouts display incorrectly
After installing KB4467682, custom Start menu layouts may display incorrectly. 
 
Resolution: This issue is resolved in KB4471324. 

Back to top		OS Build 17134.441

November 27, 2018
KB4467682		Resolved
KB4471324		Resolved:
December 11, 2018 10:00 AM PT

Opened:
November 27, 2018 10:00 AM PT
Custom Start menu layouts display incorrectly
After installing KB4467682, custom Start menu layouts may display incorrectly. 

Affected platforms:
  • Client: Windows 10, version 1803
  • Server: Windows Server, version 1803
 
Resolution: This issue is resolved in KB4471324. 

Back to top		OS Build 17134.441

November 27, 2018
KB4467682		Resolved
KB4471324		Resolved:
December 11, 2018 10:00 AM PT

Opened:
November 27, 2018 10:00 AM PT
" 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 f95662996a..c042195b17 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 @@ -33,6 +33,7 @@ sections: text: " + @@ -41,8 +42,10 @@ sections: + + @@ -57,6 +60,15 @@ sections:
" +- title: March 2019 +- items: + - type: markdown + text: " +
SummaryAffected buildStatusDate resolved
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.

See details >		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4489899		March 12, 2019 10:00 AM PT
Global DNS outage affects Windows Update customers
Windows Update customers were recently affected by a network infrastructure event caused by an external DNS service provider's global outage.

See details >


Resolved
March 08, 2019 11:15 AM PT
Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

See details >		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4482887		March 01, 2019 10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 9 file format may randomly stop working.

See details >		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4482887		March 01, 2019 10:00 AM PT
First character of the Japanese era name not recognized
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4482887		March 01, 2019 10:00 AM PT
F5 VPN clients losing network connectivity
Upgrade block: After updating to Window 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.

See details >		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4482887		March 01, 2019 10:00 AM PT
Webpages become unresponsive in Microsoft Edge
Microsoft Edge users report difficulty browsing and loading webpages.

See details >		OS Build 17763.253

January 08, 2019
KB4480116		Resolved
KB4487044		February 12, 2019 10:00 AM PT
Issues with lock screen and Microsoft Edge tabs for certain AMD Radeon video cards
Upgrade block: Devices utilizing AMD Radeon HD2000 or HD4000 series video cards may experience issues with the lock screen and Microsoft Edge tabs.

See details >		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4487044		February 12, 2019 10:00 AM PT
Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible
Upgrade block: Microsoft and Trend Micro identified a compatibility issue with the Trend Micro business endpoint security solutions OfficeScan and Worry-Free Business Security.

See details >		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
February 01, 2019 09:00 AM PT
Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.

See details >		OS Build 17763.253

January 08, 2019
KB4480116		Resolved
KB4476976		January 22, 2019 02:00 PM PT
Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.

See details >		OS Build 17763.55

October 09, 2018
KB4464330		Resolved
KB4471332		December 11, 2018 10:00 AM PT
Audio stops working after installing Intel audio driver
Upgrade block: Windows 10 audio stops working after installing Intel Smart Sound Technology driver (version 09.21.00.3755).

See details >		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4468550		December 07, 2018 10:00 AM PT
Office apps (32-bit) unable to use 'Save As…' function
Upgrade block: Devices using Morphisec Protector (or other application that uses the Morphisec SDK) may be unable to save documents when using 32-bit Microsoft Office apps.

See details >		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
December 06, 2018 12:00 PM PT
Users cannot set Win32 program defaults
Some users cannot set Win32 program defaults for certain app and file type combinations.

See details >		OS Build 17763.55

October 09, 2018
KB4464330		Resolved
KB4469342		December 05, 2018 02:00 PM PT
Mapped drives fail to reconnect after login
Upgrade block: Mapped drives may fail to reconnect after booting and logging on to a Windows device.

See details >		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4469342		December 05, 2018 02:00 PM PT
+ +
DetailsAffected buildStatusHistory
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
+ " + - title: February 2019 - items: - type: markdown @@ -97,6 +109,8 @@ sections:
Intel Audio Display (intcdaud.sys) notification during Windows 10 Setup
Upgrade block: Microsoft and Intel have identified a compatibility issue with a range of Intel Display Audio device drivers (intcdaud.sys, versions 10.25.0.3 - 10.25.0.8) that may result in excessive processor demand and reduced battery life. As a result, the update process to the Windows 10 October 2018 Update (Windows 10, version 1809) will fail and affected devices will automatically revert to the previous working configuration. 

Affected platforms:

If you see a \"What needs your attention\" notification during installation of the October 2018 Update, you have one of these affected drivers on your system. On the notification, click Back to remain on your current version of Windows 10. 
 
To ensure a seamless experience, we are blocking devices from being offered the October 2018 Update until updated Intel device drivers are installed on your current operating system. We recommend that you do not attempt to manually update to Windows 10, version 1809, using the Update Now button or the Media Creation Tool from the Microsoft Software Download Center until newer Intel device drivers are available with the update. You can either wait for newer drivers to be installed automatically through Windows Update or check with your computer manufacturer for the latest device driver software availability and installation procedures. For more information about this issue, see Intel's customer support guidance.
 
Resolution: This issue was resolved in KB4482887 and the upgrade block removed. 

Back to topOS Build 17763.134

November 13, 2018
KB4467708Resolved
KB4482887Resolved:
March 01, 2019 10:00 AM PT

Opened:
November 13, 2018 10:00 AM PT
F5 VPN clients losing network connectivity
Upgrade block: After updating to Window 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.

Affected platforms:

Resolution: This issue was resolved in KB4482887 and the upgrade block removed. 

Back to topOS Build 17763.134

November 13, 2018
KB4467708Resolved
KB4482887Resolved:
March 01, 2019 10:00 AM PT

Opened:
November 13, 2018 10:00 AM PT
Issues with lock screen and Microsoft Edge tabs for certain AMD Radeon video cards
Note: AMD no longer supports Radeon HD2000 and HD4000 series graphic processor units (GPUs).
 
Upgrade block: After updating to Window 10, version 1809, Microsoft Edge tabs may stop working when a device is configured with AMD Radeon HD2000 or HD4000 series video cards. Customers may get the following error code: \"INVALID_POINTER_READ_c0000005_atidxx64.dll\". 
 
Some users may also experience performance issues with the lock screen or the ShellExperienceHost. (The lock screen hosts widgets, and the ShellExperienceHost is responsible for assorted shell functionality.) 

Affected platforms:

Resolution: This issue was resolved in KB4487044, and the block was removed.

Back to topOS Build 17763.134

November 13, 2018
KB4467708Resolved
KB4487044Resolved:
February 12, 2019 10:00 AM PT

Opened:
November 13, 2018 10:00 AM PT +
Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible
Upgrade block: Microsoft and Trend Micro have identified a compatibility issue with Trend Micro's OfficeScan and Worry-Free Business Security software when attempting to update to Windows 10, version 1809. 

Resolution: Trend Micro has released a new version of these products that resolves the issue. To download them, please visit the Trend Micro Business Support Portal.

Once you have updated your version of Trend Micro's OfficeScan or Worry-Free Business Security software, you will be offered Windows 10, version 1809 automatically. 

Back to topOS Build 17763.134

November 13, 2018
KB4467708Resolved
Resolved:
February 01, 2019 09:00 AM PT

Opened:
November 13, 2018 10:00 AM PT +
Audio stops working after installing Intel audio driver
Upgrade block: Intel unintentionally released version 9.21.00.3755 of the Intel Smart Sound Technology (ISST) Driver through Windows Update and inadvertently offered it to a range of devices running Window 10, version 1709, 1803, and 1809. If a device contained a compatible audio driver, the new driver overrode it and caused audio to stop working. 
 
Resolution: This issue was resolved in KB4468550 and the upgrade block removed. 

Back to topOS Build 17763.134

November 13, 2018
KB4467708Resolved
KB4468550Resolved:
December 07, 2018 10:00 AM PT

Opened:
November 13, 2018 10:00 AM PT
Office apps (32-bit) unable to use 'Save As…' function
Upgrade block: Microsoft and Morphisec have identified an issue on devices that have installed Morphisec Protector or another application that uses the Morphisec Software Development Kit (SDK) including Cisco AMP for Endpoints. These applications may impact customers' ability to use the 'Save As.'dialog when saving documents in 32-bit versions of Microsoft Office applications. Saving of files is not impacted.

Affected platforms:

Resolution: Morphisec and Cisco have released updated versions of their applications to address this issue. We recommend customers update to these minimum versions before attempting to attempting to upgrade to Windows 10, version 1809: 


An upgrade block remains in place for earlier versions of the applications than those listed above.

Back to topOS Build 17763.134

November 13, 2018
KB4467708Resolved
Resolved:
December 06, 2018 12:00 PM PT

Opened:
November 13, 2018 10:00 AM PT
Mapped drives fail to reconnect after login
Upgrade block: Network drives may fail to reconnect after booting and logging on to a Windows device. Symptoms include: 
 

Affected platforms:

Resolution: This issue was resolved in KB4469342 and the upgrade block removed. 

Back to topOS Build 17763.134

November 13, 2018
KB4467708Resolved
KB4469342Resolved:
December 05, 2018 02:00 PM PT

Opened:
November 13, 2018 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 461c304525..c58f19644a 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 @@ -60,15 +60,15 @@ sections: - type: markdown text: " - - - - + + + +
SummaryAffected buildStatusLast updated
Issue using PXE to start a device from WDS
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.

See details >		OS Build 14393.2848

March 12, 2019
KB4489882		Mitigated
April 18, 2019 05:51 PM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		OS Build 14393.2848

March 12, 2019
KB4489882		Mitigated
April 18, 2019 04:36 PM PT
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM
Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM.

See details >		OS Build 14393.2608

November 13, 2018
KB4467691		Mitigated
April 18, 2019 01:05 PM PT
Issues with install and activation of Key Management Service (KMS) (CSVLK) host keys
Installation and client activation of Windows Server 2019 and 1809 LTSC Key Management Service (KMS) (CSVLK) host keys do not work as expected.

See details >		OS Build 14393.2457

August 30, 2018
KB4343884		Acknowledged
KB4467684		April 18, 2019 12:57 PM PT
Cluster service may fail if the minimum password length is set to greater than 14
The cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters.

See details >		OS Build 14393.2639

November 27, 2018
KB4467684		Mitigated
April 18, 2019 12:50 PM PT
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.

See details >		OS Build 14393.2879

March 19, 2019
KB4489889		Resolved
KB4493470		April 09, 2019 10:00 AM PT
Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.

See details >		OS Build 14393.2724

January 08, 2019
KB4480961		Resolved
KB4493470		April 09, 2019 10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >		OS Build 14393.2724

January 08, 2019
KB4480961		Resolved
KB4493470		April 09, 2019 10:00 AM PT
Cluster service may fail if the minimum password length is set to greater than 14
The cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters.

See details >		OS Build 14393.2639

November 27, 2018
KB4467684		Mitigated
March 19, 2019 10:00 AM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		OS Build 14393.2848

March 12, 2019
KB4489882		Mitigated
March 19, 2019 10:00 AM PT
Issue using PXE to start a device from WDS
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.

See details >		OS Build 14393.2848

March 12, 2019
KB4489882		Mitigated
March 19, 2019 10:00 AM PT
SCVMM cannot enumerate and manage logical switches deployed on the host
For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host.

See details >		OS Build 14393.2639

November 27, 2018
KB4467684		Mitigated
March 19, 2019 10:00 AM PT
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM
Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM.

See details >		OS Build 14393.2608

November 13, 2018
KB4467691		Mitigated
February 19, 2019 10:00 AM PT
" @@ -84,9 +84,9 @@ sections: - type: markdown text: " - - + +
DetailsAffected buildStatusHistory
Issue using PXE to start a device from WDS
After 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:
April 18, 2019 05:51 PM PT

Opened:
March 12, 2019 10:00 AM PT
Custom URI schemes may not start corresponding application
After 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

  1. Go to Tools > Internet options > Security.
  2. Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
  3. Select Trusted sites and then select Enable Protected Mode.
  4. 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:
April 18, 2019 04:36 PM PT

Opened:
March 12, 2019 10:00 AM PT
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.

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 application
After 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.

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

  1. Go to Tools > Internet options > Security.
  2. Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
  3. Select Trusted sites and then select Enable Protected Mode.
  4. 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 WDS
After 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.

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
" @@ -105,9 +105,9 @@ sections: - type: markdown text: " - - + +
DetailsAffected buildStatusHistory
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM
After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM.

Affected platforms:
  • Client: Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016

Workaround: Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart.

If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled.

Next steps: Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device.

Back to top		OS Build 14393.2608

November 13, 2018
KB4467691		Mitigated
Last updated:
April 18, 2019 01:05 PM PT

Opened:
November 13, 2018 10:00 AM PT
Cluster service may fail if the minimum password length is set to greater than 14
After installing KB4467684, the cluster service may fail to start with the error \"2245 (NERR_PasswordTooShort)\" if the Group Policy \"Minimum Password Length\" is configured with greater than 14 characters.

Affected platforms:
  • Client: Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016

Workaround: Set the domain default \"Minimum Password Length\" policy to less than or equal to 14 characters.

Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 14393.2639

November 27, 2018
KB4467684		Mitigated
Last updated:
April 18, 2019 12:50 PM PT

Opened:
November 27, 2018 10:00 AM PT
Cluster service may fail if the minimum password length is set to greater than 14
After installing KB4467684, the cluster service may fail to start with the error \"2245 (NERR_PasswordTooShort)\" if the Group Policy \"Minimum Password Length\" is configured with greater than 14 characters.

Workaround: Set the domain default \"Minimum Password Length\" policy to less than or equal to 14 characters.

Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 14393.2639

November 27, 2018
KB4467684		Mitigated
Last updated:
March 19, 2019 10:00 AM PT

Opened:
November 27, 2018 10:00 AM PT
SCVMM cannot enumerate and manage logical switches deployed on the host
For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host after installing KB4467684.

Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.

Affected platforms:
  • Client: Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016

Workaround:
Run mofcomp on the following mof files on the affected host:

  • Scvmmswitchportsettings.mof
  • VMMDHCPSvr.mof

Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).

Back to top		OS Build 14393.2639

November 27, 2018
KB4467684		Mitigated
Last updated:
March 19, 2019 10:00 AM PT

Opened:
November 27, 2018 10:00 AM PT
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM
After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM.

Workaround: Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart.

If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled.

Next steps: Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device.

Back to top		OS Build 14393.2608

November 13, 2018
KB4467691		Mitigated
Last updated:
February 19, 2019 10:00 AM PT

Opened:
November 13, 2018 10:00 AM PT
" diff --git a/windows/release-information/status-windows-10-1703.yml b/windows/release-information/status-windows-10-1703.yml index 839eb9bd94..ab86246899 100644 --- a/windows/release-information/status-windows-10-1703.yml +++ b/windows/release-information/status-windows-10-1703.yml @@ -60,10 +60,10 @@ sections: - type: markdown text: " - +
SummaryAffected buildStatusLast updated
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		OS Build 15063.1689

March 12, 2019
KB4489871		Mitigated
April 18, 2019 04:34 PM PT
LongonUI.exe stops working intermittently
LongonUI.exe stops working intermittently.

See details >		OS Build 15063.1387

October 09, 2018
KB4462937		Acknowledged
KB4467699		April 18, 2019 11:56 AM PT
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.

See details >		OS Build 15063.1716

March 19, 2019
KB4489888		Resolved
KB4493474		April 09, 2019 10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >		OS Build 15063.1563

January 08, 2019
KB4480973		Resolved
KB4493474		April 09, 2019 10:00 AM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		OS Build 15063.1689

March 12, 2019
KB4489871		Mitigated
March 19, 2019 10:00 AM PT
" @@ -79,8 +79,8 @@ sections: - type: markdown text: " - +
DetailsAffected buildStatusHistory
Custom URI schemes may not start corresponding application
After installing KB4489871, 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

1. Go to Tools > Internet options > Security.
2. Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
3. Select Trusted sites and then select Enable Protected Mode.
4. 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 15063.1689

March 12, 2019
KB4489871		Mitigated
Last updated:
April 18, 2019 04:34 PM PT

Opened:
March 12, 2019 10:00 AM PT
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.

Resolution: This issue was resolved in KB4493474.

Back to top		OS Build 15063.1716

March 19, 2019
KB4489888		Resolved
KB4493474		Resolved:
April 09, 2019 10:00 AM PT

Opened:
March 19, 2019 10:00 AM PT
Custom URI schemes may not start corresponding application
After installing KB4489871, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer.

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

1. Go to Tools > Internet options > Security.
2. Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
3. Select Trusted sites and then select Enable Protected Mode.
4. 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 15063.1689

March 12, 2019
KB4489871		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-1803.yml b/windows/release-information/status-windows-10-1803.yml index 31cc34a263..f3c9f5e6bc 100644 --- a/windows/release-information/status-windows-10-1803.yml +++ b/windows/release-information/status-windows-10-1803.yml @@ -60,11 +60,11 @@ sections: - type: markdown text: " - +
SummaryAffected buildStatusLast updated
Issue using PXE to start a device from WDS
Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.

See details >		OS Build 17134.648

March 12, 2019
KB4489868		Mitigated
April 18, 2019 05:50 PM PT
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.

See details >		OS Build 17134.677

March 19, 2019
KB4489894		Resolved
KB4493464		April 09, 2019 10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >		OS Build 17134.523

January 08, 2019
KB4480966		Resolved
KB4493464		April 09, 2019 10:00 AM PT
Stop error when attempting to start SSH from WSL
A stop error occurs when attempting to start Secure Shell from Windows Subsystem for Linux with agent forwarding using a command line switch (ssh –A) or a configuration setting.

See details >		OS Build 17134.648

March 12, 2019
KB4489868		Resolved
KB4493464		April 09, 2019 10:00 AM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		OS Build 17134.648

March 12, 2019
KB4489868		Mitigated
March 19, 2019 10:00 AM PT
Issue using PXE to start a device from WDS
Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.

See details >		OS Build 17134.648

March 12, 2019
KB4489868		Mitigated
March 19, 2019 10:00 AM PT
" @@ -80,10 +80,10 @@ sections: - type: markdown text: " - +
DetailsAffected buildStatusHistory
Issue using PXE to start a device from WDS
After 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: 
 
  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 17134.648

March 12, 2019
KB4489868		Mitigated
Last updated:
April 18, 2019 05:50 PM PT

Opened:
March 12, 2019 10:00 AM PT
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. 
 
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 WSL
After 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 application
After 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. 
 
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 
 
  1. Go to Tools > Internet options > Security 
  2. Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
  3. Select Trusted sites and then select Enable Protected Mode. 
  4. 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 WDS
After 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. 
 
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 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-10-1809-and-windows-server-2019.yml b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml index 5d13a9ae71..d2403bb154 100644 --- a/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml +++ b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml @@ -65,15 +65,12 @@ sections: - type: markdown text: " - - - - - + +
SummaryAffected buildStatusLast updated
Issue using PXE to start a device from WDS
Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.

See details >		OS Build 17763.379

March 12, 2019
KB4489899		Mitigated
April 18, 2019 05:52 PM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		OS Build 17763.379

March 12, 2019
KB4489899		Mitigated
April 18, 2019 04:26 PM PT
Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible
Upgrade block: Microsoft and Trend Micro identified a compatibility issue with the Trend Micro business endpoint security solutions OfficeScan and Worry-Free Business Security.

See details >		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
April 18, 2019 03:11 PM PT
Audio stops working after installing Intel audio driver
Upgrade block: Windows 10 audio stops working after installing Intel Smart Sound Technology driver (version 09.21.00.3755).

See details >		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4468550		April 18, 2019 03:04 PM PT
Global DNS outage affects Windows Update customers
Windows Update customers were recently affected by a network infrastructure event caused by an external DNS service provider's global outage.

See details >


Resolved
April 18, 2019 02:59 PM PT
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.

See details >		OS Build 17763.404

April 02, 2019
KB4490481		Resolved
KB4493509		April 09, 2019 10:00 AM PT
Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.

See details >		OS Build 17763.253

January 08, 2019
KB4480116		Resolved
KB4493509		April 09, 2019 10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >		OS Build 17763.253

January 08, 2019
KB4480116		Resolved
KB4493509		April 09, 2019 10:00 AM PT
Apps may stop working after selecting an audio output device other than the default
Users with multiple audio devices that select an audio output device different from the \"Default Audio Device\" may find certain applications stop working unexpectedly.

See details >		OS Build 17763.348

March 01, 2019
KB4482887		Resolved
KB4490481		April 02, 2019 10:00 AM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		OS Build 17763.379

March 12, 2019
KB4489899		Mitigated
April 02, 2019 10:00 AM PT
Issue using PXE to start a device from WDS
Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.

See details >		OS Build 17763.379

March 12, 2019
KB4489899		Mitigated
April 02, 2019 10:00 AM PT
Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort
Upgrade block: Microsoft has identified issues with certain new Intel display drivers, which accidentally turn on unsupported features in Windows.

See details >		OS Build 17763.134

November 13, 2018
KB4467708		Mitigated
March 15, 2019 12:00 PM PT
" @@ -99,11 +96,10 @@ sections: - type: markdown text: " - - - + +
DetailsAffected buildStatusHistory
Issue using PXE to start a device from WDS
After installing KB4489899, 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 17763.379

March 12, 2019
KB4489899		Mitigated
Last updated:
April 18, 2019 05:52 PM PT

Opened:
March 12, 2019 10:00 AM PT
Custom URI schemes may not start corresponding application
After installing KB4489899, 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 
 
  1. Go to Tools > Internet options > Security.
  2. Within Select a zone to view of change security settings, select Local intranet and then select Enable Protected Mode.
  3. Select Trusted Sites and then select Enable Protected Mode. 
  4. 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 17763.379

March 12, 2019
KB4489899		Mitigated
Last updated:
April 18, 2019 04:26 PM PT

Opened:
March 12, 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:
April 18, 2019 02:59 PM PT

Opened:
March 08, 2019 10:00 AM PT
Apps may stop working after selecting an audio output device other than the default
After 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: 

  1. Open Windows Media Player > Tools > Options > Devices.
  2. Select the device and choose Properties.
  3. 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
Custom URI schemes may not start corresponding application
After installing KB4489899, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites security zones on Internet Explorer. 

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 
 
  1. Go to Tools > Internet options > Security.
  2. Within Select a zone to view of change security settings, select Local intranet and then select Enable Protected Mode.
  3. Select Trusted Sites and then select Enable Protected Mode. 
  4. 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 17763.379

March 12, 2019
KB4489899		Mitigated
Last updated:
April 02, 2019 10:00 AM PT

Opened:
March 12, 2019 10:00 AM PT
Issue using PXE to start a device from WDS
After installing KB4489899, 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 17763.379

March 12, 2019
KB4489899		Mitigated
Last updated:
April 02, 2019 10:00 AM PT

Opened:
March 12, 2019 10:00 AM PT
" @@ -122,8 +118,6 @@ sections: - type: markdown text: " - -
DetailsAffected buildStatusHistory
Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible
Upgrade block: Microsoft and Trend Micro have identified a compatibility issue with Trend Micro's OfficeScan and Worry-Free Business Security software when attempting to update to Windows 10, version 1809.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019 

Resolution: Trend Micro has released a new version of these products that resolves the issue. To download them, please visit the Trend Micro Business Support Portal.

Once you have updated your version of Trend Micro's OfficeScan or Worry-Free Business Security software, you will be offered Windows 10, version 1809 automatically. 

Back to top		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
Resolved:
April 18, 2019 03:11 PM PT

Opened:
November 13, 2018 10:00 AM PT
Audio stops working after installing Intel audio driver
Upgrade block: Intel unintentionally released version 9.21.00.3755 of the Intel Smart Sound Technology (ISST) Driver through Windows Update and inadvertently offered it to a range of devices running Window 10, version 1709, 1803, and 1809. If a device contained a compatible audio driver, the new driver overrode it and caused audio to stop working.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019
 
Resolution: This issue was resolved in KB4468550 and the upgrade block removed. 

Back to top		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4468550		Resolved:
April 18, 2019 03:04 PM PT

Opened:
November 13, 2018 10:00 AM PT
Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort
Upgrade block: Microsoft has identified issues with certain new Intel display drivers. Intel inadvertently released versions of its display driver (versions 24.20.100.6344, 24.20.100.6345) to OEMs that accidentally turned on unsupported features in Windows. 
 
As a result, after updating to Windows 10, version 1809, audio playback from a monitor or television connected to a PC via HDMI, USB-C, or a DisplayPort may not function correctly on devices with these drivers.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019 

Next steps: Intel has released updated drivers to OEM device manufacturers. OEMs need to make the updated driver available via Windows Update.

For more information, see the Intel Customer Support article.

Note: This Intel display driver issue is different from the Intel Smart Sound Technology driver (version 09.21.00.3755) audio issue previously documented.

Back to top		OS Build 17763.134

November 13, 2018
KB4467708		Mitigated
Last updated:
March 15, 2019 12:00 PM PT

Opened:
November 13, 2018 10:00 AM PT
"