On a Windows Server 2003-based computer, after you use the Diskpart command, the Disk Management utility does not respond

On a Windows Server 2003-based computer, after you use the Diskpart command at a command prompt, the Disk Management utility does not respond.

Also, the following event is recorded in the event log:

Event Type: Error
Event Source: VDS Dynamic Provider 1.0
Event category: N/A
Event ID : 1
Date : Date
Time : Time
User : N/A
Computer : Computer name
Description : Provider has not been loaded. Error (8004241B)

This problem occurs because the Logical Disk Manager Administrative Service cannot resolve a communication thread. The Logical Disk Manager Administrative Service is deadlocked.

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

This problem was first corrected in Windows Server 2003 Service Pack 2.

Steps to reproduce the problem

1. Log on to a Windows Server 2003-based computer.
2. Type the following script in Notepad, and then save the script as a .cmd file:
   %systemroot%\system32\sc config vds start= auto
   %systemroot%\system32\sc start vds
   echo select disk 0 > createvol.txt
   echo create partition Primary size=800 >>createvol.txt
   echo assign letter=i >>createvol.txt
   diskpart /s createvol.txt
3. Run the script that you created in step 2 at a command prompt.
4. Click Start, click Run, type diskmgmt.msc, and then click Ok.
   
   The Disk Management utility does not respond.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: