I have a Windows 7 Guest (using VMWare Workstation 9). When I attempt to upgrade to Windows 10, it gives me 2 options - troubleshoot, or power off. After rebooting, it reverts to Windows 7, and gives me the above error message.
None of the troubleshooting options do anything effectively.
How do I get around it?
Apparently, Windows 10 does not like SCSI drives. The VMWare VDisk was defaulted to SCSI when the VM was created. All that was necessary, was to change the disk to an IDE interface, and retry the upgrade. To do this, the steps are as follows:
I had this exact problem, changing the disk type to IDE worked and allowed the Windows 10 upgrade to complete. My environment is ESX 5.5 U3.
To do this I also used a couple of tips from here: http://www.ajpdsoft.com/modules.php?traducir=es-en&name=News&file=article&sid=645 This included the use of ssh to access the ESX datastore, also the use of Putty. I then used the vi line editor to alter my 35GB .VMDK file.
Thanks for the key part of the solution!
Some blogs say, that for later updates some computers need a bios update.
So in the case examined here, the solution was to upgrade the virtual hardware version. (I don't know how to do it in VMWare Workstation, but for vsphere the steps where as following.)
In vsphere Client:
(In this case we updated from hardware version 9 to 11 in vcenter/vsphere 6)
I tried so many possible solutions only to find that it worked after installing all optional updates and not selecting to download the latest updates during installation. I tried this on both KVM vm as well as a gen 2 hyper-v conversion of the machine with an iscsi drive
User contributions licensed under CC BY-SA 3.0