Can't start Disk Management - Unable to connect to Virtual Disk Service

I use Disk Management.  I get the error "Unable to connect to Virtual Disk Service".  The following error is logged:

VDS fails to retrieve class id for provider {A86AE501-EF73-4C8D-827E-98BA5046B05F}. Error code: 2@02000009

<Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">

**-**<System>

****<ProviderName="Virtual Disk Service" />

****<EventID Qualifiers="49664">14</EventID>

****<Level>2</Level>

****<Task>0</Task>

****<Keywords>0x80000000000000</Keywords>

****<TimeCreatedSystemTime="2009-12-01T19:45:09.000Z" />

****<EventRecordID>69136</EventRecordID>

****<Channel>System</Channel>

****<Computer>Holden-PC</Computer>

****<Security/>

****</System>

**-**<EventData>

****<Data>{A86AE501-EF73-4C8D-827E-98BA5046B05F}</Data>

****<Data>2@02000009</Data>

****</EventData>

****</Event>

The VD service is set to start manually.  I can start it but it stops when I use mcc and click on Disk Management.

Vista 32-bit SP2

Solution:

Copy (or move) Clsid from HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\vds\SoftwareProviders{A86AE501-EF73-4C8D-827E-98BA5046B05F} to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\vds\SoftwareProviders{A86AE501-EF73-4C8D-827E-98BA5046B05F}

Start diskmgmt.msc and enjoy!

I have another twist on this problem.  I struggled with this for 5 days and my solution was that VDS.exe was bad even though it passed the system file checker SFC /scannow. 

I noticed that when viewing the associated Modules in the Resource Monitor while VDS.exe was running, and comparing it with a working machine that there was a difference.  "fastprox.dll" was missing from the faulty machine.  I restored "VDS.exe" from my backup copy and everything worked fine.

Why the System file checker did not catch it is a mystery since I ran it several times. Isn't VDS.exe considered a system file?

Win 7 32 bit.

update 06/09/13

This did not cure the problem.  After removing everything connected to my PC, inside and out, I found that disconnecting an internal USB hub that fed my case USB jacks, my problem came clear.  Apparently one of the jacks for SDHC cards had some bent pins thus causing windows to think a disk was there (partially).  The problem was also apparent during POST, whereby the BIOS program would spend a lot of time looking at one USB Hub before going on.

Hi Robert111222333,

Welcome to Microsoft Answers.

Check if the following steps help:

A) Try this:

i. Click start->Type Services.msc  in the search bar and hit Enter

ii. Find Virtual Disk Service and make its startup type as manual. Click on recovery tab and make

Second failure > take no action

Subsequent failure > take no action

B) System File Checker tool scans system files and replaces incorrect versions of the system files by using the correct versions.  Run the System File checker tool To run the System File Checker tool, follow these steps:

  

i) Click Start, and then type cmd in the Start Search box.

ii) Right-click cmd in the Programs list, and then click Run as administrator. If you are prompted for an administrator password or confirmation, type your password or click Continue

iii)  At the command prompt, the following line, and then press ENTER:sfc /scannow

Check the article http://support.microsoft.com/kb/936212   “How to repair the operating system and how to restore the operating system configuration to an earlier point in time in Windows Vista”

Diana

Microsoft Answers Support Engineer

Visit our Microsoft Answers Feedback Forum and let us know what you think.

 

For days I searched for the answer to this one -- THIS fix fixed it!  Virtual Disk Service was disabled.  Turned it to manual, started it, now my backups work and everything seems okay.  Thanks for sharing this!

windows 10 pro reads unable to connect virtual disk service in disk management