Hyper-V virtualization - Setup and Use in Windows 10  

Page 27 of 47 FirstFirst ... 17252627282937 ... LastLast

  1. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #260

    simrick said:
    One question: Will I be able to just import my W7 VM after that?
    Although Hyper-V has its own built-in export feature, I personally am a fan of Disk2VHD. When I need to reinstall, I run Disk2VHD on each vm I want to save and import to new installation. Easy and relatively fast.

    Hyper-V's Export feature can be found in vm context menu:
    Hyper-V virtualization - Setup and Use in Windows 10-2016_01_20_00_55_071.png

    The tutorial shows how to convert your physical Windows installation to a VHD using Disk2VHD and import it to Hyper-V as a new vm but it works as well on and applies to virtual guests: Hyper-V - Create and Use VHD of Windows 10 with Disk2VHD - Windows 10 Forums
      My Computer


  2. Posts : 16,325
    W10Prox64
       #261

    Kari said:
    Although Hyper-V has its own built-in export feature, I personally am a fan of Disk2VHD. When I need to reinstall, I run Disk2VHD on each vm I want to save and import to new installation. Easy and relatively fast.

    Hyper-V's Export feature can be found in vm context menu:
    Hyper-V virtualization - Setup and Use in Windows 10-2016_01_20_00_55_071.png

    The tutorial shows how to convert your physical Windows installation to a VHD using Disk2VHD and import it to Hyper-V as a new vm but it works as well on and applies to virtual guests: Hyper-V - Create and Use VHD of Windows 10 with Disk2VHD - Windows 10 Forums
    So if I didn't export it, is it gone now?

    Nope, still get an error when trying to create a switch:

    Hyper-V virtualization - Setup and Use in Windows 10-create-switch-error01.png
      My Computer


  3. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #262

    simrick said:
    So if I didn't export it, is it gone now?
    If you have reinstalled wiping the disk, and the vm was located on the system disk, then yes, it has left its physical presence and gone to eternal life in cyberspace. In Windows and computing, reincarnation is possible in some cases (re: saving data from accidentally formatted disk), but in Hyper-V's case mostly not successful.

    If you reinstalled on top of the old installation, not wiping the disk, we might be able to save your vm from Windows.old folder.

    That is why I recommend changing the default storage locations for virtual hard disks and virtual machine configuration files to another disk or partition. In my case, it's always the D: drive:
    Hyper-V virtualization - Setup and Use in Windows 10-2016_01_20_01_08_361.png


    Hyper-V virtualization - Setup and Use in Windows 10-2016_01_20_01_09_412.png

    A few years back I wrote a sticky post at the Seven Forums about setting up a Windows PC, starting with explaining why users in my opinion should think of the partitioning and disks even before installing Windows. it might be that I modernize that post to handle Windows 10 and post something similar here one of these days, but for now let me repeat my recommendation: It is a good idea to store the virtual hard disks on another disk or partition than the system drive C:.
      My Computer


  4. Posts : 16,325
    W10Prox64
       #263

    Okay Kari. I have vm set to save on G:. It's still there. But do you seriously want me to reimage my C drive?

    Because I would have to go all the way back to some time in December before I disabled the switch. I don't think I can do that.
      My Computer


  5. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #264

    simrick said:
    Okay Kari. I have vm set to save on G:. It's still there. But do you seriously want me to reimage my C drive?
    I want you to be happy, able to use Hyper-V. It's your decision if you want that

    Seriously, I see no working exit strategy here without reinstall. In your screenshot the error is clearly told: binding the wireless NIC and external switch to a bridge fails because of access is denied. A permissions issue, a very serious permissions issue which might be impossible for us to resolve.

    An idea: You might want to completely uninstall / disable / remove your wireless NIC and all its drivers from your PC, disable the Hyper-V feature and reboot. After reboot reinstall everything NIC related (drivers and such), and when you have a working connection again, enable Hyper-V feature and reboot, finally try to create the switch.

    I assume you already tried the disable feature / reboot / enable feature trick without success?
      My Computer


  6. Posts : 16,325
    W10Prox64
       #265

    Kari said:
    I want you to be happy, able to use Hyper-V. It's your decision if you want that
    I want to be happy too, but I don't remember when I disabled the switch - I can't know when to reimage the computer to, and even if I have an available image.

    Kari said:
    Seriously, I see no working exit strategy here without reinstall. In your screenshot the error is clearly told: binding the wireless NIC and external switch to a bridge fails because of access is denied. A permissions issue, a very serious permissions issue which might be impossible for us to resolve.
    Well that really seems silly. How can this be? I disabled the Hyper-V feature, rebooted, then re-enabled it. Everything should be reset in Hyper-V. This seems like a serious flaw in the feature. I find it hard to believe that I would have to reinstall my entire host operating system to fix this. There must be another way.

    Kari said:
    An idea: You might want to completely uninstall / disable / remove your wireless NIC and all its drivers from your PC, disable the Hyper-V feature and reboot. After reboot reinstall everything NIC related (drivers and such), and when you have a working connection again, enable Hyper-V feature and reboot, finally try to create the switch.
    Okay, I will try it tomorrow.

    Kari said:
    I assume you already tried the disable feature / reboot / enable feature trick without success?
    Yes.
    Thanks for your help. Tomorrow I'll give it another go.
      My Computer


  7. Posts : 17,838
    Windows 10
       #266

    Kari, will 'Remix' install in Hyper-V?
      My Computer


  8. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #267

    simrick said:
    Well that really seems silly. How can this be? I disabled the Hyper-V feature, rebooted, then re-enabled it. Everything should be reset in Hyper-V. This seems like a serious flaw in the feature. I find it hard to believe that I would have to reinstall my entire host operating system to fix this. There must be another way.
    It's not that simple. In fact what you did, Hyper-V and removing a switch manually in Device Manager is in my opinion about as serious than User accounts and changing the only user account from admin to guest and then wondering why it is impossible to install software. I don't want you to take this in a wrong way but you have caused this by yourself by doing something you are not supposed to do. Had you for instance checked this tutorial when setting up Hyper-V you'd known not to do that.

    In any case, I will continue thinking and searching for a solution.

    simrick said:
    Thanks for your help. Tomorrow I'll give it another go.
    This far I have not been able to help you at all. Let me know how it goes.
      My Computer


  9. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #268

    Edwin said:
    Kari, will 'Remix' install in Hyper-V?
    Sorry @Edwin, dialog with Simrick made me somehow miss your post, noticed it only now.

    No, I have had no success in getting Remix installed on Hyper-V. I will continue testing, will inform you if I find a way to get it installed.
      My Computer


  10. Posts : 16,325
    W10Prox64
       #269

    Kari said:
    ...what you did, Hyper-V and removing a switch manually in Device Manager is in my opinion about as serious than User accounts and changing the only user account from admin to guest and then wondering why it is impossible to install software....

    I did a good one, eh?!

    Well, I should be able to uninstall Hyper-V feature, and everything should go back to the way it was before installing. But hey, that's just my opinion.

    EDIT: I can get around the user account problem, by enabling the hidden administrative account and fixing things. There should be a way to fix Hyper-V as well.
      My Computer


 

Tutorial Categories

Hyper-V virtualization - Setup and Use in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:27.
Find Us




Windows 10 Forums