Softpedia >News >Microsoft >Windows
Softpedia Homepage   

Microsoft Confirms New Bug in Windows 10 Cumulative Updates KB4503293, KB4503327

The July 2019 cumulative updates do not fix the issue

Jul 11, 2019 06:59 GMT  ·  By
The issue only hits Windows Server editions
   The issue only hits Windows Server editions

Microsoft has just confirmed a new issue introduced by the June 11 cumulative updates for a series of Windows 10 versions.

The software giant says that installing these cumulative updates could cause devices using PXE from a WDS or SCCM server to fail to start.

However, please note that this issue does not affect consumer editions of Windows 10, but only server SKUs, as you can find in the table below. Microsoft explains the following:

“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 [June 11 cumulative updates] on a WDS server.”

Workaround already available

The affected Windows 10 versions are the ones listed below:  

Windows Server 2008 SP2
Windows Server 2008 R2 SP1
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
Windows Server, version 1803
Windows Server 2019
Windows Server, version 1809
Windows Server, version 1903
Microsoft says a workaround already exists, and users can mitigate the issue on a SCCM server by checking if the Variable Window Extension is enable and setting the values of TFTP block size to 4096 and TFTP window size to 1.

“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,” Microsoft adds.

The company also explains that it’s already working on a fix for this problem, and this is projected to be included “in an upcoming release.” No further specifics have been provided on when the fix is supposed to land.