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.

Write protection does not always work on SD memory cards that are plugged into a computer that runs Windows XP, Windows Vista, or Windows Server 2008


View products that this article applies to.

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.

↑ Back to the top


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.

↑ Back to the top


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: 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
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 nameFile versionFile sizeDateTimePlatformSP requirement
Sdbus.sys6.0.4069.349379,36015-Dec-200810:22x86SP2
Sffdisk.sys6.0.4069.349313,82415-Dec-200810:14x86SP2
Sffp_mmc.sys6.0.4069.349310,24015-Dec-200810:14x86SP2
Sffp_sd.sys6.0.4069.349311,52015-Dec-200810:14x86SP2
Sdbus.infNot Applicable3,70115-Dec-200808:17Not ApplicableSP2
Sffdisk.infNot Applicable4,43315-Dec-200808:17Not ApplicableSP2
Sdbus.infNot Applicable3,70115-Dec-200808:17Not ApplicableSP2
Sffdisk.infNot Applicable4,43315-Dec-200808:17Not ApplicableSP2
Windows XP with Service Pack 3, x86-based versions
File nameFile versionFile sizeDateTimePlatformSP requirement
Sdbus.infNot Applicable3,66215-Dec-200809:06Not ApplicableSP3
Sdbus.infNot Applicable3,66215-Dec-200809:06Not ApplicableSP3

↑ Back to the top


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: 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
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.
    VersionProductMilestoneService branch
    6.0.6000.16xxxWindows VistaRTMGDR
    6.0.6000.20xxxWindows VistaRTMLDR
    6.0.6001.18xxxWindows Vista SP1 and Windows Server 2008 SP1SP1GDR
    6.0.6001.22xxxWindows Vista SP1 and Windows Server 2008 SP1SP1LDR
  • 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 nameFile versionFile sizeDateTimePlatform
Sdbus.infNot Applicable7,98011-Nov-200823:34Not Applicable
Sdbus.sys6.0.6001.2230789,08812-Nov-200802:55x86
For all supported x64-based versions of Windows Server 2008 and Windows Vista
File nameFile versionFile sizeDateTimePlatform
Sdbus.infNot Applicable8,02012-Nov-200800:15Not Applicable
Sdbus.sys6.0.6001.22307111,10412-Nov-200803:30x64
For all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Sdbus.infNot Applicable8,00012-Nov-200800:20Not Applicable
Sdbus.sys6.0.6001.22307268,80012-Nov-200802:54IA-64

↑ Back to the top


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 Windows
To 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.

↑ 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 Vista and Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista
File namePackage_1_for_kb959465~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,972
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_2_for_kb959465~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,810
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_for_kb959465_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,367
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_for_kb959465_client~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,430
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_for_kb959465_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,425
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_for_kb959465_server~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,430
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File nameX86_sdbus.inf_31bf3856ad364e35_6.0.6001.22307_none_72735f60e36e5d53.manifest
File versionNot Applicable
File size1,664
Date (UTC)12-Nov-2008
Time (UTC)21:19
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows Server 2008 and Windows Vista
File nameAmd64_sdbus.inf_31bf3856ad364e35_6.0.6001.22307_none_ce91fae49bcbce89.manifest
File versionNot Applicable
File size1,666
Date (UTC)12-Nov-2008
Time (UTC)21:21
PlatformNot Applicable
File namePackage_1_for_kb959465~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,984
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_2_for_kb959465~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,820
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_for_kb959465_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,375
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_for_kb959465_client~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,438
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_for_kb959465_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,433
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_for_kb959465_server~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,438
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
Additional files for all supported Itanium-based versions of Windows Server 2008
File nameIa64_sdbus.inf_31bf3856ad364e35_6.0.6001.22307_none_72750356e36c664f.manifest
File versionNot Applicable
File size1,665
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_1_for_kb959465~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot Applicable
File size1,815
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_for_kb959465_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot Applicable
File size1,429
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable
File namePackage_for_kb959465_server~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot Applicable
File size1,434
Date (UTC)12-Nov-2008
Time (UTC)21:17
PlatformNot Applicable

↑ Back to the top


Keywords: kb, kbfixme, kbmsifixme, kbexpertisebeginner, kbautohotfix, kbsurveynew, kbbug, kbfix, kbhotfixserver, kbqfe

↑ Back to the top

Article Info
Article ID : 959465
Revision : 1
Created on : 1/7/2017
Published on : 10/9/2011
Exists online : False
Views : 195