diff --git a/windows/release-information/resolved-issues-windows-10-1507.yml b/windows/release-information/resolved-issues-windows-10-1507.yml index 58571e71cc..a7211ef42d 100644 --- a/windows/release-information/resolved-issues-windows-10-1507.yml +++ b/windows/release-information/resolved-issues-windows-10-1507.yml @@ -43,7 +43,6 @@ sections:
Applications using Microsoft Jet database fail to open
Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.

See details >OS Build 10240.18094

January 08, 2019
KB4480962Resolved
KB4487018February 12, 2019
10:00 AM PT
Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.

See details >OS Build 10240.18094

January 08, 2019
KB4480962Resolved
KB4487018February 12, 2019
10:00 AM PT
Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.

See details >OS Build 10240.18005

October 09, 2018
KB4462922Resolved
KB4471323December 11, 2018
10:00 AM 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.

See details >OS Build 10240.17976

September 11, 2018
KB4457132Resolved
KB4462922October 09, 2018
10:00 AM PT " @@ -104,12 +103,3 @@ sections:
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:
Resolution: This issue is resolved in KB4471323.

Back to topOS Build 10240.18005

October 09, 2018
KB4462922Resolved
KB4471323Resolved:
December 11, 2018
10:00 AM PT

Opened:
October 09, 2018
10:00 AM PT " - -- title: September 2018 -- items: - - type: markdown - text: " - - -
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; Windows 10 Enterprise LTSB 2015
  • 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 05e0114961..798e737b38 100644 --- a/windows/release-information/resolved-issues-windows-10-1607.yml +++ b/windows/release-information/resolved-issues-windows-10-1607.yml @@ -52,8 +52,6 @@ sections:
Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.

See details >OS Build 14393.2724

January 08, 2019
KB4480961Resolved
KB4480977January 17, 2019
02:00 PM 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.

See details >OS Build 14393.2639

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

See details >OS Build 14393.2551

October 09, 2018
KB4462917Resolved
KB4471321December 11, 2018
10:00 AM PT -
Issues with install and activation of Key Management Service (KMS) (CSVLK) host keys
Installation and client activation of Windows Server 2019 and 1809 LTSC Key Management Service (KMS) (CSVLK) host keys do not work as expected.

See details >OS Build 14393.2457

August 30, 2018
KB4343884Resolved
KB4467684November 27, 2018
10:00 AM PT -
Promotions that create non-root domains fail with optional features enabled
Windows Server 2016 promotions that create non-root domains fail in forests in which optional features like Active Directory recycle have been enabled.

See details >OS Build 14393.2515

September 20, 2018
KB4457127Resolved
KB4467684November 27, 2018
10:00 AM PT " @@ -139,21 +137,11 @@ sections: " -- title: September 2018 -- items: - - type: markdown - text: " - - -
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:
  • 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
- " - - title: August 2018 - 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, version 1607; 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, version 1607; 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 942229c994..acba0087a9 100644 --- a/windows/release-information/resolved-issues-windows-10-1703.yml +++ b/windows/release-information/resolved-issues-windows-10-1703.yml @@ -47,8 +47,6 @@ sections:
SqlConnection instantiation exception on .NET 4.6 and later
Instantiation of SqlConnection can throw an exception after certain updates have been installed.

See details >OS Build 15063.1292

August 30, 2018
KB4343889Resolved
KB4480959January 15, 2019
10:00 AM PT
Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.

See details >OS Build 15063.1563

January 08, 2019
KB4480973Resolved
KB4480959January 15, 2019
10:00 AM PT
Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.

See details >OS Build 15063.1387

October 09, 2018
KB4462937Resolved
KB4471327December 11, 2018
10:00 AM PT -
LongonUI.exe stops working intermittently
LongonUI.exe stops working intermittently.

See details >OS Build 15063.1387

October 09, 2018
KB4462937Resolved
KB4467699November 27, 2018
10:00 AM PT -
Error message beginning with “Hosted by…” when launching Microsoft Edge
Some users may encounter an error message beginning with “Hosted by…” when launching Microsoft Edge.

See details >OS Build 15063.1387

October 09, 2018
KB4462937Resolved
KB4462939October 18, 2018
10:00 AM PT " @@ -110,8 +108,6 @@ sections: 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, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • 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 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
" diff --git a/windows/release-information/resolved-issues-windows-10-1709.yml b/windows/release-information/resolved-issues-windows-10-1709.yml index 77cf5c8e23..9b56f0e53f 100644 --- a/windows/release-information/resolved-issues-windows-10-1709.yml +++ b/windows/release-information/resolved-issues-windows-10-1709.yml @@ -49,7 +49,6 @@ sections:
SqlConnection instantiation exception on .NET 4.6 and later
Instantiation of SqlConnection can throw an exception after certain updates have been installed.

See details >OS Build 16299.637

August 30, 2018
KB4343893Resolved
KB4480967January 15, 2019
10:00 AM PT
Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.

See details >OS Build 16299.904

January 08, 2019
KB4480978Resolved
KB4480967January 15, 2019
10:00 AM PT
Unable to use Seek bar in Windows Media Player
Users may not be able to use the Seek bar in Windows Media Player when playing specific files.

See details >OS Build 16299.726

October 09, 2018
KB4462918Resolved
KB4471329December 11, 2018
10:00 AM PT -
Error message beginning with “Hosted by…” when launching Microsoft Edge
Some users may encounter an error message beginning with “Hosted by…” when launching Microsoft Edge.

