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.

100 percent CPU usage occurs when the EnableLinkedConnections value is enabled in Windows 8 or Windows Server 2012


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You log on as an administrator on a computer that is running Windows 8 or Windows Server 2012.
  • You add the following value in the registry:

    Registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
    DWORD name: EnableLinkedConnections
    DWORD Value: 1

  • You add a user account (user A) as a member of the administrators group.
  • You give the user account a roaming user profile that targets a Windows 8 or Windows Server 2012 share.
  • You configure a user logon script that maps a network drive to the user's roaming profile path.
  • You log on to the computer as user A.
  • You open the mapped drive that specifies the user's roaming profile as the target folder, and then you open random files in the folder.

In this scenario, the computer exhibits 100 percent CPU usage. Additionally, the computer may stop responding (hang) for up to 15 minutes.

↑ Back to the top


Resolution

This hotfix is also available at Microsoft Update Catalog.

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, go to the following Microsoft website: 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, you must be running Windows 8 or Windows Server 2012.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information
The English (United States) 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 8 and Windows Server 2012 file information notes

Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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 8" 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.

    VersionProductMilestoneService branch
    6.2.920 0.20xxxWindows 8 and Windows Server 2012RTMLDR
  • 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 8 and Windows Server 2012" 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 8
File nameFile versionFile sizeDateTimePlatform
Rdbss.sys6.2.9200.20793321,0249-Aug-134:01x86
Mrxsmb20.sys6.2.9200.20793168,4489-Aug-134:01x86
For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Rdbss.sys6.2.9200.20793423,9369-Aug-136:56x64
Mrxsmb20.sys6.2.9200.20793214,0169-Aug-136:56x64

↑ Back to the top


Workaround

To temporarily work around this problem, or to verify that you are experiencing this problem, specify the following value in the registry:

Registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters
DWORD name: DirectoryCacheLifetime
DWORD Value: 0


Note Remember to reset this value to 1 after you are finished with this workaround. Failure to re-enable the cache can have a significant effect on client performance and show an increase in the number of metadata requests that are sent to the server.

↑ Back to the top


Status

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

↑ Back to the top


Additional file information

Additional file information for Windows 8 and for Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File nameX86_39896f9697e9607976f76b52d9bc02e0_31bf3856ad364e35_6.2.9200.20793_none_3f72dd00b9e906b5.manifest
File versionNot Applicable
File size701
Date (UTC)09-Aug-2013
Time (UTC)15:11
PlatformNot Applicable
File nameX86_85408ac086f1f0fa7bc00c641875d53a_31bf3856ad364e35_6.2.9200.20793_none_153084fb133b7ba1.manifest
File versionNot Applicable
File size693
Date (UTC)09-Aug-2013
Time (UTC)15:11
PlatformNot Applicable
File nameX86_microsoft-windows-rdbss_31bf3856ad364e35_6.2.9200.20793_none_56fdb5f44bf6ce2e.manifest
File versionNot Applicable
File size22,921
Date (UTC)09-Aug-2013
Time (UTC)05:50
PlatformNot Applicable
File nameX86_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.2.9200.20793_none_8803d3c374533f90.manifest
File versionNot Applicable
File size4,096
Date (UTC)09-Aug-2013
Time (UTC)05:50
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameAmd64_2620194121592b47d4fc019b49c4f919_31bf3856ad364e35_6.2.9200.20793_none_ce1e0383602aab88.manifest
File versionNot Applicable
File size705
Date (UTC)09-Aug-2013
Time (UTC)14:52
PlatformNot Applicable
File nameAmd64_a4f81aaf37f2a43dc8f32261a5caafa2_31bf3856ad364e35_6.2.9200.20793_none_ee8273989dfd6874.manifest
File versionNot Applicable
File size697
Date (UTC)09-Aug-2013
Time (UTC)14:52
PlatformNot Applicable
File nameAmd64_microsoft-windows-rdbss_31bf3856ad364e35_6.2.9200.20793_none_b31c517804543f64.manifest
File versionNot Applicable
File size22,927
Date (UTC)09-Aug-2013
Time (UTC)09:09
PlatformNot Applicable
File nameAmd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.2.9200.20793_none_e4226f472cb0b0c6.manifest
File versionNot Applicable
File size4,100
Date (UTC)09-Aug-2013
Time (UTC)09:10
PlatformNot Applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 2878605
Revision : 1
Created on : 1/7/2017
Published on : 10/24/2013
Exists online : False
Views : 198