List of storage related hotfixes post Service Pack 2 for Windows Server 2003

Applies to
Windows Server 2003 Service Pack 2
Windows Server 2003 SP2
W2K3 Service Pack 2
W2K3 SP2
Windows Server 2003 Service Pack 2 R2
Windows Server 2003 SP2 R2
W2K3 Service Pack 2 R2
W2K3 SP2 R2

For the latest versions of the hotfixes search https://support.microsoft.com/

List of storage related hotfixes post Service Pack 2 for Windows Server 2003 as of Mar, 2012:

Originally published May 2009.

2280732 You receive Stop error message 0x000000CD or 0x00000019 on a computer that is running Windows Server 2003 when corrupted registry hive files are loaded
https://support.microsoft.com/?id=2280732

Update(s):
Hal.dll 5.2.3790.4354
Ntkrnlmp.exe 5.2.3790.4771
Ntoskrnl.exe 5.2.3790.4771
Note:  It has the fixes that are critical and described in 942835
Supersede(s):
979683 MS10-021: Vulnerabilities in Windows Kernel could allow elevation of privilege
979128 Stop error message in Windows Server 2003 SP2: "Stop error code 0x0000000A (IRQL_NOT_LESS_OR_EQUAL)"
978243 A server that is running Windows Server 2003 Service Pack 2 restarts unexpectedly with various stop codes after you install hotfix 971280 or newer Windows Kernel Binaries
975759 An application or service that uses a file system filter driver may experience function failure on a computer that is running Windows Vista, Windows Server 2003, or Windows Server 2008
973476 A .NET Framework application crashes in the CLR version 4 on a computer that is running an Itanium-based version of Windows Server 2003 SP2 or of Windows Server 2008
971408 Windows Server 2003 does not restart as expected if a recursive error occurs while writing a dump file
971067 Windows Server 2003 stops responding (hangs) during a shutdown if SharePoint Services Tracing is enabled
970107 A Windows Server 2003-based computer stops responding when you use a debug application to suspend a thread
970054 Many events with ID 333 are added to the System log on a Windows Server 2003-based computer
968355 Audit event 567 is not recorded as expected when a file is created or modified by using a network share on a Windows Server 2003 SP2-based computer
961555 A Windows Server 2003 Service Pack 2-based computer or a Windows XP Service Pack 3-based computer randomly crashes
960772 The system may generate Stop error 0x4D when an application uses the VirtualLock function to lock pages in Windows Server 2003 or in Windows XP Professional x64 Edition
957039 A Windows Server 2003-based computer becomes unresponsive when a high volume of traffic runs through a network adapter that has a large bandwidth
956572 MS09-012: Description of the security update for Windows Service Isolation: April 2009
956341 A Windows Server 2003-based computer becomes unresponsive because of a large memory allocation request
954337 The computer could potentially have problems if DPC routines are executed at an IRQL that is greater than DISPATCH_LEVEL in Windows Server 2003
953600 Message after multiple unsuccessful calls to certain functions on a computer that is running Windows Server 2003 or Windows XP Professional x64 Edition: "Running out of physical memory"
953490 You cannot debug the DLL modules in an application if the application loads more than 500 DLL modules on a Windows Server 2003-based computer
952244 The Kernel Patch Protection code may incorrectly cross cache lines and cause the Front Side Bus lock to be raised on a computer that is running an x64-based version of Windows Server 2003 Service Pack 2
952177 When you use the VirtualProtect function together with the PAGE_WRITECOPY flag on a Windows Server 2003-based computer, the Protect property of mapped file pages is unexpectedly changed
950772 A computer that is running an x64-based version of Windows Server 2003, of Windows Vista, or of Windows Server 2008 randomly restarts and then generates a Stop error
949459 The new 64-bit CPU from VIA Technologies is not recognized on computers that are running Windows XP or later operating systems
944984 The user profile may not be correctly unloaded when you log off from a Windows Server 2003-based computer, and event 1517 is logged
942835 When client computers try to access resources on a Windows Server 2003-based file server, the Server service on the file server may stop responding
942004 A Windows Server 2003 x64 Edition-based computer does not automatically restart as expected after the .crash command is executed to generate a dump file
941410 The computer crashes, and you receive a "Stop 0x0000003b" error message after you enable large image-based page files in Windows Server 2003
941105 FIX: Error messages after SQL Server has been running for some time on Windows Server 2003 or on Windows 2000: "Failed to load FileName.dll" and "Attempts to load any type of dll might fail within the SQL Server process"
939875 A hotfix is available that adds support for crash dump file generation on a Windows Server 2003-based computer that is using iSCSI Boot Initiator 2.05
938486 A Windows Server 2003-based computer becomes unresponsive because of a memory manager trimming operation that is caused by an indeterminate module that requests lots of memory
935926 A Windows Server 2003-based computer stops responding when the registry is in heavy use
934739 The Plug and Play subsystem may not detect an external storage device when it is reconnected in Windows Server 2003
932375 A Windows Server 2003-based computer stops responding when an application frequently schedules threads
932370 The number of physical hyperthreading-enabled processors or the number of physical multicore processors is incorrectly reported in Windows Server 2003
931761 You cannot install Windows Server 2003 successfully after you use Windows Vista or Windows PE 2.0 to create partitions on a hard disk
931308 You may experience increased paging to the hard disk when you run an SAP R/3 program on a Windows Server 2003-based computer
931304 Windows Server 2003 stops responding when the event log size is larger than the default size
929020 After you restore a sparse file on a Windows Server 2003-based computer that has antivirus software enabled, data is lost
927182 When a user logs off a Windows Server 2003 Service Pack 1 or Service Pack 2-based terminal server, the terminal server may stop responding for several seconds

