Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Introduction

This article describes a hotfix that provides a mechanism for Microsoft Device Specific Module (DSM) to notify Microsoft Multipath I/O (MPIO) that a particular path is back online. This hotfix adds a new notification type to the existing DsmNotification interface.

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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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.

Notes for third-party DSM developers

If you want to implement your own DSM provider together with MS MPIO, and you want to configure PathOnLine notification type that is introduced in this update, follow the following syntax:

For the new PathOnline notification type, the DsmNotification interface takes these additional parameters: PathId (PVOID), DsmId (PVOID), Status (PNTSTATUS).

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 Service Pack 2 (SP2) or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849How to obtain the latest service pack for Windows Server 2008

For more information about how to obtain a Windows 7 or a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global 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 Server 2008 file information notesImportant Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • 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.

    Version

    Product

    SR_Level

    Service branch

    6.0.600
    2.
    22xxx

    Windows Server 2008

    SP2

    LDR

  • 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 Vista and for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Mpio.sys

6.0.6002.22946

107,392

09-Oct-2012

17:27

x86

Msdsm.sys

6.0.6002.22946

92,032

09-Oct-2012

17:31

x86

For all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Mpio.sys

6.0.6002.22946

131,968

09-Oct-2012

17:20

x64

Msdsm.sys

6.0.6002.22946

111,488

09-Oct-2012

17:24

x64

For all supported IA-64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Mpio.sys

6.0.6002.22946

294,288

09-Oct-2012

17:12

IA-64

Msdsm.sys

6.0.6002.22946

276,864

09-Oct-2012

17:16

IA-64

Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • 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.

    Version

    Product

    SR_Level

    Service branch

    6.1.760
    1.
    18xxx

    Windows Server 2008 R2

    SP1

    GDR

    6.1.760
    1.
    22xxx

    Windows 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 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 Server 2008 R2

File name

File version

File size

Date

Time

Platform

Mpio.sys

6.1.7601.18015

159,064

30-Nov-2012

06:02

x64

Mpio.sys

6.1.7601.22177

160,600

30-Nov-2012

05:58

x64

Msdsm.sys

6.1.7601.18015

141,144

30-Nov-2012

06:02

x64

Msdsm.sys

6.1.7601.22177

142,168

30-Nov-2012

05:58

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Mpio.sys

6.1.7601.18015

357,208

30-Nov-2012

04:44

IA-64

Mpio.sys

6.1.7601.22177

365,912

30-Nov-2012

04:56

IA-64

Msdsm.sys

6.1.7601.18015

348,520

30-Nov-2012

04:44

IA-64

Msdsm.sys

6.1.7601.22177

352,088

30-Nov-2012

04:56

IA-64



Status

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

More Information

When a path failure is reported by the DSM, the MPIO marks the path as failed and schedules a path recovery worker thread. If the path is back online, the DSM recognizes it as a valid path and may return the path of the MPIO. However, if the recovery worker thread of the path does not run, the path is still marked as failed. Therefore, a delay occurs when the MPIO handles the I/O requests.

After you apply this hotfix, the DSM can notify the MPIO to clear the failure mark on a path that is back online.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2008

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

File name

X86_mpio.inf_31bf3856ad364e35_6.0.6002.22946_none_1f7dc23ca5b31cd7.manifest

File version

Not applicable

File size

1,659

Date (UTC)

09-Oct-2012

Time (UTC)

17:36

Platform

Not applicable

File name

X86_msdsm.inf_31bf3856ad364e35_6.0.6002.22946_none_cc922855f1ea6ee6.manifest

File version

Not applicable

File size

1,664

Date (UTC)

09-Oct-2012

Time (UTC)

17:36

Platform

Not applicable

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

File name

Amd64_mpio.inf_31bf3856ad364e35_6.0.6002.22946_none_7b9c5dc05e108e0d.manifest

File version

Not applicable

File size

1,661

Date (UTC)

09-Oct-2012

Time (UTC)

17:36

Platform

Not applicable

File name

Amd64_msdsm.inf_31bf3856ad364e35_6.0.6002.22946_none_28b0c3d9aa47e01c.manifest

File version

Not applicable

File size

1,666

Date (UTC)

09-Oct-2012

Time (UTC)

17:36

Platform

Not applicable

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

File name

Ia64_mpio.inf_31bf3856ad364e35_6.0.6002.22946_none_1f7f6632a5b125d3.manifest

File version

Not applicable

File size

1,660

Date (UTC)

09-Oct-2012

Time (UTC)

17:36

Platform

Not applicable

File name

Ia64_msdsm.inf_31bf3856ad364e35_6.0.6002.22946_none_cc93cc4bf1e877e2.manifest

File version

Not applicable

File size

1,665

Date (UTC)

09-Oct-2012

Time (UTC)

17:36

Platform

Not applicable

Additional file information for Windows Server 2008 R2

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

File name

Amd64_mpio.inf_31bf3856ad364e35_6.1.7601.18015_none_7b59c20ea5f30ae4.manifest

File version

Not Applicable

File size

2,073

Date (UTC)

30-Nov-2012

Time (UTC)

06:36

Platform

Not Applicable

File name

Amd64_mpio.inf_31bf3856ad364e35_6.1.7601.22177_none_7ba47fe5bf3f8502.manifest

File version

Not Applicable

File size

2,073

Date (UTC)

30-Nov-2012

Time (UTC)

06:24

Platform

Not Applicable

File name

Amd64_msdsm.inf_31bf3856ad364e35_6.1.7601.18015_none_286e2827f22a5cf3.manifest

File version

Not Applicable

File size

2,079

Date (UTC)

30-Nov-2012

Time (UTC)

06:43

Platform

Not Applicable

File name

Amd64_msdsm.inf_31bf3856ad364e35_6.1.7601.22177_none_28b8e5ff0b76d711.manifest

File version

Not Applicable

File size

2,079

Date (UTC)

30-Nov-2012

Time (UTC)

06:29

Platform

Not Applicable

File name

Update-bf.mum

File version

Not Applicable

File size

30,780

Date (UTC)

30-Nov-2012

Time (UTC)

12:26

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

31,393

Date (UTC)

30-Nov-2012

Time (UTC)

12:26

Platform

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_mpio.inf_31bf3856ad364e35_6.1.7601.18015_none_1f3cca80ed93a2aa.manifest

File version

Not Applicable

File size

2,071

Date (UTC)

30-Nov-2012

Time (UTC)

06:13

Platform

Not Applicable

File name

Ia64_mpio.inf_31bf3856ad364e35_6.1.7601.22177_none_1f87885806e01cc8.manifest

File version

Not Applicable

File size

2,071

Date (UTC)

30-Nov-2012

Time (UTC)

06:17

Platform

Not Applicable

File name

Ia64_msdsm.inf_31bf3856ad364e35_6.1.7601.18015_none_cc51309a39caf4b9.manifest

File version

Not Applicable

File size

2,077

Date (UTC)

30-Nov-2012

Time (UTC)

06:17

Platform

Not Applicable

File name

Ia64_msdsm.inf_31bf3856ad364e35_6.1.7601.22177_none_cc9bee7153176ed7.manifest

File version

Not Applicable

File size

2,077

Date (UTC)

30-Nov-2012

Time (UTC)

06:21

Platform

Not Applicable

File name

Update-bf.mum

File version

Not Applicable

File size

4,318

Date (UTC)

30-Nov-2012

Time (UTC)

12:26

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

4,399

Date (UTC)

30-Nov-2012

Time (UTC)

12:26

Platform

Not Applicable


Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×