See details >OS Build 16299.726

October 09, 2018
KB4462918Resolved
KB4462932October 18, 2018
10:00 AM PT " @@ -121,7 +120,6 @@ sections: text: " -
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, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • 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 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
" diff --git a/windows/release-information/resolved-issues-windows-10-1803.yml b/windows/release-information/resolved-issues-windows-10-1803.yml index 42be5f674b..04cb4d25e1 100644 --- a/windows/release-information/resolved-issues-windows-10-1803.yml +++ b/windows/release-information/resolved-issues-windows-10-1803.yml @@ -51,10 +51,6 @@ sections:
Blue or black screen with \"System thread exception not handled\" error
Some users may get a blue or black screen with the error code, “System thread exception not handled.”

See details >OS Build 17134.441

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

See details >OS Build 17134.441

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

See details >OS Build 17134.345

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

See details >OS Build 17134.320

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

See details >OS Build 17134.376

October 24, 2018
KB4462933Resolved
KB4467702November 13, 2018
10:00 AM PT -
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.

See details >OS Build 17134.285

September 11, 2018
KB4457128Resolved
KB4458469September 26, 2018
10:00 AM PT -
Microsoft Intune takes a long time to deliver user profiles
Windows no longer recognizes the Personal Information exchange (PFX) certificate used for Wi-Fi or VPN authentication, causing delays in Microsoft Intune delivering user profiles.

See details >OS Build 17134.191

July 24, 2018
KB4340917Resolved
KB4464218September 17, 2018
10:00 AM PT " @@ -144,7 +140,6 @@ sections: text: " -
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, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • 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 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
" @@ -154,16 +149,5 @@ sections: 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, version 1607; 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; Windows 10 Enterprise LTSB 2015
  • 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 26, 2018
10:00 AM PT

Opened:
September 11, 2018
10:00 AM PT
- " - -- title: July 2018 -- items: - - type: markdown - text: " - -
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 49d4e3e4e0..34ef2a1b15 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 @@ -59,10 +59,6 @@ sections:
Unable to access hotspots with third-party applications
Third-party applications may have difficulty authenticating hotspots.

See details >OS Build 17763.253

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

See details >OS Build 17763.55

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

See details >OS Build 17763.134

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

See details >OS Build 17763.134

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

See details >OS Build 17763.55

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

See details >OS Build 17763.134

November 13, 2018
KB4467708Resolved
KB4469342December 05, 2018
02:00 PM PT -
Microsoft Edge may crash or hang while playing video
Following an nVidia driver update, Microsoft Edge may crash or hang while playing video.

See details >OS Build 17763.134

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

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

Back to topOS Build 17763.134

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

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

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

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

Back to topOS Build 17763.134

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

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

Affected platforms:
Resolution: This issue was resolved in KB4468550 and the upgrade block removed. 

Back to topOS Build 17763.134

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

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

Affected platforms:
Resolution: Morphisec and Cisco have released updated versions of their applications to address this issue. We recommend customers update to these minimum versions before attempting to attempting to upgrade to Windows 10, version 1809:
An upgrade block remains in place for earlier versions of the applications than those listed above.

Back to topOS Build 17763.134

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

Opened:
November 13, 2018
10:00 AM PT -
Mapped drives fail to reconnect after login
Upgrade block: Network drives may fail to reconnect after booting and logging on to a Windows device. Symptoms include:  
Affected platforms:
Resolution: This issue was resolved in KB4469342 and the upgrade block removed. 

Back to topOS Build 17763.134

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

Opened:
November 13, 2018
10:00 AM PT -
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:
Resolution: nVidia has released an updated driver to address this issue. Please follow the instructions found in nVidia's support article. 

Back to topOS Build 17763.134

November 13, 2018
KB4467708Resolved
Resolved:
December 05, 2018
10:00 AM PT

Opened:
November 13, 2018
10:00 AM PT " @@ -156,6 +149,5 @@ sections: text: " -
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, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • 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 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/status-windows-10-1607-and-windows-server-2016.yml b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml index 1eca3ca4f5..9a76c08ad3 100644 --- a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml +++ b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

- + @@ -87,7 +87,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

See details >		OS Build 14393.2999

May 23, 2019
KB4499177		Mitigated
June 05, 2019
05:54 PM PT
Opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

See details >		OS Build 14393.2999

May 23, 2019
KB4499177		Mitigated
June 05, 2019
07:51 PM PT
Some applications may fail to run as expected on clients of AD FS 2016
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016)

See details >		OS Build 14393.2941

April 25, 2019
KB4493473		Mitigated
June 04, 2019
05:55 PM PT
Devices running Windows Server 2016 with Hyper-V seeing Bitlocker error 0xC0210000
Some devices running Windows Server with Hyper-V enabled may start into Bitlocker recovery with error 0xC0210000

See details >		OS Build 14393.2969

May 14, 2019
KB4494440		Mitigated
May 23, 2019
09:57 AM PT
Cluster service may fail if the minimum password length is set to greater than 14
The cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters.

See details >		OS Build 14393.2639

November 27, 2018
KB4467684		Mitigated
April 25, 2019
02:00 PM PT
- +
DetailsOriginating updateStatusHistory
opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

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 1607
  • Server: Windows Server 2019; Windows Server 2016