981166 Some data is corrupted when cached and noncached I/O operations occur by using the same NTFS file handle
https://support.microsoft.com/?id=981166

Update(s):
Ntfs.sys 5.2.3790.4681
Supersede(s):
980361 Windows Server 2003 SP2 stops responding after a hard link is deleted on a NTFS volume
974127 An ERROR_ACCESS_DENIED error is returned in Windows Server 2003, in Windows Vista, or in Windows Server 2008 when you call the DeviceIoControl function together with the FSCTL_LOCK_VOLUME control code
973886 You cannot restore large files in the NTFS file system when all the data streams that have sparse attributes are deleted in the 64-bit version of Windows XP SP2 or in Windows Server 2003 SP2
973870 A computer that is running Windows Server 2003 randomly stops responding when you back up data
970998 You cannot stop safely a removable storage device on a computer that is running Windows Server 2003 after you delete a folder on the removable storage device
969352 A long delay occurs when the Ntfs.sys driver tries to mount a large volume on a computer that is running Windows Server 2003 SP2
962965 A Windows Server 2003 SP2-based computer stops responding when you move lots of files from one directory to another
959608 Error message when you run the Chkdsk.exe utility to fix a corrupted volume on a Windows Server 2003-based computer: "Stop 0x00000024"
956123 Files that are copied into replicated file shares may not be replicated for an unexpectedly long time when antivirus software is installed on the originating server
954495 Stop error 0x24 may occur on a computer that has file system filter drivers installed in Windows Server 2003 and in Windows XP Professional x64 Edition
953325 A Windows Server 2003- or 2008-based computer becomes unresponsive because the paged pool memory is exhausted when an application calls the GetFileAttributesEx and MoveFileEx functions on lots of files
950834 When you try to restore a large amount of data, a dead lock condition occurs in the NTFS file system, and a Windows Server 2003-based file server may stop responding
949123 When a cached write and a non-cached write are requested for the same file, data corruption may occur in Windows Server 2003
944830 On a Windows Server 2003 R2-based computer, the Quota function of the File Server Resource Manager (FSRM) may report incorrect disk usage when both the Quota function and the shadow copies are configured on the same volume
944804 Distributed File System Replication in Windows Server 2003 R2 performs unnecessary replication when an antivirus application is installed
942835 When client computers try to access resources on a Windows Server 2003-based file server, the Server service on the file server may stop responding
942528 You randomly receive a "STOP 0x00000044" error message after you install a third-party program on a Windows Server 2003-based computer
937455 You may receive various Stop error messages on a computer that is running Windows Server 2003
933876 The USN journal record contains an incorrect file name when you move a file in Windows Vista, in Windows Server 2003, or in Windows XP
932578 Event ID 55 may be logged in the System log when you create many files on an NTFS partition on a Windows Server 2003-based or Windows XP-based computer
925677 The server cluster fails when you bring online NTFS volume mount points that are configured as shared physical disk resources on a Windows Server 2003-based server cluster that uses iSCSI Initiator service

979451 Error message when you try to format a partition beyond the 1 terabyte address in Windows Server 2003 SP2: "The format failed to complete successfully"
https://support.microsoft.com/?id=979451

Update(s):
Atapi.sys 5.2.3790.4652
Supersede(s):
971075 Error message on a computer that runs Windows Server 2003 or Windows XP x64 Edition: "Stop 0x00000050"
934794 A Windows Server 2003-based computer stops responding when you perform a surprise removal of an IDE device
934205 The ATA PASS THRU request is unsuccessful on a Windows XP-based computer or a Windows Server 2003-based computer

979457 Some snapshots are not mounted in Windows Server 2003 SP2 after computer restarts if there are many snapshots
https://support.microsoft.com/?id=979457

