Configuration
- 
| Summary | Originating update | Status | Date resolved |
| 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 | Resolved KB4507459 | July 16, 2019 10:00 AM PT |
| Devices with Hyper-V enabled may receive BitLocker error 0xC0210000 Some devices with Hyper-V enabled may start into BitLocker recovery with error 0xC0210000. See details > | OS Build 14393.2969 May 14, 2019 KB4494440 | Resolved KB4507460 | July 09, 2019 10:00 AM PT |
| Difficulty connecting to some iSCSI-based SANs Devices may have difficulty connecting to some Storage Area Network (SAN) devices that leverage iSCSI. See details > | OS Build 14393.2999 May 23, 2019 KB4499177 | Resolved KB4509475 | June 27, 2019 02:00 PM PT |
| Event Viewer may close or you may receive an error when using Custom Views When trying to expand, view or create Custom Views in Event Viewer, you may receive an error and the app may stop responding or close. See details > | OS Build 14393.3025 June 11, 2019 KB4503267 | Resolved KB4503294 | June 18, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| 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:
Resolution: This issue was resolved in KB4507459. Back to top | OS Build 14393.2941 April 25, 2019 KB4493473 | Resolved KB4507459 | Resolved: July 16, 2019 10:00 AM PT Opened: June 04, 2019 05:55 PM PT |
| Difficulty connecting to some iSCSI-based SANs Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing KB4499177. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.” Affected platforms:
Resolution: This issue was resolved in KB4509475. Back to top | OS Build 14393.2999 May 23, 2019 KB4499177 | Resolved KB4509475 | Resolved: June 27, 2019 02:00 PM PT Opened: June 20, 2019 04:46 PM PT |
| Event Viewer may close or you may receive an error when using Custom Views When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, \"MMC has detected an error in a snap-in and will unload it.\" and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected. Affected platforms:
Resolution: This issue was resolved in KB4503294. Back to top | OS Build 14393.3025 June 11, 2019 KB4503267 | Resolved KB4503294 | Resolved: June 18, 2019 02:00 PM PT Opened: June 12, 2019 11:11 AM 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:
Resolution: This issue was resolved in KB4503267. Back to top | OS Build 14393.2999 May 23, 2019 KB4499177 | Resolved KB4503267 | Resolved: June 11, 2019 10:00 AM PT Opened: June 05, 2019 05:49 PM PT |
| Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. See details > | OS Build 15063.1631 February 12, 2019 KB4487020 | Resolved KB4487011 | February 19, 2019 02:00 PM PT |
| Applications using Microsoft Jet database fail to open Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters. See details > | OS Build 15063.1563 January 08, 2019 KB4480973 | Resolved KB4487020 | February 12, 2019 10:00 AM PT |
| Webpages become unresponsive in Microsoft Edge Microsoft Edge users report difficulty browsing and loading webpages. See details > | OS Build 15063.1563 January 08, 2019 KB4480973 | Resolved KB4487020 | February 12, 2019 10:00 AM PT |
| SqlConnection instantiation exception on .NET 4.6 and later Instantiation of SqlConnection can throw an exception after certain updates have been installed. See details > | OS Build 15063.1292 August 30, 2018 KB4343889 | Resolved KB4480959 | January 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 KB4480973 | Resolved KB4480959 | January 15, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| 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:
Resolution: This issue is resolved in KB4480959. Back to top | OS Build 15063.1292 August 30, 2018 KB4343889 | Resolved KB4480959 | Resolved: January 15, 2019 10:00 AM PT Opened: August 30, 2018 05:00 PM PT |
| Details | Originating update | Status | History |
| 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:
Resolution: This issue is resolved in KB4480967. Back to top | OS Build 16299.637 August 30, 2018 KB4343893 | Resolved KB4480967 | Resolved: January 15, 2019 10:00 AM PT Opened: August 30, 2018 05:00 PM PT |
| Details | Originating update | Status | History |
| 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:
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 |
| 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 |
| 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 Windows 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 |
| 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 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 |
| F5 VPN clients losing network connectivity Upgrade block: After updating to Windows 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 |
| 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 Windows 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 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:
Resolution: Trend Micro has released a new version of these products that resolves the issue. To download them, please visit the Trend Micro Business Support Portal. Once you have updated your version of Trend Micro's OfficeScan or Worry-Free Business Security software, you will be offered Windows 10, version 1809 automatically. Back to top | OS Build 17763.134 November 13, 2018 KB4467708 | Resolved | Resolved: February 01, 2019 09:00 AM PT Opened: November 13, 2018 10:00 AM PT |
| Details | Originating update | Status | History |
| 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:
Resolution: This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Window 10, version 1903. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Resolved | Resolved: July 11, 2019 01:54 PM PT Opened: May 24, 2019 03:10 PM 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:
Resolution: This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Window 10, version 1903. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved | Resolved: July 11, 2019 01:53 PM PT Opened: May 21, 2019 07:16 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:
Resolution: This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Window 10, version 1903. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved | Resolved: July 11, 2019 01:53 PM PT Opened: May 21, 2019 07:38 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:
Resolution: This issue was resolved in KB4497935 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Window 10, version 1903. (Posted June 11, 2019) 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 |
| 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:
Resolution: This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Resolved | Resolved: July 11, 2019 01:54 PM PT Opened: May 24, 2019 03:10 PM 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:
Resolution: This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved | Resolved: July 11, 2019 01:53 PM PT Opened: May 21, 2019 07:16 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:
Resolution: This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved | Resolved: July 11, 2019 01:53 PM PT Opened: May 21, 2019 07:38 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:
Resolution: This issue was resolved in KB4497935 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903. (Posted June 11, 2019) 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 |
| 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:
Workaround: Before updating your machine, we recommend you do one or more of the following:
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 |
| 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:
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 |
| 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:
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 |
| First character of the Japanese era name not recognized as an abbreviation The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. See details > | January 15, 2019 KB4480969 | Resolved KB4487016 | February 19, 2019 02:00 PM PT |
| Internet Explorer may fail to load images Internet Explorer may fail to load images with a backslash (\\) in their relative source path. See details > | February 12, 2019 KB4487000 | Resolved KB4487016 | February 19, 2019 02:00 PM PT |
| Applications using Microsoft Jet database fail to open Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters. See details > | January 08, 2019 KB4480963 | Resolved KB4487000 | February 12, 2019 10:00 AM PT |
| Unable to access hotspots with third-party applications Third-party applications may have difficulty authenticating hotspots. See details > | January 08, 2019 KB4480963 | Resolved KB4480969 | January 15, 2019 10:00 AM PT |
| Summary | Originating update | Status | Last updated |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 14393.3025 June 11, 2019 KB4503267 | Mitigated | July 10, 2019 07:09 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 07, 2019 04:25 PM PT |
| Cluster service may fail if the minimum password length is set to greater than 14 The cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters. See details > | OS Build 14393.2639 November 27, 2018 KB4467684 | Mitigated | April 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 |
| 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 14393.2724 January 08, 2019 KB4480961 | Mitigated | April 25, 2019 02:00 PM PT |
| Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. See details > | OS Build 14393.2608 November 13, 2018 KB4467691 | Mitigated | February 19, 2019 10:00 AM 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 | Resolved KB4507459 | July 16, 2019 10:00 AM PT |
| Devices with Hyper-V enabled may receive BitLocker error 0xC0210000 Some devices with Hyper-V enabled may start into BitLocker recovery with error 0xC0210000. See details > | OS Build 14393.2969 May 14, 2019 KB4494440 | Resolved KB4507460 | July 09, 2019 10:00 AM PT |
| Difficulty connecting to some iSCSI-based SANs Devices may have difficulty connecting to some Storage Area Network (SAN) devices that leverage iSCSI. See details > | OS Build 14393.2999 May 23, 2019 KB4499177 | Resolved KB4509475 | June 27, 2019 02:00 PM PT |
| Event Viewer may close or you may receive an error when using Custom Views When trying to expand, view or create Custom Views in Event Viewer, you may receive an error and the app may stop responding or close. See details > | OS Build 14393.3025 June 11, 2019 KB4503267 | Resolved KB4503294 | June 18, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| 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:
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 |
| 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:
Resolution: This issue was resolved in KB4507459. Back to top | OS Build 14393.2941 April 25, 2019 KB4493473 | Resolved KB4507459 | Resolved: July 16, 2019 10:00 AM PT Opened: June 04, 2019 05:55 PM PT |
| Difficulty connecting to some iSCSI-based SANs Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing KB4499177. You may also receive an error in the System log section of Event Viewer with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.” Affected platforms:
Resolution: This issue was resolved in KB4509475. Back to top | OS Build 14393.2999 May 23, 2019 KB4499177 | Resolved KB4509475 | Resolved: June 27, 2019 02:00 PM PT Opened: June 20, 2019 04:46 PM PT |
| Event Viewer may close or you may receive an error when using Custom Views When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, \"MMC has detected an error in a snap-in and will unload it.\" and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected. Affected platforms:
Resolution: This issue was resolved in KB4503294. Back to top | OS Build 14393.3025 June 11, 2019 KB4503267 | Resolved KB4503294 | Resolved: June 18, 2019 02:00 PM PT Opened: June 12, 2019 11:11 AM PT |
| Current status as of June 18, 2019: - Windows 10, version 1903 is available for any user who manually selects “Check for updates” via Windows Update for all devices that do not have a safeguard hold. If you are not offered the update, please check below for any known issues that may affect your device. The recommended servicing status is Semi-Annual Channel.
+We are now beginning to build and train the machine learning (ML) based rollout process to update devices running the April 2018 Update, and earlier versions of Windows 10, to ensure we can continue to service these devices and provide the latest updates, security updates and improvements. Note Follow @WindowsUpdate to find out when new content is published to the release information dashboard. | Current status as of July 16, 2019: + We are initiating the Windows 10 May 2019 Update for customers with devices that are at or nearing end of service and have not yet updated their device. Keeping these devices both supported and receiving monthly updates is critical to device security and ecosystem health. Based on the large number of devices running the April 2018 Update, that will reach the end of 18 months of service on November 12, 2019, we are starting the update process now for Home and Pro editions to help ensure adequate time for a smooth update process.
Our update rollout process takes into consideration the scale and complexity of the Windows 10 ecosystem, with the many hardware, software, and app configuration options users have, to provide a seamless update experience for all users. We closely monitor update feedback to allow us to prioritize those devices likely to have a good update experience and quickly put safeguards on other devices while we address known issues. Windows 10 Home and Pro edition users will have the ability to pause the update for up to 35 days so they can choose a convenient time. The Windows 10 May 2019 Update is available for any user who manually selects “Check for updates” via Windows Update on a device that does not have a safeguard hold for issues already detected. If you are not offered the update, please check below for any known issues that may affect your device. We recommend commercial customers running earlier versions of Windows 10 begin targeted deployments of Windows 10, version 1903 to validate that the apps, devices, and infrastructure used by their organizations work as expected with the new release and features. Note Follow @WindowsUpdate to find out when new content is published to the release information dashboard. |
| Summary | Originating update | Status | Last updated |
| The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU Some apps or games that needs to perform graphics intensive operations may close or fail to open on Surface Book 2 devices with Nvidia dGPU. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Acknowledged | July 12, 2019 04:20 PM PT |
| The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU Some apps or games that needs to perform graphics intensive operations may close or fail to open on Surface Book 2 devices with Nvidia dGPU. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | July 16, 2019 09:04 AM PT |
| Initiating a Remote Desktop connection may result in black screen When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | July 12, 2019 04:42 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 10, 2019 06:06 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 |
| Details | Originating update | Status | History |
| The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU Microsoft has identified a compatibility issue on some Surface Book 2 devices configured with Nvidia discrete graphics processing unit (dGPU). After updating to Windows 10, version 1903 (May 2019 Feature Update), some apps or games that needs to perform graphics intensive operations may close or fail to open. To safeguard your update experience, we have applied a compatibility hold on Surface Book 2 devices with Nvidia dGPUs from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Workaround: To mitigate the issue if you are already on Windows 10, version 1903, you can restart the device or select the Scan for hardware changes button in the Action menu or on the toolbar in Device Manager. 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.145 May 29, 2019 KB4497935 | Acknowledged | Last updated: July 12, 2019 04:20 PM PT Opened: July 12, 2019 04:20 PM PT |
| The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU Microsoft has identified a compatibility issue on some Surface Book 2 devices configured with Nvidia discrete graphics processing unit (dGPU). After updating to Windows 10, version 1903 (May 2019 Feature Update), some apps or games that needs to perform graphics intensive operations may close or fail to open. To safeguard your update experience, we have applied a compatibility hold on Surface Book 2 devices with Nvidia dGPUs from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Workaround: To mitigate the issue if you are already on Windows 10, version 1903, you can restart the device or select the Scan for hardware changes button in the Action menu or on the toolbar in Device Manager. 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.145 May 29, 2019 KB4497935 | Investigating | Last updated: July 16, 2019 09:04 AM PT Opened: July 12, 2019 04:20 PM PT |
| Initiating a Remote Desktop connection may result in black screen When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU). Affected platforms:
Next steps: We are working on a resolution that will be made available in upcoming release. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | Last updated: July 12, 2019 04:42 PM PT Opened: July 12, 2019 04:42 PM PT |
| Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503293 on a WDS server. Affected platforms:
Workaround: To mitigate this issue on an SCCM server:
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager. To mitigate this issue on a WDS server without SCCM:
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.175 June 11, 2019 KB4503293 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM PT |