Home > Blogs > VMware Fusion Blog


Trying to Upgrade to Windows 10 on Fusion but hitting the SVGA bug? Here’s the simple workaround

Windows 10 released today, and many users are teeming to get started discovering all the great things that Microsoft built.

A number of Fusion uses however are hitting an issue when trying to upgrade from Windows 7, 8 or 8.1.

During the “hardware validation check”, the VMware SVGA graphics driver is misrepresented as being incompatible. This is not true as the drivers have been signed by Microsoft and are indeed compatible with Windows 10.

The simple workaround is rather than using the upgrade method within the VM, download the .ISO and mount it to Fusion to perform the upgrade.

We put together a KB with simple to follow step-by-step instructions here: http://kb.vmware.com/kb/2126929

I had written about the issue with some more context on my personal blog here: http://www.mikeroysoft.com/windows-10-and-vmware-fusion/ 

Some users have reported that simply disabling 3D Graphics within Fusion helps as well. Join the Windows 10 discussion in the VMware Fusion Community Forum and share your experiences, we love to hear from you!

This entry was posted in Uncategorized on by .

About Michael Roy

Michael Roy is the Product Line Marketing Manager for Fusion, Fusion Pro, Workstation Pro and Workstation Player at VMware. He guides product roadmap and messaging, produces and presents technical collateral, and works across teams to refine product integration strategy.

