From d42f2c47237dc70cee8b18510fe6b40eeb77383e Mon Sep 17 00:00:00 2001 From: "Nisha Mittal (Wipro Ltd.)" Date: Fri, 26 Apr 2019 00:17:41 -0700 Subject: [PATCH] Fixed Affected Build Heading --- .../resolved-issues-windows-10-1507.yml | 10 +++++----- .../resolved-issues-windows-10-1607.yml | 14 +++++++------- .../resolved-issues-windows-10-1703.yml | 10 +++++----- .../resolved-issues-windows-10-1709.yml | 10 +++++----- .../resolved-issues-windows-10-1803.yml | 16 ++++++++-------- ...s-windows-10-1809-and-windows-server-2019.yml | 14 +++++++------- ...-windows-7-and-windows-server-2008-r2-sp1.yml | 10 +++++----- ...es-windows-8.1-and-windows-server-2012-r2.yml | 10 +++++----- .../resolved-issues-windows-server-2008-sp2.yml | 2 +- .../resolved-issues-windows-server-2012.yml | 2 +- .../status-windows-10-1507.yml | 4 ++-- ...s-windows-10-1607-and-windows-server-2016.yml | 6 +++--- .../status-windows-10-1703.yml | 4 ++-- .../status-windows-10-1709.yml | 4 ++-- .../status-windows-10-1803.yml | 4 ++-- ...s-windows-10-1809-and-windows-server-2019.yml | 8 ++++---- ...-windows-7-and-windows-server-2008-r2-sp1.yml | 6 +++--- ...us-windows-8.1-and-windows-server-2012-r2.yml | 8 ++++---- .../status-windows-server-2008-sp2.yml | 2 +- .../status-windows-server-2012.yml | 2 +- 20 files changed, 73 insertions(+), 73 deletions(-) diff --git a/windows/release-information/resolved-issues-windows-10-1507.yml b/windows/release-information/resolved-issues-windows-10-1507.yml index bd5c223e6a..1a4fc478a8 100644 --- a/windows/release-information/resolved-issues-windows-10-1507.yml +++ b/windows/release-information/resolved-issues-windows-10-1507.yml @@ -56,7 +56,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Custom URI schemes may not start corresponding application
After installing KB4489872, Custom URI Schemes for Application Protocol handlers may not start the corresponding application for local intranet and trusted sites 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 was resolved in KB4493475.

Back to top		OS Build 10240.18158

March 12, 2019
KB4489872		Resolved
KB4493475		Resolved:
April 09, 2019
10:00 AM PT

Opened:
March 12, 2019
10:00 AM PT
" @@ -65,7 +65,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
@@ -77,7 +77,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
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 KB4489872.

Back to top		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4489872		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487018, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

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 KB4489872.

Back to top		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4489872		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
First character of Japanese era name not recognized
After installing KB4487018, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

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 KB4489872.

Back to top		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4489872		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
@@ -88,7 +88,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
MSXML6 may cause applications to stop responding
After installing KB4480962, 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

Resolution: This issue was resolved in KB4493475.

Back to top		OS Build 10240.18094

January 08, 2019
KB4480962		Resolved
KB4493475		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 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 the database has column names greater than 32 characters. The database will fail to open with the error, \"Unrecognized Database Format\".

Affected platforms:
  • Client: 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 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1

Resolution: This issue is resolved in KB4487018.

Back to top		OS Build 10240.18094

January 08, 2019
KB4480962		Resolved
KB4487018		Resolved:
February 12, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
Unable to access hotspots with third-party applications
After installing KB4480962, 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 KB4487018.

Back to top		OS Build 10240.18094

January 08, 2019
KB4480962		Resolved
KB4487018		Resolved:
February 12, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Unable to use Seek bar in Windows Media Player
After installing KB4462922, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.

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 KB4471323.

Back to top		OS Build 10240.18005

October 09, 2018
KB4462922		Resolved
KB4471323		Resolved:
December 11, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
" @@ -97,7 +97,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Guest VMs running Unicast NLB fail to respond after restart
All guest virtual machines running Unicast NLB fail to respond to NLB requests after the virtual machines restart.

Affected platforms:
  • Client: Windows 10, version 1803; Windows 10, version 1507
  • Server: Windows Server, version 1803

Resolution: This issue is resolved in KB4462922.

Back to top		OS Build 10240.17976

September 11, 2018
KB4457132		Resolved
KB4462922		Resolved:
October 09, 2018
10:00 AM PT

Opened:
September 11, 2018
10:00 AM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1607.yml b/windows/release-information/resolved-issues-windows-10-1607.yml index 398c697014..b0c54bdee0 100644 --- a/windows/release-information/resolved-issues-windows-10-1607.yml +++ b/windows/release-information/resolved-issues-windows-10-1607.yml @@ -62,7 +62,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
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
" @@ -71,7 +71,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
@@ -83,7 +83,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Issue hosting multiple terminal server sessions and a user logs off on Windows Server
In some cases, Windows Server will stop working and restart when hosting multiple terminal server sessions and a user logs off. The faulting driver is win32kbase.sys.

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

Resolution: This issue is resolved in KB4489882.

Back to top		OS Build 14393.2828

February 19, 2019
KB4487006		Resolved
KB4489882		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 19, 2019
02:00 PM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487026, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

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 KB4489882.

Back to top		OS Build 14393.2791

February 12, 2019
KB4487026		Resolved
KB4489882		Resolved:
March 12, 2019
10:00 AM 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 KB4487006.

Back to top		OS Build 14393.2791

February 12, 2019
KB4487026		Resolved
KB4487006		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
@@ -96,7 +96,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Internet Explorer 11 authentication issue with multiple concurrent logons
After installing KB4480961, 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

Resolution: This issue was resolved in KB4493470.

Back to top		OS Build 14393.2724

January 08, 2019
KB4480961		Resolved
KB4493470		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 KB4480961, 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

