Symptoms

Consider the following scenario:

  • You create a folder that contains many subfolders on a file server that is running one of the following operating systems:

    • Windows Vista

    • Windows Server 2008

    • Windows 7

    • Windows Server 2008 R2

  • You share the folder.

  • You enabled Access-based Enumeration (ABE) on the shared folder.

In this scenario, you experience high CPU usage on the file server. Additionally, users who try to browse the shared folder encounter delays.

Cause

This issue occurs because there are many access check requests when ABE enumerates a folder that contains many subfolders.

Resolution

Hotfix information

Important This hotfix has been re-released to address an issue in which the digital signature on files produced and signed by Microsoft will expire prematurely, as described in Microsoft Security Advisory 2749655.

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

http://support.microsoft.com/contactus/?ws=supportNote 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, you must be running one of the following operating systems:

  • Windows Vista Service Pack 2 (SP2)

  • Windows Server 2008 Service Pack 2 (SP2)

  • Windows 7 Service Pack 1 (SP1)

  • Windows Server 2008 R2 Service Pack 1 (SP1)

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

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

After the hotfix is installed, you must create a new registry entry. To have us create the registry entry for you, go to the "Fix it for me" section. If you prefer to create the registry entry yourself, go to the "Let me fix it myself" section.

Fix it for me



To create the registry entry automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.




Notes

  • When you follow the Fix it wizard, you need enter a ABELevel value. The ABELevel value specifies the maximum level of the folders on which the ABE feature is enabled.

  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.

  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.


Then, go to the "Did this fix the problem?" section.



To create the new registry entry , follow these steps:

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

  1. Open Registry Editor. To do this, click Start, type regedit in the Start Search box, and then press Enter.

  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\

  3. On the Edit menu, point to New, and then click DWORD (32 bit) Value.

  4. Type ABELevel, and then press Enter.

  5. On the Edit menu, click Modify.

  6. In the Value data box, type a number according to the level that ABE is enabled on the shared folder, and then click OK.

  7. Exit Registry Editor.

Note The ABELevel value specifies the maximum level of the folders on which the ABE feature is enabled. For example if you enable ABE on \\Server\share, you must set the ABELevel value to 1. If you enable ABE on \\Server\share\share, you must set the ABELevel value to 2. If the ABELevel value is not set or has value of 0 , then this hotfix is not enabled.

The value of the above mentioned key is set as follows:
Value = 0 : ABE is enabled for all levels (default behavior without key as well)
Value = 1 : ABE enabled for depth of 1 (\server\share)
Value = 2: ABE enabled for depth of 2 (\server\share\folder)
And so on for multiple levels.




Did this fix the problem?

  • Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.

  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email.


Restart requirementYou must restart the computer after you apply this hotfix.

Hotfix replacement informationThis hotfix does not replace a previously released hotfix.

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 notesImportant 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
    2.
    23xxx

    Windows Vista and Windows Server 2008

    SP2

    LDR

  • 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 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 Server 2008 and of Windows Vista

File name

File version

File size

Date

Time

Platform

Srvnet.sys

6.0.6002.23075

102,912

08-Mar-2013

01:16

x86

Srv2.sys

6.0.6002.23075

148,480

08-Mar-2013

01:16

x86

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

File name

File version

File size

Date

Time

Platform

Srvnet.sys

6.0.6002.23075

146,432

08-Mar-2013

01:56

x64

Srv2.sys

6.0.6002.23075

178,176

08-Mar-2013

01:56

x64

For all supported IA-64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Srvnet.sys

6.0.6002.23075

294,912

08-Mar-2013

00:53

IA-64

Srv2.sys

6.0.6002.23075

474,624

08-Mar-2013

00:53

IA-64

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

    Version

    Product

    Milestone

    Service branch

    6.1.760
    1.22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • 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 7 and for Windows Server 2008 R2" section. 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, 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

Srv2.sys

6.1.7601.22055

312,832

13-Jul-2012

07:32

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

Srv2.sys

6.1.7601.22055

408,064

13-Jul-2012

07:55

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Srv2.sys

6.1.7601.22055

795,136

13-Jul-2012

07:25

IA-64


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, 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

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008

File name

Update.mum

File version

Not Applicable

File size

2,412

Date (UTC)

08-Mar-2013

Time (UTC)

08:53

Platform

Not Applicable

File name

