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.

Old data is displayed for an SD card that you reinsert into a Windows 7, Windows Server 2008 R2, Windows Server 2008 or Windows Vista-based computer that is in standby or in hibernation


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You insert a Secure Digital (SD) card into a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008.
  • You open Windows Explorer to view the contents of the SD card.
  • You put the computer into standby or into hibernation.
  • You remove the SD card, and then change the contents of the card by using another computer or device.
  • You reconnect the SD card to the original computer.
  • You resume the computer from standby or from hibernation.
In this scenario, Windows Explorer may not display the current contents of the SD card. Specifically, you may still see the old contents of the SD card.

Additionally, if you try to change the SD card or to add new data to the SD card, you may experience unpredictable results. For example, the file system on the SD card may be corrupted.

↑ Back to the top


Cause

This issue occurs because the SD card reader does not send a signal to the operating system when the contents of the card are changed while the computer is in standby or in hibernation. Therefore, the computer does not rescan the SD card for new or changed content.

↑ 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: 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, you must be running one of the following operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7
  • Windows Server 2008 R2
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791� How to obtain the latest Windows Vista service pack
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:
968849� How to obtain the latest service pack for Windows Server 2008

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) 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 Vista and Windows Server 2008 file information notes
Important 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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 1 . 22xxxWindows Vista and Windows Server 2008SP1LDR
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxx version number.
  • 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 and for Windows Vista" section. MUM files 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 x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Sdbus.sys6.0.6001.2274389,08817-Aug-201012:55x86
Sdbus.sys6.0.6002.2246889,08817-Aug-201013:33x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Sdbus.sys6.0.6001.22743111,10417-Aug-201013:17x64
Sdbus.sys6.0.6002.22468111,10417-Aug-201013:48x64
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Sdbus.sys6.0.6001.22743268,80017-Aug-201013:01IA-64
Sdbus.sys6.0.6002.22468268,80017-Aug-201013:23IA-64
Windows 7 and 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.1.760 0.16xxxWindows 7 and Windows Server 2008 R2RTMGDR
    6.1.760 0.20xxxWindows 7 and Windows Server 2008 R2RTMLDR
  • 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 and for Windows 7" 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 x86-based versions of Windows 7
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Sdbus.sys6.1.7600.1659384,99213-May-201020:36x86
Sdbus.sys6.1.7600.2071384,99213-May-201020:35x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Sdbus.sys6.1.7600.16593109,05613-May-201020:55x64
Sdbus.sys6.1.7600.20713109,05613-May-201020:48x64
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Sdbus.sys6.1.7600.16593271,87213-May-201020:06IA-64
Sdbus.sys6.1.7600.20713271,87213-May-201020:11IA-64

↑ Back to the top


Workaround

To work around this issue, resume the computer from standby or from hibernation before you remove the SD card.

↑ 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

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot Applicable
File size2,409
Date (UTC)17-Aug-2010
Time (UTC)22:26
PlatformNot Applicable
File nameX86_sdbus.inf_31bf3856ad364e35_6.0.6001.22743_none_72442620e3925c57.manifest
File versionNot Applicable
File size1,664
Date (UTC)17-Aug-2010
Time (UTC)22:26
PlatformNot Applicable
File nameX86_sdbus.inf_31bf3856ad364e35_6.0.6002.22468_none_7419f9a2e0c46810.manifest
File versionNot Applicable
File size1,664
Date (UTC)17-Aug-2010
Time (UTC)22:26
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_sdbus.inf_31bf3856ad364e35_6.0.6001.22743_none_ce62c1a49befcd8d.manifest
File versionNot Applicable
File size1,666
Date (UTC)17-Aug-2010
Time (UTC)22:26
PlatformNot Applicable
File nameAmd64_sdbus.inf_31bf3856ad364e35_6.0.6002.22468_none_d03895269921d946.manifest
File versionNot Applicable
File size1,666
Date (UTC)17-Aug-2010
Time (UTC)22:26
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,427
Date (UTC)17-Aug-2010
Time (UTC)22:26
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameIa64_sdbus.inf_31bf3856ad364e35_6.0.6001.22743_none_7245ca16e3906553.manifest
File versionNot Applicable
File size1,665
Date (UTC)17-Aug-2010
Time (UTC)22:26
PlatformNot Applicable
File nameIa64_sdbus.inf_31bf3856ad364e35_6.0.6002.22468_none_741b9d98e0c2710c.manifest
File versionNot Applicable
File size1,665
Date (UTC)17-Aug-2010
Time (UTC)22:26
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,587
Date (UTC)17-Aug-2010
Time (UTC)22:26
PlatformNot Applicable

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot applicable
File size1,441
Date (UTC)14-May-2010
Time (UTC)17:52
File nameX86_sdbus.inf_31bf3856ad364e35_6.1.7600.16593_none_71ac46332bb48adc.manifest
File versionNot applicable
File size2,075
Date (UTC)14-May-2010
Time (UTC)01:08
File nameX86_sdbus.inf_31bf3856ad364e35_6.1.7600.20713_none_728c644444914845.manifest
File versionNot applicable
File size2,075
Date (UTC)14-May-2010
Time (UTC)09:20
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_sdbus.inf_31bf3856ad364e35_6.1.7600.16593_none_cdcae1b6e411fc12.manifest
File versionNot applicable
File size2,079
Date (UTC)14-May-2010
Time (UTC)02:40
File nameAmd64_sdbus.inf_31bf3856ad364e35_6.1.7600.20713_none_ceaaffc7fceeb97b.manifest
File versionNot applicable
File size2,079
Date (UTC)14-May-2010
Time (UTC)04:11
File nameUpdate.mum
File versionNot applicable
File size1,653
Date (UTC)14-May-2010
Time (UTC)17:52
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_sdbus.inf_31bf3856ad364e35_6.1.7600.16593_none_71adea292bb293d8.manifest
File versionNot applicable
File size2,077
Date (UTC)14-May-2010
Time (UTC)01:51
File nameIa64_sdbus.inf_31bf3856ad364e35_6.1.7600.20713_none_728e083a448f5141.manifest
File versionNot applicable
File size2,077
Date (UTC)14-May-2010
Time (UTC)03:42
File nameUpdate.mum
File versionNot applicable
File size1,445
Date (UTC)14-May-2010
Time (UTC)17:52

↑ Back to the top


Keywords: kbsurveynew, kbexpertiseadvanced, kbhotfixserver, kbautohotfix, kbqfe, KB982479

↑ Back to the top

Article Info
Article ID : 982479
Revision : 4
Created on : 11/1/2010
Published on : 11/1/2010
Exists online : False
Views : 465