Workaround: To set the Default Search Provider, use the following steps:
  1. Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
  2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
  3. Select Search Providers in left pane.
  4. Select the link Find more search providers in the bottom left of the dialog.
  5. A new Internet Explorer window should open, allowing you to select a search provider.
  6. Select Add under the Search Provider you prefer.
  7. The Add Search Provider dialog should open, select Add.
  8. You should now be able to open Internet Explorer 11 normally.

Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Back to top		OS Build 14393.2999

May 23, 2019
KB4499177		Mitigated
Last updated:
June 05, 2019
05:54 PM PT

Opened:
June 05, 2019
05:49 PM PT
Opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

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 1607
  • Server: Windows Server 2019; Windows Server 2016
Workaround: To set the Default Search Provider, use the following steps:
  1. Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
  2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
  3. Select Search Providers in left pane.
  4. Select the link Find more search providers in the bottom left of the dialog.
  5. A new Internet Explorer window should open, allowing you to select a search provider.
  6. Select Add under the Search Provider you prefer.
  7. The Add Search Provider dialog should open, select Add.
  8. You should now be able to open Internet Explorer 11 normally.

Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Back to top		OS Build 14393.2999

May 23, 2019
KB4499177		Mitigated
Last updated:
June 05, 2019
07:51 PM PT

Opened:
June 05, 2019
05:49 PM PT
Some applications may fail to run as expected on clients of AD FS 2016
Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of KB4493473 on the server. Applications that may exhibit this behavior use an IFRAME during non-interactive authentication requests and receive X-Frame Options set to DENY.

Affected platforms:
  • Server: Windows Server 2016
Workaround: You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue \"allow-from https://example.com\"

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

Back to top		OS Build 14393.2941

April 25, 2019
KB4493473		Mitigated
Last updated:
June 04, 2019
05:55 PM PT

Opened:
June 04, 2019
05:55 PM PT
" diff --git a/windows/release-information/status-windows-10-1703.yml b/windows/release-information/status-windows-10-1703.yml index d2bbefcfbd..9fd4e8cbe6 100644 --- a/windows/release-information/status-windows-10-1703.yml +++ b/windows/release-information/status-windows-10-1703.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

- + @@ -79,7 +79,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

See details >		OS Build 15063.1839

May 28, 2019
KB4499162		Mitigated
June 05, 2019
05:54 PM PT
Opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

See details >		OS Build 15063.1839

May 28, 2019
KB4499162		Mitigated
June 05, 2019
07:51 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

See details >		OS Build 15063.1563

January 08, 2019
KB4480973		Mitigated
April 25, 2019
02:00 PM PT
Unable to access some gov.uk websites
gov.uk websites that don’t support “HSTS” may not be accessible

See details >		OS Build 15063.1805

May 14, 2019
KB4499181		Resolved
KB4505055		May 19, 2019
02:00 PM PT
Layout and cell size of Excel sheets may change when using MS UI Gothic
When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

See details >		OS Build 15063.1784

April 25, 2019
KB4493436		Resolved
KB4499181		May 14, 2019
10:00 AM PT
- +
DetailsOriginating updateStatusHistory
opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

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 1607
  • Server: Windows Server 2019; Windows Server 2016
Workaround: To set the Default Search Provider, use the following steps:
  1. Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
  2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
  3. Select Search Providers in left pane.
  4. Select the link Find more search providers in the bottom left of the dialog.
  5. A new Internet Explorer window should open, allowing you to select a search provider.
  6. Select Add under the Search Provider you prefer.
  7. The Add Search Provider dialog should open, select Add.
  8. You should now be able to open Internet Explorer 11 normally.

Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Back to top		OS Build 15063.1839

May 28, 2019
KB4499162		Mitigated
Last updated:
June 05, 2019
05:54 PM PT

Opened:
June 05, 2019
05:49 PM PT
Opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

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 1607
  • Server: Windows Server 2019; Windows Server 2016
Workaround: To set the Default Search Provider, use the following steps:
  1. Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
  2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
  3. Select Search Providers in left pane.
  4. Select the link Find more search providers in the bottom left of the dialog.
  5. A new Internet Explorer window should open, allowing you to select a search provider.
  6. Select Add under the Search Provider you prefer.
  7. The Add Search Provider dialog should open, select Add.
  8. You should now be able to open Internet Explorer 11 normally.

Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Back to top		OS Build 15063.1839

May 28, 2019
KB4499162		Mitigated
Last updated:
June 05, 2019
07:51 PM PT

Opened:
June 05, 2019
05:49 PM PT
" diff --git a/windows/release-information/status-windows-10-1709.yml b/windows/release-information/status-windows-10-1709.yml index 3e277103e3..f02eb933d8 100644 --- a/windows/release-information/status-windows-10-1709.yml +++ b/windows/release-information/status-windows-10-1709.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

- + @@ -80,7 +80,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

See details >		OS Build 16299.1182

May 28, 2019
KB4499147		Mitigated
June 05, 2019
05:54 PM PT
Opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

See details >		OS Build 16299.1182

May 28, 2019
KB4499147		Mitigated
June 05, 2019
07:51 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

See details >		OS Build 16299.904

January 08, 2019
KB4480978		Mitigated
April 25, 2019
02:00 PM PT
Unable to access some gov.uk websites
gov.uk websites that don’t support “HSTS” may not be accessible

See details >		OS Build 16299.1143

May 14, 2019
KB4498946		Resolved
KB4505062		May 19, 2019
02:00 PM PT
Layout and cell size of Excel sheets may change when using MS UI Gothic
When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

