Consider the following scenario:
- You have a shared folder on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
- A user (user A) maps a network drive to the shared folder. Therefore, user A can receive change notifications from the shared folder.
- Another user (user B) changes a file in a subfolder or adds a file to a subfolder that user A does not have permission to access. The subfolder is in the shared folder.
- The expected behavior is that user A does not receive change notifications from the subfolder.
- Change notifications are sent when any of the following activities occur:
- A user creates files or folders.
- A user changes existing files or folders.
- A user reads the documents that are temporarily written to the shared folder or automatically saved or locked in the shared folder.
This issue occurs because the SMB protocol cannot modify change notification requests for each user.
Hotfix informationThis hotfix can resolve the issue that is described in this Knowledge Base article only after you remove the "bypass traverse checking" (SeChangeNotifyPrivilege) permission for the user. However, after you remove the permission, the computer may experience some performance issues. You can monitor the system performance before and after you remove the permission to better understand the effect of the performance issues on your computer.
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: 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.
PrerequisitesTo apply this hotfix, you must be running Windows 7 SP1 or Windows Server 2008 R2 SP1.
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 informationTo apply this hotfix, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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