Resolution: This issue was resolved in KB4493470.

Back to top		OS Build 14393.2724

January 08, 2019
KB4480961		Resolved
KB4493470		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480977, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

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 KB4487006.

Back to top		OS Build 14393.2759

January 17, 2019
KB4480977		Resolved
KB4487006		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 17, 2019
02:00 PM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Instant search in Microsoft Outlook fails on Windows Server 2016
After installing KB4467684 on Windows Server 2016, instant search in Microsoft Outlook clients fail with the error, \"Outlook cannot perform the search\".

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

Resolution: This issue is resolved in KB4487026.

Back to top		OS Build 14393.2639

November 27, 2018
KB4467684		Resolved
KB4487026		Resolved:
February 12, 2019
10:00 AM PT

Opened:
November 27, 2018
10:00 AM PT
System becomes unresponsive when end-user-defined characters (EUDC) are used
When features related to end-user-defined characters (EUDC) are used, the entire system may become unresponsive. 

Affected platforms:
  • Client: Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
 
Resolution: This issue is resolved in KB4471321. 

Back to top		OS Build 14393.2639

November 27, 2018
KB4467684		Resolved
KB4471321		Resolved:
December 11, 2018
10:00 AM PT

Opened:
November 27, 2018
10:00 AM PT
@@ -106,7 +106,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Unable to use Seek bar in Windows Media Player
After installing KB4462917, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.

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 KB4471321.

Back to top		OS Build 14393.2551

October 09, 2018
KB4462917		Resolved
KB4471321		Resolved:
December 11, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
" @@ -115,7 +115,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Promotions that create non-root domains fail with optional features enabled
After installing KB4457127, Windows Server 2016 promotions that create non-root domains fail in forests in which optional features like Active Directory recycle have been enabled. The error is, “The replication operation encountered a database error.”

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

Resolution: This issue is resolved in KB4467684.

Back to top		OS Build 14393.2515

September 20, 2018
KB4457127		Resolved
KB4467684		Resolved:
November 27, 2018
10:00 AM PT

Opened:
September 20, 2018
10:00 AM PT
" @@ -124,7 +124,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
SqlConnection instantiation exception on .NET 4.6 and later
After you install the August Preview of Quality Rollup or September 11, 2018 .NET Framework update, instantiation of SqlConnection can throw an exception.

For more information about this issue, see the following article in the Microsoft Knowledge Base: 4470809, SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.

Affected platforms:
  • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016

Resolution: This issue is resolved in KB4480977.

Back to top		OS Build 14393.2457

August 30, 2018
KB4343884		Resolved
KB4480977		Resolved:
January 17, 2019
02:00 PM PT

Opened:
August 30, 2018
05:00 PM PT
Issues with install and activation of Key Management Service (KMS) (CSVLK) host keys
After installing KB4343884, installation and client activation of Windows Server 2019 and Windows 10 Enterprise 2019 LTSC Key Management Service (KMS) CSVLK host keys do not work as expected.

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

Resolution: This issue is resolved in KB4467684.

Back to top		OS Build 14393.2457

August 30, 2018
KB4343884		Resolved
KB4467684		Resolved:
November 27, 2018
10:00 AM PT

Opened:
August 30, 2018
05:00 PM PT
diff --git a/windows/release-information/resolved-issues-windows-10-1703.yml b/windows/release-information/resolved-issues-windows-10-1703.yml index 9017df00dd..05831e7123 100644 --- a/windows/release-information/resolved-issues-windows-10-1703.yml +++ b/windows/release-information/resolved-issues-windows-10-1703.yml @@ -59,7 +59,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
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 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
" @@ -68,7 +68,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
@@ -79,7 +79,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
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.

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

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 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
KB4487011		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
@@ -92,7 +92,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
MSXML6 may cause applications to stop responding
After installing KB4480973, 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

Resolution: This issue was resolved in KB4493474.

Back to top		OS Build 15063.1563

January 08, 2019
KB4480973		Resolved
KB4493474		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480959, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

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 KB4487011.

Back to top		OS Build 15063.1596

January 15, 2019
KB4480959		Resolved
KB4487011		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 15, 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 the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.

Affected platforms:
  • Client: 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 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1

Resolution: This issue is resolved in KB4487020.

Back to top		OS Build 15063.1563

January 08, 2019
KB4480973		Resolved
KB4487020		Resolved:
February 12, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
@@ -103,7 +103,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Unable to use Seek bar in Windows Media Player
After installing KB4462937, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.

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 KB4471327.

Back to top		OS Build 15063.1387

October 09, 2018
KB4462937		Resolved
KB4471327		Resolved:
December 11, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
LongonUI.exe stops working intermittently
After installing KB4462937, LogonUI.exe stops working intermittently.

Affected platforms:
  • Windows 10, version 1703

Resolution: This issue is resolved in KB4467699.

Back to top		OS Build 15063.1387

October 09, 2018
KB4462937		Resolved
KB4467699		Resolved:
November 27, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
Error message beginning with “Hosted by…” when launching Microsoft Edge
After installing KB4462937, some users may see a dialog box with a non-applicable message beginning with the words “Hosted by...” when first starting Microsoft Edge.

This dialog will only appear once if they have turned on “Block only third-party cookies” in Microsoft Edge and applied certain language packs before installing this update.

Affected platforms:
  • Client: Windows 10, version 1709; Windows 10, version 1703
  • Server: Windows Server, version 1709

Resolution: This issue is resolved in KB4462939.

Back to top		OS Build 15063.1387

October 09, 2018
KB4462937		Resolved
KB4462939		Resolved:
October 18, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
SqlConnection instantiation exception on .NET 4.6 and later
After you install the August Preview of Quality Rollup or September 11, 2018 .NET Framework update, instantiation of SqlConnection can throw an exception.

For more information about this issue, see the following article in the Microsoft Knowledge Base:
4470809 SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.