See details >		OS Build 16299.1127

April 25, 2019
KB4493440		Resolved
KB4499179		May 14, 2019
10:00 AM PT
- +
DetailsOriginating updateStatusHistory
opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

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 1607
  • Server: Windows Server 2019; Windows Server 2016
Workaround: To set the Default Search Provider, use the following steps:
  1. Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
  2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
  3. Select Search Providers in left pane.
  4. Select the link Find more search providers in the bottom left of the dialog.
  5. A new Internet Explorer window should open, allowing you to select a search provider.
  6. Select Add under the Search Provider you prefer.
  7. The Add Search Provider dialog should open, select Add.
  8. You should now be able to open Internet Explorer 11 normally.

Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Back to top		OS Build 16299.1182

May 28, 2019
KB4499147		Mitigated
Last updated:
June 05, 2019
05:54 PM PT

Opened:
June 05, 2019
05:49 PM PT
Opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

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 1607
  • Server: Windows Server 2019; Windows Server 2016
Workaround: To set the Default Search Provider, use the following steps:
  1. Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
  2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
  3. Select Search Providers in left pane.
  4. Select the link Find more search providers in the bottom left of the dialog.
  5. A new Internet Explorer window should open, allowing you to select a search provider.
  6. Select Add under the Search Provider you prefer.
  7. The Add Search Provider dialog should open, select Add.
  8. You should now be able to open Internet Explorer 11 normally.

Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Back to top		OS Build 16299.1182

May 28, 2019
KB4499147		Mitigated
Last updated:
June 05, 2019
07:51 PM PT

Opened:
June 05, 2019
05:49 PM PT
" diff --git a/windows/release-information/status-windows-10-1803.yml b/windows/release-information/status-windows-10-1803.yml index b1d61c3a2b..f2d6cb0948 100644 --- a/windows/release-information/status-windows-10-1803.yml +++ b/windows/release-information/status-windows-10-1803.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

- + @@ -81,7 +81,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

See details >		OS Build 17134.799

May 21, 2019
KB4499183		Mitigated
June 05, 2019
05:54 PM PT
Opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

See details >		OS Build 17134.799

May 21, 2019
KB4499183		Mitigated
June 05, 2019
07:51 PM PT
Issue using PXE to start a device from WDS
Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.

See details >		OS Build 17134.648

March 12, 2019
KB4489868		Mitigated
April 25, 2019
02:00 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

See details >		OS Build 17134.523

January 08, 2019
KB4480966		Mitigated
April 25, 2019
02:00 PM PT
Unable to access some gov.uk websites
gov.uk websites that don’t support “HSTS” may not be accessible

See details >		OS Build 17134.765

May 14, 2019
KB4499167		Resolved
KB4505064		May 19, 2019
02:00 PM PT
- +
DetailsOriginating updateStatusHistory
opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

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 1607
  • Server: Windows Server 2019; Windows Server 2016
Workaround: To set the Default Search Provider, use the following steps:
  1. Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
  2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
  3. Select Search Providers in left pane.
  4. Select the link Find more search providers in the bottom left of the dialog.
  5. A new Internet Explorer window should open, allowing you to select a search provider.
  6. Select Add under the Search Provider you prefer.
  7. The Add Search Provider dialog should open, select Add.
  8. You should now be able to open Internet Explorer 11 normally.

Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Back to top		OS Build 17134.799

May 21, 2019
KB4499183		Mitigated
Last updated:
June 05, 2019
05:54 PM PT

Opened:
June 05, 2019
05:49 PM PT
Opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

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 1607
  • Server: Windows Server 2019; Windows Server 2016
Workaround: To set the Default Search Provider, use the following steps:
  1. Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
  2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
  3. Select Search Providers in left pane.
  4. Select the link Find more search providers in the bottom left of the dialog.
  5. A new Internet Explorer window should open, allowing you to select a search provider.
  6. Select Add under the Search Provider you prefer.
  7. The Add Search Provider dialog should open, select Add.
  8. You should now be able to open Internet Explorer 11 normally.

Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Back to top		OS Build 17134.799

May 21, 2019
KB4499183		Mitigated
Last updated:
June 05, 2019
07:51 PM PT

Opened:
June 05, 2019
05:49 PM 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 637ed14d71..dabae3539b 100644 --- a/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml +++ b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml @@ -65,7 +65,7 @@ sections: - type: markdown text: "
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

- + @@ -92,7 +92,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

See details >		OS Build 17763.529

May 21, 2019
KB4497934		Mitigated
June 05, 2019
05:54 PM PT
Opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

See details >		OS Build 17763.529

May 21, 2019
KB4497934		Mitigated
June 05, 2019
07:51 PM PT
Devices with some Asian language packs installed may receive an error
After installing the KB4493509 devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_F

See details >		OS Build 17763.437

April 09, 2019
KB4493509		Mitigated
May 03, 2019
10:59 AM PT
Printing from Microsoft Edge or other UWP apps, you may receive the error 0x80070007
Attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive an error.

See details >		OS Build 17763.379

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

See details >		OS Build 17763.379

March 12, 2019
KB4489899		Mitigated
April 09, 2019
10:00 AM PT
- +
DetailsOriginating updateStatusHistory
opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

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 1607
  • Server: Windows Server 2019; Windows Server 2016
