Windows Server 2012 R2의 Rollup 리스트 입니다. 

Windows Server 2012 R2는 현재 주력으로 쓰이는 OS라 그런지 패치가 많습니다.

July 21, 2016 — KB3172614

  • Addressed issue in Host Bus Adapters (HBA) that was including non-Fibre Channel HBA devices in the Fibre Channel HBA list.
  • Added support to set the idle timeout value of a TCP connection used by WinHTTP.
  • When you try to configure connecting a SCSI storage device to a Windows Hyper-V Host, the Host will not recognize the SCSI storage device when Logical Unit (LUN) 0 is not present.
  • When there is more logging session churn on the system because of workloads that are being run, Event Tracking (ETW) will crash.
  • Improved reliability of Hyper-V Replica (HVR) by increasing the timeout value and the free disk space threshold. For more info, see KB3184854.
  • If you installed the May 2016 update rollup for Windows 8.1 and Windows Server 2012 R2 (KB3156418), the DFSRS.exe process may consume a high percentage of CPU processing power (up to 100 percent). This may cause the DFSR service to become unresponsive and you may be unable to stop the service. You must hard-boot affected computers to restart them.

August 16, 2016 — KB3179574

  • Addressed issue that causes the loss of available memory when running queries using the domain name service (DNS).
    Improved performance by addressing an issue that was causing duplicate broadcast data packets to be received by each network interface card (NIC) and sent to applications, when NIC Teaming or Load Balancing/Failover (LBFO) is set-up in active/passive mode.
  • Addressed issue that sometimes causes backups to fail or servers to hang with drivers that use the IoVolumeDeviceToDosName() routine.
  • Addressed issue with domain controllers that periodically reboot after a Local Security Authority Subsystem Service (LSASS) module fault, causing the interruption of application and services that are bound to the domain controller at that time.
  • Addressed issue with DNS servers that get stuck in a loop and stop responding to DNS queries.
  • Addressed issue with cluster services that stop working when network loss logging occurs. This occurs when a network connection is down and virtual machines (VM) are configured with one possible owner.
  • Addressed issue in Server Message Block (SMB) server that causes the server to crash intermittently with error 0x50.
  • Addressed issue that causes domain controllers (DC) to stop working when generating compounded tickets.

September 20, 2016 — KB3185279

  • Addressed issue that causes Windows Explorer to become unresponsive when sharing a folder that is the child of at least two shared parent folders.
  • Addressed issue with Storage Spaces log truncation which resulted in data loss and errors when reading records.
  • Addressed issue that occurs with any MPIO attached SAN disk when multiple paths fail over concurrently or in quick succession, the I/O operation may fail, and the computer may lose its connection to the storage device.
  • Addressed issue that causes wbengine.exe to fail while running Windows Backup on a GUID Partition Table (GPT) formatted disk.
  • Addressed issue (after installing KB3161606) where running data deduplication on a Cluster Shared Volume (CSV) on Windows Server 2012 R2 based Hyper-V cluster might impact live migration where resource hosting subsystem (RHS) may deadlock and become unresponsive with an 0x9E Stop error.

November 8, 2016 — KB3197874 (Monthly Rollup)

  • Addressed issue with a shared drive that becomes unavailable and takes up to 20 minutes to recover.
  • Addressed issue with memory leaks that occur in the ISCSI WMI Provider. The WMI service fails to perform certain WMI queries, and the provider terminates, which can cause an outage.
  • Addressed issue where LSASS would consume 100% CPU on domain controller role machines due to the intersecting of large database indexes when handling a search request from LDAP clients.
  • Addressed issue where Microsoft Distributed Transaction Coordinator (MS DTC) is restarted and SQL Server instances might not be able to reconnect to MS DTC successfully. Therefore, distributed transactions might fail with an error message until you restart the SQL server instances.
  • Addressed issue where virtual machines (VMs) on a Hyper-V failover cluster causes instability and crashes.

December 13, 2016—KB3205401 (Monthly Rollup)

  • Addressed issue where updating the driver for the onboard RAID controller to a version higher than the RTM version causes all impacted servers to stop responding indefinitel
  • Addressed issue where a cluster node that has lost network connectivity doesn’t fail over properly to the partner node that has full network connectivity. On the node with full network connectivity, the cluster services shut down.
  • Addressed issue where, after enabling the Cluster Service’s IgnorePersistentStateOnStartup switch for troubleshooting, you must restart the entire cluster to exit diagnostic mode when troubleshooting is done.
  • Addressed issue with a consistent five-second delay during network data transfer to a Microsoft iSCSI Initiator Server.
  • Addressed issue where a disk that’s configured with the Resilient File System (ReFS) stops working when it’s under heavy loads and is using software that makes calls to a Direct Access Storage Device (DASD) I/O. Any infrastructure or components that rely on this disk will also stop working.
  • Addressed issue where some cluster nodes become unresponsive when the Wmiprvse service fails.
  • Addressed issue with lost access to a shared Resilient File System (ReFS) volume folder when a write operation occurs and its parent folder is being renamed concurrently. The file server (ReFS) becomes unavailable.
    Improved server’s first boot time.
  • Addressed issue where timeout failures occur when using Microsoft Multipath I/O (MPIO.SYS) and a path temporarily fails.

