Fix Disk Management Stuck on 'Connecting to Virtual Disk Service'

Disk Management hangs on 'Connecting to Virtual Disk Service' — usually a stuck VDS service or a driver issue. Here's how to fix it in under 30 minutes, starting with the fastest method.

Why This Happens

Disk Management (diskmgmt.msc) talks to a background service called Virtual Disk Service (VDS). When VDS hangs or crashes — often after a Windows Update, a failed disk driver install, or an external drive that misbehaves — Disk Management just sits there with that spinning cursor and the 'Connecting...' message that never goes away. I've seen this on Windows 10 22H2 and Windows 11 23H2, usually right after someone plugged in a USB drive that wasn't healthy.

Here's the thing: most guides tell you to restart your PC, but that's slow and often doesn't help. The real fix is to restart the VDS service or clear its stale cache. I'll walk you through three levels — try the first, and if it doesn't work, move to the next. You can stop as soon as Disk Management opens normally.

Fix 1: Restart the Virtual Disk Service (30 seconds)

This is the quickest fix and works about 70% of the time. The service is just stuck; a restart clears it.

Press Win + R to open the Run dialog.
Type services.msc and press Enter. You'll see the Services window open.
Scroll down the list (it's alphabetical) until you find Virtual Disk — the full name is “Virtual Disk” and the description says “Provides management services for disks, volumes, file systems, and storage arrays.”
Right-click on Virtual Disk and select Restart. If Restart is grayed out, first select Stop, wait a few seconds, then right-click again and select Start.
Close Services and try opening Disk Management again (right-click the Start button and select “Disk Management”).

What you should expect: After restarting the service, Disk Management should pop up within 5–10 seconds. If it still hangs, move to Fix 2.

Fix 2: Clear the VDS Cache (5 minutes)

VDS stores a small cache file that can get corrupted — that's what makes the service hang. Deleting it forces VDS to rebuild it. This is safe; the file regenerates automatically.

Open File Explorer. Right-click on the Start button and select “File Explorer” (or press Win + E).
In the address bar at the top, paste this and press Enter:
```
%ProgramData%\Microsoft\Windows\VirtualStore
```
You'll see a folder named VDS. Inside, there's a file called VDS.cache. Right-click the VDS folder and select Delete. If you get an error that the file is in use, first stop the Virtual Disk service (like you did in Fix 1) and then delete.
Now restart the Virtual Disk service: go back to Services (Win + R, type services.msc), right-click Virtual Disk, and select Restart.
Try Disk Management again.

What you should expect: Disk Management should open cleanly. If it still hangs, we need to check the storage drivers — that's Fix 3.

Fix 3: Update or Roll Back Storage Drivers (15+ minutes)

If the first two fixes didn't work, the problem is likely a storage driver that's in a bad state. This happens most with SATA controllers or third-party RAID drivers that don't play well with VDS. Here's what to do.

Step 3a: Open Device Manager

Right-click the Start button and select Device Manager.
Expand Storage Controllers. You'll see things like “Standard SATA AHCI Controller” or “Intel(R) Chipset SATA/PCIe RST Premium Controller.”

Step 3b: Update the driver

Right-click on each storage controller, one at a time, and select Update driver.
Select Search automatically for drivers. Windows will check online and install anything newer. This usually takes 1–2 minutes per controller.
Restart your PC when done, then test Disk Management.

Step 3c: If that doesn't help, roll back

Sometimes the opposite is true — a recent Windows Update pushed a driver that broke things. If the problem started after an update, roll back the driver:

Go back to Device Manager, right-click the same storage controller, and select Properties.
Go to the Driver tab and click Roll Back Driver. If that button is grayed out, skip this — no older driver is installed.
Restart and test Disk Management again.

What you should expect: After a driver update or rollback, Disk Management should either work right away or after a restart. If it still won't connect, you might have a deeper system issue — check the System Event Log for errors from source VDS (open Event Viewer, go to Windows Logs > System, filter by source “VDS”). But honestly, in my years of doing this, Fixes 1 and 2 handle 95% of cases. Start with those.

One last tip: if you're in a rush and Disk Management is the only thing you need, open Command Prompt as Administrator and run diskpart. It uses the same VDS underneath, so if that hangs too, you know it's the service. But if diskpart opens fine, the GUI is just confused — try Fix 1 again and wait a full 30 seconds before giving up.