Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The system becomes unresponsive after the primary MPIO path is disconnected on a Windows Server 2008-based computer

The system becomes unresponsive after the primary MPIO path is disconnected on a Windows Server 2008-based computer

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install Windows Server 2008 on an iSCSI storage device that is enabled with multipath I/O (MPIO) paths.
  • You start the computer by using the iSCSI storage device as the boot device.
  • You disconnect the primary path.
In this scenario, instead of failing over to a secondary path, the system becomes unresponsive. Specifically, you experience the following symptoms:
  • The Start menu disappears.
  • The system clock stops refreshing.
  • Windows do not receive the focus when you click them.

↑ Back to the top

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. Apply this hotfix only to systems that are experiencing the problem described in this article. 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:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

No prerequisites are required.

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 file information notes

  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the fileversion numbers as shown in the following table.
    VersionProductMilestoneService branch
    6.0.6001.18xxxWindows Server 2008SP1SP1GDR
    6.0.6001.22xxxWindows Server 2008SP1SP1LDR
  • Service Pack 1 is integrated into Windows Server 2008.
  • The MANIFEST files (.manifest) and MUM files (.mum)installed for each environment are listed separately. MUM and MANIFEST files, andthe associated security catalog (.cat) files, are critical to maintaining thestate of the updated component. The security catalog files (attributes notlisted) are signed with a Microsoft digital signature.
For all supported 32-bit versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Iscsi.infNot Applicable7,43613-Jan-200923:42Not Applicable
Iscsilog.dll6.0.6001.2235316,38414-Jan-200902:15x86
Msiscsi.sys6.0.6001.22353180,70414-Jan-200904:34x86
For all supported 64-bit versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Iscsi.infNot Applicable7,44413-Jan-200923:43Not Applicable
Iscsilog.dll6.0.6001.2235316,38414-Jan-200902:49x64
Msiscsi.sys6.0.6001.22353215,00814-Jan-200905:09x64
For all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Iscsi.infNot Applicable7,44013-Jan-200923:43Not Applicable
Iscsilog.dll6.0.6001.2235316,38414-Jan-200902:42IA-64
Msiscsi.sys6.0.6001.22353494,56014-Jan-200904:45IA-64

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Additional file information for Windows Server 2008

Additional files for all supported 32-bit versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Package_1_for_kb961570~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,80514-Jan-200921:06Not Applicable
Package_2_for_kb961570~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,97214-Jan-200921:06Not Applicable
Package_3_for_kb961570~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,81014-Jan-200921:06Not Applicable
Package_4_for_kb961570~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,81014-Jan-200921:06Not Applicable
Package_for_kb961570_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36714-Jan-200921:06Not Applicable
Package_for_kb961570_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43114-Jan-200921:06Not Applicable
Package_for_kb961570_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42114-Jan-200921:06Not Applicable
Package_for_kb961570_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42314-Jan-200921:06Not Applicable
Package_for_kb961570_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42514-Jan-200921:06Not Applicable
Package_for_kb961570_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43114-Jan-200921:06Not Applicable
Package_for_kb961570_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42214-Jan-200921:06Not Applicable
Package_for_kb961570_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42914-Jan-200921:06Not Applicable
X86_iscsi.inf_31bf3856ad364e35_6.0.6001.22353_none_3d1a578d0cea2400.manifestNot Applicable2,25014-Jan-200921:08Not Applicable

Additional files for all supported 64-bit versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Amd64_iscsi.inf_31bf3856ad364e35_6.0.6001.22353_none_9938f310c5479536.manifestNot Applicable2,25214-Jan-200921:10Not Applicable
Package_for_kb961570_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,37514-Jan-200921:06Not Applicable
Package_for_kb961570_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43914-Jan-200921:06Not Applicable
Package_for_kb961570_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42914-Jan-200921:06Not Applicable
Package_for_kb961570_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43114-Jan-200921:06Not Applicable
Package_for_kb961570_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43314-Jan-200921:06Not Applicable
Package_for_kb961570_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43914-Jan-200921:06Not Applicable
Package_for_kb961570_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43014-Jan-200921:06Not Applicable
Package_for_kb961570_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43714-Jan-200921:06Not Applicable

Additional files for all supported Itanium-based versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Ia64_iscsi.inf_31bf3856ad364e35_6.0.6001.22353_none_3d1bfb830ce82cfc.manifestNot Applicable2,25114-Jan-200921:06Not Applicable
Package_for_kb961570_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42514-Jan-200921:06Not Applicable
Package_for_kb961570_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42614-Jan-200921:06Not Applicable
Package_for_kb961570_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42914-Jan-200921:06Not Applicable
Package_for_kb961570_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43414-Jan-200921:06Not Applicable
Package_for_kb961570_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42614-Jan-200921:06Not Applicable
Package_for_kb961570_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43314-Jan-200921:06Not Applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbexpertiseinter, kbsurveynew, kbbug, kbfix, kbhotfixserver, kbqfe

↑ Back to the top

Article Info
Article ID : 961570
Revision : 1
Created on : 1/7/2017
Published on : 10/8/2011
Exists online : False
Views : 194