Microsoft outs new cumulative updates for Windows 10 Creators and Anniversary Update PCs

We're just a calendar week beyond Microsoft's standard Patch Tuesday release, but the visitor is already issuing another set of cumulative updates for some Windows 10 PCs. This time, updates are available for PCs on the Creators Update and the Anniversary Update, bringing along a slew of fixes for both.

If your PC is all the same on the Anniversary Update, you'll run across the update as KB4093120, which ticks the build number up to 14393.2214. Here's the lengthy look at what's fixed:

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

Addresses an outcome 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 consequence that causes Microsoft and Azure Active Directory accounts to receive the countersign prompt repeatedly instead of just once.

Addresses an issue that prevents Windows Hello from generating good keys when it detects weak cryptographic keys considering 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 event that blocks failed NTLM authentications instead of only logging them when using an hallmark policy with audit mode turned on. Netlogon.log may show the following:

SamLogon: Transitive Network logon of \ from (via ) Returns 0xC0000413

SamLogon: Transitive Network logon of \ from (via ) Entered

NlpVerifyAllowedToAuthenticate: AuthzAccessCheck failed for A2ATo 0x5. This tin 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 terminate 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 downwards a reckoner afterwards applying an update. vmms.exe doesn't wait for vmwp.exe to finish copying VM retention data.

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

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

Addresses an unhandled refresh token validation event. Information technology 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 consequence 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 effort once again when connexion is available."

Addresses an effect that causes the failover of an NFS server cluster resource to take a long fourth dimension if the advice from the NFS server to the NFS client is blocked. If the failover takes more than 20 minutes, terminate error 0x9E (USER_MODE_HEALTH_MONITOR) occurs.

Addresses an issue that may generate a capacity reserve fault alert during cluster validation or while running the Debug-StorageSubSystem cmdlet even though plenty capacity is actually reserved. The warning is "The storage pool does non accept the minimum recommended reserve capacity. This may limit your power to restore data resiliency in the upshot of drive failure(south)."

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

Addresses an issue in Windows Multipoint Server 2022 that may generate the error "The MultiPoint service is non responding on this machine. To fix the upshot effort restarting the automobile."

Addresses an event that prevents a UDP profile from loading. This loading failure generates the fault "We can't sign into your business relationship", and users receive a temporary contour.

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

Addresses an consequence 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.

For those still on the Creators Update, you'll run into an update labeled KB4093117, which moves the build number upwards to 15063.1058. Here's a look at what'south fixed:

Addresses an issue that causes Microsoft Edge to terminate working after a few seconds when running a software restriction policy.

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

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

Addresses an upshot that prevents Windows Hello from generating adept keys when information technology detects weak cryptographic keys because of TPM firmware issues. This consequence just occurs if the policy to require the TPM is configured.

Addresses an outcome that prevents users from unlocking their session and that sometimes displays incorrect user-name@domain-name information on the logon screen when multiple users log on to a machine using fast user switching. Specifically, this happens when users are logging on from several different domains, are using the UPN format for their domain credentials (user-name@domain-name), and are switching between users with fast user switching.

Addresses an issue related to smart cards that allow PINs or biometric entry. If the user enters an incorrect Pivot or biometric input (east.grand., a fingerprint), an error appears, and the user must wait upward to 30 seconds. With this change, the xxx-2nd delay is no longer required.

Addresses an result that causes the browser to prompt for credentials often instead of only one time when using the Office Chrome extension.

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

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

Addresses an outcome that blocks failed NTLM authentications instead of only logging them when using an authentication policy with audit mode turned on. Netlogon.log may evidence the post-obit:

SamLogon: Transitive Network logon of \ from (via ) Entered

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

SamLogon: Transitive Network logon of \ from (via ) Returns 0xC0000413

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

Addresses an issue where the right-click context bill of fare for encrypting and decrypting files using Windows Explorer is missing.

Addresses an issue that suspends BitLocker or Device Encryption during device unenrollment instead of keeping the drive protected.

Addresses an issue that might crusade Centennial apps to block the ability to set user-level quotas for NTFS.

Addresses an issue that causes the connection bar to be missing in Virtual Auto Connection (VMConnect) when using full-screen mode on multiple monitors.

Addresses an result where using a GPO logon script to map a network drive fails if the user disconnects from the network and restarts. When the user logs in again, the mapped bulldoze isn't bachelor. This issue occurs even though the logon script has the persistence flag set to TRUE.

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

Addresses an issue that occurs when Volume Shadow Copy is enabled on a volume that hosts a file share. If the customer accesses the UNC path to view the properties in the Previous Version tab, the Date Modified field is empty.

Addresses an issue that occurs when a user with a roaming user profile offset logs on to a machine running Windows 10, version 1607, and and then logs off. Later, if the user tries to log on to a machine running Windows ten, version 1703, and opens Microsoft Border, Microsoft Border will stop working.

Addresses a reliability issue with Cyberspace Explorer when inbound text in a RichEditText command.

Addresses a potential leak caused past opening and closing a new web browser control.

Addresses an issue that causes the ContentIndexter.AddAsync API to throw an unnecessary exception.

If you have a PC that's still running the Creators or Anniversary Updates, then these cumulative updates should exist available now via Windows Update. Notably, there are no known issues to be aware of with either update.

Nosotros may earn a committee for purchases using our links. Learn more.

New report reveals Microsoft's future AR strategy; HoloLens 3 is dead

Oh Dear

New study reveals Microsoft's future AR strategy; HoloLens three is dead

Business Insider has today published a follow-up study with more details about Microsoft's canceled HoloLens iii augmented reality headset. The partnership with Samsung is said to include a headset with a set of screens within, powered by a Samsung phone in your pocket.

Review: Surface Laptop SE is the new standard for K-8 Windows PCs

Keeping it affordable

Review: Surface Laptop SE is the new standard for One thousand-8 Windows PCs

Starting at just $250, Microsoft's outset foray into affordable laptops for the teaching marketplace is a winner. With a gorgeous design, excellent thermals, and a fantastic typing experience, Microsoft would do right to sell this directly to consumers equally well. Permit'due south just promise Intel can make a improve CPU.