Windows Server 2012 R2는 2018년 1, 2월에 중요 업데이트가 없습니다.

Windows Server 2012 는 17년 11월 부터 18년 02월까지 큰 이슈는 없는 것으로 보입니다.


January 17, 2018—KB4057402 (Preview of Monthly Rollup)

Windows Server 원격 관리를 담당하는 WinRM 서비스의 크래시, Deadlock에 대한 이슈가 해결 되었습니다.

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.

이번 Windows Server 2008 R2의 업데이트 중 중요한 내용을 정리해 보았습니다..


November 14, 2017—KB4048958 (Monthly Rollup)

Azure AD와 AD FS를 연동하는 이슈가 늘어나서 관련 이슈들이 많이 수정되는 것으로 보입니다.
  • Addressed issue in which AD FS can no longer ignore "prompt=login" during authentication. A "Disabled" option was added to support scenarios in which password authentication is not used. For more information, see AD FS ignores the "prompt=login" parameter during an authentication in Windows Server 2012 R2.
  • Addressed issue in AD FS in which MSISCookies in request headers could eventually overflow the headers size limit. This caused a failure to authenticate and return HTTP status code 400: “Bad Request - Header Too Long."
AD RMS Management console이 비 정상 종료되는 이슈가 수정 되었습니다.
  • Addressed issue in which adding user rights to an RMS template caused the Active Directory RMS management console (mmc.exe) to stop working and return an unexpected exception.
USBHUB.SYS가 랜덤하게 메모리를 손상시켜서 크래시가 발생하는 이슈가 수정된 것으로 보입니다. Server 에서 USBHUB.SYS로 인한 크래시가 얼마나 있었을지는 잘 모르겠습니다.
  • Addressed issue in which USBHUB.SYS randomly caused memory corruption that caused random system crashes that are extremely difficult to diagnose.
Miniport를 사용하는 장치 드라이버에서 DMA 요청에 이슈가 있으면 Booting이 안되는 이슈가 수정 되었습니다.
  • 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)

Hyper-V Replica 관련 수정이 나왔는데 Hyper-V Replica를 실제 사용하는 사례를 아직 많이 보지는 못한 것 같습니다.
  • 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.
SQL Server Reporting Service에서 drop-down list를 사용할 수 없었던 이슈가 수정 되었습니다.
  • Addresses issue where users of SQL Server Reporting Services may not be able to use the scrollbar in a drop-down list.



February 13, 2018—KB4074594 (Monthly Rollup)

Active Directory를 사용해서 Application 에 대한 제한을 가하는 AppLocker 서비스가 중지되는 이슈가 수정 되었습니다.
  • Addresses issue where servers running AppLocker stop working.
Lsass.exe가 잘못된 접근을 하여 시스템이 재부팅 되는 이슈가 수정 되었습니다. (이러한 이슈는 원인분석을 하기 위해서 재현을 해야 하는데 재현이 어럽기 때문에 분석에 어려움이 많습니다.)
  • 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.
Power 상태 변화 때문에 시스템이 크래시 되는 이슈가 수정 되었습니다. (Server는 전원을 High Performance로 설정해 놓기 때문에 큰 문제는 없을 것으로 보이지만 랩톱에서는 영향이 있을 것으로 보입니다.)
  • 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.
메모리 관리의 동기화 이슈로 BugCheck 0x50(PAGE_FAULT_IN_NONPAGED_AREA) , 0x149(REFS_FILE_SYSTEM) 크래시가 발생하는 이슈가 수정 되었습니다. Sparse files 을 사용할 때 문제가 되는 것이라고 하니 ReFS 를 사용하는 것이 이슈가 될 수 있을것 같습니다.
  • Addresses issue where a race condition in memory management may lead to Error 0x50 or 0x149 when trimming sparse files.
Windows Server의 원격 관리를 담당하는 WinRM 서비스 관련 이슈가 수정 되었습니다. WinRM 서비스가 크래시 되거나 WinRM 서비스의 Deadlock 이슈가 수정 되었습니다.
  • 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.
