Disk Management could not start Virtual Disk Service (VDS) error occurs when users are trying to partition or rename drivers on their Windows computers. The same error message has a variation which is ‘Unable to connect to Virtual Disk Service’. There are a number of reasons why you get this error but the common cause is Firewall or your security programs blocking and interfering with the connection between the remote computer and Virtual Disk Service.
In this article, we will look at other causes of the Disk Management could not start Virtual Disk Service error and different ways to resolve it. The error blocks users from accessing and using Disk Management. Below is the exact error message that the users get:
Disk Management could not start Virtual Disk Service (VDS) on SRV2. This can happen if the remote computer does not support VDS, or if a connection cannot be established because it was blocked by Windows Firewall.
For additional information about diagnosing and correcting this problem, see Troubleshooting Disk Management in Disk Management Help.
What causes the Disk Management could not start Virtual Disk Service error?
The causes of the Disk management error can include several issues. As we said earlier, the common cause is firewall and antivirus software blocking the connection. However, there are other possible reasons that could trigger this error. They include the following:
- Temporary technical hitch: Sometimes, a bug or a glitch can affect the connection between the computer and VDS. This is a temporary issue and can be fixed by performing several preliminary steps such as restarting your computer and disconnecting the hard drives.
- Corrupted system files: If there are corrupted files in your computer, especially those Disk Management and VDS depend on, there will be faulty connections between the two components leading to the error. Fixing these files should be the priority.
- Virtual Disk Service stopped running: Disk Management relies on the VDS to facilitate the partitioning or renaming of hard disks in your computer. If the service is not running, there will be no communication and hence you get the error.
- Hardware problems: Last but not least, if there are hardware issues like faulty connecting cables, damaged ports, CPU issues, etc., the Disk Management might have an issue connecting to the service triggering the error.
Having looked at the possible reasons why the Disk Management could not start Virtual Disk Service error occurs, we can now look at different ways to resolve them. Let us now get started.
How Do I Fix Disk Management Could Not Start Virtual Disk Service Error?
If your Disk Management is not connecting to the Virtual Disk Service on your Windows PC, disconnect cables and hard drive, and then restart your computer. This should fix any temporary technical issues that are resolved by restarting the PC and resetting the connection. If these preliminary steps don’t work for you, then you can try the following solutions:
- Run SFC and DISM scan. To repair and check the integrity of your system files, you need to run the System File Checker (SFC) and Deployment Image Servicing and Management (DISM) command line tools. These tools automatically find, scan, and repair any files that are broken, missing, or corrupted. Run these tools and see if you will fix the Disk Management issue.
- Disable Microsoft Defender Temporarily. As the error message indicates, firewall issues could be the first culprit. You need to turn off Windows Defender temporarily. Note that Windows Defender is an important tool for your PC and you should turn it on immediately after you are through with this solution.
- Manually enable and run Virtual Disk Service. Enabling the Virtual Disk Service in the Services console, ensure that the connection is established between the service and Disk Management. The services may have stopped after an issue or a user stopped or disabled it knowingly or unknowingly. So check it and if it’s not running, enable and run it.
- Allow Remote Volume Management in Windows Firewall. Windows Firewall can block the connection between Disk Management and Virtual Disk. To fix this, you need to allow Remote Volume Management for both remote computers and local ones. The procedure is straightforward and we will loot that shortly.
- Disable other third-party security programs. Some third-party antivirus software can interfere with either Disk Management or Virtual Disk Service. If that is the case, disabling them temporarily will be the best option to resolve the issue.
1. Run SFC and DISM scan
- Press the Windows button + R, type cmd in the Run dialog box, and press Ctrl + Shift + Enter to open Command Prompt as an administrator.
- Run the following command line to initiate the SFC scan:
- After that, copy the following command line and press Enter after each to run the DISM scan:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
2. Disable Microsoft Defender Temporarily
- Search Windows Security in the search box and click it in the results list.
- Choose Virus & threat protection when Windows Security opens.
- Locate and click Manage settings.
- Toggle off the button next to Real-time protections.
NOTE: After you are done with this method, turn on Windows Defender to continue enjoying security against malicious attacks.
3. Manually enable and run Virtual Disk Service
- Press the Windows button + R, type services.msc in the Run dialog box, and press Enter to open the Services app.
- Look for Virtual Disk towards the end of the Services window and double-click it.
- Click the drop-down menu next to Startup type and select Automatic.
- Click Start under the Service status and then go to the Log on tab at the top,
- Tick the box next to Allow service to interact with desktop.
- Finally, click Apply and then OK to save the changes.
4. Allow Remote Volume Management in Windows Firewall
- Search Windows Defender Firewall in the Windows search box and open it.
- On the left side, click Allow an app or feature through Windows Defender Firewall and then select Change settings.
- Now, scroll down on the Allowed apps and features section and locate Remote Volume Management; tick the box next to it.
- Finally, select OK to save the changes.
We hope one of the solutions will help you fix Disk Management could not start Virtual Disk Service (VDS) error. If that is not the case, you may contact the Windows support team through the Help app or through official support pages online. Some issues are specific to certain devices and need personalized support. Alternatively, you can leave a message in the comment box below and one of our experts will get back to you.
Disk Management could not start Virtual Disk Service (VDS) error - FAQs
The Disk Management cannot open if there is no complete connection between VDS and Disk Management in a remote or local computer. It may also fail to open if the remote computer does not support Virtual Disk Service. Other possible reasons are Firewall blocking connection between the two components or VDS not running and needing to be enabled.
To fix stuck on Virtual Disk Services, run the SFC scan or temporarily disable Windows Defender or any other third-party antivirus software. Also, manually enable and run Virtual Disk Service in the Services app. If nothing works, allow Remote Volume Management in the Windows Defender settings. We have given more details on how to conduct these steps in this article.