billearl's Posts

I changed the hard disk bus type from SCSI to SATA, but now the Windows 7 VM won't boot (" a problem has been detected"), and can't be "repaired". So that was a non-starter. The VM has to boot in Windows 7 to use the Windows 10 install iso. Update: After switching back to SCSI, the Windows 7 VM booted successfully and VMware Tools installed SATA drivers. After that the upgrade to Windows 10 was successful in SATA mode. Now switching back to SCSI in the Windows 10 VM. Thanks for the advice, Mikero. Update 2: Now it seems I can't boot in SCSI mode because drivers are not present. I tried uninstalling and reinstalling VMware Tools but that didn't do it. How do I install SCSI drivers in Windows 10 / Fusion 8? Update 3: Making progress. This comment in another thread fixes booting back in SCSI mode. I followed that with uninstalling / reinstalling WMware Tools, but not yet able to drag and drop to / from the Mac Desktop.

WoodyZ wrote: billearl wrote: I have Windows 7 and 8.1 VMs. What I did was simply duplicate my Windows 7 VM, then update it to Windows 8, then 8.1. Keeping a copy of a Virtual Machine containing the previous Windows 7 OS when upgraded using Upgrade Media is not allowed as the EULA allows for only one instance, physical of virtual.  Obviously one can chooses to do as they wish however any answer that violates the products EULA is not a correct answer, nor should any answer that violates the EULA be posted to begin with as doing so violates the VMware Community Terms of use. Thanks. I hadn't thought of that. I use Windows 7, but like the idea of testing the newest version before eventually switching.

Thanks, Darius. I didn't check the other thread since I'm running Fusion 6. I had done a fresh installation of Windows 8.1 (SCSI) in a new VM, and decided to try copying the vdmk from my upgraded Windows 8.1 (IDE) to it. That had the effect of changing to a vmx file with the correct scsi0.virtualDev = "lsisas1068". So I'm back to SCSI, without knowing exactly what changed until I read your post in the other thread. And yes, my upgraded Windows 8.1 VM probably started life as a Windows XP VM. Glad this is solved.

It turns out that, after reinstalling VMware Tools, shutting down, and switching Settings back to SCSI, the VM won't boot. Only switching again to IDE allows it to boot. Assuming SCSI is better than IDE, how do I reinstall the SCSI driver so it will boot in SCSI mode?

Amazingly, that worked! Thank you very very much! I wish I knew the solution was so simple before wasting two days trying other suggestions, and I curse Microsoft for allowing this problem to happen in the first place. They're arrogant and irresponsible IMO. Thousands of others in Windows land still flying blind searching for their particular solution... Now I need to decide if I want to keep IDE or go back to SCSI.

If you check the Microsoft Community boards, there are many many others having similar problems, completely unrelated to VMware. I also hope VMware can come up with a solution specific to Fusion. Windows - Microsoft Community

Same issue, same error code here. Looks like the solution has to come from MS. They've known about this for at least 4 months. Fusion 6.0.1, OS X 10.7.5, Windows 8 VM (upgraded from Windows 7), Mac Pro 1,1.

What I mean by "forced restart" is selecting the Virtual Machine >> Restart menu item. After a little while (less than a minute), it would restart properly (might take a couple attempts to restart properly - I forget), after which it's possible to uninstall & reinstall VMware Tools. This seems like a different problem than the original poster of this thread is having.

moeff wrote: I have a black screen everytime when I boot up my Windows 7 (32bit) VM (no BootCamp) on my MBP (Core Duo 2,53GHz, 4GB). The VM was converted from Fusion 3.1.3 to 4.0.2. This is probably not much help to you: I had the same problem with Windows 7 (32bit) in Fusion 4.0.2, except it would boot okay the second time, after a forced restart. I eventually uninstalled and reinstalled VMware Tools, and that fixed it.

GWood1 wrote: same problem here. Firefox, Safari and Windows Explorer all give the same result. In my case, I filed a support request with VMware and they had the problem corrected. It took a few days.

No such problem here with 3D Graphics enabled, Windows XP / Vista / 7, Fusion 4.0.1, OSX 10.7.2 (Build 11C62). Mac Pro 1,1 with ATI Radeon HD 4870 graphics card if that matters. EDIT: My Windows VMs are 32-bit, in case that matters.

glasskopf wrote: Fusion 4 is up and running, though when I try to "Update VMware Tools" something is going wrong. The install program for tools deinstalls the old version, gets what appears to be 99% of the way through the install of the new version of tools, however then it "Rolls-back" and completely uninstalls...leaving me with no tools package installed at all. I have tried to a number of attempts at installing tools, rolling back to the last snap shot I took before upgrading to Fusion 4 and I have also come at the install from multpile directions...manually uninstalling the old version then doing a straight install of the new, running the update and then re-running the install...each time the install of the new tools gets rolled-back and completely uninstalled. I think this problem is caused by an incomplete uninstallation of the old VMware Tools. What worked for me was to completely uninstall the old VMware Tools, using Revo Uninstaller (free), prior to installation of the new VMware Tools. I used the "Advanced" setting in Revo Uninstaller, which removes all traces of VMware Tools even if the standard uninstaller fails (which it did). This worked great for XP, Vista, and Win7 VMs.