Hyper-V virtualization - Setup and Use in Windows 10  

Kari said:

We lose nothing if we try. Take ownership of all four items, the VHDX file, the config folder plus the vmcx and vmrs files.

In the mean time I upload my Ubuntu vm's VHDX file for you to test importing, I created it yesterday for screenshots and it works perfectly. it's over 4 GB so it will take some time, especially as I am currently backing up my Windows 10 TH2 1511 ISO images to OneDrive.

Take your time Kari, I need to do my grocery shopping soon any how. And thanks for taking so much time helping a junior Geek in training.

This error is starting to neeeerve!LOL
It didn't help.

Cliff S said:

This error is starting to neeeerve!LOL
It didn't help.

I've been getting the same error! I just updated to windows 10 last night and spent an hour with microsoft chat support to no avail

Edit: Started/Restarted services, Same error in logs, latest version of win 10, Bios and everything else confirms virutalization.

The one weird thing is if I run the Intel processor identification utility with the hyper-v role ACTIVE, it claims I don't support virtualization. If I turn the role OFF, then the utility claims I DO support virtualization. This seems to be a known issue so may be unrelated

@Cliff S, something worth to try:

Enter this command in admin command prompt, reboot:

Code:

bcdedit /set hypervisorlaunchtype auto

Kari said:

@Cliff S, something worth to try:

Enter this command in admin command prompt, reboot:

Code:

bcdedit /set hypervisorlaunchtype auto

I had already tried that, with no change(you had mentioned that John recommended it in your tutorial.
Edit that wasn't the code but I'm in the middle of install anyhow.

I'm in the middle of installing Win10 Pro on my spare SSD now. I let you know after I get Hyper-V set up.

To install I'm first trying the keep files only option, If that doesn't do it, I'll do a total clean install. It's just a pain in the neck though because I'll then need to disconnect my 2nd internal for install, then repoint the libraries after, for my drivers and such. Then I might as well do it on my actual system disk, and be done with it

Cliff S said:

To install I'm first trying the keep files only option, If that doesn't do it....

The above didn't work It just reset to home version(the original version on the disk), even though it was a pro ISO from MCT.

Now I'm trying something else(I can't help myself).
I'm using Macrium(an image of my 512GB SSD) and re-imaging it to my 256GB SSD. Being it's not full, I'm curious if it uses clone mode instead, then I'll try the above again. That way it goes from pro to pro wiping all software(and hopefully the registry too).

OOPS it just finished, and it worked. MACRIUM ROCKS TOTALLY!!!

Ok now I'll try the above again.

Ok @Kari I'm, on a Virgin Pro now(it activated automatically by the way), the keep only personal files(my libraries) worked.

I just tried doing a VM and this is what I got:

I'm starting to believe that maybe windows is reading my hardware wrong and letting me install Hyper-V, but for some reason not use it.

Also your imported one didn't work either

I don't get it. Starting to suspect something in BIOS / UEFI settings. A weird setting we have overlooked.

At the moment I have nothing for you. I will continue looking for possible reasons and solutions.

Kari said:

I don't get it. Starting to suspect something in BIOS / UEFI settings. A weird setting we have overlooked.

At the moment I have nothing for you. I will continue looking for possible reasons and solutions.

Ok thanks. I have in between gone back to my original disk, but the other is nice and safe(the best possible backup, right?)
I'm thinking that maybe the BIOS allows Virtualization(which mine is set for) but shouldn't be for my CPU being 2 core 2 thread: Intel Processor G3220 (3M Cache, 3.00 GHz) Specifications

Advanced Technologies

Intel® Turbo Boost Technology ‡ No

Intel® vPro Technology ‡
No

Intel® Hyper-Threading Technology ‡
No

Intel® Virtualization Technology (VT-x) ‡ Yes
Intel® Virtualization Technology for Directed I/O (VT-d) ‡
No

Intel® VT-x with Extended Page Tables (EPT) ‡
Yes

Intel® TSX-NI No

Intel® 64 ‡
Yes

Idle States Yes

Enhanced Intel SpeedStep® Technology
Yes

Thermal Monitoring Technologies Yes

Intel® Stable Image Platform Program (SIPP) No