From c9397be610ca855223e8747036320af23a927005 Mon Sep 17 00:00:00 2001 From: DocsPreview <49669258+DocsPreview@users.noreply.github.com> Date: Tue, 21 May 2019 09:57:22 -0700 Subject: [PATCH] Add 1903 issues (#242) * Added 1093 issue pages * Changed TOC menu links * New Announcements and issues added for 1903 * Fixed no issue messages * Latest updates for 1809 and 1903 * Latest updates with KB Number * New update for 1607 --- windows/release-information/TOC.md | 33 ++++-- ...indows-10-1809-and-windows-server-2019.yml | 2 + .../resolved-issues-windows-10-1903.yml | 36 ++++++ .../status-windows-10-1507.yml | 20 ++-- ...indows-10-1607-and-windows-server-2016.yml | 22 ++-- .../status-windows-10-1703.yml | 20 ++-- .../status-windows-10-1709.yml | 20 ++-- .../status-windows-10-1803.yml | 20 ++-- ...indows-10-1809-and-windows-server-2019.yml | 24 ++-- .../status-windows-10-1903.yml | 108 ++++++++++++++++++ ...ndows-7-and-windows-server-2008-r2-sp1.yml | 20 ++-- ...windows-8.1-and-windows-server-2012-r2.yml | 20 ++-- .../status-windows-server-2008-sp2.yml | 20 ++-- .../status-windows-server-2012.yml | 20 ++-- .../windows-message-center.yml | 23 ++-- 15 files changed, 286 insertions(+), 122 deletions(-) create mode 100644 windows/release-information/resolved-issues-windows-10-1903.yml create mode 100644 windows/release-information/status-windows-10-1903.yml diff --git a/windows/release-information/TOC.md b/windows/release-information/TOC.md index 188c87f7a3..735c4e5527 100644 --- a/windows/release-information/TOC.md +++ b/windows/release-information/TOC.md @@ -1,23 +1,36 @@ # [Windows 10 release information](index.md) ## [Message center](windows-message-center.yml) -## [Version 1809 and Windows Server 2019](status-windows-10-1809-and-windows-server-2019.yml) +## Version 1903 +### [Known issues and notifications](status-windows-10-1903.yml) +### [Resolved issues](resolved-issues-windows-10-1903.yml) +## Version 1809 and Windows Server 2019 +### [Known issues and notifications](status-windows-10-1809-and-windows-server-2019.yml) ### [Resolved issues](resolved-issues-windows-10-1809-and-windows-server-2019.yml) -## [Version 1803](status-windows-10-1803.yml) +## Version 1803 +### [Known issues and notifications](status-windows-10-1803.yml) ### [Resolved issues](resolved-issues-windows-10-1803.yml) -## [Version 1709](status-windows-10-1709.yml) +## Version 1709 +### [Known issues and notifications](status-windows-10-1709.yml) ### [Resolved issues](resolved-issues-windows-10-1709.yml) -## [Version 1703](status-windows-10-1703.yml) +## Version 1703 +### [Known issues and notifications](status-windows-10-1703.yml) ### [Resolved issues](resolved-issues-windows-10-1703.yml) -## [Version 1607 and Windows Server 2016](status-windows-10-1607-and-windows-server-2016.yml) +## Version 1607 and Windows Server 2016 +### [Known issues and notifications](status-windows-10-1607-and-windows-server-2016.yml) ### [Resolved issues](resolved-issues-windows-10-1607.yml) -## [Version 1507](status-windows-10-1507.yml) +## Version 1507 +### [Known issues and notifications](status-windows-10-1507.yml) ### [Resolved issues](resolved-issues-windows-10-1507.yml) ## Previous versions -### [Windows 8.1 and Windows Server 2012 R2](status-windows-8.1-and-windows-server-2012-r2.yml) +### Windows 8.1 and Windows Server 2012 R2 +#### [Known issues and notifications](status-windows-8.1-and-windows-server-2012-r2.yml) ####[Resolved issues](resolved-issues-windows-8.1-and-windows-server-2012-r2.yml) -### [Windows Server 2012](status-windows-server-2012.yml) +### Windows Server 2012 +#### [Known issues and notifications](status-windows-server-2012.yml) ####[Resolved issues](resolved-issues-windows-server-2012.yml) -### [Windows 7 and Windows Server 2008 R2](status-windows-7-and-windows-server-2008-r2-sp1.yml) +### Windows 7 and Windows Server 2008 R2 +#### [Known issues and notifications](status-windows-7-and-windows-server-2008-r2-sp1.yml) ####[Resolved issues](resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml) -### [Windows Server 2008 SP2](status-windows-server-2008-sp2.yml) +### Windows Server 2008 SP2 +#### [Known issues and notifications](status-windows-server-2008-sp2.yml) ####[Resolved issues](resolved-issues-windows-server-2008-sp2.yml) \ No newline at end of file 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 955bf10881..49d4e3e4e0 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 @@ -32,6 +32,7 @@ sections: - type: markdown text: "
Summary | Originating update | Status | Date resolved |
Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort Upgrade block: Microsoft has identified issues with certain new Intel display drivers, which accidentally turn on unsupported features in Windows. See details > | OS Build 17763.134 November 13, 2018 KB4467708 | Resolved | May 21, 2019 07:42 AM PT |
Unable to access some gov.uk websites gov.uk websites that don’t support “HSTS” may not be accessible See details > | OS Build 17763.503 May 14, 2019 KB4494441 | Resolved KB4505056 | May 19, 2019 02:00 PM PT |
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 |
Details | Originating update | Status | History |
Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort Upgrade block: Microsoft has identified issues with certain new Intel display drivers. Intel inadvertently released versions of its display driver (versions 24.20.100.6344, 24.20.100.6345) to OEMs that accidentally turned on unsupported features in Windows. As a result, after updating to Windows 10, version 1809, audio playback from a monitor or television connected to a PC via HDMI, USB-C, or a DisplayPort may not function correctly on devices with these drivers. Note: This Intel display driver issue is different from the Intel Smart Sound Technology driver (version 09.21.00.3755) audio issue previously documented. Affected platforms:
Next steps: Intel has released updated drivers to OEM device manufacturers. OEMs need to make the updated driver available via Windows Update. For more information, see the Intel Customer Support article. Resolution: Microsoft has removed the safeguard hold. Back to top | OS Build 17763.134 November 13, 2018 KB4467708 | Resolved | Resolved: May 21, 2019 07:42 AM PT Opened: November 13, 2018 10:00 AM PT |
Shared albums may not sync with iCloud for Windows Upgrade block: Users who attempt to install iCloud for Windows (version 7.7.0.27) will see a message displayed that this version iCloud for Windows isn't supported and the install will fail. Affected platforms:
To ensure a seamless experience, Microsoft is blocking devices with iCloud for Windows (version 7.7.0.27) software installed from being offered Window 10, version 1809 until this issue has been resolved. We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool from the Microsoft software download website until this issue is resolved. Resolution: Apple has released an updated version of iCloud for Windows (version 7.8.1) that resolves compatibility issues encountered when updating or synching Shared Albums after updating to Windows 10, version 1809. We recommend that you update your iCloud for Windows to version 7.8.1 when prompted before attempting to upgrade to Windows 10, version 1809. You can also manually download the latest version of iCloud for Windows by visiting https://support.apple.com/HT204283. Back to top | OS Build 17763.134 November 13, 2018 KB4467708 | Resolved KB4482887 | Resolved: March 01, 2019 10:00 AM PT Opened: November 13, 2018 10:00 AM PT |
Intel Audio Display (intcdaud.sys) notification during Windows 10 Setup Upgrade block: Microsoft and Intel have identified a compatibility issue with a range of Intel Display Audio device drivers (intcdaud.sys, versions 10.25.0.3 - 10.25.0.8) that may result in excessive processor demand and reduced battery life. As a result, the update process to the Windows 10 October 2018 Update (Windows 10, version 1809) will fail and affected devices will automatically revert to the previous working configuration. Affected platforms:
If you see a \"What needs your attention\" notification during installation of the October 2018 Update, you have one of these affected drivers on your system. On the notification, click Back to remain on your current version of Windows 10. To ensure a seamless experience, we are blocking devices from being offered the October 2018 Update until updated Intel device drivers are installed on your current operating system. We recommend that you do not attempt to manually update to Windows 10, version 1809, using the Update Now button or the Media Creation Tool from the Microsoft Software Download Center until newer Intel device drivers are available with the update. You can either wait for newer drivers to be installed automatically through Windows Update or check with your computer manufacturer for the latest device driver software availability and installation procedures. For more information about this issue, see Intel's customer support guidance. Resolution: This issue was resolved in KB4482887 and the upgrade block removed. Back to top | OS Build 17763.134 November 13, 2018 KB4467708 | Resolved KB4482887 | Resolved: March 01, 2019 10:00 AM PT Opened: November 13, 2018 10:00 AM PT |
F5 VPN clients losing network connectivity Upgrade block: After updating to Window 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration. Affected platforms:
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 |
Summary | Originating update | Status | Last updated |
Machines running Windows Server 2016 with Hyper-V seeing Bitlocker error 0xC0210000 Some machines running Windows Server with Hyper-V enabled may boot into Bitlocker recovery See details > | N/A | Investigating | May 21, 2019 09:21 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 |
SCVMM cannot enumerate and manage logical switches deployed on the host For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host. See details > | OS Build 14393.2639 November 27, 2018 KB4467684 | Mitigated | April 25, 2019 02:00 PM PT |
Details | Originating update | Status | History |
Machines running Windows Server 2016 with Hyper-V seeing Bitlocker error 0xC0210000 We are investigating reports that some machines running Windows Server 2016 with Hyper-V enabled may enter Bitlocker recovery mode with an error 0xC0210000 after installing KB4494440 and rebooting. Affected platforms:
Workaround: You can reboot machines successfully after suspending Bitlocker from Windows Recovery Environment. Below steps can be followed to suspend Bitlocker
The workaround needs to be followed on every system boot. To prevent hitting the issue, execute following command to temporarily suspend Bitlocker just before rebooting the system:
Next steps: Microsoft is presently investigating this issue and will provide an update when available. Back to top | N/A | Investigating | Last updated: May 21, 2019 09:21 AM PT Opened: May 21, 2019 08:50 AM PT |
Unable to access some gov.uk websites After installing the May 14, 2019 update, some gov.uk websites that don’t support HTTP Strict Transport Security (HSTS) may not be accessible through Internet Explorer 11 or Microsoft Edge. Affected platforms:
Resolution: We have released an \"optional, out-of-band\" update for Windows 10 (KB4505052) to resolve this issue. If you are affected, we recommend you apply this update by installing KB4505052 from Windows Update and then restarting your device. This update will not be applied automatically. To download and install this update, go to Settings > Update & Security > Windows Update and select Check for updates. To get the standalone package for KB4505052, search for it in the Microsoft Update Catalog. Back to top | OS Build 14393.2969 May 14, 2019 KB4494440 | Resolved KB4505052 | Resolved: May 19, 2019 02:00 PM PT Opened: May 16, 2019 01:57 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:
Resolution: This issue has been resolved. Back to top | OS Build 14393.2941 April 25, 2019 KB4493473 | Resolved KB4494440 | Resolved: May 14, 2019 10:00 AM PT Opened: May 10, 2019 10:35 AM PT |
Details | Originating update | Status | History |
Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort Upgrade block: Microsoft has identified issues with certain new Intel display drivers. Intel inadvertently released versions of its display driver (versions 24.20.100.6344, 24.20.100.6345) to OEMs that accidentally turned on unsupported features in Windows. As a result, after updating to Windows 10, version 1809, audio playback from a monitor or television connected to a PC via HDMI, USB-C, or a DisplayPort may not function correctly on devices with these drivers. Affected platforms:
Next steps: Intel has released updated drivers to OEM device manufacturers. OEMs need to make the updated driver available via Windows Update. For more information, see the Intel Customer Support article. Note: This Intel display driver issue is different from the Intel Smart Sound Technology driver (version 09.21.00.3755) audio issue previously documented. Back to top | OS Build 17763.134 November 13, 2018 KB4467708 | Mitigated | Last updated: March 15, 2019 12:00 PM PT Opened: November 13, 2018 10:00 AM PT |
Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort Upgrade block: Microsoft has identified issues with certain new Intel display drivers. Intel inadvertently released versions of its display driver (versions 24.20.100.6344, 24.20.100.6345) to OEMs that accidentally turned on unsupported features in Windows. As a result, after updating to Windows 10, version 1809, audio playback from a monitor or television connected to a PC via HDMI, USB-C, or a DisplayPort may not function correctly on devices with these drivers. Note: This Intel display driver issue is different from the Intel Smart Sound Technology driver (version 09.21.00.3755) audio issue previously documented. Affected platforms:
Next steps: Intel has released updated drivers to OEM device manufacturers. OEMs need to make the updated driver available via Windows Update. For more information, see the Intel Customer Support article. Resolution: Microsoft has removed the safeguard hold. Back to top | OS Build 17763.134 November 13, 2018 KB4467708 | Resolved | Resolved: May 21, 2019 07:42 AM PT Opened: November 13, 2018 10:00 AM PT |
Current status: + Windows 10, version 1903 is available by manually by 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.
+ |
Summary | Originating update | Status | Last updated |
Display brightness may not respond to adjustments Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel drivers. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Investigating | May 21, 2019 07:56 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 20, 2019 KB4505057 | Investigating | May 21, 2019 07:35 AM 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 20, 2019 KB4505057 | Investigating | May 21, 2019 07:17 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 battery drain. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Mitigated | May 21, 2019 08:34 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 20, 2019 KB4505057 | Mitigated | May 21, 2019 07:38 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. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Mitigated | May 21, 2019 07:34 AM 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 20, 2019 KB4505057 | Mitigated | May 21, 2019 07:29 AM PT |
Night light settings do not apply in some cases Microsoft has identified some scenarios where night light settings may stop working. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Mitigated | May 21, 2019 07:28 AM 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 20, 2019 KB4505057 | Mitigated | May 21, 2019 07:20 AM PT |
Intermittent Wi-Fi connectivity loss Some older devices may experience losing Wi-Fi connectivity due to an outdated Qualcomm driver. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Mitigated | May 21, 2019 07:13 AM PT |
AMD RAID driver incompatibility Installation process may stop when trying to instal Windows 10, version 1903 update on computers that run certain versions of AMD RAID drivers. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Mitigated | May 21, 2019 07:12 AM PT |
D3D applications and games may fail to enter full-screen mode on rotated displays Some Direct 3D (D3D) applications and games may fail to enter full-screen mode on rotated displays. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Mitigated | May 21, 2019 07:05 AM PT |
Details | Originating update | Status | History |
Display brightness may not respond to adjustments Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel 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:
Workaround: Restart your device to apply changes to brightness. Next steps: We are working on a resolution that will be made available in upcoming release. 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 21, 2019 07:56 AM PT Opened: May 21, 2019 07:56 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:
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 20, 2019 KB4505057 | Investigating | Last updated: May 21, 2019 07:35 AM PT Opened: May 21, 2019 07:35 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:
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 20, 2019 KB4505057 | Investigating | Last updated: May 21, 2019 07:17 AM PT Opened: May 21, 2019 07:16 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 the latest Windows feature update, you have an Intel Audio Display device driver (intcdaud.sys, versions 10.25.0.3 through 10.25.0.8) installed on your machine. 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:
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. 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. Note We recommend you do not attempt to update your devices until newer device drivers are installed. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 08:34 AM PT Opened: May 21, 2019 07:22 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, 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:
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. Next steps: Microsoft is working on a resolution and estimate a solution will be available in late May. 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. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 07:38 AM PT Opened: May 21, 2019 07:38 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:
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:
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 20, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 07:34 AM PT Opened: May 21, 2019 07:34 AM PT |
Unable to discover or connect to Bluetooth devices Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers. To safeguard your update experience, we have applied a compatibility hold on certain devices with Realtek or Qualcomm Bluetooth radio drivers from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated. Affected platforms:
Workaround: Check with your device manufacturer (OEM) to see if an updated driver is available and install it.
Next steps: Microsoft is working with Realtek and Qualcomm to release new drivers for all affected system via Windows Update. 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. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 07:29 AM PT Opened: May 21, 2019 07:29 AM PT |
Night light settings do not apply in some cases Microsoft has identified some scenarios where night light settings may stop working. The night light feature may stop working in the following scenarios:
Affected platforms:
Workaround: If you find that your night light settings have stopped working, try turning the night light on and off, or restart your computer. Next steps: We are working on a resolution and will provide an update in an upcoming release. 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 | Mitigated | Last updated: May 21, 2019 07:28 AM PT Opened: May 21, 2019 07:28 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:
Workaround: To temporarily resolve this issue, perform one of the following:
or
or
Note This workaround will only resolve the issue until your next system restart. Next steps: We are working on a resolution and will provide an update in an upcoming release. 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 | Mitigated | Last updated: May 21, 2019 07:20 AM PT Opened: May 21, 2019 07:20 AM PT |
Intermittent Wi-Fi connectivity loss Some older computers may experience losing Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available by your device manufacturer. 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:
Workaround: Download and install an updated Wi-Fi driver from your computer 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 20, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 07:13 AM PT Opened: May 21, 2019 07:13 AM PT |
AMD RAID driver incompatibility Microsoft and Intel have identified an incompatibility with AMD RAID driver versions lower than 9.2.0.105. When you install the Windows 10, version 1903 update on a Windows 10-based computer, 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.” On computers that have AMD Ryzen™ or AMD Ryzen™ Threadripper™ processors, AMD RAID drivers less than version 9.2.0.105 are not compatible with the this update. If a computer has these drivers installed and configured in RAID mode, it cannot install the Windows 10, version 1903 update. Computers with an AMD RAID driver, version 9.2.0.105 or higher, installed will not encounter this issue. For more information about this issue, please see the AMD support article. To safeguard your update experience, we have applied a quality hold on devices with these AMD drivers from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
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 20, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 07:12 AM PT Opened: May 21, 2019 07:12 AM PT |
D3D applications and games may fail to enter full-screen mode on rotated displays Some Direct 3D (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:
Workaround: To work around this issue, do one of the following:
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 20, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 07:05 AM PT Opened: May 21, 2019 07:05 AM PT |
Message | Date |
Windows 10, version 1903 rollout begins The Windows 10 May 2019 Update (Windows 10, version 1903) is available today to commercial customers via Windows Server Update Services (WSUS), Windows Update for Business, and the Volume Licensing Service Center (VLSC)—and to end users who manually select “Check for updates.” We are slowly throttling up availability while we carefully monitor data and feedback. | May 21, 2019 10:00 AM PT |
What’s new in Windows Update for Business We are enhancing and expanding the capabilities of Windows Update for Business to make the move to the cloud even easier. From simplified branch readiness options to better control over deadlines and reboots, read about the enhancements to Windows Update for Business as a part of Windows 10, version 1903. | May 21, 2019 10:00 AM PT |
What’s new for businesses and IT pros in Windows 10 Explore the newest capabilities for businesses and IT in the latest feature update in the areas of intelligent security, simplified updates, flexible management, and enhanced productivity. | May 21, 2019 10:00 AM PT |
Reminder: Install the latest SSU for a smoother update experience We strongly recommend that you install the latest servicing stack update (SSU) before installing any Windows update; especially as an SSU may be a prerequisite for some updates. If you have difficulty installing Windows updates, verify that you have installed the latest SSU package for your version of Windows and then try installing the update again. Links to the latest SSU are always provided in the “How to get this update” section of each update KB article (e.g., KB4494441). For more information about SSUs, see our Servicing stack updates guidance. | May 14, 2019 10:00 AM PT |
Take action: Update Remote Desktop Services on older versions of Windows Today, we released fixes for a critical wormable, remote code execution vulnerability (CVE-2019-0708) in Remote Desktop Services—formerly known as Terminal Services. This vulnerability affects Windows 7, Windows Server 2008 R2, and earlier versions of Windows nearing end of support. It does not affect Windows 8, Windows Server 2012, or newer operating systems. While we have not observed attacks exploiting this vulnerability, affected systems should be patched with priority. Here is what you need to know: Call to action: |