Error message in Windows Vista when you try to rename a new subfolder in a shared folder on a network: "The <SharedFolderName> folder does not exist"

Assume that on a Windows Vista-based computer, you create a subfolder in a shared folder on a network. Then, you try to rename the new subfolder. In this scenario, you receive the following error message:Note This error message incorrectly states that the shared folder does not exist.

Additionally, if you save a file to a shared folder on a network, you may receive the following error message:

To work around this issue, a registry entry must be changed. To have us make this change for you, go to the "Fix it for me" section. If you would rather do this yourself, go to the "Let me fix it myself" section.

Fix it for me

To make this change to the registry automatically, click the Fix this problem link. Then, click Run in the File Download dialog box, and follow the steps in this wizard.

Fix this problem

Note

• This wizard is temporarily 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: To work around this issue yourself, add the FormatDatabase registry entry to the following registry subkey: Then, set the FormatDatabase registry entry to 1.

To do this, follow these steps:

1. Click Start
   Collapse this imageExpand this image

   
   , type regedit in the Start Search box, and then click regedit in the Programs list.
   
   
   Collapse this imageExpand this image

   
   If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Csc\Parameters
   Note If the Parameters subkey does not exist, create it. To do this, follow these steps:
   1. Click the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Csc
   2. On the Edit menu, point to New, and then click Key.
   3. Type Parameters, and then press ENTER.
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type FormatDatabase, and then press ENTER.
5. On the Edit menu, click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor, and then restart the computer.

Did this fix the problem?

• Check whether the problem is fixed. If it is fixed, you are finished with this article. If it is not fixed, you can contact support (http://support.microsoft.com/contactus) .
• 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 (http://blogs.technet.com/fixit4me/) , or send us an e-mail (mailto:fixit4me@microsoft.com?Subject=KB934160 - Format Offline Files database) message.

Scenarios in which to apply the workaround

Apply this workaround in scenarios that resemble the following:

• For an image that you are currently deploying, apply this workaround in a custom action in the state restore phase. This procedure requires you to restart the computer.
• For an image that you have already deployed, apply this workaround. This procedure requires you to restart the computer.
• For a new image, apply this workaround, and then restart the computer. Create the image after you restart the computer and before you configure network connections.
• You can also apply this workaround to the registry of a Microsoft Windows Imaging Format (WIM) image file. To do this, use the ImageX.exe tool that is included in the Windows Automated Installation Kit (AIK). For more information about Windows AIK, visit the following Microsoft Web site:
  http://technet2.microsoft.com/WindowsVista/en/library/129a1712-e3d8-46c1-bc09-a14349dc67db1033.mspx?mfr=true (http://technet2.microsoft.com/WindowsVista/en/library/129a1712-e3d8-46c1-bc09-a14349dc67db1033.mspx?mfr=true)
  For more information about the ImageX.exe tool and about the WIM image format in Windows Vista, visit the following Microsoft Web site:
  http://technet.microsoft.com/en-us/windowsvista/aa905070.aspx (http://technet.microsoft.com/en-us/windowsvista/aa905070.aspx)
  One possible advantage of using this procedure is that you do not have to create a new image. Additionally, you do not have to restart the computer.

This issue occurs if the following conditions are true:

• Windows Vista was deployed to the computer from an image by using the Microsoft Systems Management Server (SMS) 2003 Operating System Deployment (OSD) Feature Pack Update.
• The client-side cache database that the Offline Files feature uses was corrupted when Windows Vista was deployed.

For more information about the SMS 2003 OSD Feature Pack Update, visit the following Microsoft Web site: