When I try to assign a drive letter to a hard disk drive in Windows Server 2003, I receive an error message: "The path cannot be used for creating a drive path"
When you use the Disk Management tool to assign a drive letter to a hard disk drive in Windows Server 2003, you receive the following error message:
The path cannot be used for creating a drive path likely because the folder does not exist or is already a drive path to some other volume.
When this problem occurs, the following Error event is logged in the System log:
Event source: VDS Basic Provider 1.0
Event category: None Event ID: 1 Date: date Time: time Type: Error User: N/A Computer: ServerName Description: Unexpected failure. Error code: 1@01010018
To have us fix this problem for you, go to the "
Fix it for me
" section. If you'd rather fix this problem yourself, go to the "
Let me fix it myself
To fix this problem automatically, click the
Fix this problem
link. Then, click
dialog box and follow the steps in this wizard.
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 so that you can run it on the computer that has the problem.
Now go to the "
Did this fix the problem?
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:
How to back up and restore the registry in Windows
This problem occurs if the Windows disk filter driver entry is missing from the registry. When the entry is missing, the PartMgr filter driver may not start. To resolve this problem, add the UpperFilters entry to the registry, make sure that the PartMgr driver is configured to start when the computer starts, and then restart the computer. To do this, follow these steps:
Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:
On the Edit menu, point to New, and then click Multi-String Value. Type UpperFilters to name the new entry, and then press ENTER. Right-click UpperFilters, and then click Modify. In the Value data box, type PartMgr, and then click OK. Locate and then click the following registry subkey:
In the details pane, examine the value of the Start registry entry. To start PartMgr when the computer starts, this value must be 0x00000000. Exit all programs, and then restart the computer. Note
The following table lists the service startup types that are available in Windows.
Startup type Hexadecimal value Boot 0x00000000 System 0x00000001 Automatic 0x00000002 Manual 0x00000003 Disabled 0x00000004
Typically, device drivers are set to use a startup type of
. Typical Windows services are set to use a startup type of
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
fixit fix it
Article ID: 939320 - Last Review: 09/11/2011 06:40:00 - Revision: 4.0
Applies to Microsoft Windows Server 2003, Standard Edition (32-bit x86) Microsoft Windows Server 2003, Enterprise Edition (32-bit x86) Microsoft Windows Server 2003, Datacenter Edition (32-bit x86) Microsoft Windows Server 2003, Web Edition Microsoft Windows Server 2003, Standard x64 Edition Microsoft Windows Server 2003, Enterprise x64 Edition Microsoft Windows Server 2003, Datacenter x64 Edition Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems Keywords: kbfixme kbmsifixme kbdiskmemory kbregistry kbeventlog kbtshoot kberrmsg kbprb KB939320