Affected platforms:
  • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016

Resolution: This issue is resolved in KB4480959.

Back to top		OS Build 15063.1292

August 30, 2018
KB4343889		Resolved
KB4480959		Resolved:
January 15, 2019
10:00 AM PT

Opened:
August 30, 2018
05:00 PM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1709.yml b/windows/release-information/resolved-issues-windows-10-1709.yml index 8c6c8c22b7..93ff2b61dc 100644 --- a/windows/release-information/resolved-issues-windows-10-1709.yml +++ b/windows/release-information/resolved-issues-windows-10-1709.yml @@ -59,7 +59,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
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 is resolved in KB4493441.

Back to top		OS Build 16299.1059

March 19, 2019
KB4489890		Resolved
KB4493441		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 KB4489886, 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 is resolved in KB4493441.

Back to top		OS Build 16299.1029

March 12, 2019
KB4489886		Resolved
KB4493441		Resolved:
April 09, 2019
10:00 AM PT

Opened:
March 12, 2019
10:00 AM PT
@@ -69,7 +69,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
@@ -80,7 +80,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4486996, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

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 KB4489886.

Back to top		OS Build 16299.967

February 12, 2019
KB4486996		Resolved
KB4489886		Resolved:
March 12, 2019
10:00 AM 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 KB4487021.

Back to top		OS Build 16299.967

February 12, 2019
KB4486996		Resolved
KB4487021		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
After installing KB4486996, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

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 KB4487021.

Back to top		OS Build 16299.967

February 12, 2019
KB4486996		Resolved
KB4487021		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
@@ -93,7 +93,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
MSXML6 causes applications to stop responding if an exception was thrown
After installing KB4480978, 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

Resolution: This issue is resolved in KB4493441.

Back to top		OS Build 16299.904

January 08, 2019
KB4480978		Resolved
KB4493441		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480967, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

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 KB4487021.

Back to top		OS Build 16299.936

January 15, 2019
KB4480967		Resolved
KB4487021		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 15, 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 the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format.”

Affected platforms:
  • Client: 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 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1 

Resolution: This issue is resolved in KB4486996.

Back to top		OS Build 16299.904

January 08, 2019
KB4480978		Resolved
KB4486996		Resolved:
February 12, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Unable to use Seek bar in Windows Media Player
After installing KB4462918, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.

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 KB4471329.

Back to top		OS Build 16299.726

October 09, 2018
KB4462918		Resolved
KB4471329		Resolved:
December 11, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
Error message beginning with “Hosted by…” when launching Microsoft Edge
After installing KB4462918, some users may see a dialog box with a non-applicable message beginning with the words “Hosted by...” when first starting Microsoft Edge.

This dialog will only appear once if they have turned on “Block only third-party cookies” in Microsoft Edge and applied certain language packs before installing this update.

Affected platforms:
  • Client: Windows 10, version 1709; Windows 10, version 1703
  • Server: Windows Server, version 1709

Resolution: This issue is resolved in KB4462932.

Back to top		OS Build 16299.726

October 09, 2018
KB4462918		Resolved
KB4462932		Resolved:
October 18, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
@@ -103,7 +103,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
SqlConnection instantiation exception on .NET 4.6 and later
After you install the August Preview of Quality Rollup or September 11, 2018 .NET Framework update, instantiation of SqlConnection can throw an exception.

For more information about this issue, see the following article in the Microsoft Knowledge Base:
4470809 SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.

Affected platforms:
  • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016

Resolution: This issue is resolved in KB4480967.

Back to top		OS Build 16299.637

August 30, 2018
KB4343893		Resolved
KB4480967		Resolved:
January 15, 2019
10:00 AM PT

Opened:
August 30, 2018
05:00 PM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1803.yml b/windows/release-information/resolved-issues-windows-10-1803.yml index e59eefb539..af3cab2c74 100644 --- a/windows/release-information/resolved-issues-windows-10-1803.yml +++ b/windows/release-information/resolved-issues-windows-10-1803.yml @@ -64,7 +64,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
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 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
@@ -74,7 +74,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487017, users may received \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files. 

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 KB4489868.

Back to top		OS Build 17134.590

February 12, 2019
KB4487017		Resolved
KB4489868		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
After installing KB4487017, Internet Explorer may fail to load images with a backslash (\\) in their relative source path. 

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 KB4487029. 

Back to top		OS Build 17134.590

February 12, 2019
KB4487017		Resolved
KB4487029		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
@@ -84,7 +84,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
@@ -97,7 +97,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
MSXML6 may cause applications to stop responding
After installing KB4480966, 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

Resolution: This issue was resolved in KB4493464. 

Back to top		OS Build 17134.523

January 08, 2019
KB4480966		Resolved
KB4493464		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
First character of Japanese era name not recognized
After installing KB4480976, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

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 KB4487029. 

Back to top		OS Build 17134.556

January 15, 2019
KB4480976		Resolved
KB4487029		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 15, 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 KB4487017.

Back to top		OS Build 17134.523

January 08, 2019
KB4480966		Resolved
KB4487017		Resolved:
February 12, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Cannot pin a web link on the Start menu or the taskbar
After installing KB4471324, some users cannot pin a web link on the Start menu or the taskbar. 

Affected platforms:
  • Client: Windows 10, version 1803
  • Server: Windows Server, version 1803

Resolution: This issue is resolved in KB4487029. 

Back to top		OS Build 17134.471

December 11, 2018
KB4471324		Resolved
KB4487029		Resolved:
February 19, 2019
02:00 PM PT

Opened:
December 11, 2018
10:00 AM PT
" @@ -106,7 +106,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
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.\"

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
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
@@ -116,7 +116,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Unable to use Seek bar in Windows Media Player
After installing KB4462919, users may not be able to use the Seek bar in Windows Media Player when playing specific files. This issue does not affect normal playback.

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 KB4471324. 

