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.
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.
Prerequisites
To apply this hotfix on Windows Vista-based computer, you must have Windows Vista Service Pack 1 (SP1) installed.
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 MANIFEST files (.manifest) and the 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 Windows Vista
File name | File version | File size | Date | Time | Platform |
---|
Credui.dll | 6.0.6001.22368 | 178,176 | 04-Feb-2009 | 05:28 | x86 |
For all supported x64-based versions of Windows Server 2008 and Windows Vista
File name | File version | File size | Date | Time | Platform |
---|
Credui.dll | 6.0.6001.22368 | 190,976 | 04-Feb-2009 | 06:04 | x64 |
For all supported IA-64-based versions of Windows Server 2008
File name | File version | File size | Date | Time | Platform |
---|
Credui.dll | 6.0.6001.22368 | 328,192 | 04-Feb-2009 | 04:41 | IA-64 |
After you have applied the hotfix, you must add the server name of the DAV server, together with the associated certificate, to Credential Manager. To do this, follow these steps:
- Start Credential Manager. To do this, click Start, click Run, type control keymgr.dll, and then click OK.
- In the Stored User Names and Passwords dialog box, click Add.
- In the Log on to box, type the DAV server name.
Note The server name should match the syntax of the name in the user certificate. For example, the server name should be "SERVERNAME" or "SERVERNAME.company.com." - In the User name box, select the user certificate that has a client authentication extended key usage (EKU) that lets you connect to the DAV server.
- Keep the default setting for the Credential type check box.
- Click OK, and then click Close.