SharePoint가 SQL Server의 filesystem share를 사용하는데 SMB3이 Enable 되어 있으면 느려지는 이슈가 수정 되었습니다.
  • Addresses issue where when SharePoint writes to a SQL Server filestream share with SMB3 encryption enabled, the write may fail or execute very slowly.


Windows Server 2016 중요 update


August 23, 2016 — KB3176934 (OS Build 14393.82)

  • Addressed issue that was causing nodes to be disconnected from a Cluster service intermittently.


September 29, 2016 — KB3194496 (OS Builds 14393.222)

  • Improved reliability of the Windows Update Agent, shared drives, virtual private network (VPN), clustering, HTTP downloads, Internet Explorer 11, Hyper-V platform, multimedia playback, and Microsoft Edge.
  • Improved performance of push and local notifications, Hyper-V platform, and some social media websites using Microsoft Edge.


December 9, 2016 — KB3201845 (OS Build 14393.479)

  • Addressed issue that causes the loss of optional component (OC) state information, including all Hyper-V virtual machines, after upgrade.


December 13, 2016 — KB3206632 (OS Build 14393.576)

  • Addressed an issue with PCI.SYS saving and restoring invalid data for the Virtual Channel (VC) that was causing system errors during reboot cycles as well as failures to enumerate devices, that may lead to bugchecks.
  • Addressed issue where a Catalog-signed module installation does not work on Nano Server.


March 14, 2017—KB4013429 (OS Build 14393.953)

  • Addressed issue in KB3213986 where the Cluster Service may not start automatically on the first reboot after applying the update.
  • Addressed an issue which improves the reliability of Enable-ClusterS2D PowerShell cmdlet.
  • Addressed an issue where the Virtual Machine Management Service (Vmms.exe) may crash during a live migration of virtual machines.
  • Improved the bandwidth of SSD/NVMe drives available to application workloads during S2D rebuild operations.
  • Addressed an issue where Remote Desktop Servers crash with a Stop 0x27 in RxSelectAndSwitchPagingFileObject when RDP clients connect and utilize redirected drives, printers, or removable USB drives.
  • Addressed issue that occurs whenever the multipath IO attempts to log I/O statistics with no paths present.
  • Addressed issue that may decrease performance by up to 50% when Ethernet adapters that support receive side scaling (RSS) fail to re-enable RSS after a fault or system upgrade.
  • Addressed issue with multipath I/O failure that can lead to data corruption or application failures.
  • Addressed issue that occurs when a Network Driver Interface Specification function NdisMFreeSharedMemory() is not called at the correct Interrupt Request Level.
  • Addressed issue where SQL server takes 30 minutes to shut down on machines with a lot of RAM (>2TB).


April 11, 2017—KB4015217 (OS Build 14393.1066 and 14393.1083)

  • Improved the Host Network Service (HNS) to support an overlay network driver for use on Windows Server 2016 to connect containers across hosts using Docker Engine in Swarm Mode.
  • Addressed issue that causes virtual machines to fail during high I/O scenarios where the user may log in multiple times.
    Improved the reliability of Load Balancing/Failover (LBFO) whenever there is a resource rebalance, a device failure, or a surprise removal of a device.


May 9, 2017—KB4019472 (OS Build 14393.1198)

  • Addressed issue where multipath I/O did not properly restore service after the check condition "Illegal request, LUN not available (sense codes 05/25/00)" occurs.
  • Addressed issue where a Stop 0x27 error occurs after a user provides the domain username and password.
  • Addressed an issue with a paging file space leak that leads Windows to a crash, blue screen, or data loss.


June 13, 2017—KB4022715 (OS Build 14393.1358)

  • Addressed an issue where the network interface description name of a network adapter is not updated in Hyper-V after a device driver update.
  • Management of a NIC Team or vSwitch within Hyper-V Administrator or System Center Virtual Machine Manager may be affected.
  • Addressed issue that was causing devices to crash when hot plugging USB 3.0 Network Adapters
  • Addressed an issue where Cluster health service fails to report fault event to MAS HM component.


