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.

Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows.

Problem description

Your computer runs Windows XP, Windows Vista, or Windows Server 2008. You plugged a Secure Digital (SD) memory card into the computer while the write protection on the SD memory card was turned off. Then, you put the computer to sleep or in hibernation. When the computer was asleep or in hibernation, you turned on the write protection on the SD memory card. Finally, you resumed the computer, and then you tried to write to the SD memory card.

When you tried to write to the SD memory card, you experienced one of the following issues:

  • The write operation was committed on the SD memory card instead of being prevented by the write protection. Therefore, you may have overwritten the data on the SD memory card unexpectedly.

  • You received a warning, and therefore expected that the operation would be canceled. However, the operation seemed to be successful. When you tried to access the newly written data, however, you received an error message that reported that the disk is corrupted.

To fix this problem, you can either download a hotfix or you can do a workaround. To download the hotfix, see the "Resolution" section. To run the workaround, see the "Workaround" section.

Resolution

This problem occurs because some incorrect parameters are written into the registry when the Sdbus.sys driver initializes.

Hotfix information

Windows XP

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.

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, submit a request to 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=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.

Prerequisites

To apply this hotfix on a Windows XP-based computer, you must have Windows XP Service Pack 2 or Windows XP Service Pack 3 installed on the computer.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

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 XP with Service Pack 2, x86-based versions

File name

File version

File size

Date

Time

Platform

SP requirement

Sdbus.sys

6.0.4069.3493

79,360

15-Dec-2008

10:22

x86

SP2

Sffdisk.sys

6.0.4069.3493

13,824

15-Dec-2008

10:14

x86

SP2

Sffp_mmc.sys

6.0.4069.3493

10,240

15-Dec-2008

10:14

x86

SP2

Sffp_sd.sys

6.0.4069.3493

11,520

15-Dec-2008

10:14

x86

SP2

Sdbus.inf

Not Applicable

3,701

15-Dec-2008

08:17

Not Applicable

SP2

Sffdisk.inf

Not Applicable

4,433

15-Dec-2008

08:17

Not Applicable

SP2

Sdbus.inf

Not Applicable

3,701

15-Dec-2008

08:17

Not Applicable

SP2

Sffdisk.inf

Not Applicable

4,433

15-Dec-2008

08:17

Not Applicable

SP2

Windows XP with Service Pack 3, x86-based versions

File name

File version

File size

Date

Time

Platform

SP requirement

Sdbus.inf

Not Applicable

3,662

15-Dec-2008

09:06

Not Applicable

SP3

Sdbus.inf

Not Applicable

3,662

15-Dec-2008

09:06

Not Applicable

SP3

Windows Vista and Windows Server 2008

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.

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

Prerequisites

To apply this hotfix on a Windows Vista-based computer, you must have Windows Vista Service Pack 1 installed on the computer.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service pack

No prerequisites are required for Windows Server 2008-based computers.

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 Vista and 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 file version numbers as shown in the following table.

    Version

    Product

    Milestone

    Service branch

    6.0.6000.16xxx

    Windows Vista

    RTM

    GDR

    6.0.6000.20xxx

    Windows Vista

    RTM

    LDR

    6.0.6001.18xxx

    Windows Vista SP1 and Windows Server 2008 SP1

    SP1

    GDR

    6.0.6001.22xxx

    Windows Vista SP1 and Windows Server 2008 SP1

    SP1

    LDR

  • 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, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and Windows Vista

File name

File version

File size

Date

Time

Platform

Sdbus.inf

Not Applicable

7,980

11-Nov-2008

23:34

Not Applicable

Sdbus.sys

6.0.6001.22307

89,088

12-Nov-2008

02:55

x86

For all supported x64-based versions of Windows Server 2008 and Windows Vista

File name

File version

File size

Date

Time

Platform

Sdbus.inf

Not Applicable

8,020

12-Nov-2008

00:15

Not Applicable

Sdbus.sys

6.0.6001.22307

111,104

12-Nov-2008

03:30

x64

For all supported Itanium-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Sdbus.inf

Not Applicable

8,000

12-Nov-2008

00:20

