Windows Server 2016은 가장 최신 Windows 라 그런지 새로운 기능에 대한 Fix가 아직 많은 것으로 보입니다.


February 13, 2018—KB4074590 (OS Build 14393.2068)

MPIO에서 IO에 대한 제약이 설정 되어 있을때 Path에 대한 Failover 발생시 모든 사용 가능한 Path가 Failed 될 수 있는 이슈가 수정 되었습니다.
  • Addresses issue where a failover in MPIO while throttling input and output requests may cause all available paths to fail.
KB4057142, KB4056890 를 SMB 파일 서버에 설치 하였을때 junction point와 volume mount point 접근시 발생하는 이슈가 수정 되었습니다.
  • Addresses issue where, after installing KB4057142 or KB4056890 on an SMB server, accessing files in directory junction points or volume mount points hosted on the server may fail. The error is “ERROR_INVALID_REPARSE_DATA”. For example, this symptom may be observed:



February 22, 2018—KB4077525 (OS Build 14393.2097)

WinRM event query 할때 발생하는 이슈가 수정 되었습니다.
  • Addresses issue where the WinRM event query returns the error "0x6c6 (RPC_S_INVALID_BOUND)" from the target server. The error appears when servers are configured to push their security event logs to a central server for analysis using a subscription.
File 전송을 할 때 tcpip.sys 에서 BugCheck 0xD1이 발생하면서 시스템이 크래시 되는 이슈가 수정 되었습니다.
  • Addresses issue where a server error occurs occasionally during file transfer. The error is “Stop D1 in tcpip!TcpSegmentTcbSend”.
iSCSI redirection 을 사용하였을때 BugCheck 0x9F가 발생하는 이슈가 수정 되었습니다.
  • Addresses issue where iSCSI target redirection during login may lead to stop error 9f.
MPIO를 사용할 때 Disk의 상태가 pending removal 일 경우 pass-through SCSI 요청이 멈출 수 있는 이슈가 수정 되었습니다.
  • Addresses issue in MPIO where pass-through SCSI requests may lead to a stop error if the disk is pending removal.
MPIO에서 Path를 선택하는 알고리즘이 수정 되었습니다.
  • Updates MPIO path selection algorithm to match the documentation when all paths are Active or Unoptimized.
NVMe 디바이서의 사용이 증가되면서 관련 이슈가 나오는 것으로 보입니다. 응용 프로그램을 시작할 때 StorNVMe 의 지연 기능으로 인해 CPU 사용량이 증가되는 이슈가 수정 되었습니다.
  • Addresses issue where a delay function in StorNVMe may cause a small CPU usage increase when launching applications.
ReFS 는 계속 사용 시나리오가 늘어 나면서 새로운 이슈들이 등장하고 새로운 튜닝 옵션들이 많이 증가하고 있습니다. ReFS를 백업 용도로 사용하는 Veeam 제품에서 Physical Memory에서 Metadata 영역이 메모리를 많이 사용하는 이슈가 있어서 fix가 나왔습니다. ReFS는 Allocate-on-write 방식으로 metadata를 관리하는데 metadata에 변경 사항이 있을때 기존 메모리를 변경하는 것이 아니고 새로운 메모리를 할당해서 쓰는 방식을 사용합니다. 이 방식을 사용하는 경우 변경사항이 있을 때마다 metadata용 메모리를 할당해야 해서 물리 메모리에 부하가 걸리게 됩니다.
  • Improves ReFS performance by more thoroughly unmapping multiple views of a file. See KB4090104 for additional tunable registry parameters to address large ReFS metadata streams.
  • Improves ReFS performance by removing idle containers from its hash table.
Unified Writer Filter (예전에 PC방에서 사용하던 하드디스크 보안관 같은 기능으로 디스크에 대한 쓰기가 별도의 공간으로 리디렉트 되는 것입니다.) 를 사용할 때 BugCheck 0xE1 (WORKER_THREAD_RETURNED_AT_BAD_IRQL)이 발생하는 이슈가 수정 되었습니다.
  • Addresses issue where booting with Unified Write Filter and a connected USB hub may lead to stop error E1.
SDN 관련 이슈도 보고 되었네요 이 이슈는 Azure Stack에도 적용되지 않을까 싶습니다.
  • Cleans the public IP with the correct information for the SDN Network Manager.
Deduplication 기능이 나왔을때 가장 걱정 했던 이슈가 파일이 손상되는 것인데 2.2TB 정도 되는 파일에 이슈가 있었습니다.
  • Addresses issue where a file that is optimized and is less than 2.2 TB may be corrupted by the Dedup process when the file is updated to exceed 2.2 TB.
  • Addresses issue where a file is always marked as corrupted—even though it isn't—when running a full Dedup scrub on a file larger than 2.2 TB.




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 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.

감사합니다.



+ Recent posts