KB4074588

Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.

This issue is resolved in KB4088776.

After installing this update, some USB devices and onboard devices, such as a built-in laptop camera, keyboard or mouse, may stop working.  This may occur when the windows update servicing stack incorrectly skips installing the newer version of some critical drivers in the cumulative update and uninstalls the currently active drivers during maintenance.

This issue is resolved in KB4090913.

After installing this update, some devices may fail to boot with INACCESSIBLE_BOOT_DEVICE.

This issue occurs when the windows update servicing stack incorrectly skips installing the newer version of some critical drivers in the cumulative update and uninstalls the currently active drivers during maintenance. 

This issue is resolved in KB4090913.

Because of an AD FS server issue that causes the WID AD FS database to become unusable after a restart, the AD FS service may fail to start.

This issue is resolved in KB4088776.

Users with Windows 10 Version 1709 Enterprise that have installed the January 2018 Delta package may encounter failure issues when installing the February and March 2018 updates from the Microsoft Update Catalog. Specifically, the Windows 10, version 1709 February Delta Update may silently fail.

Microsoft is aware of this issue and has expired the following Windows 10 version 1709 Delta Update KBs on the Microsoft Catalog on March 13, 2018:

KB4056892– January 2018

KB4074588 – February 2018

KB4088776 – March 2018

Microsoft recommends that users uninstall the Windows 10 version 1709 January KB4056892 Delta Update package and install the March 2018 full latest cumulative update, KB4088776. Customers may resume using Delta Update packages with the April 2018 Windows 10 version 1709 monthly cumulative update.

After installing this update, applications may not be able to reserve or bind to ports that previously worked.

To resolve this issue, use the following workaround.

Check if the port you want to bind to or reserve is already reserved on the container host. For example, you can use  netsh as follows:   

netsh interface ipv4 show excludedportrange protocol=tcp

 
If the port is not reserved, you may use it. If it is reserved, choose a different port.