Workaround: To set the Default Search Provider, use the following steps:
  1. Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
  2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
  3. Select Search Providers in left pane.
  4. Select the link Find more search providers in the bottom left of the dialog.
  5. A new Internet Explorer window should open, allowing you to select a search provider.
  6. Select Add under the Search Provider you prefer.
  7. The Add Search Provider dialog should open, select Add.
  8. You should now be able to open Internet Explorer 11 normally.

Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Back to top		OS Build 17763.529

May 21, 2019
KB4497934		Mitigated
Last updated:
June 05, 2019
05:54 PM PT

Opened:
June 05, 2019
05:49 PM PT
Opening Internet Explorer 11 may fail
Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.

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 1607
  • Server: Windows Server 2019; Windows Server 2016
Workaround: To set the Default Search Provider, use the following steps:
  1. Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
  2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
  3. Select Search Providers in left pane.
  4. Select the link Find more search providers in the bottom left of the dialog.
  5. A new Internet Explorer window should open, allowing you to select a search provider.
  6. Select Add under the Search Provider you prefer.
  7. The Add Search Provider dialog should open, select Add.
  8. You should now be able to open Internet Explorer 11 normally.

Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Back to top		OS Build 17763.529

May 21, 2019
KB4497934		Mitigated
Last updated:
June 05, 2019
07:51 PM PT

Opened:
June 05, 2019
05:49 PM PT
" diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index ec803d2fa7..bc340b7f1a 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -21,8 +21,8 @@ sections: Find information on known issues for Windows 10, version 1903 and Windows Server, version 1903. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). -
Current status:
-
Windows 10, version 1903 is available by manually selecting “Check for updates” via Windows Update. (Note We are slowly throttling up this availability while we carefully monitor data and feedback.) The recommended servicing status is Semi-Annual Channel.
+		Current status as of June 6, 2019:
+
Windows 10, version 1903 is available for any user who manually selects “Check for updates” via Windows Update. The recommended servicing status is Semi-Annual Channel.
Note follow @WindowsUpdate to find out when new content is published to the release information dashboard.
" @@ -65,20 +65,20 @@ sections: - type: markdown text: "
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

- + - - - - - + + + + +
SummaryOriginating updateStatusLast updated
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Acknowledged
May 24, 2019
04:20 PM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
June 06, 2019
11:05 AM PT
Loss of functionality in Dynabook Smartphone Link app
After updating to Windows 10, version 1903, you may experience a loss of functionality when using the Dynabook Smartphone Link application.

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
May 24, 2019
03:10 PM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Investigating
May 21, 2019
04:47 PM PT
Audio not working with Dolby Atmos headphones and home theater
Users may experience audio loss with Dolby Atmos headphones or Dolby Atmos home theater.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Investigating
May 21, 2019
07:17 AM PT
Duplicate folders and documents showing in user profile directory
If known folders (e.g. Desktop, Documents, or Pictures folders) are redirected, an empty folder with that same name may be created.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Investigating
May 21, 2019
07:16 AM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 24, 2019
11:02 AM PT
AMD RAID driver incompatibility
Installation process may stop when trying to install Windows 10, version 1903 update on computers that run certain versions of AMD RAID drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 23, 2019
09:28 AM PT
Error attempting to update with external USB device or memory card attached
PCs with an external USB device or SD memory card attached may get error: \"This PC can't be upgraded to Windows 10.\"

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:49 PM PT
Unable to discover or connect to Bluetooth devices
Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:48 PM PT
Intel Audio displays an intcdaud.sys notification
Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:47 PM PT
Cannot launch Camera app
Microsoft and Intel have identified an issue affecting Intel RealSense SR300 or Intel RealSense S200 camera apps.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:47 PM PT
Intermittent loss of Wi-Fi connectivity
Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:46 PM PT
D3D applications and games may fail to enter full-screen mode on rotated displays
Some Direct3D (D3D) applications and games may fail to enter full-screen mode on rotated displays.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:45 PM PT
Older versions of BattlEye anti-cheat software incompatible
Microsoft and BattlEye have identified a compatibility issue with some games that use older versions of BattlEye anti-cheat software.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
07:34 AM PT
Duplicate folders and documents showing in user profile directory
If known folders (e.g. Desktop, Documents, or Pictures folders) are redirected, an empty folder with that same name may be created.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4497935		May 29, 2019
02:00 PM PT
AMD RAID driver incompatibility
Installation process may stop when trying to install Windows 10, version 1903 update on computers that run certain versions of AMD RAID drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
June 06, 2019
11:06 AM PT
Error attempting to update with external USB device or memory card attached
PCs with an external USB device or SD memory card attached may get error: \"This PC can't be upgraded to Windows 10.\"

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4497935		May 29, 2019
02:00 PM PT
D3D applications and games may fail to enter full-screen mode on rotated displays
Some Direct3D (D3D) applications and games may fail to enter full-screen mode on rotated displays.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4497935		May 29, 2019
02:00 PM PT
Older versions of BattlEye anti-cheat software incompatible
Microsoft and BattlEye have identified a compatibility issue with some games that use older versions of BattlEye anti-cheat software.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
June 06, 2019
11:04 AM PT
" @@ -94,19 +94,19 @@ sections: - type: markdown text: " - + - - - - - + + + + +
DetailsOriginating updateStatusHistory
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution and estimate a solution will be available in late June.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Acknowledged
Last updated:
May 24, 2019
04:20 PM PT

Opened:
May 24, 2019
04:20 PM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution and estimate a solution will be available mid-to-late June.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
Last updated:
June 06, 2019
11:05 AM PT