March 14, 2017—KB4012216 (Monthly Rollup)

  • Improved performance during monthly patching when Address Windowing Extensions are enabled for SQL.
  • Improved reliability for Server 2012 r2 clustered environments.

April 11, 2017—KB4015550 (Monthly Rollup)

  • Addressed issue where a Scale-Out File Server that uses dual parity disks loses access to a disk if a disk fails while the parity log is being written.
  • Addressed issue with the Spaceport driver that causes disks to detach after a hard restart.
  • Addressed issue in multipath I/O when Driver Verifier is enabled.
  • Addressed issue that causes crashes in a customer’s data path management software because of a regression in multipath I/O after installing KB3185279, KB3185331, or KB3192404.
  • Addressed issue where installation of KB3121261 on a third-party, thinly provisioned Storage Area Network causes multipath I/O Event ID 48. This is in response to Small Computer System Interface status - 0X28 - SCSISTAT_QUEUE_FULL (SRB Status - 0X4 - SRB_STATUS_ERROR).
  • Addressed issue with multipath I/O failure that can lead to data corruption or application failures.
  • Addressed issue that causes a crash when the user tries to connect to the server using WinShare and Remote Desktop Services. Stop error 0x50 at win32k!pDCIAdjClr+0x4f.
  • Addressed issue that breaks high-availability and fail over of a clustered virtual machine (VM). This occurs when the default data store settings for the VMs are configured inconsistently across the nodes in the cluster. For example, some data store settings are in %ProgramData%, while others use shared storage.
  • Addressed issue where, under high load, the background tasks threads are blocked. None of the clusters that use Virtual Hard Disk Sharing can access their disks. This results in unresponsive virtual machines.
  • Addressed issue (error 0x800b) that causes System Center Virtual Machine Manager to fail after live migrating a virtual machine between two Hyper-V clusters.
  • Addressed issue with random crashes on Hyper-V servers when users access Virtual Hard Disk files on Cluster Shared Volumes.
  • Addressed issue that causes file share witnesses stored on a Scale-Out File Server cluster 2012R2 to fail. Event ID for this Error is 1562 and you will get an Error 64 in the Cluster Log for the failed Healthcheck (from RFC 7205769).
  • Addressed issue to add the LiveDump capture feature that will trigger a live kernel dump if requests are stuck for an extended period.
  • Addressed issue where Failover Cluster Manager crashes when connecting to a cluster with a long name (15+ characters). This occurs after .NET 4.6.1 is installed.
  • Addressed issue that crashes Exchange servers whenever a customer installs an Exchange cumulative or security update. Error code: STOP 0x3B
  • Addressed a bug check encountered on Windows Server 2012 R2 Hyper-V hosts with error code 0xE4 after installing KB4012216.
  • Addressed issue where a server may fail with STOP 0x3B error leading to data loss when Input Method Editors (IME) like keyboards are installed.

May 9, 2017—KB4019215 (Monthly Rollup)

  • Addressed an issue that may cause the WSMan Service (WsmSvc) to crash randomly when multiple Windows Remote Management (WinRM) requests are being executed in the WSMan Service.
  • Addressed issue where the Event subscription service stops working, does not send events to the collector server, and drop events when using Windows Remote Management (WinRM) and event forwarding.
  • Addressed high CPU utilization by the Wmiprvse.exe process on a computer that is running Windows 8.1 or Windows Server 2012 R2. If you run scripts or use software that queries WMI, the Wmiprvse.exe process may consume a lot of CPU resources even after you stop the script or software
  • Addressed issue where Hyper-V hosts may crash when performing incremental backups with Change Block Tracking (CBT) enabled
  • Addressed issue that caused backups to fail on Hyper-V clusters with CSV volumes enabled.
  • Addressed issue where MPIO did not properly restore service after the check condition "Illegal request, LUN not available (sense codes 05/25/00)" occurs.
  • Addressed issue where a node cluster experiences sporadic crashes during high I/O activities such as backup or maintenance windows. Error: Common bucket ID  (WIN8_DRIVER_FAULT) - 0x3B_msiscsi!iSpReleaseConnectionReferences
  • Addressed issue that causes poor CPU performance when Virtual Switch Ports leak when a machine is migrated live from one host to another.
  • Addressed issue where thin clients connected to the server fail (STOP 0x3B) and unsaved data is lost.

June 13, 2017—KB4022726 (Monthly Rollup)

  • Addressed issue where the Server Message Block 3.0’s Continuous Availability feature degrades software performance when the FindFirstFileEx() function receives a path that ends with ".." or ".".
  • Addressed issue where the Common Log File System references an invalid parameter when users create new folders and new tasks using Task Scheduler, which generates Stop Error 0x24.
  • Addressed issue where a Virtual Machine sporadically loses its network connection completely.
  • Addressed issue where Windows Event Forwarding between two 2012 R2 servers makes reports incompatible with third-party Security Information and Event Management software.
  • Addressed an issue where LSASS consumes large amounts of memory on 2012 R2 Domain Controllers during a security descriptor propagation operation. This issue occurs when a security descriptor change is made on a root object with lots of descendants. Additionally, Applies To is set to "This object and all descendant objects."
  • Addressed issue where an unsupported hardware notification is shown and Windows Updates not scanning, for systems using the AMD Carrizo DDR4 processor or Windows Server 2012 R2 systems using Xeon E3V6 processor. For the affected system, follow the steps in the Additional Information section below to install this update.