Update(s):
Volsnap.sys 5.2.3790.4650
W03a3409.dll 5.2.3790.4590
Ww03a3409.dll 5.2.3790.4590
Supersede(s):
979407 A node of a cluster may stop responding in Windows Server 2003 SP2
967551 Rollup update for the volsnap.sys driver in Windows Server 2003
967327 Shadow copies that you create in Windows Server 2008 cannot be detected in Windows Server 2003
940349 Availability of a Volume Shadow Copy Service (VSS) update rollup package for Windows Server 2003 to resolve some VSS snapshot issues
940252 The Volume Shadow Copy Service may leak private bytes and virtual memory when you use the service to take frequent snapshots in Windows Server 2003 or in Windows XP
940239 VSS cannot create a volume snapshot even when VSS has sufficient memory space in Windows Server 2003
940041 Volume Shadow Copy Service snapshots may be unexpectedly deleted after you restart a Windows Server 2003-based computer
933653 A memory leak occurs when an application performs a snapshot on a computer that is running Windows Server 2003
931312 Windows Server 2003 may not start when the Volume Shadow Copy Service is enabled
929774 Exchange Server 2007 cannot run simultaneous VSS-based backup and restore operations on Exchange databases in Windows Server 2003

975759 An application or service that uses a file system filter driver may experience function failure on a computer that is running Windows Vista, Windows Server 2003, or Windows Server 2008
https://support.microsoft.com/?id=975759

Update(s):
Fltmgr.sys 5.2.3790.4601
Supersede(s):
973495 A hotfix is available that addresses unresponsiveness when a file system minifilter driver is running on a computer that is running Windows Server 2003

968502 A system state backup operation fails on a Windows Server 2003-based computer if the computer belongs to a site that uses high latency WAN links https://support.microsoft.com/?id=968502

Update(s):
Swprv.dll 5.2.3790.4476
Vssapi.dll 5.2.3790.4476
Vssvc.exe 5.2.3790.4476
Wvssapi.dll 5.2.3790.4476
Supersede(s):
957778 VSS requestor instances fail when you start multiple VSS requestor instances with a VSS hardware provider to delete snapshots in Windows Server 2003
952826 When you call the "IVssBackupComponents::SetFileRestoreStatus" method by specifying the value of the status parameter as VSS_RS_FAILED, the restore status is set incorrectly on a computer that is running Windows Server 2003 SP1 or SP2
951568 VSS-based backup operations may fail if VSS tracing is enabled on a Windows Server 2003-based computer that has hotfix 940349 applied
949391 When Volume Shadow Copy Service (VSS) tries to delete hardware support snapshots on a computer that is running Windows Server 2003 or an x64 version of Windows XP, the operation may fail
943669 When you try to restart a Windows Server 2003 R2-based computer that has both VSS and the FSRM quota enabled, the computer stops responding
940349 Availability of a Volume Shadow Copy Service (VSS) update rollup package for Windows Server 2003 to resolve some VSS snapshot issues
940252 The Volume Shadow Copy Service may leak private bytes and virtual memory when you use the service to take frequent snapshots in Windows Server 2003 or in Windows XP
940239 VSS cannot create a volume snapshot even when VSS has sufficient memory space in Windows Server 2003
940041 Volume Shadow Copy Service snapshots may be unexpectedly deleted after you restart a Windows Server 2003-based computer
933653 A memory leak occurs when an application performs a snapshot on a computer that is running Windows Server 2003
931312 Windows Server 2003 may not start when the Volume Shadow Copy Service is enabled
929774 Exchange Server 2007 cannot run simultaneous VSS-based backup and restore operations on Exchange databases in Windows Server 2003

957910 A Windows Server 2003 SP2-based iSCSI boot server cannot generate dump files if the server uses a Storport virtual miniport as the LUN controller
https://support.microsoft.com/?id=957910

Update(s):
Storport.sys 5.2.3790.4485
Note:  You should check the SAN vendor website for tested/approved version of storport, if you do not, you might not be supported by your SAN vendor.
Supersede(s):
950903 The system may not detect that a logical unit was replaced on a Windows Server 2003-based computer
950448 You cannot move cluster resources back to the original node on a Windows Server 2003 cluster node that has UMPD driver from Unisys installed
946448 You cannot remove a persistent iSCSI target if Physical Address Extension (PAE) is enabled on a Windows Server 2003-based computer
945119 Stop error that is related to the Storport.sys driver on a Windows Server 2003-based computer: "0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL"
943545 Error returned by the IOCTL_SCSI_GET_INQUIRY_DATA operation on a Windows Server 2003-based computer: "STATUS_INVALID_DEVICE_REQUEST"
943295 An update enables support for Storport virtual miniports in Windows Server 2003
941276 A Windows Server 2003-based computer stops responding when the system is under a heavy load and when the Storport driver is being used
940467 MMC stops responding, or you cannot access VDS-dependent tools after you install the Storport storage driver from Microsoft Knowledge Base article 932755 in Windows Server 2003
939315 You receive a "Stop 0x0000009C" error message, or the system stops responding, when you shut down a computer that is running the Microsoft Storport storage driver in Windows Server 2003 SP2
935561 StorPort may not delete zombie LUN objects when a storage adapter is surprise-removed by software in Windows Server 2003
932755 An updated Storport storage driver is available for Windows Server 2003

