Windows 10: Cumulative Update KB4093120 Windows 10 v1607 Build 14393.2214 April 17

Brink · Apr 16, 2018

April 17, 2018 - KB4093120 (OS Build 14393.2214)

Applies to: Windows 10 Version 1607, Windows Server 2016

Improvements and fixes

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

Addresses an issue in apps that occurs when using the Japanese IME.

Addresses an issue where AppLocker publisher rules applied to MSI files don’t match the files correctly.

Increases the minimum password length in Group Policy to 20 characters.

Addresses an issue that causes Microsoft and Azure Active Directory accounts to receive the password prompt repeatedly instead of only once.

Addresses an issue that prevents Windows Hello from generating good keys when it detects weak cryptographic keys because of TPM firmware issues. This issue only occurs if the policy to require the TPM is configured.

Addresses an issue that displays name-constraint information incorrectly when displaying certificate properties. Instead of presenting properly formatted data, the information is presented in hexadecimal format.

Addresses an issue that blocks failed NTLM authentications instead of only logging them when using an authentication policy with audit mode turned on. Netlogon.log may show the following:

SamLogon: Transitive Network logon of <domain>\<user> from <machine2> (via <machine1>) Returns 0xC0000413

SamLogon: Transitive Network logon of <domain>\<user> from <machine2> (via <machine1>) Entered

NlpVerifyAllowedToAuthenticate: AuthzAccessCheck failed for A2ATo 0x5. This can be due to the lack of claims and compound support in NTLM

Addresses an issue that generates certificate validation error 0x800B0109 (CERT_E_UNTRUSTEDROOT) from http.sys.

Addresses an issue that prevents ReFS partitions from being expanded if the volume was originally formatted using ReFS v1.

Addresses an issue that causes the host Hyper-V node to stop working when starting the hosted VM.

Addresses a Kernel deadlock that affects server availability.

Addresses an issue with Windows Update that prevents VMs from being saved after restarting or shutting down a computer after applying an update. vmms.exe doesn't wait for vmwp.exe to finish copying VM memory data.

Addresses an issue in which DTC stops responding in msdtcprx!CIConnSink::SendReceive during an XA recovery. During this failure, IXaMapper objects with identical RMIDs become corrupted.

Addresses an issue that prevents you from modifying or restoring Active Directory objects that have invalid backlink attributes populated in their class. The error you receive is, “Error 0x207D An attempt was made to modify an object to include an attribute that is not legal for its class.”

Addresses an unhandled refresh token validation issue. It generates the following error: “Microsoft.IdentityServer.Web.Protocols.OAuth.Exceptions.OAuthInvalidRefreshTokenException: MSIS9312: Received invalid OAuth refresh token. The refresh token was received earlier than the permitted time in the token.”

Addresses an issue that prevents ADDS DSAC from running on a client that has PowerShell Transcripting enabled. The following error appears: “Cannot connect to any domain. Refresh or try again when connection is available.”

Addresses an issue that causes the failover of an NFS server cluster resource to take a long time if the communication from the NFS server to the NFS client is blocked. If the failover takes more than 20 minutes, stop error 0x9E (USER_MODE_HEALTH_MONITOR) occurs.

Addresses an issue that may generate a capacity reserve fault warning during cluster validation or while running the Debug-StorageSubSystem cmdlet even though enough capacity is actually reserved. The warning is "The storage pool does not have the minimum recommended reserve capacity. This may limit your ability to restore data resiliency in the event of drive failure(s)."

Addresses an issue that may cause some files to be skipped and may create duplicate files in the Work Folder locations during full enumeration sync sessions.

Addresses an issue in Windows Multipoint Server 2016 that may generate the error “The MultiPoint service is not responding on this machine. To fix the issue try restarting the machine.”

Addresses an issue that prevents a UDP profile from loading. This loading failure generates the error "We can't sign into your account", and users receive a temporary profile.

Addresses an issue that causes the high contrast theme setting to be applied incorrectly when a user logs in using RDP.

Addresses an issue that causes a pairing problem for low-energy Bluetooth devices.

Addresses a reliability issue with Microsoft Outlook.

Addresses a reliability issue that occurs while pressing the Alt key when using a Microsoft Office application hosted in an ActiveX container.

If you installed earlier updates, only the new fixes in this package will be downloaded and installed on your device.

For more information about the resolved security vulnerabilities, see the Security Update Guide.

Windows Update Improvements
Microsoft has released an update directly to the Windows Update client to improve reliability. Any device running Windows 10 configured to receive updates automatically from Windows Update, including Enterprise and Pro editions, will be offered the latest Windows 10 Feature Update based on device compatibility and Windows Update for Business deferral policy. This does not apply to long-term servicing editions.

Known issues in this update

Symptom Workaround After installing the March 13, 2018 or later Cumulative Update for Windows 10 version 1607, only the latest Windows 10 feature update is returned as applicable. This prevents the deployment of previously released feature updates using ConfigMgr (current branch) and Windows 10 servicing plans. Decline all feature updates on the WSUS Server(s) except for the one that you want to deploy using ConfigMgr. Run another software update scan cycle from the ConfigMgr control panel (or wait until the client devices perform their next scan).