Back to top		OS Build 17134.345

October 09, 2018
KB4462919		Resolved
KB4471324		Resolved:
December 11, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
Developer Tools (F12) fail to start in Microsoft Edge
Developer Tools (F12) may fail to start in Microsoft Edge.

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

Back to top		OS Build 17134.376

October 24, 2018
KB4462933		Resolved
KB4467702		Resolved:
November 13, 2018
10:00 AM PT

Opened:
October 24, 2018
02:00 PM PT
@@ -126,7 +126,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
@@ -137,7 +137,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
SqlConnection instantiation exception on .NET 4.6 and later
After you install the August Preview of Quality Rollup or September 11, 2018 .NET Framework update, instantiation of SqlConnection can throw an exception.  

For more information about this issue, see the following article in the Microsoft Knowledge Base: 4470809, SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.

Affected platforms:
  • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016

Resolution: This issue is resolved in KB4480976. 

Back to top		OS Build 17134.285

September 11, 2018
KB4457128		Resolved
KB4480976		Resolved:
January 15, 2019
10:00 AM PT

Opened:
September 11, 2018
10:00 AM PT
Users cannot set Win32 program defaults
After installing KB4458469, some users cannot set Win32 program defaults for certain app and file type combinations using the Open with... command or Settings > Apps > Default apps. 
 
In some cases, Microsoft Notepad or other Win32 programs cannot be set as the default.

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

Resolution: This issue is resolved in KB4467682. 

Back to top		OS Build 17134.320

September 26, 2018
KB4458469		Resolved
KB4467682		Resolved:
November 27, 2018
10:00 AM PT

Opened:
September 26, 2018
02:00 PM PT
Guest VMs running Unicast NLB fail to respond after restart
All guest virtual machines running Unicast NLB fail to respond to NLB requests after the virtual machines restart. 

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

Back to top		OS Build 17134.285

September 11, 2018
KB4457128		Resolved
KB4458469		Resolved:
September 20, 2018
10:00 AM PT

Opened:
September 11, 2018
10:00 AM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Microsoft Intune takes a long time to deliver user profiles
After installing KB4457128, Windows no longer recognizes the Personal Information exchange (PFX) certificate that's used for authenticating to a Wi-Fi or VPN connection. As a result, Microsoft Intune takes a long time to deliver user profiles because it doesn't recognize that the required certificate is on the device. 

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

Back to top		OS Build 17134.191

July 24, 2018
KB4340917		Resolved
KB4464218		Resolved:
September 17, 2018
10:00 AM PT

Opened:
July 24, 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 7f2b797115..ba10d0ec4a 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 @@ -68,7 +68,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
End-user-defined characters (EUDC) may 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

Workaround: To avoid this issue, don't enable per font EUDC. As an alternative, you can edit the registry to mitigate this issue; for more information, see KB4496149.

Resolved: This issue was resolved in KB4493509.

Back to top		OS Build 17763.404

April 02, 2019
KB4490481		Resolved
KB4493509		Resolved:
April 09, 2019
10:00 AM PT

Opened:
April 02, 2019
10:00 AM PT
" @@ -77,7 +77,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
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
" @@ -86,7 +86,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
@@ -98,7 +98,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487044, users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files. 

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 KB4489899. 

Back to top		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4489899		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
After installing KB4487044, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

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 KB4482887.

Back to top		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4482887		Resolved:
March 01, 2019
10:00 AM 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 KB4482887.

Back to top		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4482887		Resolved:
March 01, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
@@ -111,7 +111,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Internet Explorer 11 authentication issue with multiple concurrent logons
After 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		N/A

Resolved
Resolved:
March 08, 2019
11:15 AM PT

Opened:
January 29, 2019
02:00 PM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Microsoft Edge may crash or hang while playing video
nVidia has notified Microsoft of an issue where Microsoft Edge may crash or hang while playing video. This issue occurs following an nVidia driver update.

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

Resolution: nVidia has released an updated driver to address this issue. Please follow the instructions found in nVidia's support article. 

Back to top		OS Build 17763.165

December 05, 2018
KB4469342		Resolved
Resolved:
November 29, 2018
10:03 AM PT

Opened:
December 05, 2018
02:00 PM PT
" @@ -120,7 +120,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
@@ -136,7 +136,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Shared albums may not sync with iCloud for Windows
Upgrade block: Users who attempt to install iCloud for Windows (version 7.7.0.27) will see a message displayed that this version iCloud for Windows isn't supported and the install will fail.

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

To ensure a seamless experience, Microsoft is blocking devices with iCloud for Windows (version 7.7.0.27) software installed from being offered Window 10, version 1809 until this issue has been resolved. 

We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool from the Microsoft software download website until this issue is resolved. 
 
Resolution: Apple has released an updated version of iCloud for Windows (version 7.8.1) that resolves compatibility issues encountered when updating or synching Shared Albums after updating to Windows 10, version 1809. We recommend that you update your iCloud for Windows to version 7.8.1 when prompted before attempting to upgrade to Windows 10, version 1809. You can also manually download the latest version of iCloud for Windows by visiting https://support.apple.com/en-us/HT204283.

Back to top		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4482887		Resolved:
March 01, 2019
10:00 AM PT

Opened:
November 13, 2018
10:00 AM PT
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:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019

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 top		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4482887		Resolved:
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:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019

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

Back to top		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4482887		Resolved:
March 01, 2019
10:00 AM PT

Opened:
November 13, 2018
10:00 AM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Unable to use Seek bar in Windows Media Player
After installing KB4464330, users may not be able to use the Seek bar in Windows Media Player when playing specific files. This issue does not affect normal playback. 

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 KB4471332. 

Back to top		OS Build 17763.55

October 09, 2018
KB4464330		Resolved
KB4471332		Resolved:
December 11, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
Users cannot set Win32 program defaults
After installing KB4464330, some users cannot set Win32 program defaults for certain app and file type combinations using the Open with... command or Settings > Apps > Default apps.
 
