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.

Error message when you try to access a mapped drive that is mapped to a Windows XP-based computer from a Windows Vista-based computer: "System error 5 has occurred"


View products that this article applies to.

Problem description

Consider the following scenario. You map a drive to a Windows XP-based computer from a Windows Vista-based computer. When you try to access the mapped drive from the Windows XP-based computer, you receive the following error message:
System error 5 has occurred.
Access is denied.
This problem occurs if the following conditions are true:
  • Both computers are members of a workgroup.
  • You do not give the Full Control shared permission to the Everyone group.
  • You give the Full Control shared permission to the Administrators group.
Note This access failure occurs regardless of the NTFS file system permissions that are assigned to the mapped drive.

This article helps you work around this problem.

↑ Back to the top


Workaround

To work around this problem, change the value of the LocalAccountTokenFilterPolicy registry entry on the Windows Vista-based computer so that full credentials can be passed between Windows Vista and Windows XP.

To have us change the registry for you, go to the “Fix it for me” section. If you would rather change the registry yourself, go to the “Let me fix it myself” section.

Fix it for me

To work around this problem automatically, click the Fix this problem link. Then, click Run in the File Download dialog box, and follow the steps in this wizard.





Notes
  • 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, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.
Now go to the "Did this fix the problem?" section.

Let me fix it myself

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. Click Start, type
    regedit in the Start Search box, and then click regedit.exe in the Programs list.


    If you are prompted for an administrator password, type your password. Or, if you are prompted for confirmation, click Continue.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
    1. On the Edit menu, point to
      New, and then click DWORD Value.
    2. Type
      LocalAccountTokenFilterPolicy, and then press ENTER.
  4. Right-click LocalAccountTokenFilterPolicy, and then click Modify.
  5. In the Value data box, type
    1, and then click OK.
  6. Exit Registry Editor.
Now go to the "Did this fix the problem?" section.

Did this fix the problem?

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

↑ Back to the top


More information

The LocalAccountTokenFilterPolicy registry entry in the registry can have a value of 0 or of 1. These values change the behavior of the registry entry as follows.
ValueDescription
0This value builds a filtered token. This is the default value. The administrator credentials are removed.
1This value builds an elevated token.

↑ Back to the top


Cause

This problem occurs because User Account Control (UAC) in Windows Vista does not automatically grant administrative rights to local users. This behavior occurs even though the local users are members of the Administrators group.

↑ Back to the top


Keywords: kb, kbfixme, kbmsifixme, kbexpertiseinter, kbtshoot, kbprb

↑ Back to the top

Article Info
Article ID : 947235
Revision : 3
Created on : 4/17/2018
Published on : 4/18/2018
Exists online : False
Views : 250