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, your computer 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
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 use one of the hotfixes in this package, you must create a registry key. To do this, follow these steps:
- Click Start, type regedit in the Search programs and files box, and then press ENTER.
If you are prompted for an administrator password, type the password. If you are prompted for confirmation, provide confirmation.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SystemWriter
Note If this registry subkey does not exist, please create it manually. - On the Edit menu, point to New, and then click Multi-String Value.
- Type ExcludedBinaryPaths, and then press ENTER. Note
- Right-click ExcludedBinaryPaths, and then click Modify.
- In the Value data box, type all binary paths that should be excluded from the system state backup operation, and then click OK.
Note The binary paths should be absolute paths. They should not include environment variables (such as %windir%) and should not be enclosed in double or single quotation marks. Be sure to also include the full binary name with the path to be excluded, for example:D:\ProgramFolder\bin\program.exe
- Exit Registry Editor.
Note- If you use this method to exclude the service data from the system state backup scope, you have to back up the service data on the shared volume manually.
- If you assign a drive letter to a shared volume that is excluded from the system state backup scope, you have to manually re-enter all the registry keys again by using a new path because the assigned drive letter does not function any longer.
Important You have to exclude services carefully because wrong entries can corrupt the system state.
Restart requirement
You may 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 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 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.
Version | Product | SR_Level | Service branch |
---|
6.0.600 1. 22xxx | Windows Vista and Windows Server 2008 | SP1 | LDR |
6.0.600 2. 22xxx | Windows Vista and Windows Server 2008 | SP2 | LDR |
- 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.xxxxxx 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 maintaining the state of the updated component. 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
File name | File version | File size | Date | Time | Platform |
---|
Cryptsvc.dll | 6.0.6001.22636 | 130,560 | 18-Feb-2010 | 13:58 | x86 |
Cryptsvc.dll | 6.0.6002.22341 | 131,072 | 18-Feb-2010 | 13:41 | x86 |
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File name | File version | File size | Date | Time | Platform |
---|
Cryptsvc.dll | 6.0.6001.22636 | 168,448 | 18-Feb-2010 | 14:24 | x64 |
Cryptsvc.dll | 6.0.6002.22341 | 169,472 | 18-Feb-2010 | 13:42 | x64 |
Cryptsvc.dll | 6.0.6001.22636 | 130,560 | 18-Feb-2010 | 13:58 | x86 |
Cryptsvc.dll | 6.0.6002.22341 | 131,072 | 18-Feb-2010 | 13:41 | x86 |
For all supported IA-64-based versions of Windows Server 2008
File name | File version | File size | Date | Time | Platform |
---|
Cryptsvc.dll | 6.0.6001.22636 | 343,552 | 18-Feb-2010 | 14:58 | IA-64 |
Cryptsvc.dll | 6.0.6002.22341 | 343,552 | 18-Feb-2010 | 13:26 | IA-64 |
Cryptsvc.dll | 6.0.6001.22636 | 130,560 | 18-Feb-2010 | 13:58 | x86 |
Cryptsvc.dll | 6.0.6002.22341 | 131,072 | 18-Feb-2010 | 13:41 | x86 |
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 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
File name | File version | File size | Date | Time | Platform |
---|
Cryptsvc.dll | 6.1.7600.20756 | 136,704 | 16-Jul-2010 | 10:21 | x86 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File name | File version | File size | Date | Time | Platform |
---|
Cryptsvc.dll | 6.1.7600.20756 | 176,640 | 16-Jul-2010 | 10:46 | x64 |
Cryptsvc.dll | 6.1.7600.20756 | 136,704 | 16-Jul-2010 | 10:21 | x86 |
For all supported IA-64-based versions of Windows Server 2008 R2
File name | File version | File size | Date | Time | Platform |
---|
Cryptsvc.dll | 6.1.7600.20756 | 367,616 | 16-Jul-2010 | 09:49 | IA-64 |
Cryptsvc.dll | 6.1.7600.20756 | 136,704 | 16-Jul-2010 | 10:21 | x86 |