[SOLVED] After changing disk type for Windows-VM boot fails

[alp1]

When I tried to run the dism command from the recovery console, I got an error that C: didn't exist. So first I had to use the Drvload command so C: would show up in the recovery console. Then I was able to run the dism command to add the driver permanently.

(My CD-ROM shows up as D: )
drvload d:\vioscsi\2k19\amd64\vioscsi.inf
dism /image:C:\ /add-driver /driver:D:\vioscsi\2k19\amd64

To see the status of the drives, you can run this command:
wmic logicaldisk get deviceid, volumename, description

didn't work for me. :-( I loaded drivers via recovery mode option, but still when I select scsi as disk type -> getting dump. (windows 2016 server). There is also scsi device controller in the device list.

but the question is: is scsi controller really important to get the highest Read\Write speed?

 

[ENG.]

to keep in history:
in order to have windows installed drivers prior changing the controller add the new drive 1-2GB on the target controller and reboot windows.
When it see the SCSI drive - it will load drivers and then you can change the boot drive controller - everything will work then.

Thanks, thats works for me