Improvements and fixes
This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:
- Addresses issue where child accounts are able to access InPrivate mode on ARM devices even though their browsing and search history is sent to their parents. This occurs only on Microsoft accounts belonging to children that are managed using the Microsoft Family service and for which parents have enabled activity reporting. This applies to Microsoft Edge and Internet Explorer.
Addresses issue with docking and undocking Internet Explorer windows.
Addresses issue in Internet Explorer where pressing the delete key inserted a new line in input boxes in an application.
Addresses issue in Internet Explorer where selected elements wouldn't update under certain circumstances.
Addresses issue where some users may have experienced issues logging into some websites when using third-party account credentials in Microsoft Edge.
- Updates time zone information.
- Addresses issue with browser Compatibility View settings that occurs during updates.
- Addresses issue where, in certain hardware configurations, the frame rates of DirectX Games were unintentionally limited to a factor of the display's vertical synchronization.
- Addresses issue that causes delays when switching keyboard languages using Alt+Shift.
- Addresses issue where surround sound audio endpoints reverted to stereo after restarting.
- Improves and reduces conditions where certain Bluetooth keyboards drop keys during reconnection scenarios.
- Corrects mouse delays for devices that incorrectly report the battery level status.
- Addresses issue where MMC application snap-ins—such as Services, Local Policy Admin, and Printer Management—fail to run when Windows Defender Application Control (Device Guard) is turned on. The error is "Object doesn't support this property or method".
- Prevents use of the Pre-production Onesettings endpoint for Windows Setup when test signing is enabled.
- Addresses issue where installations of Windows Server, version 1709 are not automatically activated using the Automated Virtual Machine Activation (AVMA) feature on Hyper-V hosts that have been activated.
Addresses issue with the Auto-register Inbox templates feature for UEV where the Scheduled Task didn't have the proper trigger.
Addresses issue where the App-V client didn't read the policy for SyncOnBatteriesEnabled when the policy was set using a Group Policy Object (GPO).
Addresses issue where the Supported On field for the Enable App-V Client policy is blank in the Group Policy editor.
Addresses issue where the user’s hive data in the registry is not maintained correctly when some App-V packages belong to the connection group.
Provides additional logging for administrators to take action, such as picking a proper configuration for their App-V package, when there are multiple configuration files for a single package.
Addresses issue with App-V packages that aren't compatible with registry virtualization using kernel containers. To address the issue, we changed the registry virtualization to use the earlier (non-container) method by default. Customers who would like to use the new (kernel container) method for registry virtualization can still switch to it by setting the following registry value to 1:
- Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Compatibility
- Setting: ContainerRegistryEnabled
- DataType: DWORD
- Addresses issue in which WPF applications that are running on touch or stylus-enabled systems may stop working or stop responding after some time without any touch activity.
- Security updates to Microsoft Scripting Engine, Microsoft Edge, Internet Explorer, Microsoft Windows Search component, Windows Kernel, Windows Authentication, Device Guard, Common Log File System driver, and the Windows storage and file systems.
If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.
For more information about the resolved security vulnerabilities, see the Security Update Guide.
Known issues in this update
|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:
How to get this update
This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website.
For a list of the files that are provided in this update, download the file information for cumulative update 4074588.