In some cases, Microsoft Notepad or other Win32 programs cannot be set as the default. 

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

Resolution: This issue is resolved in KB4469342. 

Back to top		OS Build 17763.55

October 09, 2018
KB4464330		Resolved
KB4469342		Resolved:
December 05, 2018
02:00 PM PT

Opened:
October 09, 2018
10:00 AM PT
diff --git a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml index 56ce7a94dd..47a53752d1 100644 --- a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml @@ -58,7 +58,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Devices may not respond at login or Welcome screen if running certain Avast software.
Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install KB4493472 and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.

Affected platforms: 
  • Client: Windows 8.1; Windows 7, Service Pack 1 
  • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1 

Resolution: Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.

Back to top		April 09, 2019
KB4493472		Resolved
Resolved:
April 09, 2019
10:00 AM PT

Opened:
April 09, 2019
10:00 AM PT
" @@ -67,7 +67,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Custom URI schemes may not start corresponding application.
After installing KB4489878, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites 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 KB4493472.

Back to top		March 12, 2019
KB4489878		Resolved
KB4493472		Resolved:
April 09, 2019
10:00 AM PT

Opened:
March 12, 2019
10:00 AM PT
NETDOM.EXE fails to run.
After installing KB4489878, NETDOM.EXE fails to run, and the on-screen error, “The command failed to complete successfully.” appears.

Affected platforms: 
  • Client: Windows 7, Service Pack 1 
  • Server: Windows Server 2008 R2 SP1 

Resolution: This issue is resolved in KB4493472.

Back to top		March 12, 2019
KB4489878		Resolved
KB4493472		Resolved:
April 09, 2019
10:00 AM PT

Opened:
March 12, 2019
10:00 AM PT
@@ -77,7 +77,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Internet Explorer may fail to load images.
After installing KB4486563, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

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 KB4486565.

Back to top		February 12, 2019
KB4486563		Resolved
KB4486565		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 KB4486565.

Back to top		February 12, 2019
KB4486563		Resolved
KB4486565		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
@@ -87,7 +87,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
@@ -100,7 +100,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Virtual machines fail to restore.
After installing KB4480970, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).”

This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.

Affected platforms: 
  • Client: Windows 7, Service Pack 1 
  • Server: Windows Server 2008 R2 SP1 

Resolution: This issue is resolved in KB4490511.

Back to top		January 08, 2019
KB4480970		Resolved
KB4490511		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 08, 2019
10:00 AM PT
Local Administrators unable to remotely access shares.
Local users who are part of the local Administrators group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing KB4480970. This does not affect domain accounts in the local Administrators group.
 
Affected platforms: 
  • Client: Windows 7, Service Pack 1 
  • Server: Windows Server 2008 R2 SP1 

Resolution: This issue is resolved in KB4487345.

Back to top		January 08, 2019
KB4480970		Resolved
KB4487345		Resolved:
January 11, 2019
02:00 PM PT

Opened:
January 08, 2019
10:00 AM PT
Internet Explorer 11 authentication issue with multiple concurrent logons.
After installing KB4480970, 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 

Resolution: This issue is resolved in KB4493472.

Back to top		January 08, 2019
KB4480970		Resolved
KB4493472		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Event Viewer may not show some event descriptions for network interface cards.
After installing KB4462927, the Event Viewer may not show some event descriptions for network interface cards (NICs).

Affected Platforms:
  • Client: Windows 7, Service Pack 1 
  • Server: Windows Server 2008 R2 SP1 

Resolution: This issue is resolved in KB4489878.

Back to top		October 18, 2018
KB4462927		Resolved
KB4489878		Resolved:
March 12, 2019
10:00 AM PT

Opened:
October 18, 2018
10:00 AM PT
Unable to use Seek bar in Windows Media Player
After installing KB4462923, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.

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 KB4471318.

Back to top		October 09, 2018
KB4462923		Resolved
KB4471318		Resolved:
December 11, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
diff --git a/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml b/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml index ea34024180..f9888653f7 100644 --- a/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml +++ b/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml @@ -59,7 +59,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Devices may not respond at login or Welcome screen if running certain Avast software
Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install KB4493446 and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.

Affected platforms: 
  • Client: Windows 8.1; Windows 7, Service Pack 1 
  • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1 


Resolution: Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.

Back to top		April 09, 2019
KB4493446		Resolved
Resolved:
April 09, 2019
10:00 AM PT

Opened:
April 09, 2019
10:00 AM PT
" @@ -68,7 +68,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Custom URI schemes may not start corresponding application
After 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
Devices with winsock kernel client may receive error
After installing KB4489881, devices with a winsock kernel client may receive D1, FC, and other errors. Additionally, systems that run the Skype for Business or Lync Server Edge Transport role may be affected by this issue.

Affected platforms: 
  • Client: Windows 8.1 
  • Server: Windows Server 2012 R2 

Resolution: This issue is resolved in KB4489893.

Back to top		March 12, 2019
KB4489881		Resolved
KB4489893		Resolved:
March 19, 2019
10:00 AM PT

Opened:
March 12, 2019
10:00 AM PT
@@ -78,7 +78,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
@@ -89,7 +89,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color.

Affected platforms: 
  • Client: Windows 8.1 
  • Server: Windows Server 2012 R2 

Resolution: This issue is resolved in KB4493446.

Back to top		February 12, 2019
KB4487000		Resolved
KB4493446		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487016, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

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 KB4489881.

Back to top		February 19, 2019
KB4487016		Resolved
KB4489881		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 KB4487000, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

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 KB4487016.

Back to top		February 12, 2019
KB4487000		Resolved
KB4487016		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
@@ -103,7 +103,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Internet Explorer 11 authentication issue with multiple concurrent logons
After installing KB4480963, 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 

Resolution: This issue is resolved in KB4493446.

