New
#1
Unable to connect to Virtual Disk Service
Hello
For some months I have had a problem on my Windows 10 Pro (1607) desktop where I cannot use "Create and format hard disk partitions" Start Menu item, diskpart on elevated and non-elevated command prompt nor Disk Management(Local) snap-in in mmc.
Diskpart gives me "DiskPart encountered an error starting the COM services" and the other two give me the usual popup "Virtual Disk Management could not start the Virtual Disk Service (VDS) on ..." - the service is actually running.
I have tried all the suggested service startup and disable options concerning the "Remote Access Connection Manager", "Remote Access Auto Connection Manager" and "Virtual Disk Service" .
I have played around with windows firewall. I detached all non-essential hard drives and SATA cables. I even disabled USB controllers (took me 3 days to find a PS/2 adaptor for keyboard). Disabled or removed anything witch could cause an external short on possible storage devices (i.e all case USB headers).
Uninstalled all software which could somehow interact with storage on lower levels (Etcher, SDFormatter, DaemonTools, Image burning software).
I tried to follow the solution at Unable to Connect to Virtual Disk Service. but the VDS.log was never created in system32, nor anything appeared into event viewer.
I took three procmon captures: One with the Start Menu item, one with mmc snap-in and the final with elevated command prompt and diskpart. My untrained eye can't find anything irregular in them, tho I can say that at least the start menu item processes are a bit different compared to my 1709 laptop (virtual disk loader vs virtual disk service).
One observation I made is that no matter what of the three options I use, virtual disk management service is never triggered.
I have tried both "sfc /scannow" and "chkdsk c:" to check for corruption but no dice. Also I have updated all drivers I can find for this old motherboard (mainly intel chipset)
At this point my only solution is to try a clean install, which will be a true headache. I did a test install on a fresh SSD with 1709 and on the clean system the disk management interface works as intended.
I did manage without the feature and used alternative products (for example EeasUS Partition Master works), but looks like I can't upgrade windows 10 to 1709 without getting the VDS working properly. Windows 10 upgrade gives me error code 80070032 and in the C:\$WINDOWS.~BT\Sources\Panther\setuperr.log I can see:
Code:2018-01-27 01:27:30, Error WMI Helper Library: Getting WMI Uint16 property DriveLetter: unexpected VARIANT type 1 2018-01-27 01:27:30, Error Failed to read MSFT_Volume.DriveLetter, although the property exists; unexpected type? (0x8007070c) 2018-01-27 01:27:30, Error SP CSetupPlatform::Initialize: Disk provisioning is not available; hr = 0x80070032 2018-01-27 01:27:30, Error MOUPG CAutomationManager::Initialize(120): Result = 0x80070032 2018-01-27 01:27:30, Error MOUPG SetupHost: Automation initialization failed: [0x80070032]
I might have made a wrong conclusion that VDS problem and windows 10 upgrade problem are connected but that is all I have to go on.
procmon capture links: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
I have posted this also to reddit and technet, but those post haven't given me anything useful or promising to try.
Thank you all in advance! All solutions and ideas are welcome.