I ran into this today with multiple systems and after running a few different bcdedit commands on reboot saw this error:įile: \windows\system32\drivers\pvscsi.Sys System should now boot.Make sure to remove your snapshot, once successful, and remove tools mounted. Run the following dism /image:E:\ /add-driver /driver:".\pvscsi.inf"Īfter success on there, you can exit via exit otherwise the following command you'll need to adjust to where the scsi driver is. Note: at this point you still should be in the iso mounted drive on D. Once you've gone back and removed all of them, most likely there will be more than one if the server has been around a while, you will now add in the one back from vmware tools that you still have mounted. Do the following BUT CHANGE THE NUMBER ON OEM!! Don't run it copy paste blindly dism /image:E:\ /remove-driver /driver:oem1.inf you will want to remove all of the pvscsi.inf ones. Take note of all the oem.inf names that have pvscsi.inf listed by them the other ones for vmnet3,display, printer, etc should be ok to leave alone. Note this will take a hot minute depending on your system dism /image:E:\ /get-drivers
Vmware esxi 6 windows server 2012 r2 drivers#
Note the letter of the C drive, mine was always E when i checked.Now run the next set of commands to get all the base drivers installed on the system.
![vmware esxi 6 windows server 2012 r2 vmware esxi 6 windows server 2012 r2](https://i.ytimg.com/vi/woGZno-XQlE/maxresdefault.jpg)
To verify / view do the following diskpart Should come back as drvload: successfully loadedYou should now see your drives, you may have to assign a drive letter to the "C" drive but in my cases i didn't. Take a snapshot first just in case.Boot into windows recovery and start the command promptMount the vmware tools through Vcenter either via the datastore location or guest ->install tools -> mountrun the following commandsNote: D should be the mounted tools ISO if not skip down to the diskpart command to see which drive letter you're using for the ISO d:Ĭd “program files\vmware\wmware tools\drivers\pvscsi\win8\amd64"
![vmware esxi 6 windows server 2012 r2 vmware esxi 6 windows server 2012 r2](https://upload.wikimedia.org/wikipedia/en/1/17/VMwareESXiHostClientSummary.png)
Vmware esxi 6 windows server 2012 r2 install#
In repair mode remove all pvscsi.inf drivers installed and install the one from the VMWare tools install of the ESXi host.Įdit - the official method(s) from VMWARE in case you don't want to do the below. Attempting to do normal BCDedit and bootrec commands to repair did not fix the issue. When applying the update, along with other patches, it caused the machine to go into automatic repair mode (possibly blue screen but it did not display as such) and no drives would show in diskpart when opening the command prompt. Side note VMWare is stating 1.3.17 as the latest from 9/16. When patching Windows 2012 R2 ( I believe it applies to 2012 as well MS Catalog is showing Windows 8, 8.1, 20 R2 ) directly from MS there was an update - VMWare, Inc. This was a fun one, figured to write it up to hopefully help someone else.