Back to top		January 08, 2019
KB4480963		Resolved
KB4493446		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 KB4480963, 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.

Resolution: This issue is resolved in KB4493446.

Back to top		January 08, 2019
KB4480963		Resolved
KB4493446		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480969, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

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 KB4487016.

Back to top		January 15, 2019
KB4480969		Resolved
KB4487016		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 15, 2019
10:00 AM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Unable to use Seek bar in Windows Media Player
After installing KB4462926, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.

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 KB4471320.

Back to top		October 09, 2018
KB4462926		Resolved
KB4471320		Resolved:
December 11, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT
" diff --git a/windows/release-information/resolved-issues-windows-server-2008-sp2.yml b/windows/release-information/resolved-issues-windows-server-2008-sp2.yml index 1b9ea0be8e..75498de24e 100644 --- a/windows/release-information/resolved-issues-windows-server-2008-sp2.yml +++ b/windows/release-information/resolved-issues-windows-server-2008-sp2.yml @@ -54,7 +54,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
diff --git a/windows/release-information/resolved-issues-windows-server-2012.yml b/windows/release-information/resolved-issues-windows-server-2012.yml index 6da451eb86..d43b402ca9 100644 --- a/windows/release-information/resolved-issues-windows-server-2012.yml +++ b/windows/release-information/resolved-issues-windows-server-2012.yml @@ -57,7 +57,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480974, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

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 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Resolution: This issue is resolved in KB4489880.

Back to top		N/A
January 17, 2019
KB4480974		Resolved
KB4489880		Resolved:
March 12, 2019
10:00 AM PT

Opened:
April 25, 2019
03:32 PM 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 the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.

Affected platforms: 
  • Client: 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 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Resolution: This issue is resolved in KB4487023.

Back to top		N/A
January 08, 2019
KB4480968		Resolved
KB4487023		Resolved:
February 12, 2019
10:00 AM PT

Opened:
April 25, 2019
03:32 PM PT
Unable to use Seek bar in Windows Media Player
After installing KB4463097, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.

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 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Resolution: This issue is resolved in KB4471325.

Back to top		N/A
October 09, 2018
KB4463097		Resolved
KB4471325		Resolved:
December 11, 2018
10:00 AM PT

Opened:
April 25, 2019
03:28 PM PT
+
DetailsAffected buildStatusHistory
diff --git a/windows/release-information/status-windows-10-1507.yml b/windows/release-information/status-windows-10-1507.yml index efe90a9f97..120633fde0 100644 --- a/windows/release-information/status-windows-10-1507.yml +++ b/windows/release-information/status-windows-10-1507.yml @@ -76,7 +76,7 @@ sections: - items: - type: markdown text: " -
DetailsOriginating updateStatusHistory
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.

Resolution: This issue is resolved in KB4487024.

Back to top		February 12, 2019
KB4487025		Resolved
KB4487024		Resolved:
February 19, 2019
02:00 PM PT

Opened:
April 25, 2019
04:04 PM PT
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480971, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Resolution: This issue is resolved in KB4487024.

Back to top		January 15, 2019
KB4480971		Resolved
KB4487024		Resolved:
February 19, 2019
02:00 PM PT

Opened:
April 25, 2019
04:01 PM PT
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color.

Resolution: This issue is resolved in KB4493451.

Back to top		February 12, 2019
KB4487025		Resolved
KB4493451		Resolved:
April 09, 2019
10:00 AM PT

Opened:
April 25, 2019
04:00 PM PT
+
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
Custom URI schemes may not start corresponding application
After installing KB4489872, Custom URI Schemes for Application Protocol handlers may not start the corresponding application for local intranet and trusted sites 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 was resolved in KB4493475.

Back to top		OS Build 10240.18158

March 12, 2019
KB4489872		Resolved
KB4493475		Resolved:
April 09, 2019
10:00 AM PT

Opened:
March 12, 2019
10:00 AM PT
" @@ -85,7 +85,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
MSXML6 may cause applications to stop responding
After installing KB4480962, 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

Resolution: This issue was resolved in KB4493475.

Back to top		OS Build 10240.18094

January 08, 2019
KB4480962		Resolved
KB4493475		Resolved:
April 09, 2019
10:00 AM 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 65c93c715a..a36fdff01f 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 @@ -82,7 +82,7 @@ sections: - items: - type: markdown text: " - +
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory
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 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:
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.

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
@@ -94,7 +94,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

       
Internet Explorer 11 authentication issue with multiple concurrent logons
After installing KB4480961, 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

Resolution: This issue was resolved in KB4493470.

Back to top		OS Build 14393.2724

January 08, 2019
KB4480961		Resolved
KB4493470		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 KB4480961, 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

Resolution: This issue was resolved in KB4493470.

Back to top		OS Build 14393.2724

January 08, 2019
KB4480961		Resolved
KB4493470		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
January 08, 2019 
10:00 AM PT

       

@@ -104,7 +104,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory

diff --git a/windows/release-information/status-windows-10-1703.yml b/windows/release-information/status-windows-10-1703.yml
index 035ac5c2c4..a7cfff3a9d 100644
--- a/windows/release-information/status-windows-10-1703.yml
+++ b/windows/release-information/status-windows-10-1703.yml
@@ -77,7 +77,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
DetailsOriginating updateStatusHistory

       
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:
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.

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:
February 19, 2019 
10:00 AM PT

Opened:
November 13, 2018 
10:00 AM PT

+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

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

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

Opened:
March 12, 2019 
10:00 AM PT

       

@@ -87,7 +87,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

       
MSXML6 may cause applications to stop responding 
After installing KB4480973, 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

Resolution: This issue was resolved in KB4493474.

Back to top		OS Build 15063.1563

