This is an update rollup for the Single Instance Storage (SIS) component in Windows Storage Server 2008 R2. This update rollup resolves the following issues: Issue 1 When data is written to a file which resides on a SIS volume of a remote server and an application on the remote server reads the file by using file mapping, the new data may be lost. An antivirus application is an example application which may read files locally by using file mapping.
Issue 2 When a file is compressed or decompressed on a SIS volume and the file was previously changed and the modification was interrupted or failed, the file may be corrupted. Issue 3 After a file is truncated to empty size on a SIS volume by using the CreateFile function together with the TRUNCATE_EXISTING creation disposition:
If the file is read without reopening it, the system may return data as if the file was not truncated. For example, consider a situation where the original file is 2 megabytes (MB) and is opened by using the CreateFile function together with the TRUNCATE_EXISTING creation disposition. When the first 1 MB is read, the system may return the original 1 MB of content even though the file size is zero.
If the file is written without reopening it, the system may behave as if the file was not truncated. For example, consider a situation where the original file is 2 MB and is opened by using the CreateFile function together with the TRUNCATE_EXISTING creation disposition. When the first 1 MB is written with new data, the new file may be 2 MB with the first 1 MB of new data and second 1 MB of original data.
Issue 4 When a file is opened on a SIS volume that uses file system transaction and the file is compressed by using NTFS compression, the file may be corrupted.
Important
Windows Storage Server products are OEM-only products. OEMs must set up a contract with Microsoft Licensing through their OEM account managers before the OEMs can access update packages for Windows Storage Server. This update rollup is distributed only through Microsoft OEM Online. Send questions about this update package to the following email address:
Issue 1 This issue occurs because the SIS filter does not filter the fast I/O operations or the memory descriptor list (MDL) operations which are used by the Server Message Block (SMB) protocol.
Issue 2 This issue occurs because certain read operations that originate from NTFS for compression or decompression on SIS-managed files are invisible to the SIS filter. This prevents the SIS filter from returning the actual file data and results in file corruption.
Issue 3 This issue occurs because the SIS filter does not filter the FileAllocationInformation information class of IRP_MJ_SET_INFORMATION requests.
Issue 4 This issue occurs because of a timing issue. When the SIS filter restores a SIS-managed file to a normal file because of a file system transaction, the NTFS.sys driver performs compression on the file at the same time. In this scenario, some read operations that originate from NTFS for compression are invisible to the SIS filter. This prevents the SIS filter from returning the actual file data and results in file corruption.
To apply this update, you must be running one of the following operating systems:
Windows Storage Server 2008 R2
Windows Storage Server 2008 R2 Service Pack 1 (SP1)
Registry information
To use the update in this package, you do not have to make any changes to the registry.
Restart requirement
You may have to restart the computer after you apply this update.
Update replacement information
This update does not replace a previously released update.
File information
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Storage Server 2008 R2 file information notes
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
Version
Product
SR_Level
Service branch
6.1.760
0
.
16xxx
Windows Storage Server 2008 R2
RTM
GDR
6.1.760
0
.
20xxx
Windows Storage Server 2008 R2
RTM
LDR
6.1.760
1
.
17xxx
Windows Storage Server 2008 R2
SP1
GDR
6.1.760
1
.
21xxx
Windows Storage Server 2008 R2
SP1
LDR
GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Storage Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Storage Server 2008 R2
Back to the top
