Persistent Shares Remain After You Remove Windows Services for UNIX (322675)

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

CAUSE

When you remove Windows Services for UNIX, either of the following actions occur:

Umount.exe starts and then removes network file system (NFS) shares.

-or-
Gwshare.exe starts and then removes NFS Gateway shares

If either Umount.exe or Gwshare.exe are missing or have been deleted, the persistent shares are not removed properly.

WORKAROUND

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this problem, use either of the procedures that are described in this section.

Workaround 1: Client for NFS

Start Registry Editor (Regedt32.exe).
Locate and then click the following registry key:
HKEY_CURRENT_USER\Network\Drive_letter
If the provider name is "NFS," delete the drive.

Workaround 2: Gateway for NFS

Start Registry Editor (Regedt32.exe).
Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Client for NFS\CurrentVersion\Users\SID\Persistent\Drive_letter
Delete any drives that are listed.