955543 All snapshots may be deleted unexpectedly in Windows Server 2003 and in Windows XP Professional x64 Edition when the snapshot protection mode is enabled, and the system is under memory stress
https://support.microsoft.com/?id=955543

Update(s):
DMIO.SYS
Supersede(s):
928124 The status of a dynamic volume unexpectedly changes to "Online (Error)" after the system detects bad blocks on a Windows Server 2003-based computer

943669 When you try to restart a Windows Server 2003 R2-based computer that has both VSS and the FSRM quota enabled, the computer stops responding
https://support.microsoft.com/?id=943669

Update(s):
PARTMGR.SYS

943669 When you try to restart a Windows Server 2003 R2-based computer that has both VSS and the FSRM quota enabled, the computer stops responding
https://support.microsoft.com/?id=943669

Update(s):
FTDISK.SYS

941602 The Dmdiag.exe utility does not correctly list the volume information on a Windows Server 2003-based computer that contains more than 1024 volumes
https://support.microsoft.com/?id=941602

Update(s):
Dmdiag.exe 5.2.3790.4235

940307 A Microsoft Windows Server 2003-based computer may stop responding if an application frequently uses the mount manager to query volume information
https://support.microsoft.com/?id=940307

Update(s):
MOUNTMGR.SYS

929161 You receive a Stop error message on a Windows Server 2003 SP1-based computer when a device is suddenly disconnected from a host bus adapter
https://support.microsoft.com/?id=929161

Update(s):
Disk.sys 5.2.3790.4006

Optional:  If using iSCSI
2277122 Stop error in Windows Server 2003 or in Windows Server 2008 R2 if a computer has some iSCSI disks and the computer is under a heavy stress situation: "0x000000D1"
https://support.microsoft.com/?id=2277122

Update(s):
Iscsiprt.sys 5.2.3790.4774
Msiscsi.sys 5.2.3790.4774

Optional:  If using MPIO
982109 Access to an MPIO-controlled storage device fails after you disconnect all data cables in Windows Server 2003
https://support.microsoft.com/?id=982109

Update(s):
Mpio.sys 5.2.3790.4706
Mpspfltr.sys 5.2.3790.4706 
Note:  If your storage vendor ships a version of the Microsoft MPIO, you should use the one that the vendor ships.
Supersede(s):
961640 Nonpaged pool kernel memory leak on Windows Server 2003 with Multipathing solution installed

Update(s): MPSPFLTR.SYS
Note: Updated when the MPIO is updated
Update(s):MPDEV.SYS
Note: Updated when the MPIO is updated

Optional:  If using FSRM (File System Resource Manager)
 
968451 Stop error message when you enable File Server Resource Manager quota management on an NTFS volume on a Windows Server 2003 R2-based computer: "Stop 0x0000007E"
https://support.microsoft.com/?id=968451

Update(s):
Quota.sys 5.2.3790.4482
Supersede(s):
947390 You receive a "Stop 0x000000C2" error message on a Windows Server 2003 R2-based computer if a compressed folder resides on an NTFS volume that has FSRM quota management enabled
942586 The computer may stop responding if you enable the Quota function of the File Server Resource Manager (FSRM) component on a Windows Server 2003 R2-based computer
939446 The computer may stop responding when you run the disk quota-related functions that are provided by the File Server Resource Manager (FSRM) component on a Windows Server 2003 R2-based computer

Optional:  If using NFS
958376 On a Windows Server 2003 R2-based server, you may be unable to open or to import a file that is located on the same drive as an NFS share
https://support.microsoft.com/?id=958376

Update(s):
Msnfsflt.sys 5.2.3790.4393
Supersede(s):
951571 The "Delete" permission entry for owner or group is intentionally set to "Deny" on the discretionary access control list (DACL) when you examine the security settings of the NTFS folder from a Windows Server 2003 R2-based NFS server

939767 Error message when an NFS client accesses a file on an NFS share in Windows Storage Server 2003, in Windows Server 2003 R2, or in Windows Services for UNIX 3.5: "Stop 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)"
https://support.microsoft.com/?id=939767

Update(s):
Nfssvr.sys 5.2.3790.4182
Supersede(s):
941812 The Server for Network File System service may stop responding on a Windows Server 2003 R2-based computer