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 34ef2a1b15..141727f4e2 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
@@ -58,7 +58,6 @@ sections:
Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible Upgrade block: Microsoft and Trend Micro identified a compatibility issue with the Trend Micro business endpoint security solutions OfficeScan and Worry-Free Business Security.
See details > | OS Build 17763.134
November 13, 2018 KB4467708 | Resolved
| February 01, 2019 09:00 AM PT |
Unable to access hotspots with third-party applications Third-party applications may have difficulty authenticating hotspots.
See details > | OS Build 17763.253
January 08, 2019 KB4480116 | Resolved KB4476976 | January 22, 2019 02:00 PM PT |
Unable to use Seek bar in Windows Media Player Users may not be able to use the Seek bar in Windows Media Player when playing specific files.
See details > | OS Build 17763.55
October 09, 2018 KB4464330 | Resolved KB4471332 | December 11, 2018 10:00 AM PT |
- Audio stops working after installing Intel audio driver Upgrade block: Windows 10 audio stops working after installing Intel Smart Sound Technology driver (version 09.21.00.3755).
See details > | OS Build 17763.134
November 13, 2018 KB4467708 | Resolved KB4468550 | December 07, 2018 10:00 AM PT |
"
@@ -139,7 +138,6 @@ sections:
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 |
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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Resolution: This issue was resolved in KB4487044, and the block was removed. Back to top | OS Build 17763.134
November 13, 2018 KB4467708 | Resolved KB4487044 | Resolved: 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Once you have updated your version of Trend Micro's OfficeScan or Worry-Free Business Security software, you will be offered Windows 10, version 1809 automatically. Back to top | OS Build 17763.134
November 13, 2018 KB4467708 | Resolved
| Resolved: 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: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Resolution: This issue was resolved in KB4468550 and the upgrade block removed. Back to top | OS Build 17763.134
November 13, 2018 KB4467708 | Resolved KB4468550 | Resolved: December 07, 2018 10:00 AM PT
Opened: November 13, 2018 10:00 AM PT |
"
diff --git a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml
index 9a76c08ad3..014eb724eb 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,8 +60,8 @@ 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.
Summary | Originating update | Status | Last updated |
+ 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 07, 2019 04:25 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 |
Issue using PXE to start a device from WDS There may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension.
See details > | OS Build 14393.2848
March 12, 2019 KB4489882 | Mitigated
| April 25, 2019 02:00 PM PT |
@@ -87,8 +87,8 @@ sections:
- type: markdown
text: "
Details | Originating update | Status | History |
+ Some applications may fail to run as expected on clients of AD FS 2016Some 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 07, 2019 04:25 PM PT
Opened: June 04, 2019 05:55 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: - Open an Administrator Command prompt and type the following: \"C:\\Program Files\\Internet Explorer\\iexplore.exe\" http://microsoft.com
- After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
- Select Search Providers in left pane.
- Select the link Find more search providers in the bottom left of the dialog.
- A new Internet Explorer window should open, allowing you to select a search provider.
- Select Add under the Search Provider you prefer.
- The Add Search Provider dialog should open, select Add.
- 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 2016Some 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-1809-and-windows-server-2019.yml b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml
index dabae3539b..f3ada14b3b 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
@@ -75,8 +75,6 @@ sections:
Windows 10, version 1809 update history may show an update installed twice Some customers are reporting that KB4494441 installed twice on their device
See details > | OS Build 17763.503
May 14, 2019 KB4494441 | Resolved
| May 16, 2019 02:37 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 17763.475
May 03, 2019 KB4495667 | Resolved KB4494441 | May 14, 2019 10:00 AM PT |
Zone transfers over TCP may fail Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.
See details > | OS Build 17763.475
May 03, 2019 KB4495667 | Resolved KB4494441 | May 14, 2019 10:00 AM PT |
- Latest cumulative update (KB 4495667) installs automatically Reports that the optional cumulative update (KB 4495667) installs automatically.
See details > | OS Build 17763.475
May 03, 2019 KB4495667 | Resolved
| May 08, 2019 03:37 PM PT |
- System may be unresponsive after restart if ArcaBit antivirus software installed After further investigation ArcaBit has confirmed this issue is not applicable to Windows 10, version 1809
See details > | OS Build 17763.437
April 09, 2019 KB4493509 | Resolved
| May 08, 2019 03:30 PM PT |
"
@@ -107,16 +105,6 @@ sections:
Windows 10, version 1809 update history may show an update installed twice Affected platforms: - Client: Windows 10, version 1809
Cause: In certain situations, installing an update requires multiple download and restart steps. In cases where two intermediate steps of the installation complete successfully, the View your Update history page will report that installation completed successfully twice.
Resolution: No action is required on your part. The update installation may take longer and may require more than one restart, but will install successfully after all intermediate installation steps have completed. We are working on improving this update experience to ensure the Update history correctly reflects the installation of the latest cumulative update (LCU). Back to top | OS Build 17763.503
May 14, 2019 KB4494441 | Resolved
| Resolved: May 16, 2019 02:37 PM PT
Opened: May 14, 2019 02:56 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. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
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
- 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
Resolution: This issue has been resolved. Back to top | OS Build 17763.475
May 03, 2019 KB4495667 | Resolved KB4494441 | Resolved: May 14, 2019 10:00 AM PT
Opened: May 10, 2019 10:35 AM PT |
Zone transfers over TCP may failZone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4495667. Affected platforms: - Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
- Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016
Resolution: This issue was resolved in KB4494441. Back to top | OS Build 17763.475
May 03, 2019 KB4495667 | Resolved KB4494441 | Resolved: May 14, 2019 10:00 AM PT
Opened: May 14, 2019 01:19 PM PT |
- Latest cumulative update (KB 4495667) installs automaticallyDue to a servicing side issue some users were offered KB4495667 (optional update) automatically and rebooted devices. This issue has been mitigated.
Affected platforms: - Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
Resolution:: This issue has been mitigated on the servicing side to prevent auto installing of this update. Customers do not need to take any action. Back to top | OS Build 17763.475
May 03, 2019 KB4495667 | Resolved
| Resolved: May 08, 2019 03:37 PM PT
Opened: May 05, 2019 12:01 PM PT |
-
- "
-
-- title: April 2019
-- items:
- - type: markdown
- text: "
- Details | Originating update | Status | History |
- System may be unresponsive after restart if ArcaBit antivirus software installed ArcaBit has confirmed this issue is not applicable to Windows 10, version 1809 (client or server).
Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart.
Affected platforms: - Client: Windows 8.1; Windows 7 SP1
- Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
Workaround: ArcaBit has released an update to address this issue for affected platforms. For more information, see the ArcaBit support article.
Resolution: This issue has been resolved. ArcaBit has confirmed this issue is not applicable to Windows 10, version 1809 (client or server). Back to top | OS Build 17763.437
April 09, 2019 KB4493509 | Resolved
| Resolved: May 08, 2019 03:30 PM PT
Opened: April 09, 2019 10:00 AM PT |
"
diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml
index d00e89505d..4a95d4db9f 100644
--- a/windows/release-information/status-windows-10-1903.yml
+++ b/windows/release-information/status-windows-10-1903.yml
@@ -22,7 +22,7 @@ sections:
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.
+ 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.
|
"
@@ -74,7 +74,7 @@ sections:
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 |
- 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 01:33 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 07, 2019 04:26 PM 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 |
@@ -103,7 +103,7 @@ sections:
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.
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 |
- 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.
Resolution: This issue was resolved externally by BattlEye for all known impacted games. You will need to ensure you are running the latest version of your game before updating to Windows 10, version 1903. For a list of recent games that use BattlEye, go to https://www.battleye.com/. The compatibility hold will remain in place on older versions of BattlEye as a safeguard. For customers already running Windows 10, version 1903, opening games with incompatible versions of BattleEye may fail. If you have any issues with opening games related to a BattlEye error, please see https://www.battleye.com/support/faq/. Back to top | OS Build 18362.116
May 21, 2019 KB4505057 | Resolved
| Resolved: June 06, 2019 01:33 PM PT
Opened: May 21, 2019 07:34 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.
Resolution: This issue was resolved externally by BattlEye for all known impacted games. For a list of recent games that use BattlEye, go to https://www.battleye.com/. We recommend following the workaround before updating to Windows 10, version 1903, as games with incompatible versions of BattleEye may fail to open after updating Windows. If you have confirmed your game is up to date and you have any issues with opening games related to a BattlEye error, please see https://www.battleye.com/support/faq/. Back to top | OS Build 18362.116
May 21, 2019 KB4505057 | Resolved
| Resolved: June 07, 2019 04:26 PM 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 |
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 70bb640684..aae03cfacf 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
@@ -60,6 +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.
Summary | Originating update | Status | Last updated |
+ IE11 may stop working when loading or interacting with Power BI reports Power BI reports that contain line charts with markers may cause Internet Explorer 11 to stop working
See details > | May 14, 2019 KB4499164 | Mitigated
| June 07, 2019 02:57 PM PT |
System may be unresponsive after restart with certain McAfee antivirus products Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.
See details > | April 09, 2019 KB4493472 | 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 > | May 14, 2019 KB4499164 | Resolved KB4505050 | May 18, 2019 02:00 PM PT |
System may be unresponsive after restart if ArcaBit antivirus software installed Devices with ArcaBit antivirus software installed may become unresponsive upon restart.
See details > | April 09, 2019 KB4493472 | Resolved
| May 14, 2019 01:23 PM PT |
@@ -76,6 +77,15 @@ sections:
"
+- title: June 2019
+- items:
+ - type: markdown
+ text: "
+ Details | Originating update | Status | History |
+ IE11 may stop working when loading or interacting with Power BI reports Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
Affected platforms: - Client: Windows 7 SP1; Windows 8.1
- Server: Windows Server 2008 R2 SP1; Windows Server 2012; Windows Server 2012 R2
Workaround: To mitigate the issue with Power BI reports, the report needs to be republished with markers turned off. Markers can be turned off by selecting the line chart that is having issues and going to the Visualizations pane. Then on the Format tab under Shapes, set the Show marker slider to off.
Next steps: We are working on a resolution and estimate a solution will be available in mid-July. Back to top | May 14, 2019 KB4499164 | Mitigated
| Last updated: June 07, 2019 02:57 PM PT
Opened: June 07, 2019 02:57 PM PT |
+
+ "
+
- title: May 2019
- items:
- type: markdown
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 e76412be72..8d3e9cc582 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
@@ -60,6 +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.
Summary | Originating update | Status | Last updated |
+ IE11 may stop working when loading or interacting with Power BI reports Power BI reports that contain line charts with markers may cause Internet Explorer 11 to stop working
See details > | May 14, 2019 KB4499151 | Mitigated
| June 07, 2019 02:57 PM PT |
Japanese IME doesn't show the new Japanese Era name as a text input option If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option.
See details > | April 25, 2019 KB4493443 | Mitigated
| May 15, 2019 05:53 PM PT |
Issue using PXE to start a device from WDS There may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension.
See details > | March 12, 2019 KB4489881 | 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 > | January 08, 2019 KB4480963 | Mitigated
| April 25, 2019 02:00 PM PT |
@@ -79,6 +80,15 @@ sections:
"
+- title: June 2019
+- items:
+ - type: markdown
+ text: "
+ Details | Originating update | Status | History |
+ IE11 may stop working when loading or interacting with Power BI reports Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
Affected platforms: - Client: Windows 7 SP1; Windows 8.1
- Server: Windows Server 2008 R2 SP1; Windows Server 2012; Windows Server 2012 R2
Workaround: To mitigate the issue with Power BI reports, the report needs to be republished with markers turned off. Markers can be turned off by selecting the line chart that is having issues and going to the Visualizations pane. Then on the Format tab under Shapes, set the Show marker slider to off.
Next steps: We are working on a resolution and estimate a solution will be available in mid-July. Back to top | May 14, 2019 KB4499151 | Mitigated
| Last updated: June 07, 2019 02:57 PM PT
Opened: June 07, 2019 02:57 PM PT |
+
+ "
+
- title: May 2019
- items:
- type: markdown
diff --git a/windows/release-information/status-windows-server-2012.yml b/windows/release-information/status-windows-server-2012.yml
index e98321c34c..878f02de70 100644
--- a/windows/release-information/status-windows-server-2012.yml
+++ b/windows/release-information/status-windows-server-2012.yml
@@ -60,6 +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.
Summary | Originating update | Status | Last updated |
+ IE11 may stop working when loading or interacting with Power BI reports Power BI reports that contain line charts with markers may cause Internet Explorer 11 to stop working
See details > | May 14, 2019 KB4499171 | Mitigated
| June 07, 2019 02:57 PM PT |
Japanese IME doesn't show the new Japanese Era name as a text input option If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option.
See details > | April 25, 2019 KB4493462 | Mitigated
| May 15, 2019 05:53 PM PT |
Issue using PXE to start a device from WDS There may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension.
See details > | March 12, 2019 KB4489891 | 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 > | January 08, 2019 KB4480975 | Mitigated
| April 25, 2019 02:00 PM PT |
@@ -77,6 +78,15 @@ sections:
"
+- title: June 2019
+- items:
+ - type: markdown
+ text: "
+ Details | Originating update | Status | History |
+ IE11 may stop working when loading or interacting with Power BI reports Internet Explorer 11 may stop working when loading or interacting with Power BI reports that have line charts with markers. This issue may also occur when viewing other content that contains Scalable Vector Graphics (SVG) markers.
Affected platforms: - Client: Windows 7 SP1; Windows 8.1
- Server: Windows Server 2008 R2 SP1; Windows Server 2012; Windows Server 2012 R2
Workaround: To mitigate the issue with Power BI reports, the report needs to be republished with markers turned off. Markers can be turned off by selecting the line chart that is having issues and going to the Visualizations pane. Then on the Format tab under Shapes, set the Show marker slider to off.
Next steps: We are working on a resolution and estimate a solution will be available in mid-July. Back to top | May 14, 2019 KB4499171 | Mitigated
| Last updated: June 07, 2019 02:57 PM PT
Opened: June 07, 2019 02:57 PM PT |
+
+ "
+
- title: May 2019
- items:
- type: markdown