Opened:
May 24, 2019
04:20 PM PT
Loss of functionality in Dynabook Smartphone Link app
Some users may experience a loss of functionality after updating to Windows 10, version 1903 when using the Dynabook Smartphone Link application on Windows devices. Loss of functionality may affect the display of phone numbers in the Call menu and the ability to answer phone calls on the Windows PC.

To safeguard your update experience, we have applied a compatibility hold on devices with Dynabook Smartphone Link from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: Microsoft and Dynabook are working on a resolution; the Dynabook Smartphone Link application may have a loss of functionality until this issue is resolved.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
Last updated:
May 24, 2019
03:10 PM PT

Opened:
May 24, 2019
03:10 PM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Window 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change.

To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: Restart your device to apply changes to brightness.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution that will be made available in upcoming release.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Investigating
Last updated:
May 21, 2019
04:47 PM PT

Opened:
May 21, 2019
07:56 AM PT
Audio not working with Dolby Atmos headphones and home theater
After updating to Windows 10, version 1903, you may experience loss of audio with Dolby Atmos for home theater (free extension) or Dolby Atmos for headphones (paid extension) acquired through the Microsoft Store due to a licensing configuration error.
 
This occurs due to an issue with a Microsoft Store licensing component, where license holders are not able to connect to the Dolby Access app and enable Dolby Atmos extensions.
 
To safeguard your update experience, we have applied protective hold on devices from being offered Windows 10, version 1903 until this issue is resolved. This configuration error will not result in loss of access for the acquired license once the problem is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution for Microsoft Store and estimate a solution will be available in mid-June.
Note We recommend you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. 

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Investigating
Last updated:
May 21, 2019
07:17 AM PT

Opened:
May 21, 2019
07:16 AM PT
Duplicate folders and documents showing in user profile directory
If you have redirected known folders (e.g. Desktop, Documents, or Pictures folders) you may see an empty folder with the same name in your %userprofile% directories after updating to Windows 10, version 1903. This may occur if known folders were redirected when you chose to back up your content to OneDrive using the OneDrive wizard, or if you chose to back up your content during the Windows Out-of-Box-Experience (OOBE). This may also occur if you redirected your known folders manually through the Properties dialog box in File Explorer. ​This issue does not cause any user files to be deleted and a solution is in progress.

To safeguard your update experience, we have applied a quality hold on devices with redirected known folders from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: Microsoft is working on a resolution and estimates a solution will be available in late May.
Note We recommend that you do not attempt to manually update to Windows 10, version 1903 using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Investigating
Last updated:
May 21, 2019
07:16 AM PT

Opened:
May 21, 2019
07:16 AM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

Microsoft has identified some scenarios where night light settings may stop working, for example:
  • Connecting to (or disconnecting from) an external monitor, dock, or projector
  • Rotating the screen
  • Updating display drivers or making other display mode changes
  • Closing full screen applications
  • Applying custom color profiles
  • Running applications that rely on custom gamma ramps
Affected platforms:
  • Client: Windows 10, version 1903
Workaround: If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer. For other color setting issues, restart your computer to correct the issue.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

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

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 24, 2019
11:02 AM PT

Opened:
May 21, 2019
07:28 AM PT
AMD RAID driver incompatibility
Microsoft and AMD have identified an incompatibility with AMD RAID driver versions earlier than 9.2.0.105. When you attempt to install the Windows 10, version 1903 update on a Windows 10-based computer with an affected driver version, the installation process stops and you get a message like the following:

AMD Ryzen™ or AMD Ryzen™ Threadripper™ configured in SATA or NVMe RAID mode.

“A driver is installed that causes stability problems on Windows. This driver will be disabled. Check with your software/driver provider for an updated version that runs on this version of Windows.”

 
To safeguard your update experience, we have applied a compatibility hold on devices with these AMD drivers from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: To resolve this issue, download the latest AMD RAID drivers directly from AMD at https://www.amd.com/en/support/chipsets/amd-socket-tr4/x399. The drivers must be version 9.2.0.105 or later. Install the drivers on the affected computer, and then restart the installation process for the Windows 10, version 1903 feature update.
 
Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.
 

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 23, 2019
09:28 AM PT

Opened:
May 21, 2019
07:12 AM PT
Error attempting to update with external USB device or memory card attached
If you have an external USB device or SD memory card attached when installing Windows 10, version 1903, you may get an error message stating \"This PC can't be upgraded to Windows 10.\" This is caused by inappropriate drive reassignment during installation.

Sample scenario: An update to Windows 10, version 1903 is attempted on a computer that has a thumb drive inserted into its USB port. Before the update, the thumb drive is mounted in the system as drive G based on the existing drive configuration. After the feature update is installed; however, the device is reassigned a different drive letter (e.g., drive H).

Note The drive reassignment is not limited to removable drives. Internal hard drives may also be affected.

To safeguard your update experience, we have applied a hold on devices with an external USB device or SD memory card attached from being offered Windows 10, version 1903 until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: To work around this issue, remove all external media, such as USB devices and SD cards, from your computer and restart installation of the Windows 10, version 1903 feature update. The update should then proceed normally.
Note If you need to keep your external device, SD memory card, or other devices attached to your computer while updating, we recommend that you do not attempt to manually update to Windows 10, version 1903 using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: Microsoft is working on a resolution and estimate a solution will be available in late May.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 21, 2019
04:49 PM PT

