Article ID: 2288055 - Last Review: August 12, 2010 - Revision: 1.0 The backup data is corrupted when you use the Windows Backup utility to back up some SQL Server databases or the AD LDS instance data in Windows 7
On This PageSYMPTOMSWhen you use the Windows Backup utility on a computer that is running Windows 7, the following two issues may occur. Issue 1You run Microsoft SQL Server on the computer. When you use the Windows Backup utility to back up some SQL Server databases by using Volume Shadow Copy Service (VSS), the backup may be corrupted.Issue 2You install Active Directory Lightweight Directory Services (AD LDS) for Windows 7 on the computer. When you try to restore the AD LDS instance data backup that was created by the Windows Backup utility, the instance data is corrupted.CAUSEThese issues occurs because the Windows Backup utility relies on a hard-coded list of VSS writers. However, the VSS writers for SQL Server and for AD LDS are not used to create the backups. Therefore, the backup data is corrupted. Note These issues may occur to some other applications that do not have the corresponding in-box VSS writers when you use the Windows Backup utility to back up data. RESOLUTIONAfter you apply this hotfix, you can create a multi-string value that has the EnabledWriters name to specify additional VSS writers for the backup in the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP
You can also create a DWORD value that has the BackupType name for the default backup type in the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP Hotfix informationA 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.PrerequisitesTo apply this hotfix, you must be running Windows 7.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe 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 7 file information notesImportant 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.
For all supported x86-based versions of Windows 7Collapse this table
For all supported x64-based versions of Windows 7Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about how to use VSS, visit the following Microsoft Developer Network (MSDN) website: General information about how to use VSS
(http://msdn.microsoft.com/en-us/library/aa384629(VS.85).aspx)
For more information about AD LDS for Windows7, visit the following Microsoft website:General information about AD LDS for Windows7
(http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a45059af-47a8-4c96-afe3-93dab7b5b658)
For more information about the Wbadmin command, visit the following Microsoft website: General information about the "Wbadmin" command
(http://technet.microsoft.com/en-us/library/cc754015(WS.10).aspx)
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Additional file informationAdditional file information for Windows 7Additional files for all supported x86-based versions of Windows 7Collapse this table
Additional files for all supported x64-based versions of Windows 7Collapse this table
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