June 27, 2017—KB4022723 (OS Build 14393.1378)

  • Addressed issue where multipath I/O does not use other available paths during a failover scenario.
  • Addressed issue where Page faults for Demand Zero Pages are significantly slower (> 10%), which causes many applications to run slower.
  • Addressed issue with the Server Message Block Bandwidth limiting feature not working.
  • Addressed issue where the storage replication driver (wvrf.sys) is in an infinite loop.
  • Addressed issue where a 2012 R2 or below Remote Desktop License Server causes the 2016 Remote Desktop Services Host to crash and stop giving sessions to clients.
  • Addressed issue where you may lose access to storage disks when there are still available paths if there is an error on one of the multipath I/O paths.
  • Addressed issue where the creation of virtual disks fails in Windows Server 2016 storage spaces when the physical disk allocation is set to manual for all the selected disks.


July 11, 2017—KB4025339 (OS Build 14393.1480)

  • Addressed issue with 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 with memory leaks in the nonpaged pool with the "NDnd" tag, which causes the OS to crash.


July 18, 2017—KB4025334 (OS Build 14393.1532)

  • 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 (KB4015217) through July 11, 2017 (KB4025339).
  • This issue was called out as known issue in the corresponding release notes for these updates.
  • Addressed issue where faulty silicon in Solid-State Drives impacted the performance of the Microsoft Standard NVM Express Driver (stornvme).
  • Addressed issue where the Windows NVDIMM driver will attempt to dismount any volumes on the device and transition into a read-only state when NVDIMM devices lose persistence.
  • Addressed issue where when you use SCVMM to manage virtual servers, if any CSV is offline, SCVMM cannot enumerate or locate the CSVs on the clusters.
  • Addressed issue where when you enable deduplication on a volume larger than 10 TB, optimization may stop prematurely and never complete.
  • 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 an MPIO path failure on a Hyper-V host might lead to complete loss of disk access.
  • Addressed issue where a missing break statement might cause an MPIO LUN to be unexpectedly removed.
  • Addressed issue where NTFS referenced an invalid parameter when using Task Scheduler, resulting in Stop Error 0x24.
  • Addressed issue where the system would throw an error when attempting to mount a corrupt ReFS volume in Read-Only mode.
  • Addressed performance issues in ReFS when backing up many terabytes of data.
  • Addressed issue where a stuck thread in ReFS might cause memory corruption.
  • Addressed issue where the health of S2D clusters was inconsistently reported.


August 16, 2017—KB4034661 (OS Build 14393.1613)

  • Addressed issue where a black screen appears when launching an application on Citrix XenApp that was deployed from Windows Server 2016. For more details, read CTX225819.
  • Addressed issue where third-party directory structures caused Disk Cleanup to render a boot drive inaccessible.
  • Addressed issue where unsynchronized access in NtfsQueryLinksInfo led to a system crash.
  • Addressed issue where an extremely high number of I/O flushes might lead to an error.
  • Addressed issue by increasing the time out window when starting Docker for Windows to avoid 0x5b4 errors.


September 12, 2017—KB4038782 (OS Build 14393.1715)

  • Addressed issue where Windows Error Reporting doesn't clean up temporary files when there is a redirection on a folder.
  • Addressed issue where some Windows clients receive a 0xc0000005 ACCESS_VIOLATION error when trying to install drivers.


September 28, 2017—KB4038801 (OS Build 14393.1737)

  • Addressed issue where the size of a cloned file was improperly calculated by ReFS.
  • Addressed error STOP 0x44 in Npfs!NpFsdDirectoryControl.
  • Addressed error 0x1_SysCallNum_71_nt!KiSystemServiceExitPico.
  • Addressed issue that may occur when you inspect a corrupted VHDX file on a Hyper-V host; the error is “Multiple Bugcheck BAD_POOL_CALLER (c2) 0000000000000007; Attempt to free pool which was already freed”. However, when Special Pool is enabled, the error is “0xCC PAGE_FAULT_IN_FREED_SPECIAL_POOL”.
  • Addressed issue where ksecdd.sys causes LSASS to leak kernel memory in paged pool. This most commonly affects servers that host an HTTPS service and handle a heavy load of TLS handshakes from clients.
  • Addressed issue where attempting to extend a Clustered Shared Volume (the source disk) beyond 2 TB using Disk Management in the Storage Replica feature of Windows Server 2016 Datacenter Edition fails. The error is “There is not enough space available on the disk to complete this operation”. The same problem may occur when using the Resize-Partition PowerShell cmdlet. In this case, the error is “Not enough available capacity”.


