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.

If an iSCSI target is configured to use the old Initiator Name for authentication, the iSCSI Initiator may fail to login into the target using Favorite Target entries that are created after the Initiator Name is changed. Also, you may no longer be able to discover the iSCSI target once the Initiator Name is changed.

This issue occurs because the iSCSI target service has insufficient buffers to send a message to an iSCSI initiator. Resolution. To resolve this issue in Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2, install update rollup 2975719. For more information, click the following article number to view the article in the Microsoft Knowledge ...

FIX: Stop error when you replace an iSCSI network adapter or a motherboard by using an identical device on a Windows Server 2008-based or Windows Vista-based computer: "0x0000007B" - Microsoft Support.

This issue occurs because the iSCSI target service has insufficient buffers to send a message to an iSCSI initiator. Resolution To resolve this issue in Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2, install update rollup 2975719.

This article describes an issue in which the iSCSI target service crashes randomly on a Windows Server 2012 R2 server. An update is available to fix this issue. Before you install this update, see the Prerequisites section.

This article describes an issue when you make a stress test in iSCSI initiator in Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1. Check out the details of the stress test where this problem occurs. Resolution

If an iSCSI target is configured to use the old Initiator Name for authentication, the iSCSI Initiator may fail to login into the target using Favorite Target entries that are created after the Initiator Name is changed. Also, you may no longer be able to discover the iSCSI target once the Initiator Name is changed.

An issue is found in Windows Server 2012 R2 that may cause iSCSI Target to stop responding to requests. Resolution. Hotfix information. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article.

Iscsicpl.exe process stops responding when you try to reconnect a storage device to a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 - Microsoft Support.