You are currently offline, waiting for your internet to reconnect

The "Automatically restore this connection when computer starts" option may not work on a Windows Server 2008-based computer when CHAP authentication is used

This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
  • You are running a Windows Server 2008-based computer.
  • You establish an iSCSI session on this computer.
  • In the iSCSI session, you click to select the Automatically restore this connection when computer starts check box.
After you restart the computer, you expect the Microsoft Software Initiator to automatically log on and to make the logical unit numbers (LUNs) available without requiring you to manually create an iSCSI session. However, this feature may not work as expected if you are using Challenge Handshake Authentication Protocol (CHAP) authentication.
This problem may occur because the encrypted CHAP secret may be corrupted in memory after it is read from the registry on a Windows Server 2008-based computer.

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. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain 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 do not 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 Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.


To apply this hotfix, you must have Windows Server 2008 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2008, x86 version
File nameFile versionFile sizeDateTimePlatform
Package_1_for_kb951058~31bf3856ad364e35~x86~~ Applicable1,80529-Apr-200821:12Not Applicable
Package_2_for_kb951058~31bf3856ad364e35~x86~~ Applicable1,97229-Apr-200821:12Not Applicable
Package_3_for_kb951058~31bf3856ad364e35~x86~~ Applicable1,81029-Apr-200821:12Not Applicable
Package_4_for_kb951058~31bf3856ad364e35~x86~~ Applicable1,81029-Apr-200821:12Not Applicable
Package_for_kb951058_client_1~31bf3856ad364e35~x86~~ Applicable1,36729-Apr-200821:12Not Applicable
Package_for_kb951058_client~31bf3856ad364e35~x86~~ Applicable1,43129-Apr-200821:12Not Applicable
Package_for_kb951058_sc_0~31bf3856ad364e35~x86~~ Applicable1,42129-Apr-200821:12Not Applicable
Package_for_kb951058_sc~31bf3856ad364e35~x86~~ Applicable1,42329-Apr-200821:12Not Applicable
Package_for_kb951058_server_0~31bf3856ad364e35~x86~~ Applicable1,42529-Apr-200821:12Not Applicable
Package_for_kb951058_server~31bf3856ad364e35~x86~~ Applicable1,43129-Apr-200821:12Not Applicable
Package_for_kb951058_winpesrv_0~31bf3856ad364e35~x86~~ Applicable1,42229-Apr-200821:12Not Applicable
Package_for_kb951058_winpesrv~31bf3856ad364e35~x86~~ Applicable1,42929-Apr-200821:12Not Applicable
X86_iscsi.inf_31bf3856ad364e35_6.0.6001.22168_none_3d1485470cedc456.manifestNot Applicable2,25029-Apr-200821:17Not Applicable
Windows Server 2008, x64 version
File nameFile versionFile sizeDateTimePlatform
Amd64_iscsi.inf_31bf3856ad364e35_6.0.6001.22168_none_993320cac54b358c.manifestNot Applicable2,25229-Apr-200821:23Not Applicable
Package_1_for_kb951058~31bf3856ad364e35~amd64~~ Applicable1,81529-Apr-200821:12Not Applicable
Package_2_for_kb951058~31bf3856ad364e35~amd64~~ Applicable1,98429-Apr-200821:12Not Applicable
Package_3_for_kb951058~31bf3856ad364e35~amd64~~ Applicable1,82029-Apr-200821:12Not Applicable
Package_4_for_kb951058~31bf3856ad364e35~amd64~~ Applicable1,82029-Apr-200821:12Not Applicable
Package_for_kb951058_client_1~31bf3856ad364e35~amd64~~ Applicable1,37529-Apr-200821:12Not Applicable
Package_for_kb951058_client~31bf3856ad364e35~amd64~~ Applicable1,43929-Apr-200821:12Not Applicable
Package_for_kb951058_sc_0~31bf3856ad364e35~amd64~~ Applicable1,42929-Apr-200821:12Not Applicable
Package_for_kb951058_sc~31bf3856ad364e35~amd64~~ Applicable1,43129-Apr-200821:12Not Applicable
Package_for_kb951058_server_0~31bf3856ad364e35~amd64~~ Applicable1,43329-Apr-200821:12Not Applicable
Package_for_kb951058_server~31bf3856ad364e35~amd64~~ Applicable1,43929-Apr-200821:12Not Applicable
Package_for_kb951058_winpesrv_0~31bf3856ad364e35~amd64~~ Applicable1,43029-Apr-200821:12Not Applicable
Package_for_kb951058_winpesrv~31bf3856ad364e35~amd64~~ Applicable1,43729-Apr-200821:12Not Applicable
Windows Server 2008, IA-64 version
File nameFile versionFile sizeDateTimePlatform
Iscsi.infNot Applicable7,44028-Apr-200822:59Not Applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Users and applications request and receive data from high-performance data storage devices over standard network switches and over IP routers. The iSCSI protocol sends SCSI commands that are encapsulated in IP packets over TCP/IP networks. Because iSCSI is IP-based, data can be transmitted over local area networks (LANs), over wide area networks (WANs), and over the Internet to remote storage locations.

Article ID: 951058 - Last Review: 01/16/2015 02:27:03 - Revision: 2.0

Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 Standard

  • kbnosurvey kbarchive kbautohotfix kbexpertiseadvanced kbhotfixserver kbqfe KB951058