Microsoft released the update KB4093105 for Windows 10 Fall Creators Update Version 1709 tonight , that is on the night of April 24, 2018 . The update is now available from Windows Update and Microsoft’s Windows Update Catalog. The update KB4093105 brings the Windows 10 build number to version 16299.402 .
Since this is again a cumulative update, all changes since the Fall Creators Update appeared in this update KB4093105 . Apparently Microsoft still needed this update so that there would be no problems when the Spring Creators Update 1803 is released.
The following changes are included in the update KB4093105 .
- Resolves issues that cause applications to reappear after upgrading the operating system version even though those applications were deprovisioned using remove-AppXProvisionedPackages-Online.
- Applications running as an administrator could cause the application to stop working if the user name or password was inserted into the user prompt (LUA).
- Problems with Skype and Xbox have been fixed.
- Addresses an issue that prevents Autodiscover from being used in Microsoft Outlook 2013 to set up email accounts when UE-V is enabled.
- Resolves issues where AppLocker Publisher rules applied to MSI files do not match the files correctly.
- Windows Hello was able to generate good keys due to TPM firmware problems when weak cryptographic keys are detected. This problem only occurs if the policy that the TPM requires is configured.
- Addresses an issue that prevents users from being able to unlock their session and sometimes displays incorrect username @ domain name information on the login screen when multiple users log on to a computer with quick user changes. This is especially true when users log in from multiple different domains, use the UPN format for their domain credentials (username @ domain name), and switch between users who use the fast user switch.
- Addresses an issue where the browser often asks for credentials instead of just once when using the Office Chrome extension.
- Addresses issues related to smart cards that allow PINs or biometric input . If the user enters an incorrect PIN or biometric input (e.g. a fingerprint), an error is displayed and the user has to wait up to 30 seconds. With this change, the 30 second delay is no longer required.
- Increases the minimum password length in GPOs to 20 characters.
- Addresses an issue in which the name restriction information is not displayed correctly when viewing certificate properties. Instead of displaying properly formatted data, the information is presented in hexadecimal format.
- Addresses an issue that blocks failed NTLM authentication instead of only logging it when using an authentication policy with audit mode enabled. Netlogon.log may display the following: SamLogon: Transitive network login from <domain> <user> from <
machine2 > (via < machine1 >) NlpVerifyAllowedToAuthenticate: AuthzAccessCheck failed for A2ATo 0x5. This may be the lack of claims and composite support NTLM be due
SamLogon Transitive Network logon of <domain> <user> of <Machine2> (about <Machine1>) Returns 0xC0000413 Back - Addresses an issue that generated a certificate check error 0x800B0109 (CERT_E_UNTRUSTEDROOT) from http.sys.
- Addresses an issue in which resetting the Windows Hello PIN at the login prompt puts the system in a state that makes it impossible to reset the PIN again.
- Addresses an issue where the right-click context menu for encrypting and decrypting files using Windows Explorer is missing.
- Addresses issues where BitLocker or device encryption is suspended during device registration instead of protecting the drive.
- Addresses an issue that caused Microsoft Edge to stop working after a few seconds while running a software restriction policy.
- A filesystem minifilter could not be unloaded due to a leak in the Filter Manager that required a restart.
- Addresses an issue that causes the connection bar to be missing when connecting to virtual machines (VMConnect) when using full-screen mode on multiple monitors .
- Addresses an issue that prevents certain devices from being used on computers running Windows 10 version 1709 when Group Policy ” Disables new DMA devices when the computer is locked ” is active. The non-functioning devices are internal, PCI-based peripheral devices (wireless network drivers and input and audio peripheral devices). These peripherals can fail on systems whose firmware prevents the peripherals from performing direct memory access (DMA) at system startup.
- Addresses issues that may cause Windows Server 2016 domain controllers to log Microsoft Windows security audit events ID 4625 and ID 4776. The user name and domain name in the events may be truncated and only display the first character for client application logons with wldap32. DLL.
- Addresses an issue where users can exist in a trusted domain that uses the transitive trust. However, you cannot find a PDC or domain controller for the extranet lockout feature. The following exception occurs: “Microsoft.IdentityServer.Service.AccountPolicy.ADACcountLookupException: MSIS6080: An attempt to bind to domain” globalivewireless.local “failed with error code” 1722.
The following message is also displayed on the IDP page: “Incorrect user ID or password. Enter the correct user ID and password and try again. ” - Addresses an issue that prevents Active Directory objects with invalid backlink attributes from being changed or restored in their class. The error you get is “ Error 0x207D An attempt was made. ”
- Addresses an issue that prevents the AdminSDHolder task from running when a protected group contains a member attribute that points to a deleted object. Additionally, event 1126 is logged as “Active Directory Domain Services was unable to connect to the global catalog. Error value: 8430. The directory service encountered an internal error. Internal ID: 320130e. ”
- Addresses an issue that occurs when Volume Shadow Copy is enabled on a volume that hosts a file share. When the client accesses the UNC path to view the properties on the Previous Version tab, the Date Modified field is blank.
- Addresses an issue that occurs when a user with a roaming user profile first logs on to and logs off from a Windows 10 version 1607 computer. If the user later tries to log on to a computer running Windows 10, Version 1703 executed and Microsoft Edge opens, Microsoft Edge will no longer work.
- Addresses issues that prevent a Japanese keyboard from being used in remote support sessions.
- Fixes an issue that caused the cursor to move unexpectedly to the center of the screen when changing display mode.
- Addresses a potential leak caused by opening and closing a new web browser control.
- Addresses an issue with the Find tab from Microsoft Outlook 2016 during the upgrade from Windows 10 version 1703 to Windows 10 version 1709.
- Also fixes the issue where updates for large game apps fail.
- Addresses an issue that in some cases removes user-pinned folders or tiles from the Start menu
- Fixes the problem that invisible apps appear in the start menu .
- Addresses an issue that could cause some users to pan or scroll unexpectedly when using the pen in certain apps.
You can download the update KB4093105 here:
– 2018-04 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4093105)
– 2018-04 Cumulative Update for Windows 10 Version 1709 for x86-based Systems (KB4093105)
– 2018-04 Cumulative Update for Windows Server 2016 (KB4093105 )