January 08, 2019
KB4480973		Resolved
KB4493474		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
January 08, 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 fcddc35508..fb2e9c8c5e 100644
--- a/windows/release-information/status-windows-10-1709.yml
+++ b/windows/release-information/status-windows-10-1709.yml
@@ -78,7 +78,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory

@@ -89,7 +89,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
DetailsOriginating updateStatusHistory

       
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 is resolved in KB4493441.

Back to top		OS Build 16299.1059

March 19, 2019
KB4489890		Resolved
KB4493441		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 KB4489886, 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 is resolved in KB4493441.

Back to top		OS Build 16299.1029

March 12, 2019
KB4489886		Resolved
KB4493441		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 KB4489886, 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 16299.1029

March 12, 2019
KB4489886		Mitigated
Last updated:
March 19, 2019 
10:00 AM PT

Opened:
March 12, 2019 
10:00 AM PT

+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

       
MSXML6 causes applications to stop responding if an exception was thrown
After installing KB4480978, 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

Resolution: This issue is resolved in KB4493441.

Back to top		OS Build 16299.904

January 08, 2019
KB4480978		Resolved
KB4493441		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
January 08, 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 f311534faf..604066333a 100644
--- a/windows/release-information/status-windows-10-1803.yml
+++ b/windows/release-information/status-windows-10-1803.yml
@@ -79,7 +79,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory

@@ -92,7 +92,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
DetailsOriginating updateStatusHistory

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

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 17134.648

March 12, 2019
KB4489868		Mitigated
Last updated:
March 19, 2019 
10:00 AM PT

Opened:
March 12, 2019 
10:00 AM PT

+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

       
MSXML6 may cause applications to stop responding 
After installing KB4480966, 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

Resolution: This issue was resolved in KB4493464. 

Back to top		OS Build 17134.523

January 08, 2019
KB4480966		Resolved
KB4493464		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
January 08, 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 f38fa35c52..5e0c34357f 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
@@ -86,7 +86,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

       
End-user-defined characters (EUDC) may 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

Workaround: To avoid this issue, don't enable per font EUDC. As an alternative, you can edit the registry to mitigate this issue; for more information, see KB4496149.

Resolved: This issue was resolved in KB4493509.

Back to top		OS Build 17763.404

April 02, 2019
KB4490481		Resolved
KB4493509		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
April 02, 2019 
10:00 AM PT

       

       "
@@ -95,7 +95,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory

@@ -107,7 +107,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
DetailsOriginating updateStatusHistory

       
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 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

+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

       
Internet Explorer 11 authentication issue with multiple concurrent logons
After 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

       

@@ -117,7 +117,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

       
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

       

       "
diff --git a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml
index 7d740a94cb..b09a3aac6f 100644
--- a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml
+++ b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml
@@ -84,7 +84,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory

@@ -96,7 +96,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
DetailsOriginating updateStatusHistory

       
System may be unresponsive after restart if Avira antivirus software installed.
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493472.

Microsoft has temporarily blocked devices from receiving this update if Avira antivirus software is installed.

Next steps: We are presently investigating this issue with Avira and will provide an update when available.

Back to top		April 09, 2019
KB4493472		Investigating
Last updated:
April 09, 2019 
10:00 AM PT

Opened:
April 09, 2019 
10:00 AM PT

       
System unresponsive after restart if Sophos Endpoint Protection installed.
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493472.

Microsoft has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available. 

Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

Back to top		April 09, 2019
KB4493472		Mitigated
Last updated:
April 09, 2019 
10:00 AM PT

Opened:
April 09, 2019 
10:00 AM PT

       
System may be unresponsive after restart if ArcaBit antivirus software installed.
Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493472.

Microsoft has temporarily blocked devices from receiving this update if ArcaBit antivirus software is installed.

ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.

Back to top		April 09, 2019
KB4493472		Mitigated
Last updated:
April 09, 2019 
10:00 AM PT

Opened:
April 09, 2019 
10:00 AM PT

+      
DetailsAffected buildStatusHistory

@@ -107,7 +107,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
DetailsOriginating updateStatusHistory

       
Authentication may fail for services after the Kerberos ticket expires.
After installing KB4489878, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.

Workaround: To mitigate this issue, use one of the following options:

  • Option 1: Purge the Kerberos tickets on the application server. After the Kerberos ticket expires, the issue will occur again, and you must purge the tickets again.
  • Option 2: If purging does not mitigate the issue, restart the application; for example, restart the Internet Information Services (IIS) app pool associated with the SQL server.
  • Option 3: Use constrained delegation.

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

Back to top		March 12, 2019
KB4489878		Mitigated
Last updated:
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 KB4489878, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites 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 KB4493472.

Back to top		March 12, 2019
KB4489878		Resolved
KB4493472		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
March 12, 2019 
10:00 AM PT

       
NETDOM.EXE fails to run.
After installing KB4489878, NETDOM.EXE fails to run, and the on-screen error, “The command failed to complete successfully.” appears.

Affected platforms: 
  • Client: Windows 7, Service Pack 1 
  • Server: Windows Server 2008 R2 SP1 

Resolution: This issue is resolved in KB4493472.

Back to top		March 12, 2019
KB4489878		Resolved
KB4493472		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
March 12, 2019 
10:00 AM PT

+      
DetailsAffected buildStatusHistory

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 ccc67d41d8..aec950f873 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
@@ -84,7 +84,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
DetailsOriginating updateStatusHistory

       
Virtual machines fail to restore.
After installing KB4480970, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).”

This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.

Affected platforms: 
  • Client: Windows 7, Service Pack 1 
  • Server: Windows Server 2008 R2 SP1 

Resolution: This issue is resolved in KB4490511.

Back to top		January 08, 2019
KB4480970		Resolved
KB4490511		Resolved:
February 19, 2019 
02:00 PM PT

Opened:
January 08, 2019 
10:00 AM PT

       
Local Administrators unable to remotely access shares.
Local users who are part of the local Administrators group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing KB4480970. This does not affect domain accounts in the local Administrators group.
 
