Related topics
Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Release Date:



Preview of Monthly Rollup

Improvements and fixes

This non-security update includes improvements and fixes that were a part of KB4074594 (released February 13, 2018) and also includes these new quality improvements as a preview of the next Monthly Rollup update:

  • Addresses issue where  iSCSI target redirection during login may cause Stop error 9f.

  • Addresses issue that causes services.exe to stop working after applying the "Obtain an impersonation token for another user in the same session” privilege to Windows Server 2012 R2 computers. These computers then enter a restart loop. The system may report the SceCli event ID 1202 with error 0x4b8. It may also report the Application Error event ID 1000 with the faulting module name scesrv.dll and the exception code 0xc0000409. This privilege was first introduced in Windows Server 2016.

  • Updates time zone information.

  • Addresses issue in which unidrv.dll was not updated after updating.

  • Addresses issue in which the Microsoft Management Console becomes unresponsive while creating a scheduled task from a Group Policy Object (GPO).

  • Addresses issue in which a server error occurs occasionally during file transfer. The error is “Stop D1 in tcpip!TcpSegmentTcbSend”.

  • Addresses issue in which, when large snapshots are created during the backup of Hyper-V clusters, the Spaces volume may fail to come online after being offline. To recover the Space volume after this issue occurs, install this update and then follow the steps described in KB4089120.

  • Addresses issue in which the Microsoft Management Console stops working when processing clipboard copy notifications.

  • Addresses issue in which the Remote Desktop client returns a generic error message when the session limit has been reached. This occurs when the session limit has been set using the RDMS console.

  • Addresses issue in which a stop 0x9E error may occur in a Windows Server 2012 R2 Failover Cluster node when it hosts an NFS resource with NFS Activity Logging enabled.

  • Addresses issue in which, after installing .NET 4.7, creating a new DFS-Replication group or adding a member to an existing replication group in the DFS Management snap-in causes an error. The error is “The value does not fall within the expected range”.

  • Addresses issue in which SMB write operation that encrypts a packet may cause an error at RDR_FILE_SYSTEM (27) when the system is running low on memory.

  • Addresses a crash in LSASS.exe that causes unscheduled restarts on a Read-Only Domain Controller (RODC) computer. Logged events include:

    • USER32 Event 1074, noting that LSSAS.exe terminated unexpectedly with status code -1073740286.

    • WINNIT Event 1015: LSSAS.exe failed with status code c0000602.

    • APPLICATION ERROR Event 1000, citing a fault in LSSAS.exe version 6.3.9600.16384 and ESENT.dll version 6.3.9600.16384.

  • Addresses issue in which servers are configured to push their security event logs to a central server for analysis through a subscription. WinRM event query returns error "0x6c6 (RPC_S_INVALID_BOUND)" from the target server.

  • Addresses issue in which a Server Message Block (SMB) file share may fail to be created on scale-out file server (SOFS) resources. This occurs after the owner nodes are drained, the resources fail back, and the system uptime is between 25 and 49 days.

  • Addresses issue in which the certutil.exe -MergePfx command could not produce a merged EPF file for multiple V1 certificates.

  • Addresses issue in which failover in MPIO while throttling input and output requests may cause all available paths to fail.

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 KB4093121. You no longer need the following ALLOW REGKEY to detect and be offered this update: 


How to get this update

This is provided as an optional update on Windows Update. For more information about how to run Windows Update, see How to get an update through Windows 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 update 4075212

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?

Thank you for your feedback!