Not Applicable

Sdbus.sys

6.0.6001.22307

268,800

12-Nov-2008

02:54

IA-64

Workaround

This problem occurs because some incorrect parameters are written into the registry when the Sdbus.sys driver initializes. This workaround writes the correct parameters into the registry. To have us run this workaround for you, go to the “Fix it for me” section. If you’d rather run this workaround yourself, go to the “Let me fix it myself” section.

Fix it for me

To fix this problem automatically, click the
Fix this problemlink. Then click
Runin the
File Downloaddialog box, and follow the steps in this wizard.




Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.

Now go to the "Did this fix the problem?" section.

Let me fix it myself

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in WindowsTo work around this problem, manually you must change a registry setting. To do this, follow these steps:

  1. Start Notepad, and then paste the following text into Notepad: Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sdbus\Parameters]
    "SdCmdFlags"=hex:06,01,09,19,0a,19,0d,11,10,01,11,01,12,01,18,05,19,05,1a,01,1b,01,1c,01,20,05,21,05,26,05,2a,01,34,02,35,02,37,01,38,01,22,01,23,05,24,01,25,01

  2. Save the file as a .reg file.

  3. Right-click the file that you saved in step 2, and then click Merge.

    User Account Control permission If you are prompted for an administrator password or for confirmation, type your password, or click
    Continue.

  4. Click Yes when you are prompted to confirm.

Did this fix the problem?

Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support.

Status

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

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

Additional file information for Windows Vista and Windows Server 2008

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

File name

Package_1_for_kb959465~31bf3856ad364e35~x86~~6.0.1.0.mum

File version

Not Applicable

File size

1,972

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_2_for_kb959465~31bf3856ad364e35~x86~~6.0.1.0.mum

File version

Not Applicable

File size

1,810

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_for_kb959465_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum

File version

Not Applicable

File size

1,367

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_for_kb959465_client~31bf3856ad364e35~x86~~6.0.1.0.mum

File version

Not Applicable

File size

1,430

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_for_kb959465_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum

File version

Not Applicable

File size

1,425

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_for_kb959465_server~31bf3856ad364e35~x86~~6.0.1.0.mum

File version

Not Applicable

File size

1,430

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

X86_sdbus.inf_31bf3856ad364e35_6.0.6001.22307_none_72735f60e36e5d53.manifest

File version

Not Applicable

File size

1,664

Date (UTC)

12-Nov-2008

Time (UTC)

21:19

Platform

Not Applicable

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

File name

Amd64_sdbus.inf_31bf3856ad364e35_6.0.6001.22307_none_ce91fae49bcbce89.manifest

File version

Not Applicable

File size

1,666

Date (UTC)

12-Nov-2008

Time (UTC)

21:21

Platform

Not Applicable

File name

Package_1_for_kb959465~31bf3856ad364e35~amd64~~6.0.1.0.mum

File version

Not Applicable

File size

1,984

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_2_for_kb959465~31bf3856ad364e35~amd64~~6.0.1.0.mum

File version

Not Applicable

File size

1,820

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_for_kb959465_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum

File version

Not Applicable

File size

1,375

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_for_kb959465_client~31bf3856ad364e35~amd64~~6.0.1.0.mum

File version

Not Applicable

File size

1,438

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_for_kb959465_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum

File version

Not Applicable

File size

1,433

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_for_kb959465_server~31bf3856ad364e35~amd64~~6.0.1.0.mum

File version

Not Applicable

File size

1,438

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

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

File name

Ia64_sdbus.inf_31bf3856ad364e35_6.0.6001.22307_none_72750356e36c664f.manifest

File version

Not Applicable

File size

1,665

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_1_for_kb959465~31bf3856ad364e35~ia64~~6.0.1.0.mum

File version

Not Applicable

File size

1,815

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_for_kb959465_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum

File version

Not Applicable

File size

1,429

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

Platform

Not Applicable

File name

Package_for_kb959465_server~31bf3856ad364e35~ia64~~6.0.1.0.mum

File version

Not Applicable

File size

1,434

Date (UTC)

12-Nov-2008

Time (UTC)

21:17

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!

×