October 17, 2017—KB4041688 (OS Build 14393.1794)

  • Improved M.2 NVMe SSD throughput when the queue size increases.
  • Addressed issue where running Event Tracing for Windows with Volsnap may result in error 0x50.
  • Addressed issue where Miniports that make 64-bit DMA requests from a single 4 GB region may fail, preventing the system from booting.
  • Addressed issue where a disk losing communication with its S2D cluster may lead to a stale fault domain descriptor for the enclosure.
  • Addressed issue where, if an update to a pool config header occurs when it’s performing a read function, a stop error may occur in a Windows Server 2016 Storage Spaces Directory (S2D) deployment.


November 27, 2017—KB4051033 (OS Build 14393.1914)

  • Addressed issue where a Storage Spaces Direct (S2D) drive that is failing or being removed from a node is incorrectly reported as healthy in admin tools. These tools include Get-Physical Disk, Server Manager, and Failover Cluster Manager.
  • Addressed issue where a repair job could be suspended indefinitely after re-adding a node to an S2D cluster.
  • Addressed issue where an incomplete Storage Spaces repair could lead to faulty metadata causing future repairs to stop working.
  • Addressed a token leak in services.exe that occurs after applying MS16-111/KB3175027. This results in a kernel session object leak that degrades system performance over time. This especially affects Terminal Server implementations, where more user logons typically occur.
  • Improved performance when launching applications that use Virtual Disk Service to manage volumes.
  • Addressed issue that causes the VmCompute process to stop working when you reset the Virtual Machine (VM) after Dynamic Memory (DM) changes its memory footprint. This occurs when Non-Uniform Memory Access (NUMA) spanning is disabled and DM is enabled.


December 12, 2017—KB4053579 (OS Build 14393.1944)

  • Addresses issue where users of SQL Server Reporting Services may not be able to use the scrollbar in a drop-down list.


January 17, 2018—KB4057142 (OS Build 14393.2034)

  • Addresses issue where some customers on a small subset of older AMD processors get into an unbootable state.
  • Improves compatibility with U.2 NVMe devices, specifically in hot-add/removal cases.
  • Addresses issue where the iSCSI Initiator Properties Devices list doesn't display certain targets.
  • Addresses synchronization issue where backing up large Resilient File System (ReFS) volumes may lead to errors 0xc2 and 7E.
  • Enables IT administrators to scientifically troubleshoot I/O failures using a comprehensive event log for the resiliency state transition.

감사합니다.



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.


감사합니다.
















Windows Server 2012의 중요 Rollup 입니다.


August 16, 2016 — KB3179575

  • Addressed issue that caused Cluster service on remaining nodes to stop unexpectedly when a failover cluster node experiences a power outage.


November 8, 2016 — KB3197877 (Monthly Rollup)

  • Addressed issue that causes high CPU usage whenever a significant number of files are opened simultaneously and folders are being renamed. 
  • Improved the reliability of Windows Kernel. 


December 13, 2016 — KB3205409 (Monthly Rollup)

  • Addressed issue where a cluster fails to form or nodes fail to join a cluster if the cluster database contains duplicate network or interface entries.


March 14, 2017—KB4012217 (Monthly Rollup)

  • Addressed issue that leads to a read I/O latency of > 70 milliseconds when the disk commit exceeds 90%, < 16 GB commit available, and the paging file is at its maximum size


