Today, Microsoft released new cumulative updates for some older versions of Windows 10. Not to be forgotten about, the firm is also offering an update for Windows 8.1 and Server 2012 R2.
It"s a preview for next month"s Monthly Rollup, which means that it will show up as an optional update, likely until the second Tuesday of February, which is Patch Tuesday. You can manually download KB4057401 here.
Here"s what"s been fixed:
Addresses issue where every smart card logon to a Windows Terminal Server/Remote Desktop Server may result in a handle leak in the certprop service. Token leaks result in session leaks on computers that have installed MS16-111/KB3175024 and superseding fixes.
Addresses issue where servers running AppLocker stop working.
Addresses issue where an unexpected system restart occurs because of exception code 0xc0000005 (Access Violation) in LSASS.exe, where the faulting module is cryptnet.dll.
Addresses issue where, if the Online Certificate Status Protocol (OCSP) renewal date comes after the certificate expiration date, the OCSP-stapled response is used until the renewal date even though the certificate has expired.
Addresses multiple symptoms that occur during power transitions including a stop error 0x9F (0000009F) when a device tries to enter sleep mode or restart. USB PnP devices may also be unusable after waking from sleep.
Addresses issue where the iSCSI Initiator Properties Devices list doesn"t display certain targets.
Addresses issue where Event ID 1511 appears when you start a task that is created in Task Scheduler.
Addresses issue where a race condition in memory management may lead to Error 0x50 or 0x149 when trimming sparse files.
Addresses issue where AD FS incorrectly processed the wct parameter in a ws-federation request as a local time instead of a UTC value. This affects customers that federate AD FS with other third-party identity providers. Authentication failed because incorrect wct values implied bad or old requests.
Addresses issue where attempts to view the previous versions of a file on a file share fail. This occurs after a disk that hosts file shares goes offline and comes back online.
Addresses the following issues with the WinRM service:
A threading issue that may cause the WinRM service to crash under load. This is a client-side solution, so you must apply it to the affected computers(s) and the computers that communicate with the WinRM service.
A system performance issue that may cause logon to stop responding with the message, "Please wait for the Remote Desktop Configuration". This was caused by a deadlock in the WinRM service.
Addresses issue originally called out in KB4056895 where calling CoInitializeSecurity with the authentication parameter set to RPC_C_AUTHN_LEVEL_NONE resulted in the error STATUS_BAD_IMPERSONATION_LEVEL.
There"s also one known issue to be aware of:
| Symptom | Workaround |
|---|---|
| Due to an issue with some versions of antivirus software, this fix only applies to the machines where the antivirus ISV has updated the ALLOW REGKEY. | Contact your antivirus AV to confirm that their software is compatible and have set the following REGKEY on the machine Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD” Data="0x00000000” |
If you"re on the original version of Windows Server 2012, you"ll see KB4057402 as the preview for your Monthly Rollup. You can manually download it here, and it contains the following fixes:
Addresses issue where every smart card logon to a Windows Terminal Server/Remote Desktop Server may result in a handle leak in the certprop service. Token leaks result in session leaks on computers that have installed MS16-111/KB3175024 and superseding fixes.
Addresses the following issues with the WinRM service:
A threading issue that may cause the WinRM service to crash under load. This is a client-side solution, so you must apply it to the affected computers(s) and the computers that communicate with the WinRM service.
A system performance issue that may cause logon to stop responding with the message, "Please wait for the Remote Desktop Configuration". This was caused by a deadlock in the WinRM service.
Addresses issue originally called out in KB4056896 where calling CoInitializeSecurity with the authentication parameter set to RPC_C_AUTHN_LEVEL_NONE resulted in the error STATUS_BAD_IMPERSONATION_LEVEL.
There are no known issues in KB4057402.
Oddly enough, Microsoft hasn"t released anything new for Windows 7 or Server 2008 R2 SP1. Presumably, those previews will arrive later on this month.