![]() ![]() When you try to initialize hard drive via Disk Management and receive error message such as “This request cannot be completed because of an I/O device error” or “The device is not ready”, the usual cause is that there is something wrong with the hard drives connection cable. After you have scanned your drive and removed the viruses, you should be able to initialize it. In this case, we recommend that you run anti-virus software such as Windows Defender or Emsisoft Anti-Malware to scan your hard drive and protect your computer against viruses. If you have connected your hard drive to a compromised computer and it now shows up as disk unknown and can’t be initialized in Disk Management, then it may have been infected with a virus. Solution 1: Run professional anti-virus software Now that we know some of the possible causes of the error, we can use some of the below measures to fix the issue. ![]() ▪ Connection problem 5 solutions to the “unable to initialize disk” issue ▪ Inappropriate CMOS (complementary metal-oxide-semiconductor) setting Regardless of what kind of error message you’ve received, you need to work out why Disk Management cannot initialize disk and then seek out the appropriate ways to fix the issue. “The request could not be completed because of an I/O device error” or “The system cannot find the file specified” or “ The device is not ready” or “Incorrect function”. Unfortunately, you will most likely be unable to initialize hard drive via Windows Disk Management and will receive one of the following error messages when you try. In order to access your hard drive and make full use of it, you will need to initialize it. Press Ctrl L to launch the Process Monitor filter.It is not uncommon for a hard drive to fail to be listed under the ‘This PC’ option and when you open Disk Management, it shows up either as ‘disk unknown’, as unallocated space, or just doesn’t show the disk capacity. Please save the captured data from Process Monitor to a file (File->Save) Under Process Monitor, Press Ctrl E to stop capturing. Try to Open Disk Management console to reproduce the issue with the error message "Unable to Connect to Virtual Disk Service" Under Process Monitor, press Ctrl E to start gathering data. Press Ctrl X to clear the currently captured data. You will see File/Registry activity is being captured. Run the process monitor on the problematic server Download process monitor from the link given here.Meanwhile, please also try using Process monitor to capture the process when you can reproduce the issue. The $VDS$.log file is created in the %Systemroot%\System32 folder. Right-click the new DebugLog key, point to New, and then click DWORD Value.ĭouble-click the new Level value, Set the value to 15 (hex 0xF) to on the Value data text box, and then click OK. Right-click the vds subkey, point to New, and then click Key.Į. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\vdsĬ. ![]() Click Start, click Run, type Regedit, and then click OK. If the above method not works, we may need to collect some information to analyze the issue.Īs Disk Management snap-in works closely with Virtual Disk Service, We may enable VDS registry key on the problematic server to capture the VDS log file for the analysis.Ī. Please check if there's any disk error in the event log, if yes, please try to un-attach the non-system drive, check if it could work. Please check if you are running any third-party anti-virus application, if yes, please uninstall the anti-virus application.įor test purposes, please try to clean-boot the system, and check if the issue still exists in clean boot. ![]()
0 Comments
Leave a Reply. |