April 11, 2017—KB4015551 (Monthly Rollup)

  • Addressed issue that causes outages and malfunctions in applications when a server machine is set up with the Resilient File System. Scenario triggers include: Use of built-in disk management utility and server manager; Antivirus software scans; Backup activity; Accessing network shares; Calls to the Direct Access Storage Device IO when under heavy load; Using File Explorer.
  • Addressed issue that causes servers to randomly lose the ability to make outbound TCP connections. The TCPIP log shows Events 4227 and 4231. http://support.microsoft.com/en-us/kb/3078411. 
  • 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 fail.


May 9, 2017—KB4019216 (Monthly Rollup)

  • Addressed issue where Active Directory servers become unresponsive and must be rebooted when they have a heavy load of services using group managed service accounts (gMSAs).


June 13, 2017—KB4022724 (Monthly Rollup)

  • Addressed issue where the WinRM service and subscriptions stop working and events are dropped when monitoring events and using event forwarding for large deployments.
  • 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 ".".


July 11, 2017—KB4025331 (Monthly Rollup)

  • Addressed issue that may occur when a service such as Exchange server tries to reestablish the Kerberos client session. The service may cause the system to become unresponsive because a Local Security Authority Subsystem Service (LSASS) CPU spike occurs because Kerberos purges compound tickets.


October 10, 2017—KB4041690 (Monthly Rollup)

  • Addressed issue where a service using a Managed Service Account (MSA) fails to connect to the domain after an automatic password update.
  • Addressed issue where some Remote Desktop users fail to log on to a Remote Desktop Server and encounter a black screen instead.
  • Addressed issue where a WMI handle leak may cause a system error when using the Unified Write Filter. The error code is “PAGE_FAULT_IN_NONPAGED_AREA (uwfreg.sys) 0x50”.





Windows Server 2008 R2 중요 업데이트 내용

아시는 것과 같이 Windows Server 2008 R2도 Monthly Rollup으로 제공되고 있으며 아래와 같은 중요 업데이트가 있었습니다.


August 16, 2016 — KB3179573

  • Improved performance on specific networks that have a high-bandwidth and low latency.


September 20, 2016 — KB3185278

  • Improved support for the Disk Cleanup tool to free up space by removing older Windows Updates after they are superseded by newer updates.
  • Addressed issue that causes mmc.exe to consume 100% of the CPU on one processor when trying to close the Exchange 2010 Exchange Management Console (EMC), after installing KB3125574.


May 9, 2017—KB4019264 (Monthly Rollup)

  • Addressed issue to improve the reliability of dual-controller storage systems.


September 12, 2017—KB4038777 (Monthly Rollup)

  • Addressed issue where a DNS server stops working and doesn't respond to DNS requests in Windows Server 2008 R2.


October 10, 2017—KB4041681 (Monthly Rollup)

  • Addressed issue in which Failover Cluster Manager incorrectly reports replication networks as down when they're actually online after installing KB3125574 or KB2937350.

감사합니다.



4월 26일자 Hotfix 리스트 입니다.

 

 

 

LSASS fails and returns a "0xc0000005" error when you run "Full Import" on AAD Connect against a Windows Server 2012 R2 DC
https://support.microsoft.com/en-us/kb/3145339

 

Connection to Oracle database fails when you use Microsoft ODBC or OLE DB Driver for Oracle or Microsoft DTC in Windows
https://support.microsoft.com/en-us/kb/3147071?sd=rss&spid=16796

 

Windows Azure VMs don't recover from a network outage and data corruption issues occur
https://support.microsoft.com/en-us/kb/3137061

 

BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2
https://support.microsoft.com/en-us/kb/3133977

 

"0x00000024" Stop error in FsRtlNotifyFilterReportChange and copy file may fail in Windows
https://support.microsoft.com/en-us/kb/3121255

 

Reliability and scalability improvements in TCP/IP for Windows 8.1 and Windows Server 2012 R2
https://support.microsoft.com/en-us/kb/3149157

 

Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update: April 2014
https://support.microsoft.com/en-us/kb/2919355

 

WMI service crashes randomly in Windows Server 2012 R2 or Windows Server 2012
https://support.microsoft.com/en-us/kb/3146604

 