X86_6df2524a855db25db8debd1a3c61fbdd_31bf3856ad364e35_6.0.6002.23075_none_f0b063736186f369.manifest

File version

Not Applicable

File size

1,048

Date (UTC)

08-Mar-2013

Time (UTC)

08:53

Platform

Not Applicable

File name

X86_microsoft-windows-smbserver-common_31bf3856ad364e35_6.0.6002.23075_none_05ff7be9269f61de.manifest

File version

Not Applicable

File size

4,227

Date (UTC)

08-Mar-2013

Time (UTC)

04:00

Platform

Not Applicable

File name

X86_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.0.6002.23075_none_dc15e7240cf3feed.manifest

File version

Not Applicable

File size

4,426

Date (UTC)

08-Mar-2013

Time (UTC)

03:57

Platform

Not Applicable

Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008

File name

Amd64_8b11ed075b0befcdc4550779950d2123_31bf3856ad364e35_6.0.6002.23075_none_5ab58f521e40bc57.manifest

File version

Not Applicable

File size

1,054

Date (UTC)

08-Mar-2013

Time (UTC)

08:53

Platform

Not Applicable

File name

Amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.0.6002.23075_none_621e176cdefcd314.manifest

File version

Not Applicable

File size

4,493

Date (UTC)

08-Mar-2013

Time (UTC)

04:12

Platform

Not Applicable

File name

Amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.0.6002.23075_none_383482a7c5517023.manifest

File version

Not Applicable

File size

4,688

Date (UTC)

08-Mar-2013

Time (UTC)

04:07

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

2,430

Date (UTC)

08-Mar-2013

Time (UTC)

08:53

Platform

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008

File name

Ia64_b3890cea3a7e9c29ba0cc20141acdb57_31bf3856ad364e35_6.0.6002.23075_none_4b574d121928e337.manifest

File version

Not Applicable

File size

1,051

Date (UTC)

08-Mar-2013

Time (UTC)

08:53

Platform

Not Applicable

File name

Ia64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.0.6002.23075_none_06011fdf269d6ada.manifest

File version

Not Applicable

File size

4,488

Date (UTC)

08-Mar-2013

Time (UTC)

02:28

Platform

Not Applicable

File name

Ia64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.0.6002.23075_none_dc178b1a0cf207e9.manifest

File version

Not Applicable

File size

4,683

Date (UTC)

08-Mar-2013

Time (UTC)

02:25

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

2,255

Date (UTC)

08-Mar-2013

Time (UTC)

08:53

Platform

Not Applicable

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name

Update.mum

File version

Not Applicable

File size

1,643

Date (UTC)

17-Sep-2012

Time (UTC)

14:21

Platform

Not Applicable

File name

X86_e72bc273f644e60d54fcdca202bc65e9_31bf3856ad364e35_6.1.7601.22055_none_63b615ddfbb7e26c.manifest

File version

Not Applicable

File size

700

Date (UTC)

17-Sep-2012

Time (UTC)

14:21

Platform

Not Applicable

File name

X86_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7601.22055_none_dc533e936dfb206d.manifest

File version

Not Applicable

File size

2,655

Date (UTC)

13-Jul-2012

Time (UTC)

10:00

Platform

Not Applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_5b544784de2c15a7653245d1dcffeb10_31bf3856ad364e35_6.1.7601.22055_none_575d12729f381228.manifest

File version

Not Applicable

File size

704

Date (UTC)

17-Sep-2012

Time (UTC)

14:21

Platform

Not Applicable

File name

Amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7601.22055_none_3871da17265891a3.manifest

File version

Not Applicable

File size

2,657

Date (UTC)

13-Jul-2012

Time (UTC)

11:00

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

1,853

Date (UTC)

17-Sep-2012

Time (UTC)

14:21

Platform

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_854dfe5defc20e72c0d97628b3643e98_31bf3856ad364e35_6.1.7601.22055_none_36fe35d9345f6cf4.manifest

File version

Not Applicable

File size

702

Date (UTC)

17-Sep-2012

Time (UTC)

14:21

Platform

Not Applicable

File name

Ia64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7601.22055_none_dc54e2896df92969.manifest

File version

Not Applicable

File size

2,656

Date (UTC)

13-Jul-2012

Time (UTC)

11:00

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

1,447

Date (UTC)

17-Sep-2012

Time (UTC)

14:21

Platform

Not Applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×