Opened:
May 21, 2019
07:38 AM PT
Unable to discover or connect to Bluetooth devices
Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Realtek and Qualcomm. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Realtek or Qualcomm Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Workaround: Check with your device manufacturer (OEM) to see if an updated driver is available and install it.

  • For Qualcomm drivers, you will need to install a driver version greater than 10.0.1.11.
  • For Realtek drivers, you will need to install a driver version greater than 1.5.1011.0.
Note Until an updated driver has been installed, we recommend you do not attempt to manually update using the Update now button or the Media Creation Tool. 

Next steps: Microsoft is working with Realtek and Qualcomm to release new drivers for all affected system via Windows Update.  


Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 21, 2019
04:48 PM PT

Opened:
May 21, 2019
07:29 AM PT
Intel Audio displays an intcdaud.sys notification
Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in higher than normal battery drain. If you see an intcdaud.sys notification or “What needs your attention” notification when trying to update to Windows 10, version 1903, you have an affected Intel Audio Display device driver installed on your machine (intcdaud.sys, versions 10.25.0.3 through 10.25.0.8).
  
To safeguard your update experience, we have applied a compatibility hold on devices with drivers from being offered Windows 10, version 1903 until updated device drivers have been installed.

Affected platforms:
  • Client: Windows 10, version 1903; Windows 10, version 1809
Workaround:
On the “What needs your attention\" notification, click the Back button to remain on your current version of Windows 10. (Do not click Confirm as this will proceed with the update and you may experience compatibility issues.) Affected devices will automatically revert to the previous working configuration.

For more information, see Intel's customer support guidance and the Microsoft knowledge base article KB4465877.

Note We recommend you do not attempt to update your devices until newer device drivers are installed.

Next steps: You can opt to wait for newer drivers to be installed automatically through Windows Update or check with the computer manufacturer for the latest device driver software availability and installation procedures.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 21, 2019
04:47 PM PT

Opened:
May 21, 2019
07:22 AM PT
Cannot launch Camera app
Microsoft and Intel have identified an issue affecting Intel RealSense SR300 and Intel RealSense S200 cameras when using the Camera app. After updating to the Windows 10 May 2019 Update and launching the Camera app, you may get an error message stating:

\"Close other apps, error code: 0XA00F4243.”


To safeguard your update experience, we have applied a protective hold on machines with Intel RealSense SR300 or Intel RealSense S200 cameras installed from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: To temporarily resolve this issue, perform one of the following:

  • Unplug your camera and plug it back in.

or

  • Disable and re-enable the driver in Device Manager. In the Search box, type \"Device Manager\" and press Enter. In the Device Manager dialog box, expand Cameras, then right-click on any RealSense driver listed and select Disable device. Right click on the driver again and select Enable device.

or

  • Restart the RealSense service. In the Search box, type \"Task Manager\" and hit Enter. In the Task Manager dialog box, click on the Services tab, right-click on RealSense, and select Restart. 
Note This workaround will only resolve the issue until your next system restart.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

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

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 21, 2019
04:47 PM PT

Opened:
May 21, 2019
07:20 AM PT
Intermittent loss of Wi-Fi connectivity
Some older computers may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM).

To safeguard your upgrade experience, we have applied a hold on devices with this Qualcomm driver from being offered Windows 10, version 1903, until the updated driver is installed.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: Download and install an updated Wi-Fi driver from your device manufacturer (OEM).
 
Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 21, 2019
04:46 PM PT

Opened:
May 21, 2019
07:13 AM PT
D3D applications and games may fail to enter full-screen mode on rotated displays
Some Direct3D (D3D) applications and games (e.g., 3DMark) may fail to enter full-screen mode on displays where the display orientation has been changed from the default (e.g., a landscape display in portrait mode).

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Workaround: To work around this issue, do one of the following:
  • Run applications in windowed mode or, if available, on a secondary non-rotated display. 
  • Change compatibility settings for the applications to “Disable Full Screen Optimizations.”
Next steps: Microsoft is working on a resolution and estimates a solution will be available in late May.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 21, 2019
04:45 PM PT

Opened:
May 21, 2019
07:05 AM PT
Older versions of BattlEye anti-cheat software incompatible
Microsoft and BattlEye have identified a compatibility issue with some games that use older versions of BattlEye anti-cheat software. When launching a game that uses an older, impacted version of BattlEye anti-cheat software on a device running Windows 10, version 1903, the device may experience a system crash.

To safeguard your gaming experience, we have applied a compatibility hold on devices with the impacted versions of BattlEye software used by games installed on your PC. This will prevent Windows 10, version 1903 from being offered until the incompatible version of BattlEye software is no longer installed on the device. 

Affected platforms:
  • Client: Windows 10, version 1903
Mitigated: BattlEye has provided an updated patch to known impacted games. For a list of recent games that use BattlEye, go to https://www.battleye.com/.

Workaround: Before updating your machine, we recommend you do one or more of the following:

  • Verify that your game is up to date with the latest available version of BattlEye software. Some game platforms allow you to validate your game files, which can confirm that your installation is fully up to date.
  • Restart your system and open the game again.
  • Uninstall BattlEye using https://www.battleye.com/downloads/UninstallBE.exe, and then reopen your game.
  • Uninstall and reinstall your game.
For more troubleshooting options, see https://www.battleye.com/support/faq/.