WMI query doesn't work in Windows Server 2012 R2 or Windows Server 2012
https://support.microsoft.com/en-us/kb/3103616

 

iSCSI target service crashes randomly in Windows Server 2012 R2
https://support.microsoft.com/en-us/kb/3146621

 

LSASS deadlocks cause Windows Server 2012 R2 or Windows Server 2012 not to respond
https://support.microsoft.com/en-us/kb/3125424

 

Various network and computer issues occur when TCP ephemeral ports are exhausted in Windows 8 or Windows Server 2012
https://support.microsoft.com/en-us/kb/3014399

 

"Directory service is busy" error when you rename a domain-joined computer on a Windows Server 2012 R2 DC
https://support.microsoft.com/en-us/kb/3152220

 

High network usage after you implement file screening on a Windows Server 2012 R2-based Work Folders sync server
https://support.microsoft.com/en-us/kb/3148217

 

Wbengine.exe crashes when you run a backup on a GPT formatted drive in Windows Server 2012
https://support.microsoft.com/en-us/kb/3146600

 

RDS redirected resources showing degraded performance in Windows 8.1 or Windows Server 2012 R2
https://support.microsoft.com/en-us/kb/3146978

 

Cluster service fails when shutting down or data deduplication fails with "Drive is locked" in Windows Server 2012 R2
https://support.microsoft.com/en-us/kb/3143777

 

Loading DNS zones takes a long time on a Windows Server 2008 R2-based DNS server
https://support.microsoft.com/en-us/kb/3145126

감사합니다.

 

svxp tag

Nonpaged pool memory leak occurs in a Windows Server 2012 R2-based failover cluster
https://support.microsoft.com/en-us/kb/3130939?sd=rss&spid=17383
Article ID: 3130939 - Last Review: 03/08/2016 19:38:00 - Revision: 3.0
This article describes a memory leak issue that occurs in the svhdxflt.sys filter driver in Windows Server 2012 R2. The leak occurs against nonpaged pool with the svxp tag. You can fix this issue by using the update in this article. Before you install this update, see the Prerequisites and the Restart requirement section.

Failover Clustering & Hyper-V 관련 Hotfix 모음 입니다.

Windows Server 2012 
  Recommended hotfixes and updates for Windows Server 2012-based failover clusters
  https://support.microsoft.com/en-us/kb/2784261 

 

Creating multiple File Server resources in one group may not work correctly in a Windows Server 2012 Failover Cluster
  https://support.microsoft.com/en-us/kb/2993295

 

  Starting or Live Migrating Hyper-V virtual machines may fail with error 0x80070569 on

Windows Server 2012-based computers
  https://support.microsoft.com/en-us/kb/2779204

 

  Stop error 0x9E and failover cluster can't come online in Windows Server 2012
  https://support.microsoft.com/en-us/kb/3130902

 

 

Windows Server 2012 and Windows Server 2012 R2
  Hyper-V virtual machines cannot be connected to sometimes when TCP connections reconnect in Windows
https://support.microsoft.com/en-us/kb/2972254
Article ID: 2972254 - Last Review: 03/10/2016 08:04:00 - Revision: 8.0
  This issue occurs when a TCP connection breaks and then reconnects. A TCP acknowledgement is not received in the node-to-node communication on a Windows Server 2012 R2 failover cluster, and the node that does not receive the TCP acknowledgement is removed from the active failover cluster membership. Error 5023 is logged in the cluster.log file of the node that is removed from the active failover cluster membership. For example, the following error 5023 is logged in the cluster.log file on the   FC-NODE2 node that corresponds to the previous System log:
00000b7c.00001254::Date-Time WARN [PULLER FC-NODE2] ReadObject failed with GracefulClose(1226)' because of 'channel to remote endpoint fe80::####:####:####:####%##:~49256~ is closed'.
00000b7c.00000fa8::Date-Time ERR [CORE] mscs::NodeObject::OnMessageReceived:

(5023)' because of 'Can't remove sent messages from an empty sent messages queue.'
00000b7c.00000fa8::Date-Time ERR [NODE] Node 8: Error processing message from n1, starting Regroup.