July 11, 2017—KB4025336 (Monthly Rollup)

  • Addressed an issue where MPIO failover stops after a disk has been surprise removed, identified by Event ID 157: "Disk X has been surprised removed" when there are still viable paths to use. Scenario may occur when the newly selected path belongs to the disk that has been surprised removed
  • Addressed issue where a server crash causes loss of access to files and requires full recoveries for mirrored data.
  • Addressed issue with NTFS error event, ID:55, that occurs when using Unified Write Filter in DISK mode.
  • Addressed issue where, when running ChkDsk on a volume that has several million files, ChkDsk may take several weeks to complete and appears to be stuck in Stage 3.
  • Addressed issue about the Hyper-V integration service that causes users to lose network access when Accelerated Networking (single root I/O virtualization (SR-IOV)) is enabled on guest Virtual Machines (VM). The netvsc_vfpp protocol provides IO virtualization functionality for NICs that support SR-IOV. If the protocol is removed and multiple NICs are attached to a guest VM, network access is lost.
  • Addressed issue where the Microsoft Standard NVM Express Driver (stornvme) incorrectly exposed inactive namespaces as disks to the OS. The OS cannot use inactive namespaces and they should not be exposed to the OS.

August 8, 2017—KB4034681 (Monthly Rollup)

  • Addressed issue with a port and thread leak that can cause a broad array of symptoms including unresponsive systems and iSCSI target connection failures. This occurs after installing monthly updates released between April 11, 2017 (KB4015550) through July 11, 2017 (KB4025336). This issue was called out as known issue in the corresponding release notes for these releases
  • Addressed issue where LSASS.EXE encounters a deadlock and the server must be rebooted.
  • Addressed issue with a race condition that causes Lync Edge servers to randomly crash (Stop Error D1). Any active, open session within a federated domain loses connectivity for conference calls, instant messaging, etc.
  • Addressed issue where when a failover cluster fails over from one server to another, a clustered IP address resource does not come online and causes the failover to stop functioning.
  • Addressed issue where a LUN connection that was received after the buffer allocation during iSCSI statistic collection overflowed the buffer and caused error 0x19. A UI issue that hides the iSCSI targets will be addressed in an upcoming release..
  • Addressed issue where if there was an error on a storage controller, some paths could not fail over to other paths. Instead, access to the disk was completely lost.
  • Addressed issue where both transient and listener process TCP ports for the loopback sockets leak because of a leaked reference count. Such ports do not appear in NETSTAT.

September 12, 2017—KB4038792 (OS Build Monthly Rollup)

  • Addressed issue where unsynchronized access within NTFS may lead to an error.
  • Addressed issue where a LUN connection that was received after the buffer allocation during iSCSI statistic collection overflowed the buffer and caused error 0x19.
  • Addressed a UI issue that hides the iSCSI targets from the iSCSI initiator property windows.
  • Addressed issue where an extremely high number of I/O flushes may lead to an error.
  • Addressed issue where deleting an object that has many links in Active Directory causes replication to fail with Event 1084, error 8409 "A database error has occurred". For additional information, read KB3149779.
  • Addressed issue with an access violation in LSASS that occurs when Active Directory receives a malformed LsaLookupNames response. The signature of the LSASS AV is "The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819”. The system shuts down and restarts. Error 107374181 maps to 0xc0000005/STATUS_ACCESS_VIOLATION.
  • Addressed issue where running chkdsk /scan unexpectedly triggers spotfix. Sometimes spotfix times out, and the system goes down.
  • Addressed issue where the hardware clock may drift by hours or days when running Linux VM's on Hyper-V.

October 10, 2017—KB4041693 (Monthly Rollup)

  • Addressed issue where the performance counter query causes CPU usage to increase for extended periods of time. This occurs because EnumCounterObjects() queries the data for all counters when it tries to get the names of all counters.
  • Cleaned up leaked validation ports associated with snapshots in VMMS.
  • Addressed issue where users can't access file shares when the Windows Server 2012 R2 file server resource comes back online after it has gone offline.

November 14, 2017—KB4048958 (Monthly Rollup)

  • Addressed issue where Miniports that make 64-bit DMA requests from a single 4 GB region may fail, preventing the system from booting.

December 12, 2017—KB4054519 (Monthly Rollup)

  • Addressed issue to provide complete transparency about Replication Health. Replication Health represents the state of replication based on the following criteria: low free disk space, the Hyper-V Replica Log (HRL) reaching its maximum size, and violation of the Recovery Point Objectives (RPO) threshold.


+ Recent posts