Data is corrupted after iSCSI sessions or paths recover in Windows Server 2012 R2 or Windows Server 2012

This article describes an issue in which data is corrupted after iSCSI paths or sessions recover in Windows 8.1, Windows Server 2012 R2, Windows 8, or Windows Server 2012. A hotfix is available to fix this issue. Before you install this hotfix for Windows Server 2012 R2 or Windows 8.1, see the Prerequisites section.
Symptoms
If the connection to an iSCSI array is disconnected because of a certain issue, one or more iSCSI sessions or paths to the array fail. In this situation, Windows iSCSI initiator recovers the connection. However, the recovery causes data corruption.

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, install update 2919355 in Windows 8.1 or Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the the terminology that Microsoft uses to describe software updates.
File Information
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.

Windows 8 and Windows Server 2012

Notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    Version Product Milestone Service branch
    6.2.920 0.20 xxxWindows 8, Windows RT, or Windows Server 2012RTMLDR
    6.2.920 0.21 xxxWindows 8, Windows RT, or Windows Server 2012RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical 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 in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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.
x64 Windows 8 and Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Iscsilog.dll6.2.9200.2055516,38406-Nov-201204:04x64
Msiscsi.sys6.2.9200.21687278,87209-Nov-201502:20x64
x86 Windows 8
File nameFile versionFile sizeDateTimePlatform
Iscsilog.dll6.2.9200.2055516,38406-Nov-201204:02x86
Msiscsi.sys6.2.9200.21687238,42409-Nov-201501:17x86

Windows 8.1 and Windows Server 2012 R2

Notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.3.960 0.16 xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
    6.3.960 0.18 xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical 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 in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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.
x86 Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Iscsilog.dll6.3.9600.1638416,38422-Aug-201304:16x86
Msiscsi.sys6.3.9600.18123239,96008-Nov-201522:46x86
x64 Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Iscsilog.dll6.3.9600.1638416,38422-Aug-201311:44x64
Msiscsi.sys6.3.9600.18123275,80009-Nov-201500:42x64

Additional file information

x64 Windows 8 and Windows Server 2012
File propertyValue
File nameAmd64_iscsi.inf_31bf3856ad364e35_6.2.9200.21687_none_9619f7c59685e7e3.manifest
File versionNot applicable
File size2,740
Date (UTC)09-Nov-2015
Time (UTC)15:45
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,020
Date (UTC)09-Nov-2015
Time (UTC)15:45
PlatformNot applicable
x86 Windows 8
File propertyValue
File nameUpdate.mum
File versionNot applicable
File size1,790
Date (UTC)09-Nov-2015
Time (UTC)15:45
PlatformNot applicable
File nameX86_iscsi.inf_31bf3856ad364e35_6.2.9200.21687_none_39fb5c41de2876ad.manifest
File versionNot applicable
File size2,736
Date (UTC)09-Nov-2015
Time (UTC)15:49
PlatformNot applicable
x86 Windows 8.1
File propertyValue
File nameUpdate.mum
File versionNot applicable
File size1,592
Date (UTC)09-Nov-2015
Time (UTC)07:04
PlatformNot applicable
File nameX86_iscsi.inf_31bf3856ad364e35_6.3.9600.18123_none_d1a3381d0f10bf63.manifest
File versionNot applicable
File size2,736
Date (UTC)09-Nov-2015
Time (UTC)07:07
PlatformNot applicable
x64 Windows 8.1 and Windows Server 2012 R2
File propertyValue
File nameAmd64_iscsi.inf_31bf3856ad364e35_6.3.9600.18123_none_2dc1d3a0c76e3099.manifest
File versionNot applicable
File size2,740
Date (UTC)09-Nov-2015
Time (UTC)07:04
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,820
Date (UTC)09-Nov-2015
Time (UTC)07:04
PlatformNot applicable
Properties

Article ID: 3102997 - Last Review: 12/08/2015 23:54:00 - Revision: 1.0

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1, Windows Server 2012 Datacenter, Windows Server 2012 Standard, Windows Server 2012 Essentials, Windows Server 2012 Foundation, Windows 8 Enterprise, Windows 8 Pro, Windows 8

  • kbqfe kbsurveynew kbfix kbexpertiseadvanced kbautohotfix kbhotfixserver KB3102997
Feedback