Notefe80::####:####:####:####%## represents the hexadecimal number that represents an IPv6 address.  

 

Stop error code 0xD1, 0x139, or 0x3B and cluster nodes go down in Windows Server 2012 R2 or Windows Server 2012
https://support.microsoft.com/en-us/kb/3055343
  Article ID: 3055343 - Last Review: 03/08/2016 19:13:00 - Revision: 6.0
  Issue 1
  When you delete network interfaces on a server that is running Windows Server 2012   R2 or Windows Server 2012, you experience random and intermittent crashes on the system, and you also receive one of the following Stop error messages:
  •0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  •0X139: KERNEL_SECURITY_CHECK_FAILURE
  •0x3B: SYSTEM_SERVICE_EXCEPTION
  Issue 2
  Some cluster nodes that are running Windows Server 2012 R2 or Windows Server 2012 go down because of the corruption in NDIS and netcfg.

 

  Hyper-V integration components update for Windows virtual machines that are running on a Windows 10-based host
  https://support.microsoft.com/en-us/kb/3063109 

 

Cluster service stops during the VSS backup in a Windows Server 2012 R2 or Windows Server 2012-based Hyper-V cluster 
  https://support.microsoft.com/en-us/kb/3090343

 

 

Windows Server 2012 R2
  A virtual machine that is running on Windows Server 2012 R2 may not start
  https://support.microsoft.com/en-us/kb/2962295

 

  Disk resource does not come online in Windows Server 2012 R2 or Windows Server 2008 R2-based failover cluster
  https://support.microsoft.com/en-us/kb/3033918
  Article ID: 3033918 - Last Review: 03/11/2016 03:55:00 - Revision: 4.0
  Assume that a disk resource name contains unauthorized file system characters, such as colon (:) or backslash (\), in a Windows Server 2012 R2 or Windows Server 2008 R2-based failover cluster, and the disk becomes dirty. In this situation, the chkdsk command does not run as expected, and the disk resource cannot come online.

  Stop Error "0x0000007E" occurs in a Windows Server 2012 R2-based Hyper-V cluster
  https://support.microsoft.com/en-us/kb/3063000

 

Cluster validation fails in the "Validate Simultaneous Failover" test in a Windows Server 2012 R2-based failover cluster
https://support.microsoft.com/en-us/kb/3091057
Article ID: 3091057 - Last Review: 03/11/2016 06:33:00 - Revision: 3.0
When you run failover cluster validation, the validation may fail during the storage validation tests. It may occur by using Validate a Configuration Wizard from Failover Cluster Manager or by initiating validation that uses the "Test-Cluster" PowerShell cmdlet. 

 

 

Windows 10

Hy  A multi-site failover cluster goes into a split brain situation in Windows Server 2012 R2 
  https://support.microsoft.com/en-us/kb/3123593

 

Hyper-V integration components update for Windows virtual machines that are running on a Windows 10-based host

https://support.microsoft.com/en-us/kb/3063109?sd=rss&spid=16796
Article ID: 3063109 - Last Review: 03/11/2016 01:56:00 - Revision: 4.0
Issue 1
Consider the following scenario:
•You connect a VM to a virtual switch that uses a physical adapter.
•You enable the single root I/O virtualization (SR-IOV) option in Virtual Switch Manager.
•You disable the physical adapter on the Hyper-V guest while network I/O is running in the VM.
In this scenario, the VM crashes.
Issue 2
The current Write Ahead Logging (WAL) implementation incorrectly assumes that the Virtual Hard Disk (VHD) ownership never changes. However, the ownership does change in multiple VM group replication in a shared VHD scenario

 

'KB' 카테고리의 다른 글

[2016-04-26] KB Updates  (0) 2016.04.26
[2016-03-12]Pool Leak  (0) 2016.03.12
[2016-03-12]BugCheck 0x139 KERNEL_SECURITY_CHECK_FAILURE  (0) 2016.03.12
[2016-03-02]Storage Issue  (0) 2016.03.02
[2016-03-02]Network related issue  (0) 2016.03.02

+ Recent posts