Affected platforms: 
  • Client: Windows 7, Service Pack 1 
  • Server: Windows Server 2008 R2 SP1 

Resolution: This issue is resolved in KB4487345.

Back to top		January 08, 2019
KB4480970		Resolved
KB4487345		Resolved:
January 11, 2019 
02:00 PM PT

Opened:
January 08, 2019 
10:00 AM PT

       
Internet Explorer 11 authentication issue with multiple concurrent logons.
After installing KB4480970, 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 

Resolution: This issue is resolved in KB4493472.

Back to top		January 08, 2019
KB4480970		Resolved
KB4493472		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
January 08, 2019 
10:00 AM PT

+      
DetailsAffected buildStatusHistory

@@ -97,7 +97,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
DetailsOriginating updateStatusHistory

       
System may be unresponsive after restart if Avira antivirus software installed
Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493446.

Microsoft has temporarily blocked devices from receiving this update if Avira antivirus software is installed.

Affected platforms: 
  • Client: Windows 8.1; Windows 7, Service Pack 1 
  • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1 

Next steps: We are presently investigating this issue with Avira and will provide an update when available.

Back to top		April 09, 2019
KB4493446		Investigating
Last updated:
April 09, 2019 
10:00 AM PT

Opened:
April 09, 2019 
10:00 AM PT

       
System unresponsive after restart if Sophos Endpoint Protection installed
Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493446.

Microsoft has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available. 

Affected platforms: 
  • Client: Windows 8.1; Windows 7, Service Pack 1 
  • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1 

Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

Back to top		April 09, 2019
KB4493446		Mitigated
Last updated:
April 09, 2019 
10:00 AM PT

Opened:
April 09, 2019 
10:00 AM PT

       
System may be unresponsive after restart if ArcaBit antivirus software installed
Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493446.

Microsoft has temporarily blocked devices from receiving this update if ArcaBit antivirus software is installed. 

Affected platforms: 
  • Client: Windows 8.1; Windows 7, Service Pack 1 
  • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1 

ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.

Back to top		April 09, 2019
KB4493446		Mitigated
Last updated:
April 09, 2019 
10:00 AM PT

Opened:
April 09, 2019 
10:00 AM PT

+      
DetailsAffected buildStatusHistory

@@ -108,7 +108,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
DetailsOriginating updateStatusHistory

       
Issue using PXE to start a device from WDS
After 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

       
Custom URI schemes may not start corresponding application
After 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

+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

       
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color.

Affected platforms: 
  • Client: Windows 8.1 
  • Server: Windows Server 2012 R2 

Resolution: This issue is resolved in KB4493446.

Back to top		February 12, 2019
KB4487000		Resolved
KB4493446		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
February 12, 2019 
10:00 AM PT

       

       "
@@ -117,7 +117,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

       
Internet Explorer 11 authentication issue with multiple concurrent logons
After installing KB4480963, 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 

Resolution: This issue is resolved in KB4493446.

Back to top		January 08, 2019
KB4480963		Resolved
KB4493446		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 KB4480963, 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.

Resolution: This issue is resolved in KB4493446.

Back to top		January 08, 2019
KB4480963		Resolved
KB4493446		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
January 08, 2019 
10:00 AM PT

       

diff --git a/windows/release-information/status-windows-server-2008-sp2.yml b/windows/release-information/status-windows-server-2008-sp2.yml
index 3fe98de4f9..6949f4fbc1 100644
--- a/windows/release-information/status-windows-server-2008-sp2.yml
+++ b/windows/release-information/status-windows-server-2008-sp2.yml
@@ -85,7 +85,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
+      
DetailsAffected buildStatusHistory

diff --git a/windows/release-information/status-windows-server-2012.yml b/windows/release-information/status-windows-server-2012.yml
index 11a37d5e1a..f87dab169b 100644
--- a/windows/release-information/status-windows-server-2012.yml
+++ b/windows/release-information/status-windows-server-2012.yml
@@ -89,7 +89,7 @@ sections:
 - items:
   - type: markdown
     text: "
-      
DetailsOriginating updateStatusHistory

       
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480974, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

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 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Resolution: This issue is resolved in KB4489880.

Back to top		N/A 
January 17, 2019
KB4480974		Resolved
KB4489880		Resolved:
March 12, 2019 
10:00 AM PT

Opened:
April 25, 2019 
03:32 PM 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 the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.

Affected platforms: 
  • Client: 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 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Resolution: This issue is resolved in KB4487023.

Back to top		N/A 
January 08, 2019
KB4480968		Resolved
KB4487023		Resolved:
February 12, 2019 
10:00 AM PT

Opened:
April 25, 2019 
03:32 PM PT

       
Unable to use Seek bar in Windows Media Player
After installing KB4463097, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.

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 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Resolution: This issue is resolved in KB4471325.

Back to top		N/A 
October 09, 2018
KB4463097		Resolved
KB4471325		Resolved:
December 11, 2018 
10:00 AM PT

Opened:
April 25, 2019 
03:28 PM PT

+      
DetailsAffected buildStatusHistory
DetailsOriginating updateStatusHistory

       
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.

Resolution: This issue is resolved in KB4487024.

Back to top		February 12, 2019
KB4487025		Resolved
KB4487024		Resolved:
February 19, 2019 
02:00 PM PT

Opened:
April 25, 2019 
04:04 PM PT

       
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480971, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Resolution: This issue is resolved in KB4487024.

Back to top		January 15, 2019
KB4480971		Resolved
KB4487024		Resolved:
February 19, 2019 
02:00 PM PT

Opened:
April 25, 2019 
04:01 PM PT

       
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color.

Resolution: This issue is resolved in KB4493451.

Back to top		February 12, 2019
KB4487025		Resolved
KB4493451		Resolved:
April 09, 2019 
10:00 AM PT

Opened:
April 25, 2019 
04:00 PM PT