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.

When a user logs on to a domain from a Windows Vista-based client computer or from a Windows Server 2008-based client computer, the client computer takes a long time (about 10 minutes) to process the logon script

View products that this article applies to.


Consider the following scenario. In an Active Directory domain environment, you deploy a user logon script to client computers in the domain. The logon script contains calls to Active Directory Service Interfaces (ADSI), such as Lightweight Directory Access Protocol (LDAP) queries. However, every time that a user logs on to the domain from a Windows Vista-based client computer, the client computer takes a long time (about 10 minutes) to process the logon script. During this time, no other ADSI queries can be executed.

This issue occurs if the ADSI call in the logon script involves downloading a schema cache file.

↑ Back to the top


This issue is caused by an error in ADSI. Because of this error, the schema cache files are downloaded every time that the logon script is processed. However, the schema cache files should be downloaded only the first time that the logon script is processed or when the schema changes.

↑ Back to the top


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: 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.


To apply this hotfix, you must have Windows Vista Service Pack 1 (SP1) or Windows Server 2008 installed.

Restart requirement

You must restart 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 SP1 and Windows Server 2008, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Package_1_for_kb952611~31bf3856ad364e35~x86~~ Applicable1,81517-Jun-200818:01Not Applicable
Package_2_for_kb952611~31bf3856ad364e35~x86~~ Applicable1,98217-Jun-200818:01Not Applicable
Package_3_for_kb952611~31bf3856ad364e35~x86~~ Applicable1,82017-Jun-200818:01Not Applicable
Package_4_for_kb952611~31bf3856ad364e35~x86~~ Applicable1,82017-Jun-200818:01Not Applicable
Package_for_kb952611_client_1~31bf3856ad364e35~x86~~ Applicable1,36717-Jun-200818:01Not Applicable
Package_for_kb952611_client~31bf3856ad364e35~x86~~ Applicable1,43117-Jun-200818:01Not Applicable
Package_for_kb952611_sc_0~31bf3856ad364e35~x86~~ Applicable1,42117-Jun-200818:01Not Applicable
Package_for_kb952611_sc~31bf3856ad364e35~x86~~ Applicable1,42317-Jun-200818:01Not Applicable
Package_for_kb952611_server_0~31bf3856ad364e35~x86~~ Applicable1,42517-Jun-200818:01Not Applicable
Package_for_kb952611_server~31bf3856ad364e35~x86~~ Applicable1,43117-Jun-200818:01Not Applicable
Package_for_kb952611_winpesrv_0~31bf3856ad364e35~x86~~ Applicable1,42217-Jun-200818:01Not Applicable
Package_for_kb952611_winpesrv~31bf3856ad364e35~x86~~ Applicable1,42917-Jun-200818:01Not Applicable
Update.mumNot Applicable3,07717-Jun-200818:01Not Applicable
X86_d43262d7360564c9ba9359600e70e9fb_31bf3856ad364e35_6.0.6001.22204_none_b80384513a513063.manifestNot Applicable73517-Jun-200818:01Not Applicable
X86_microsoft-windows-a..terface-ldapc-layer_31bf3856ad364e35_6.0.6001.22204_none_5fc014127f975bc9.manifestNot Applicable9,79817-Jun-200804:10Not Applicable
Windows Vista SP1 and Windows Server 2008, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Amd64_cabc2411d50e0ee4dde658ae1eca2dd3_31bf3856ad364e35_6.0.6001.22204_none_a68cee861ef908e4.manifestNot Applicable1,11817-Jun-200818:01Not Applicable
Amd64_fa4ab17d77f8887b3be502aeef9219ee_31bf3856ad364e35_6.0.6001.22204_none_8f1f8f58f57490d0.manifestNot Applicable73917-Jun-200818:01Not Applicable
Amd64_microsoft-windows-a..terface-ldapc-layer_31bf3856ad364e35_6.0.6001.22204_none_bbdeaf9637f4ccff.manifestNot Applicable10,13417-Jun-200806:32Not Applicable
Package_1_for_kb952611~31bf3856ad364e35~amd64~~ Applicable1,82517-Jun-200818:01Not Applicable
Package_2_for_kb952611~31bf3856ad364e35~amd64~~ Applicable2,24717-Jun-200818:01Not Applicable
Package_3_for_kb952611~31bf3856ad364e35~amd64~~ Applicable2,08317-Jun-200818:01Not Applicable
Package_4_for_kb952611~31bf3856ad364e35~amd64~~ Applicable2,08317-Jun-200818:01Not Applicable
Package_for_kb952611_client_1~31bf3856ad364e35~amd64~~ Applicable1,37517-Jun-200818:01Not Applicable
Package_for_kb952611_client~31bf3856ad364e35~amd64~~ Applicable1,43917-Jun-200818:01Not Applicable
Package_for_kb952611_sc_0~31bf3856ad364e35~amd64~~ Applicable1,42917-Jun-200818:01Not Applicable
Package_for_kb952611_sc~31bf3856ad364e35~amd64~~ Applicable1,43117-Jun-200818:01Not Applicable
Package_for_kb952611_server_0~31bf3856ad364e35~amd64~~ Applicable1,43317-Jun-200818:01Not Applicable
Package_for_kb952611_server~31bf3856ad364e35~amd64~~ Applicable1,43917-Jun-200818:01Not Applicable
Package_for_kb952611_winpesrv_0~31bf3856ad364e35~amd64~~ Applicable1,43017-Jun-200818:01Not Applicable
Package_for_kb952611_winpesrv~31bf3856ad364e35~amd64~~ Applicable1,43717-Jun-200818:01Not Applicable
Update.mumNot Applicable3,09917-Jun-200818:01Not Applicable

↑ Back to the top


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 the schema cache, visit the following Microsoft Web site:For more information about ADSI, visit the following Microsoft Web site: For more information, 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

↑ Back to the top

Keywords: kbautohotfix, kbexpertiseadvanced, kbfix, kbqfe, KB952611

↑ Back to the top

Article Info
Article ID : 952611
Revision : 2
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 357