73 thoughts on “Trying to Upgrade to Windows 10 on Fusion but hitting the SVGA bug? Here’s the simple workaround

  1. Joel

    Hi

    I was able to upgrade my Windows 8.1 VM to Windows 10, but my network adapter was not functioning. I could see the network controller in device manager after the upgrade, but it was not listed in the network settings. I tried removing it and re-adding it, etc… with no luck. I’m on vmware fusion 7.1.2. Have you heard anything about network adapter related issues?

    1. Vilem

      I have issues with network as well. Normal websites are working well, but Outlook 2013 is not catching up the Exchange server. Very frustrating.

    2. nick

      I am getting same issue, have you had any luck fixing? I have tried re-installing tools etc but no luck
      Thanks
      Nick

      1. nick

        Solved
        basically in device manager in windows 10 I uninstalled the network card, reinstalled it and hey presto working

  2. Larry Nolan

    I downloaded the Windows10 .iso for 32 bit systems and attached it to my Win8.1 VM and it ran Setup.exe . I was asked for my Product ID and I used my Win8.1 ID but it was rejected. Tried three time to make sure I was entering the ID correctly. Doesn’t work.

    Any idea why? Is it wanting a Win10 Product ID? If so Where would I get that since I downloaded the installer?

    thanks,
    Larry

    1. Fred

      Hi Larry,

      This was mentioned earlier in the community.

      It seems you loaded a COUNTRY iso version.

      Downl the general 64/32 iso, that does not ask for an ID, worked for me

      Fred

      1. Larry Nolan

        Fred,
        I finally dowloaded the first ‘edition’ Win10 and it installed without prompting for a Product ID. Seems to be working fine for me as a 32bit VM.

        Does MS describe what each of the ‘editions’ of Win10 are for? I stupidly thought the Single Language edition would just give me an English lang. Win10.

        1. Cyrille

          @Larry : did you have all your personal data, apps, settings after the upgrade with the ISO ?
          Thanks,

          Cyrille

  3. Ryan

    Followed the knowledge base steps worked however my display is messed up now. It doesn’t recognize that I have three monitors and the i can’t get the resolution smaller.

  4. Stefan

    Thought this was going to do it for me after 3 days of trying. No go, same error: The installation failed in the SAFE_OS phase with an error during BOOT operation. 0xC1900101 – 0x20017. I’m on Fusion 6 though – is 7 absolutely required?

  5. Michele

    I, too, had the SVGA issue and the Win10 app t told me I couldn’t install Win 10.

    After having read these posts, I thought I was going great by downloading the Media and installing from there. However, I had trouble with my display regressing to low resolution and couldn’t find any way to resolve it.

    Happily, I took a snapshot before and am back on 8.1. If anyone has any ideas what my Fusion display setting should be to fix this (if that’s the answer), then I’d love to hear them.

    1. Michael Roy Post author

      For the display getting ‘small’ or ‘too big’ looking, try toggling the ‘Use full resolution for Retina display’ in the VM’s Display settings.
      Make sure Tools is up to date too

  6. David

    “The installation failed in the SAFE_OS phase with an error during BOOT operation. 0xC1900101 – 0x20017.”

    I have this same problem and I am using Fusion 7.1.2

    I ideas for a new blog post on this issue?

  7. Sean

    I too have tried many a fix including ISO and other fun. Nothing has worked so far. Same error as others (“The installation failed in the SAFE_OS phase with an error during BOOT operation. 0xC1900101 – 0x20017.”). I’m just going to cool my heels. It’s just an upgrade, not anything revolutionary.

    1. Michael Roy Post author

      I’ve seen a few of these errors now, so I’ve circled with the Support team to give us some insight into how to make it happen (so we can debug). I’ll do a follow up post when I have more to share on the issue, but we’re actively looking into it.

    2. Michael Roy Post author

      Random thought for you or anyone else hitting this issue… Is your Hard Disk setup as SATA or SCSI?
      (VM Settings > Hard Disk (SCSI) or Hard Disk (SATA)
      It says in the label.
      In the setting itself, under ‘Advanced Options’, when the VM is powered off, you can change it.
      It should be SCSI.

      1. Oren Wolfe

        My install would not work until I changed the HD type from SCSI to SATA. Possibly it was the act of changing that forced VMWare to load drivers, and that is what made it work. In any case, my HD is SATA.
        While I have your attention, systems installed under Fusion 7 (Win 10 and Ubuntu 15.4) do not take full advantage of my monitor’s full resolution (2560×1440). Older OS installations installed by Fusion 6 do use the screen’s full capability. Any suggestions?

        1. David

          I changed my drive type to SATA from SCSI to see what happens. I got a successful install of Windows 10. However, just like Oren’s experience, I am not getting the full resolution of the monitor, which is identified as Generic Non-PnP Monitor. I should be able to get 1920×1200 on my 2009 Macbookpro5.2, but I can only specify 1152×864 as the height resolution. So, I reinstalled VMware Tools. Nothing new. So I uninstalled VMware Tools and then installed them again. I now have proper screen resolution.

          Should I change back to SCSI from SATA now that everything is working?

          1. Michael Roy Post author

            This is exactly what I was suggesting… The error code is about a device driver, so it’s weird the SCSI driver causes this during upgrade considering it works and is what folks should be using. We used to see this with XP back in the day, and sometimes you’d have to attach a floppy disk file which contained the SCSI device driver.
            (The SCSI protocol is faster than SATA when virtualized, doesn’t matter what the physical hardware us underneath which is why we use it by default)

            And glad the re-install of Tools fixed the resolution issue, that’s been my experience as well.
            It’s less of an issue with the Fusion Tech Preview 2105.

          2. Michael Roy Post author

            As for changing back, I’d be interested to know if it works after changing it back. It’s easy to toggle if it crashes, so.
            But ideally, you’d want it to be SCSI.

          3. David

            It really, really did not want to go back to SCSI from SATA. Wouldn’t boot, wouldn’t repair. I returned back to SATA and it wouldn’t boot, wouldn’t repair. Shutdown a few times and rebooted until it started working again. I guess you can’t have everything.

        2. Len

          Fusion 7.1.2 user here.

          I encountered the Safe_OS issue back on 7/29 when the production version of Windows hit my mailbox. After hours of searching I found a thread with someone suggesting the drive interface be changed from SCSI to IDE to fix. I did that and the installation completed without another incident. Like everyone here though, I cannot change the drive back to SCSI. Windows fails to boot. Everything works fine again when I switch back to IDE. I eagerly await the moment someone cracks this nut.

          On the resolution issue, I encountered that one as well. Uninstalling / Reinstalling Tools didn’t quite get it for me, however. I also had to uncheck the resolution boxes in the Virtual Display>Settings>Display window and then recheck them AFTER reinstalling Tools. All is now good.

          1. Adrian W

            Summary: Virtual SCSI drives will work if you Install the Storage controller driver “LSI Adapter, SAS 3000 series, 8-port with 1068”

            Len
            After hitting the Safe_OS issue, thanks to this blog I managed to upgrade my Win 7 VM to Windows 10 by changing the boot drive to SATA.
            Windows 10 wouldn’t boot when I tried to change the boot drive back to SCSI after the install.
            My Win 7 VM had had a couple of other drives which I left as SCSI drives which weren’t visible after the upgrade to Win 10.

            But I’ve been running a Windows 10 Preview VM with SCSI disks quite happily.
            The Win 10 Preview device manager had under Storage Controller the following device driver:
            LSI Adapter, SAS 3000 series, 8-port with 1068

            When I installed that on my new upgraded “official” Windows 10, it cured the problem.
            (just ignore the warning that it might not work)
            My other SCSI drives became visible instantly, and after I shut down and changed the boot drive to SCSI, that worked too.

            I had previously added the following line to the .vmx file to make sure the VM booted from the SATA drive
            bios.hddOrder = “sata0:0”

            So I changed that back (with a text editor) to be:
            bios.hddOrder = “scsi0:0”

  8. Ingwie Phoenix

    That weirdly didn’t cause an issue on my upgrade. Using my Boot Camp partition in a VM and having upgraded it natively by booting into the OS itself; so all that went fine.

    However, for me, unity mode is broken. I firstly wasnt able to get into it. After the upgrade, I went back into my Mac, ran the VM once again and then made VMWare insert the Tools Installation disc again and ran the setup, resulting running the Repair step.

    Now, when I go into Unity mode, I get to see my windows desktop with a totally grey background – and my mac desktop is almost covered up. So I am unable to really use the Unity mode as I once did.

    Do I have to completely uninstall the tools first and reinstall, or what could the culprit be?

    1. Pam

      I am having the same issue with Unity. I don’t see the windows desktop, but nothing opens from the VM. I have to go back into single window mode, where I find the background and taskbar have disappeared from the VM. Restarting explorer.exe fixes this.

      I miss Unity.

  9. Kash

    I am having the SVGA issue from win 7 pro to Win 10. i installed Win 10 as a clean install through Fusion and now its asking for a Product key?

  10. Mike T

    Anyone know what to do if I get an error that says hard drive is locked? Fusion v7.1.2 during Windows 7 – > 10 upgrade.

  11. Peter M

    I managed to upgrade to Windows 10 from Windows 7 using latest VMWare Fusion. I experienced the “SAFE_OS phase with an error during BOOT operation. 0xC1900101 – 0x20017” error with the Windows10.iso upgrade path.

    After much trial and error I managed to install Windows 10 by changing my hard disk setting from scsi to sata and I also turned off the windows defender virus protection. I’m not sure which of these changes did the trick. On changing the hard disk setting the windows startup asked if I wanted to boot normally or in safe mode to check the system. I just booted normally for no ill affect.

    1. Peter M

      PS I also got the disk locked message when trying to have the installation program repair after the “SAFE_OS phase with an error during BOOT operation. 0xC1900101 – 0x20017” error. Didn’t seem any way around that. However it didn’t appear again when I proceeded as above.

  12. Alfred Schlatter

    When I interpret the workaround for the SVGA-driver “incompatibility” correctly the I have at the end a windows 10 environment instead of a windows 8 BUT I HAVE LOST ALL THE INSTALLED PROGRAMS? If so, than this is not acceptable. I have all that little things distributed somewhere in the windows system, that can’t be generated quickly. An ODBC-driver here, a special paper-format in a browser app there, or a program that can’t be installed only once… Lots of obstacles.

    Is there a chance, that there will be another workaround?

    By the way: Disabling the 3D-Graphics didn’t work on my mac. The “incompatibility” still exists.

  13. Bob S

    So I had to also change from scsi to sata drive. but now i can’t seem to go back to scsi as it won’t boot up from that. can you help?

    1. Adrian W

      See my longer reply to Len above – Virtual SCSI drives will work if you Install the Storage controller driver “LSI Adapter, SAS 3000 series, 8-port with 1068″

      1. Dan

        Pardon my windows ignorance but how do you “Install the Storage controller driver “LSI Adapter, SAS 3000 series, 8-port with 1068″”?

  14. Todd B

    I don’t know if this will be useful to anybody, but found a few useful things in this thread in examining my issues, so thought I’d contribute back what I found.
    After upgrading to Windows 10 – an ordeal in itself – I found that I no longer had internet access, and couldn’t resize my screen. It appears the reason was because W10 had replaced all of the VMWare drivers. In the latter case it was just using the basic Microsoft display adapter, with very course screen resolution.

    I reinstalled VMWare tools – by mounting the windows.iso as a virtual drive (following instructions elsewhere on the vmware site), and running setup64.exe, as just clicking on Reinstall VMWare Tools in the Fusion console did nothing. I noticed after this that the internet connection had been restored. I also saw VMWare tools had appeared under Settings -> Sharing. Nothing happened with the screen though. However, when I re-ran setup64.exe and told it to repair rather than reinstall, this seemed to do the trick, and replaced the screen driver with the VMWare driver.

  15. Stephen England

    What is the timing on a fix and new version of Fusion Pro, please? Don’t have time for the work around but want my free Windows 10.

    1. Michael Roy Post author

      While we don’t pre-announce our release dates, we have expressed that Fusion 8 will release before the end of this summer.
      As for the work around, if you’re referring to the SVGA issue, there’s no version of Fusion that can fix this because the ‘bug’ is a problem with certain versions of Microsoft’s validation tool.

      We worked with them, they fixed it, but they can’t retroactively apply that fix to users who already have the ‘broken’ version.

      The workaround takes just as long as it does to simply ‘upgrade’ from within the guest… you have to download Windows 10 one way or the other, and it’s 6-of-one-half-dozen-of-the-other getting the .iso file vs. the in-guest upgrade.

      1. Chuck

        Nice. So those of us ‘stuck in the water’ trying to upgrade Win 7 to Win 10 under Fusion 7 need to pay an ‘extortion-ware’ fee for Fusion 8 to get it working? Nice business model.

        BTW: for most users, the workaround you noted probably work fine. But, for some of us, we’re still struggling with upgrade install issues related to Fusion 7 that aren’t so easily resolved.

  16. S Vandersteel

    Re SVGA issue on upgrade to Win 10; I tried most to the approaches mentioned so far, but in the end opened a case with VM Support. They were wonderful and essentially took control of my Macbook (Mid-2012) Air, and completed the Win 10 install. They strongly advised that to run Yosemite and Win10 under Fusion, I should upgrade from 4GB to 8GB RAM. I quickly checked some sites to see that this was possible (I have done it myself on Pro’s) and it looked possible.

    So I called Apple and got an appointment for them to do upgrade. Long story short – they will not do it as RAM is soldered to the m-board. Even Apple licensed shops will refuse. So looks like I will live with 4GB. I allocated 2GB each to Win and Yosemite in VM-ware. The Mac side runs OK – but the Win side is quite slow. I only run Quicken on the Win side so I think I can live with this, but for heavy Win users, be forewarned of this limitation

  17. Alex Stanhope

    Sadly, we too have been “victims” of the SVGA upgrade bug on a Windows 7 VM we were trying to update!

    Having followed the instructions on the relevant KB article – http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2126929 – we noticed that on our version of Fusion 6.0.6, it was not possible to select Windows 10 as the OS in Settings > General, and it looks like v6.0.6 is the latest possible version.

    Is it therefor the case that a Windows 7 VM can only be upgraded to Windows 10 if you are running Fusion 7?

    Please do let me know either way!

    1. Michael Roy Post author

      You should be able to select Windows 8 or 8.1 as the OS type and that will let Windows 10 work, albeit not fully optimized.

  18. Mark Edmonds

    I’m stuck on Step 2.

    It states: For Fusion: “Click the Virtual Machine menu and click Settings > General. Change OS type to Windows 10 or Windows 10 x64”. This options is not available and I am running the latest version 7.1.2 (2779224).

    Any idea?

    Thanks.

  19. David L.

    After the upgrade from VMware Fusion 7 to Fusion 8.0, I’m not able yet to upgrade my VM Win 8.1 to Win 10.
    The MS report say that I have to contact the producer (VMware) because SVGA 3D is not compatible for Win 10 upgrade.
    Could you explain me why VMware write that Fusion 8 is correct to run Win 10? How can I resolve this issue?

    Fon information my Mac is a MacBook Pro (CPU: Intel Core i7 – 3 GHz – dual core with 16 GB ram)

  20. Jim Rand

    Same issue here. I have to assume VMWare and Microsoft will work together to solve this issue.

    Thanks.

  21. Andy Clayton

    I was seeing the graphics driver error message too. Turning off 3D acceleration or uninstalling VMTools made no difference however downloading and installing via the ISO as a mounted disk image (as recommended above) fixed the problem for me and I’m now upgraded to Windows 10 (showing as activated).

  22. MHA

    I’m still having this same issue (cannot upgrade to Windows 10), even after upgrading to VMware Fusion 8. Here’s the (same) error message:

    Compatibility issue:

    VMware SVGA 3D

    The display manufacturer hasn’t made your display compatible with Windows 10. Check with the manufacturer for support.

  23. Tom Hornyak

    I alos experienced the “SAFE_OS phase with an error during BOOT operation. 0xC1900101 – 0x20017″ error with the Windows10.iso upgrade path. I got around it by:
    1. Switching the disk frim SCSI ti SATA
    2. Now windows would not boot.
    3. Switched back to SCSI – windows booted but SATA drivers stated to be installed.
    4. Rebooted winddows when prompted
    5. Shutdown and switched back to SCSI
    6. Installed windows 10 from the downloaded ISO
    7. Re-installed VMWare Tools.
    8. Shut down and switched the disks back to SCSI.
    Based on 45 years of professional hardware & software engineering experience, I suspect both SATA and SCSI drivers need to be loaded.

  24. steve

    I Didn’t expect to require brain surgeon level intelligence to make this work ! C’mon VMWare. I think you guys should be fixing this . I have already upgraded to Fusion 8 thinking that was the simple remedy. I do not see why I should have to pay someone to try to sort it out and imagine plenty of others like me are way out of their depth if WMWare can not fix it.
    I think many are now wasting money paying for a product that appears to NOT WORK for me as advertised. I can not even find a phone number to call to speak with a real person for advice here in Australia.

    1. Michael Roy Post author

      Hi Steve =)
      I can certainly understand that this is a nuisance, but I want to remind you that this is Microsoft’s bug and we can’t change their code!
      We couldn’t “fix” it because we don’t own their code which needs fixing.

      Their bug affects all desktop virtualization products, which includes Parallels and VirtualBox. It surprisingly doesn’t affect Microsoft’s own Hyper-V.

      We can’t change their code unfortunately, but we did raise the issue with them and they told us they were going to fix it.

      In order for our SVGA driver to achieve Windows 10 certification, we had to pass 2.5 million tests (in 1 continuous run) with 100% success, and we have done that. The bug is that their tool is wrong.

      This workaround does the same thing which the tool is supposed to do (Download Windows 10 and install it), it just requires that you download the file manually rather than just click the ‘upgrade’ button. I apologize for the trouble, but I can’t apologize on behalf of Microsoft who owns this bug.

      Again, I totally get that this is something of a nuisance, but the workaround is actually quite simple. I tried to explain it as easily as I could using pictures and text, but it’s only a 2-step process… Download the .iso, connect it to the CD-Rom.

      If you’d like to speak directly to me about it, please feel free to email me at mroy AT vmware DOT com, I’d be happy to help you in any way or offer clarification about the issue.

      1. Paul Porter

        Michael, I can certainly understand that this is a Microsoft problem. My issue and I think this is where people are frustrated, is that VMWare advertises Fusion 8 is Windows 10 ready. If VMWare is going to advertise this, then they can’t just have be conditionally ready. If it wasn’t completely ready, then it shouldn’t have been released as such.

      2. Charles Henry Giancarlo

        Will downloading the iso and installing from there provide an upgrade, or a clean install? As a clean install will force re-installation of applications I want to go the upgrade route. What is not clear in your description (or anywhere on VMWare’s website) is whether this workaround for the SVGA Win10 Upgrade Tool bug will force the user to go through the clean install or whether it provides the same type of upgrade as in the Microsoft Upgrade tool.

        1. Michael Roy Post author

          You can do either, just as if it were a physical PC. Going through the .ISO method, you’re presented the option to replace or upgrade your existing installation.

  25. Richard Doyle

    This worked for me:
    Device Manager/Display Adapters/VMware SVGA 3D – right click and choose Update Driver Software
    Choose ‘Browse my computer’ and Let me pick from a list of device drivers.
    Choose Microsoft Basic Display Adapter.

    run in admin command prompt:
    schtasks.exe /Run /TN “\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser”

  26. joe dzurinda

    I have upgraded to Fusion 8. Saw that I don’t want a win 10 with specific language. Guess what, there is no version for ISO that doesn’t have a language. My 2 cents on windows 10 with VMFUSION, don’t waste your time on VMWARE, it won’t work with Windows 10.

    Tomorrow I’ll just go buy a tablet that runs windows 10, cheaper and easier solution. I’m not impressed with VMFUSION at this point.

    1. Michael Roy Post author

      Hi Joe,

      I think there’s some confusion here…

      Saw that I don’t want a win 10 with specific language

      Not sure what you mean? You saw you didn’t want something? I apologize, but I’m not understanding what you’re referring to.

      Guess what, there is no version for ISO that doesn’t have a language.

      Well, all of the .iso’s have to have SOME language, English or otherwise, not sure what you mean by ‘no version for ISO that doesn’t have a language’
      There are 4 .iso files that Microsoft makes available, and we respect the settings for each of them:
      – ‘default’ installer .iso containing all languages
      – EU version
      – Korean version
      – ‘Single Language’ version, which you then get to pick from the language list (English is one of them)

      My 2 cents on windows 10 with VMFUSION, don’t waste your time on VMWARE, it won’t work with Windows 10.

      Your comments don’t correlate? I am not sure what you’re referring to, but as millions of other users have obviously seen it works fantastically with Windows 10, and I personally use it every day.

      Could you clarify what you’re specifically having an issue with?

      1. joe dzurinda

        It’s almost clear as mud to install Windows 10. I downloaded 10 with English. Burned the image to CD and tried to install it. All I get is it won’t accept my product key from Windows 7.

        Fred
        July 31, 2015 at 1:26 pm up above says don’t do a specific country version. Not sure what he is talking about because they all seem to be tied to a specific country.

        I’m trying to upgrade Windows 7. I’m sure I’m doing something wrong but this seems to be an involved task, But thanks for the response.

  27. Alyosha Karamazov

    I was able to upgrade from Windows 7 to Windows 10 using VMware Fusion 8 as follows:

    1. clicking on the Get Windows 10 icon gave me the SVGA error.
    2. I went to Windows website inside windows 7 using Internet Exporer ( http://www.microsoft.com/en-us/windows/windows-10-upgrade )
    3 Scroll down to the middle of the page and select the click here after the line “If you’d like to creat a USB drive or DVD to download once and upgrade multiple PCs-click here”
    4. Click on “Download Tool Now (32 bit version)
    It did not seem to make any USB device, but just went into downloading the software and started the upgrade.
    5. After the upgrade I was stuck with a basic Microsoft VGA driver.
    6. Looking through the Windows 10 apps, I found “Computer Management”, opened that, found “Display Adapters” clicked on the adapter and searched for the update on my C: Drive. It went searched and found VMware SVGA 3D.
    7. Reboot, and it looks good.

    1. Michael Roy Post author

      But why do this? This very blog post gives the preferred way to upgrade, and it’s a hundred times easier.

      1. Alyosha Karamazov

        If the blog post was easier, ignore me. I started to following the instructions on blog post and this option just jumped out at me from Microsoft’s website. I couldn’t see any reason not to try it. A few clicks and I was done. I’ve been testing my software (I only use Windows for a couple of programs) and everything looks good.

        1. Michael Roy Post author

          Na, your method is fine, but do make sure you update the OS type and re-install VMware Tools to make sure things work as expected going forward.

          I had thought you had replaced the drivers with the MS generic ones before doing the update, which is a bunch of work and unnecessary.

    2. Alyosha Karamazov

      Between step 4 and 5 the website asked if I wanted to upgrade this PC now or create media. I selected upgrade this PC now. Then just followed the instructions.

      1. Michael Roy Post author

        ah, I see what you did there then… you didn’t even get the SVGA error, but after the within-windows-upgrade you had the generic drivers. Gotcha!

        In this case, I would make sure that you have the correct Guest OS type (change it from Windows 7 to Windows 10) and then re-install Tools.
        This way you can be sure you have the latest drivers for everything.
        (Unless you’re using Fusion 7, then choose Windows 8 as your Guest OS type because it’s the closest)

        1. Alyosha Karamazov

          OK. Add to my procedure:
          7. Shut down Windows (shut down the virtual machine)
          8. in Fusion go to Virtual Machine>Settings>General
          9. Change Name to “Windows 10”
          10. Click the Windows 7 text next to OS
          11. Select Microsoft Windows>Windows 10

          Still only a few clicks

          1. Michael Roy Post author

            Now that’s done, you’ll want to uninstall and re-install Tools from the Virtual Machine menu. When I do it, I do a ‘remove’ and then a regular ‘install’ just so that I know I’m replacing everything.
            Once you do, you should notice a performance boost actually, the new drivers are much more capable, especially when it comes to graphics =)

          2. Alyosha Karamazov

            Then:
            12. Try Virtual Machine>Reinstall VMware tools (it didn’t start)
            13. Click the windows icon>File Explorer>This PC>DVD Drive>Install.exe (It started)
            Reboot. I hope I’m done, and now I believe the blog method is equal to or less work than my unauthorized method!

          3. Michael Roy Post author

            beautiful! And it’s not that it’s unauthorized, just a round-about way of doing the same thing. Grabbing the .iso file from the Mac and using that would have saved you steps 1-6 is all.

  28. Alyosha Karamazov

    OK, Michael!
    after step 13
    14. Select “Remove” then “Finish”
    15. Restart
    16. Virtual Machine>Install VMware tools (nothing happens but the D drive becomes available)
    17. Window>File Explorer>This PC>DVD Drive (D:) VMware Tools (Installer starts)
    18. Setup type “typical” “Install”

    Thanks for all your help! you are great!

Comments are closed.