Next steps: We are working with BattlEye and gaming partners to ensure games are automatically updated with the latest BattlEye software. We have confirmed the latest version of impacted games do not exhibit this issue. To minimize the chance of hitting this upgrade compatibility hold, please make sure you are running the latest version of your games before attempting to update the operating system.  
Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until you have installed an updated version of BattlEye software that resolves this issue.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 21, 2019
07:34 AM PT

Opened:
May 21, 2019
07:34 AM PT
Duplicate folders and documents showing in user profile directory
If you have redirected known folders (e.g. Desktop, Documents, or Pictures folders) you may see an empty folder with the same name in your %userprofile% directories after updating to Windows 10, version 1903. This may occur if known folders were redirected when you chose to back up your content to OneDrive using the OneDrive wizard, or if you chose to back up your content during the Windows Out-of-Box-Experience (OOBE). This may also occur if you redirected your known folders manually through the Properties dialog box in File Explorer. ​This issue does not cause any user files to be deleted and a solution is in progress.

To safeguard your update experience, we have applied a quality hold on devices with redirected known folders from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4497935. The safeguard hold will be removed following the June Update Tuesday release.
Note We recommend that you do not attempt to manually update to Windows 10, version 1903 using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4497935		Resolved:
May 29, 2019
02:00 PM PT

Opened:
May 21, 2019
07:16 AM PT
AMD RAID driver incompatibility
Microsoft and AMD have identified an incompatibility with AMD RAID driver versions earlier than 9.2.0.105. When you attempt to install the Windows 10, version 1903 update on a Windows 10-based computer with an affected driver version, the installation process stops and you get a message like the following:

AMD Ryzen™ or AMD Ryzen™ Threadripper™ configured in SATA or NVMe RAID mode.

“A driver is installed that causes stability problems on Windows. This driver will be disabled. Check with your software/driver provider for an updated version that runs on this version of Windows.”

 
To safeguard your update experience, we have applied a compatibility hold on devices with these AMD drivers from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue has been resolved externally by AMD. To resolve this issue, you will need to download the latest AMD RAID drivers directly from AMD at https://www.amd.com/en/support/chipsets/amd-socket-tr4/x399. The drivers must be version 9.2.0.105 or later. Install the drivers on the affected computer, and then restart the installation process for the Windows 10, version 1903 feature update.
 
Note The safeguard hold will remain in place on machines with the older AMD RAID drivers. We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
Resolved:
June 06, 2019
11:06 AM PT

Opened:
May 21, 2019
07:12 AM PT
Error attempting to update with external USB device or memory card attached
If you have an external USB device or SD memory card attached when installing Windows 10, version 1903, you may get an error message stating \"This PC can't be upgraded to Windows 10.\" This is caused by inappropriate drive reassignment during installation.

Sample scenario: An update to Windows 10, version 1903 is attempted on a computer that has a thumb drive inserted into its USB port. Before the update, the thumb drive is mounted in the system as drive G based on the existing drive configuration. After the feature update is installed; however, the device is reassigned a different drive letter (e.g., drive H).

Note The drive reassignment is not limited to removable drives. Internal hard drives may also be affected.

To safeguard your update experience, we have applied a hold on devices with an external USB device or SD memory card attached from being offered Windows 10, version 1903 until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4497935. The safeguard hold will be removed following the June Update Tuesday release.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4497935		Resolved:
May 29, 2019
02:00 PM PT

Opened:
May 21, 2019
07:38 AM PT
D3D applications and games may fail to enter full-screen mode on rotated displays
Some Direct3D (D3D) applications and games (e.g., 3DMark) may fail to enter full-screen mode on displays where the display orientation has been changed from the default (e.g., a landscape display in portrait mode).

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Resolution: This issue was resolved in KB4497935. 

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4497935		Resolved:
May 29, 2019
02:00 PM PT

Opened:
May 21, 2019
07:05 AM PT
Older versions of BattlEye anti-cheat software incompatible
Microsoft and BattlEye have identified a compatibility issue with some games that use older versions of BattlEye anti-cheat software. When launching a game that uses an older, impacted version of BattlEye anti-cheat software on a device running Windows 10, version 1903, the device may experience a system crash.

To safeguard your gaming experience, we have applied a compatibility hold on devices with the impacted versions of BattlEye software used by games installed on your PC. This will prevent Windows 10, version 1903 from being offered until the incompatible version of BattlEye software is no longer installed on the device. 

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: Before updating your machine, we recommend you do one or more of the following:

  • Verify that your game is up to date with the latest available version of BattlEye software. Some game platforms allow you to validate your game files, which can confirm that your installation is fully up to date.
  • Restart your system and open the game again.
  • Uninstall BattlEye using https://www.battleye.com/downloads/UninstallBE.exe, and then reopen your game.
  • Uninstall and reinstall your game.
For more troubleshooting options, see https://www.battleye.com/support/faq/.

We are working with BattlEye and gaming partners to ensure games are automatically updated with the latest BattlEye software. We have confirmed the latest version of impacted games do not exhibit this issue. To minimize the chance of hitting this upgrade compatibility hold, please make sure you are running the latest version of your games before attempting to update the operating system.  

Resolution: This issue was resolved externally by BattlEye. You will need to update the BattlEye service for impacted games. For a list of recent games that use BattlEye, go to https://www.battleye.com/. The safeguard hold will remain in place on older version of the BattlEye service. We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until you have installed an updated version of BattlEye software that resolves this issue.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
Resolved:
June 06, 2019
11:04 AM PT

Opened:
May 21, 2019
07:34 AM PT
"