Microsoft is working on a resolution and will provide an update in an upcoming release.
How to get this update

To download and install this update, go to Settings > Update & Security > Windows Update and select Check online for updates from Microsoft Update.
To get the standalone package for this update, go to the Microsoft Update Catalog website.

File information

For a list of the files that are provided in this update, download the file information for cumulative update 4093120.
Click to expand...

Source: https://support.microsoft.com/en-us/help/4093120

*Arrow Download KB4093120 MSU for Windows 10 Version 1607 32-bit (x86) - 650.2 MB

*Arrow Download KB4093120 MSU for Windows 10 Version 1607 64-bit (x64) - 1230.3 MB

:)

ECRCSR · Apr 16, 2018

Mail and People Windows 10 April 2017

I tried setting up the test account and clicked the box to allow Microsoft to make changes to the computer. I did a restart, but my original account is the only option I have to sign in. I shut down and tried again with the same result. User accounts
only show my personal account. I'll check again tomorrow, but don't know how I would find or sign in to the "test" account. I understand computer logic, but have very limited knowledge about the technical setup.

- There are no other accounts on the PC

- April 21 update caused the issues to arise

- No error messages on the April 21 update

There are some interesting things in the update history. From oldest to current, here's what's on my computer.

- Mar 17/17 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4013429). Successfully installed.

- Mar 18/17 Update for Windows 10 Version 1607 ...(KB 3150513) Successfully installed

The above two updates seemed to fix the link between Mail and People. Mail was looking at People instead of the email cache.

- Apr 12/17 Cumulative Update ..... (KB4015217) Failed to install

- Apr 12/17 Security Update for Microsoft Silverlight (KB4017094) Failed to install

- Apr 12/17 Cumulative Update...(looks like it tried again) (4015217) Failed to install

-Apr 14/17 Security Update for Microsoft Silverlight (KB4017094) Successfully installed

-Apr 14/17 Adobe Flash Player (KB4018483) Successfully installed

-Apr 14/17 Malicious software removal (KB890830) Successfully installed

-Apr 14/17 Cumulative Update .... (KB4015217) Successfully installed

Failed updates were successfully installed on April 14. It was around April 17 that I noticed that you could set up a group name in People and add a list of email addresses. It was working fine until the Apr. 21 update.

-Apr 21/17 Update for Windows 10.... (KB3150513) Successfully installed

-May 1/17 Update for Windows 10......(KB3150513) Failed to install

-May 2/17 Update for Windows 10......(KB3150513) Successfully installed

-May 4/17 Update for Windows 10......(KB3150513) Successfully installed

Something seems wrong with this April 21 update. Why would it keep re-installing after it was already successful? Is it missing a cumulative update? The last cumulative update had all of the fixes that I noticed on April 17. but were gone after
April 21.

Rameez Alam Butt · Apr 16, 2018

May 9, 2017—KB4019472 (OS Build 14393.1198) won't install

Dear kindly download from given link and install it manually.

Windows 10 Help Forums

14393-1198-a.html

Brink · Apr 18, 2018

Update 4/18:

Known issues in this update

Symptom Workaround After installing the March 13, 2018 or later Cumulative Update for Windows 10 version 1607, only the latest Windows 10 feature update is returned as applicable. This prevents the deployment of previously released feature updates using ConfigMgr (current branch) and Windows 10 servicing plans. Decline all feature updates on the WSUS Server(s) except for the one that you want to deploy using ConfigMgr. Run another software update scan cycle from the ConfigMgr control panel (or wait until the client devices perform their next scan).

Microsoft is working on a resolution and will provide an update in an upcoming release.

Windows 10: Cumulative Update KB4093120 Windows 10 v1607 Build 14393.2214 April 17

Cumulative Update KB4093120 Windows 10 v1607 Build 14393.2214 April 17

Cumulative Update KB4093120 Windows 10 v1607 Build 14393.2214 April 17

Cumulative Update KB4093120 Windows 10 v1607 Build 14393.2214 April 17

Cumulative Update KB4093120 Windows 10 v1607 Build 14393.2214 April 17 - Similar Threads - Cumulative Update KB4093120

Cumulative Update KB4512495 Windows 10 v1607 Build 14393.3181 Aug. 17

Cumulative Update KB4493473 Windows 10 v1607 Build 14393.2941 April 25

Cumulative Update KB4493470 Windows 10 v1607 Build 14393.2906 April 9

Cumulative Update KB4480977 Windows 10 v1607 Build 14393.2759 -Jan. 17

Cumulative Update KB4103720 Windows 10 v1607 Build 14393.2273 - May 17

Cumulative Update KB4093117 Windows 10 v1703 Build 15063.1058 April 17

Cumulative Update KB4016635 for Windows 10 v1607 Build 14393.970

Cumulative Update KB4025334 Windows 10 v1607 Build 14393.1532

Cumulative Update KB4056890 Windows 10 v1607 Build 14393.2007

Users found this page by searching for:

Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4093120)

KB4093120

kb4093120 installation take long time?