| Summary | Originating update | Status | Date resolved |
| Loss of functionality in Dynabook Smartphone Link app After updating to Windows 10, version 1903, you may experience a loss of functionality when using the Dynabook Smartphone Link application. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Resolved | July 11, 2019 01:54 PM PT |
| Audio not working with Dolby Atmos headphones and home theater Users may experience audio loss with Dolby Atmos headphones or Dolby Atmos home theater. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved | July 11, 2019 01:53 PM 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 | July 11, 2019 01:53 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 18362.175 June 11, 2019 KB4503293 | Resolved KB4501375 | June 27, 2019 10:00 AM PT |
| Duplicate folders and documents showing in user profile directory If known folders (e.g. Desktop, Documents, or Pictures folders) are redirected, an empty folder with that same name may be created. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved KB4497935 | May 29, 2019 02:00 PM PT |
| 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 |
| 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 |
| 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 |
| 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 KB4486563 | Resolved KB4486565 | February 19, 2019 02:00 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 > | February 12, 2019 KB4486563 | Resolved KB4486565 | 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 KB4480970 | Resolved KB4486563 | February 12, 2019 10:00 AM PT |
| Local Administrators unable to remotely access shares Local users who are part of the local Administrators group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines. See details > | January 08, 2019 KB4480970 | Resolved KB4487345 | January 11, 2019 02:00 PM 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 02:51 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) 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 |
| Details | Originating update | Status | History |
| 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 KB4503267 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 14393.3025 June 11, 2019 KB4503267 | Mitigated | Last updated: July 10, 2019 02:51 PM PT Opened: July 10, 2019 02:51 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 KB4503267 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 14393.3025 June 11, 2019 KB4503267 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM 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 16299.1217 June 11, 2019 KB4503284 | Mitigated | July 10, 2019 07:09 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\". See details > | OS Build 16299.904 January 08, 2019 KB4480978 | Mitigated | April 25, 2019 02:00 PM PT |
| 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 16299.1182 May 28, 2019 KB4499147 | Resolved KB4509477 | June 26, 2019 04: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 16299.1217 June 11, 2019 KB4503284 | Resolved KB4503281 | June 18, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| 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 KB4503284 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 16299.1217 June 11, 2019 KB4503284 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM 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 17134.829 June 11, 2019 KB4503286 | Mitigated | July 10, 2019 02:51 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) may fail to start with error \"0xc0000001.\" See details > | OS Build 17134.829 June 11, 2019 KB4503286 | Mitigated | July 10, 2019 07:09 PM PT |
| Startup to a black screen after installing updates Your device may startup to a black screen during the first logon after installing updates. See details > | OS Build 17134.829 June 11, 2019 KB4503286 | Mitigated | June 14, 2019 04:41 PM PT |
| Certain operations performed on a Cluster Shared Volume may fail Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\". See details > | OS Build 17134.523 January 08, 2019 KB4480966 | Mitigated | April 25, 2019 02:00 PM PT |
| 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 17134.799 May 21, 2019 KB4499183 | Resolved KB4509478 | June 26, 2019 04:00 PM PT |
| Details | Originating update | Status | History |
| 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 KB4503286 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 17134.829 June 11, 2019 KB4503286 | Mitigated | Last updated: July 10, 2019 02:51 PM PT Opened: July 10, 2019 02:51 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 KB4503286 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 17134.829 June 11, 2019 KB4503286 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM 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 17763.557 June 11, 2019 KB4503327 | Mitigated | July 10, 2019 02:51 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) may fail to start with error \"0xc0000001.\" See details > | OS Build 17763.557 June 11, 2019 KB4503327 | Mitigated | July 10, 2019 07:09 PM PT |
| Startup to a black screen after installing updates Your device may startup to a black screen during the first logon after installing updates. See details > | OS Build 17763.557 June 11, 2019 KB4503327 | Mitigated | June 14, 2019 04:41 PM PT |
| Devices with some Asian language packs installed may receive an error After installing the KB4493509 devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_F See details > | OS Build 17763.437 April 09, 2019 KB4493509 | Mitigated | May 03, 2019 10:59 AM PT |
| 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 17763.253 January 08, 2019 KB4480116 | Mitigated | April 09, 2019 10:00 AM PT |
| Details | Originating update | Status | History |
| 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 KB4503327 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 17763.557 June 11, 2019 KB4503327 | Mitigated | Last updated: July 10, 2019 02:51 PM PT Opened: July 10, 2019 02:51 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 KB4503327 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 17763.557 June 11, 2019 KB4503327 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM PT |
| Summary | Originating update | Status | Last updated |
| Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Investigating | June 10, 2019 06:06 PM PT |
| Loss of functionality in Dynabook Smartphone Link app After updating to Windows 10, version 1903, you may experience a loss of functionality when using the Dynabook Smartphone Link application. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Investigating | May 24, 2019 03:10 PM PT |
| Display brightness may not respond to adjustments Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Investigating | May 21, 2019 04:47 PM PT |
| Audio not working with Dolby Atmos headphones and home theater Users may experience audio loss with Dolby Atmos headphones or Dolby Atmos home theater. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Investigating | May 21, 2019 07:17 AM PT |
| 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 18362.175 June 11, 2019 KB4503293 | Mitigated | July 10, 2019 02:51 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) may fail to start with error \"0xc0000001.\" See details > | OS Build 18362.175 June 11, 2019 KB4503293 | Mitigated | July 10, 2019 07:09 PM PT |
| RASMAN service may stop working and result in the error “0xc0000005” The Remote Access Connection Manager (RASMAN) service may stop working and result in the error “0xc0000005” with VPN profiles configured as an Always On VPN connection. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Mitigated | July 01, 2019 05:04 PM PT |
| Error attempting to update with external USB device or memory card attached PCs with an external USB device or SD memory card attached may get error: \"This PC can't be upgraded to Windows 10.\" See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | June 11, 2019 12:34 PM PT |
| Gamma ramps, color profiles, and night light settings do not apply in some cases Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 24, 2019 11:02 AM PT |
| Unable to discover or connect to Bluetooth devices Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:48 PM PT |
| Intel Audio displays an intcdaud.sys notification Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:47 PM PT |
| Cannot launch Camera app Microsoft and Intel have identified an issue affecting Intel RealSense SR300 or Intel RealSense S200 camera apps. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:47 PM PT |
| Intermittent loss of Wi-Fi connectivity Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:46 PM PT |
| Loss of functionality in Dynabook Smartphone Link app After updating to Windows 10, version 1903, you may experience a loss of functionality when using the Dynabook Smartphone Link application. See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Resolved | July 11, 2019 01:54 PM PT |
| Audio not working with Dolby Atmos headphones and home theater Users may experience audio loss with Dolby Atmos headphones or Dolby Atmos home theater. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved | July 11, 2019 01:53 PM 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 | July 11, 2019 01:53 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 18362.175 June 11, 2019 KB4503293 | Resolved KB4501375 | June 27, 2019 10:00 AM PT |
| Duplicate folders and documents showing in user profile directory If known folders (e.g. Desktop, Documents, or Pictures folders) are redirected, an empty folder with that same name may be created. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved KB4497935 | May 29, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| 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 02:51 PM PT Opened: July 10, 2019 02:51 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 |
| Details | Originating update | Status | History |
| Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903. Affected platforms:
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 20, 2019 KB4505057 | Investigating | Last updated: June 10, 2019 06:06 PM PT Opened: May 24, 2019 04:20 PM PT |
| Loss of functionality in Dynabook Smartphone Link app Some users may experience a loss of functionality after updating to Windows 10, version 1903 when using the Dynabook Smartphone Link application on Windows devices. Loss of functionality may affect the display of phone numbers in the Call menu and the ability to answer phone calls on the Windows PC. To safeguard your update experience, we have applied a compatibility hold on devices with Dynabook Smartphone Link from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Next steps: Microsoft and Dynabook are working on a resolution; the Dynabook Smartphone Link application may have a loss of functionality until this issue is resolved. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Investigating | Last updated: May 24, 2019 03:10 PM PT Opened: May 24, 2019 03:10 PM PT |
| Display brightness may not respond to adjustments Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Window 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change. To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Workaround: Restart your device to apply changes to brightness. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: We are working on a resolution that will be made available in upcoming release. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Investigating | Last updated: May 21, 2019 04:47 PM PT Opened: May 21, 2019 07:56 AM PT |
| Audio not working with Dolby Atmos headphones and home theater After updating to Windows 10, version 1903, you may experience loss of audio with Dolby Atmos for home theater (free extension) or Dolby Atmos for headphones (paid extension) acquired through the Microsoft Store due to a licensing configuration error. This occurs due to an issue with a Microsoft Store licensing component, where license holders are not able to connect to the Dolby Access app and enable Dolby Atmos extensions. To safeguard your update experience, we have applied protective hold on devices from being offered Windows 10, version 1903 until this issue is resolved. This configuration error will not result in loss of access for the acquired license once the problem is resolved. Affected platforms:
Next steps: We are working on a resolution for Microsoft Store and estimate a solution will be available in mid-June. Note We recommend you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Investigating | Last updated: May 21, 2019 07:17 AM PT Opened: May 21, 2019 07:16 AM PT |
| 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:
Workaround: This issue has been partially resolved but to ensure seamless update experience, the safeguard hold is still in place. In the short term, we recommend you do the following workaround to update to Windows 10, version 1903. Remove all external media, such as USB devices and SD cards, from your computer and restart installation of the Windows 10, version 1903 feature update. The update should then proceed normally. Note If you need to keep your external device, SD memory card, or other devices attached to your computer while updating, we recommend that you do not attempt to manually update to Windows 10, version 1903 using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: 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: June 11, 2019 12:34 PM PT Opened: May 21, 2019 07:38 AM PT |
| Gamma ramps, color profiles, and night light settings do not apply in some cases Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working. Microsoft has identified some scenarios where night light settings may stop working, for example:
Affected platforms:
Workaround: If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer. For other color setting issues, restart your computer to correct the issue. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 24, 2019 11:02 AM PT Opened: May 21, 2019 07:28 AM PT |
| Unable to discover or connect to Bluetooth devices Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Realtek and Qualcomm. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Realtek or Qualcomm Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated. Affected platforms:
Workaround: Check with your device manufacturer (OEM) to see if an updated driver is available and install it.
Note Until an updated driver has been installed, we recommend you do not attempt to manually update using the Update now button or the Media Creation Tool. Next steps: Microsoft is working with Realtek and Qualcomm to release new drivers for all affected system via Windows Update. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:48 PM PT Opened: May 21, 2019 07:29 AM PT |
| Intel Audio displays an intcdaud.sys notification Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in higher than normal battery drain. If you see an intcdaud.sys notification or “What needs your attention” notification when trying to update to Windows 10, version 1903, you have an affected Intel Audio Display device driver installed on your machine (intcdaud.sys, versions 10.25.0.3 through 10.25.0.8). To safeguard your update experience, we have applied a compatibility hold on devices with drivers from being offered Windows 10, version 1903 until updated device drivers have been installed. Affected platforms:
Workaround: On the “What needs your attention\" notification, click the Back button to remain on your current version of Windows 10. (Do not click Confirm as this will proceed with the update and you may experience compatibility issues.) Affected devices will automatically revert to the previous working configuration. For more information, see Intel's customer support guidance and the Microsoft knowledge base article KB4465877. Note We recommend you do not attempt to update your devices until newer device drivers are installed. Next steps: You can opt to wait for newer drivers to be installed automatically through Windows Update or check with the computer manufacturer for the latest device driver software availability and installation procedures. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:47 PM PT Opened: May 21, 2019 07:22 AM PT |
| Cannot launch Camera app Microsoft and Intel have identified an issue affecting Intel RealSense SR300 and Intel RealSense S200 cameras when using the Camera app. After updating to the Windows 10 May 2019 Update and launching the Camera app, you may get an error message stating: \"Close other apps, error code: 0XA00F4243.” To safeguard your update experience, we have applied a protective hold on machines with Intel RealSense SR300 or Intel RealSense S200 cameras installed from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
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. 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:
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 |
| 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 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 |
| 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 > | June 11, 2019 KB4503276 | Mitigated | July 10, 2019 02:51 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) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503276 | Mitigated | July 10, 2019 07:09 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 |
| 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 |
| 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 KB4493446 | Mitigated | April 18, 2019 05:00 PM PT |
| Details | Originating update | Status | History |
| 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 KB4503276 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 | June 11, 2019 KB4503276 | Mitigated | Last updated: July 10, 2019 02:51 PM PT Opened: July 10, 2019 02:51 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 KB4503276 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 | June 11, 2019 KB4503276 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM 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 > | June 11, 2019 KB4503285 | Mitigated | July 10, 2019 02:51 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) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503285 | Mitigated | July 10, 2019 07:09 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 |
| 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 |
| Some devices and generation 2 Hyper-V VMs may have issues installing updates Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing some updates when Secure Boot is enabled. See details > | June 11, 2019 KB4503285 | Resolved KB4503295 | June 21, 2019 02:00 PM PT |
| Details | Originating update | Status | History |
| 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 KB4503285 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 | June 11, 2019 KB4503285 | Mitigated | Last updated: July 10, 2019 02:51 PM PT Opened: July 10, 2019 02:51 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 KB4503285 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 | June 11, 2019 KB4503285 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM PT |