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

Symptoms
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 reportedthat 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 informationWindows 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 tocreate a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(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 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?(http://support.microsoft.com/kb/322389/) How to obtain the latest Windows XP service packRestart requirement You must restart the computer after you apply this hotfix. Hotfix replacement information This hotfix does not replace any other hotfixes. File informationThe 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementSdbus.sys6.0.4069.349379,36015-Dec-200810:22x86SP2Sffdisk.sys6.0.4069.349313,82415-Dec-200810:14x86SP2Sffp_mmc.sys6.0.4069.349310,24015-Dec-200810:14x86SP2Sffp_sd.sys6.0.4069.349311,52015-Dec-200810:14x86SP2Sdbus.infNot Applicable3,70115-Dec-200808:17Not ApplicableSP2Sffdisk.infNot Applicable4,43315-Dec-200808:17Not ApplicableSP2Sdbus.infNot Applicable3,70115-Dec-200808:17Not ApplicableSP2Sffdisk.infNot Applicable4,43315-Dec-200808:17Not ApplicableSP2Windows XP with Service Pack 3, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementSdbus.infNot Applicable3,66215-Dec-200809:06Not ApplicableSP3Sdbus.infNot Applicable3,66215-Dec-200809:06Not ApplicableSP3Windows Vista and Windows Server 2008Important 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=support(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 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?(http://support.microsoft.com/kb/935791/) How to obtain the latest Windows Vista service pack No prerequisites are required for Windows Server 2008-based computers. Restart requirementYou 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 notesThe 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 branch6.0.6000.16xxxWindows VistaRTMGDR6.0.6000.20xxxWindows VistaRTMLDR6.0.6001.18xxxWindows Vista SP1 and Windows Server 2008 SP1SP1GDR6.0.6001.22xxxWindows Vista SP1 and Windows Server 2008 SP1SP1LDRService 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSdbus.infNot Applicable7,98011-Nov-200823:34Not ApplicableSdbus.sys6.0.6001.2230789,08812-Nov-200802:55x86For all supported x64-based versions of Windows Server 2008 and Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSdbus.infNot Applicable8,02012-Nov-200800:15Not ApplicableSdbus.sys6.0.6001.22307111,10412-Nov-200803:30x64For all supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSdbus.infNot Applicable8,00012-Nov-200800:20Not ApplicableSdbus.sys6.0.6001.22307268,80012-Nov-200802:54IA-64

Offline files that are ghost items on a computer that is running Windows Vista or Windows Server 2008 cannot be synchronized with the corresponding files on a file server

Symptoms
On a computer that is running Windows Vista orWindows Server 2008, you have some offline files that are ghost items. In this situation, you cannot synchronize the offline files on this computer with the corresponding files on a file server. Additionally, you cannot access or delete these offline files.
Note Ghosting is a new feature for offline files in Windows Vista and in Windows Server 2008. Sometimes, a synchronization process may stop responding because ofnetwork issues that occur when the contents of a file ordirectory are only partly cached. In this case, client-side caching (CSC) creates ghost items on the client computer. Ghost items cannot be deleted. Additionally, the ghosting feature cannot be disabled.
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 this specific problem. 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(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.PrerequisitesTo apply this hotfix, the computer must be running one of the following: Windows Vista Windows Vista SP1Windows Server 2008Restart requirementYou mustrestart the computer after you apply this hotfix.Hotfix replacement information This hotfix does not replace any other previously released hotfixes. Registry information To use this hotfix, you do not have to make any changes to the registry.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 notesThe files that apply to a specific product, milestone (RTM, SPn) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
VersionProductMilestoneService branch 6.0.6000.20xxx Windows RTM LDR 6.0.6001.22xxx Windows Vista SP1 and Windows Server 2008 SP1 SP1 LDR Service Pack 1 is integrated into Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number. The MANIFEST files (.manifest) and MUM files (.mum) that are 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 of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCscobj.dll6.0.6000.20793131,58415-Mar-200803:30x86Offlinefileswmiprovider.mofNot Applicable42,87713-Dec-200720:11Not ApplicableOfflinefileswmiprovider_uninstall.mofNot Applicable42,87713-Dec-200720:11Not ApplicableCscsvc.dll6.0.6000.20793489,47215-Mar-200803:30x86Microsoft-windows-offlinefiles.mofNot Applicable1,93113-Dec-200720:11Not ApplicableCscsvc.dll6.0.6001.22137487,42415-Mar-200803:32x86Microsoft-windows-offlinefiles.mofNot Applicable1,93118-Dec-200721:26Not ApplicableFor all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCscobj.dll6.0.6000.20793216,57615-Mar-200803:46x64Offlinefileswmiprovider.mofNot Applicable42,87714-Dec-200721:49Not ApplicableOfflinefileswmiprovider_uninstall.mofNot Applicable42,87714-Dec-200721:49Not ApplicableCscsvc.dll6.0.6000.20793603,13615-Mar-200803:46x64Microsoft-windows-offlinefiles.mofNot Applicable1,93114-Dec-200721:48Not ApplicableCscsvc.dll6.0.6001.22137603,64815-Mar-200803:58x64Microsoft-windows-offlinefiles.mofNot Applicable1,93118-Dec-200721:26Not ApplicableCscobj.dll6.0.6000.20793131,58415-Mar-200803:30x86Offlinefileswmiprovider.mofNot Applicable42,87713-Dec-200720:11Not ApplicableOfflinefileswmiprovider_uninstall.mofNot Applicable42,87713-Dec-200720:11Not ApplicableFor all supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCscsvc.dll6.0.6001.221371,226,75215-Mar-200803:44IA-64Microsoft-windows-offlinefiles.mofNot Applicable1,93118-Dec-200721:26Not Applicable

MS09-058: Vulnerabilities in Windows kernel could allow elevation of privilege

Symptoms
Microsoft has released security bulletin MS09-058. To view the complete security bulletin, visit one of the following Microsoft Web sites:Home users:
http://www.microsoft.com/security/updates/bulletins/200910.aspx(http://www.microsoft.com/security/updates/bulletins/200910.aspx)Skip the details: Download the updates for your home computer or laptop from the Microsoft Update Web site now:
http://update.microsoft.com/microsoftupdate(http://update.microsoft.com/microsoftupdate/)IT professionals:
http://www.microsoft.com/technet/security/bulletin/MS09-058.mspx(http://www.microsoft.com/technet/security/bulletin/MS09-058.mspx)
How to obtain help and support for this security update For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for support issues with security updates, visit the Microsoft International Support Web site:
http://support.microsoft.com/common/international.aspx?rdpath=4(http://support.microsoft.com/common/international.aspx?rdpath=4) North American customers can also obtain instant access to unlimited no-charge e-mail support or to unlimited individual chat support by visiting the following Microsoft Web site:
http://support.microsoft.com/oas/default.aspx?&prid=7552(http://support.microsoft.com/oas/default.aspx?&prid=7552) For enterprise customers, support for security updates is available through your usual support contacts.
Resolution
Known issues with this security updateAfter you install this security update, you may receive a stop error message on a terminal server that is running Windows Server 2003 SP2. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
978243?(http://support.microsoft.com/kb/978243/) A terminal server that is running Windows Server 2003 Service Pack 2 restarts unexpectedly after hotfix 971280 or security update 971486 (MS09-058) is installed
To resolve this issue, either install hotfix 978243 or security update 977165 (documented in security bulletin MS10-015). Security update 971486 is superseded by security update 977165, which includes hotfix 978243.For more information about security update 977165, click the following article number to view the article in the Microsoft Knowledge Base:
977165?(http://support.microsoft.com/kb/977165/) MS10-015: Vulnerabilities in Windows kernel could allow elevation of privilege

FIX: You receive an error message when you try to install the original release version of SQL Server 2005 or SQL Server 2005 Service Pack 1 on a computer that is running Windows Vista

Symptoms
When you try to install the original release version of Microsoft SQL Server 2005 or Microsoft SQL Server 2005 Service Pack 1 (SP1) on a computer that is running Windows Vista, you receive the following error message:

SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Windows NT user or group ‘ COMPUTERNAME \SQLServer2005MSSQLUser$ COMPUTERNAME $INSTANCENAME’ not found. Check the name again. Refer to the server error logs and Setup logs for detailed error information.This problem occurs if the following conditions are true:The name of the computer that is running Windows Vista consists of lowercase characters or of a mixture of lowercase characters and uppercase characters. For example, the name of the computer resembles the following name:
Workstation-1You specify a case-sensitive collation setting for the SQL Server service when you install SQL Server 2005.Note In some cases, this problem may occur if the name of the computer contains some special characters. For example, this problem may occur if the name of the computer contains some characters in Turkish.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935791?(http://support.microsoft.com/kb/935791/) How to obtain the latest Windows Vista service pack
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 this specific problem. 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 tocreate a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(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.File informationThe 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, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformUpdate.mumNot Applicable3,19520-Mar-200701:24Not ApplicableX86_70ff42da86d723f67a3f3a1411ddf687_31bf3856ad364e35_6.0.6000.20560_none_e17f2a45666acde1.manifestNot Applicable72520-Mar-200701:24Not ApplicableX86_7e706e7fa6f9cb7ac9e0efb16a9500db_31bf3856ad364e35_6.0.6000.20560_none_afaa4884915dfbea.manifestNot Applicable72520-Mar-200701:24Not ApplicableX86_91f11115ca1bbc0ccb9db5ad2b9e733e_31bf3856ad364e35_6.0.6000.20560_none_669c115aeb3b43e8.manifestNot Applicable72520-Mar-200701:24Not ApplicableX86_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.0.6000.20560_none_0a84b2fb0e7427fe.manifestNot Applicable4,53720-Mar-200701:27Not ApplicableX86_microsoft-windows-a..ence-mitigations-c2_31bf3856ad364e35_6.0.6000.20560_none_0a85b3450e734155.manifestNot Applicable3,54020-Mar-200701:27Not ApplicableX86_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_6.0.6000.20560_none_0a87b3d90e717403.manifestNot Applicable9,99920-Mar-200701:27Not ApplicableAcres.dll6.0.6000.205602,56018-Mar-200720:55x86Sysmain.sdbNot Applicable3,203,65218-Mar-200720:07Not ApplicableMsimain.sdbNot Applicable1,545,32818-Mar-200720:07Not ApplicableAcspecfc.dll6.0.6000.20560449,53618-Mar-200723:26x86Windows Vista, 64-bit versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformAmd64_2140efa18e94f1269e0ad3a59f4becac_31bf3856ad364e35_6.0.6000.20560_none_49030b48e61a592a.manifestNot Applicable1,10020-Mar-200701:24Not ApplicableAmd64_60e64020e67d0c34a5ac2bd955ab1682_31bf3856ad364e35_6.0.6000.20560_none_de1de1020fe7553c.manifestNot Applicable1,09820-Mar-200701:24Not ApplicableAmd64_c74321cbbee835f448ea76ca0b3a6482_31bf3856ad364e35_6.0.6000.20560_none_f913af93c7080ecc.manifestNot Applicable72920-Mar-200701:24Not ApplicableAmd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.0.6000.20560_none_66a34e7ec6d19934.manifestNot Applicable3,55720-Mar-200701:31Not ApplicableAmd64_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_6.0.6000.20560_none_66a64f5cc6cee539.manifestNot Applicable4,68420-Mar-200701:31Not ApplicableUpdate.mumNot Applicable3,70120-Mar-200701:24Not ApplicableWow64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.0.6000.20560_none_70f7f8d0fb325b2f.manifestNot Applicable4,46020-Mar-200701:31Not ApplicableWow64_microsoft-windows-a..ence-mitigations-c2_31bf3856ad364e35_6.0.6000.20560_none_70f8f91afb317486.manifestNot Applicable3,46320-Mar-200701:31Not ApplicableX86_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_6.0.6000.20560_none_0a87b3d90e717403.manifestNot Applicable9,99920-Mar-200701:31Not ApplicableSysmain.sdbNot Applicable41,73018-Mar-200720:08Not ApplicableAcspecfc.dll6.0.6000.2056088,06419-Mar-200700:41x64Acres.dll6.0.6000.205602,56018-Mar-200720:55x86Sysmain.sdbNot Applicable3,203,65218-Mar-200720:07Not ApplicableMsimain.sdbNot Applicable1,545,32818-Mar-200720:07Not ApplicableAcspecfc.dll6.0.6000.20560449,53618-Mar-200723:26×86

FIX: Error message when you send an e-mail by using a private Database Mail profile in SQL Server 2005 or in SQL Server 2008: “profile name is not valid”

Symptoms
You create a non-administrator Windows account that is a member of multiple Windows groups. These Windows groups have the same permission setting. In Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, you add these Windows groups as SQL Server logins. You configure Database Mail accounts and profiles by using these SQL Server logins. When you use Database Mail to send an e-mail, you receive Error 14607 in the following scenarios:
Scenario 1
You create a private Database Mail profile that uses the Windows account as the Simple Mail Transfer Protocol (SMTP) account. You configure the private profile for one of the Windows groups that was not first added as a SQL Server login. When you send an e-mail by using the profile, you receive the following error message:

Msg 14607, Level 16, State 1, Procedure sp_send_dbmail, Line 136
profile name is not validScenario 2
You create two private Database Mail profiles that use the Windows account as the SMTP account. You configure the private profile for one of the Windows groups. When you send an e-mail by using the nondefault instance in the two private profiles, you receive the following error message:

Msg 14607, Level 16, State 1, Procedure sp_send_dbmail, Line 136
profile name is not valid
Scenario 3
You create a private Database Mail profile that uses the Windows account as the SMTP account. You configure the private profile for one of the Windows groups. Then, you explicitly add the Windows account as a SQL Server login. When you send an e-mail by using the profile, you receive the following error message:

Msg 515, Level 16, State 2, Procedure sp_validate_user, Line 19
Cannot insert the value NULL into column ‘permission path’, table ‘@temp’; column does not allow nulls. INSERT fails.
The statement has been terminated.
Msg 14607, Level 16, State 1, Procedure sp_send_dbmail, Line 136
profile name is not valid
Resolution
Cumulative update informationThe release version of SQL Server 2008Important You must install this cumulative update package if your computer is running the release version of SQL Server 2008.
The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
971490?(http://support.microsoft.com/kb/971490/) Cumulative update package 6 for SQL Server 2008Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909?(http://support.microsoft.com/kb/956909/) The SQL Server 2008 builds that were released after SQL Server 2008 was releasedSQL Server 2008 Service Pack 1Important You must install this cumulative update package if your computer is running SQL Server 2008 Service Pack 1.
The fix for this issue was also released in Cumulative Update3 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
971491?(http://support.microsoft.com/kb/971491/LN/) Cumulative update package 3 for SQL Server 2008 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365?(http://support.microsoft.com/kb/970365/LN/) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedMicrosoft SQL Server 2008hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack. SQL Server 2005 Service Pack 3Important You must install this cumulative update package if your computer is running SQL Server 2005 Service Pack 3.
The fix for this issue was first released in Cumulative Update4 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
970279?(http://support.microsoft.com/kb/970279/LN/) Cumulative update package 4 for SQL Server 2005 Service Pack 3Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598?(http://support.microsoft.com/kb/960598/LN/) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was releasedMicrosoft SQL Server 2005hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.