Trying to activate hyper-v after ssd clone

Question

On my windows 1o machine, i am unable to enable the hyper-v services. After I enable it and restart the machine, the start screen says that the changes will be reverted again. (This is when i try to enable it as windows features ).

After restart, the event viewer shows me problems enabling all hyper-v services

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Servicing" Guid="{BD12F3B8-FC40-4A61-A307-B7A013A069C1}" /> 
  <EventID>11</EventID> 
  <Version>0</Version> 
  <Level>0</Level> 
  <Task>1</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2016-11-08T19:50:29.554418200Z" /> 
  <EventRecordID>222</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="2316" ThreadID="2372" /> 
  <Channel>Setup</Channel> 
  <Computer>yyyyyyyy</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <UserData>
- <CbsUpdateChangeState xmlns="http://manifests.microsoft.com/win/2004/08/windows/setup_provider">
  <UpdateName>Microsoft-Hyper-V-Services</UpdateName> 
  <PackageIdentifier>Microsoft-Hyper-V-ClientEdition-Package</PackageIdentifier> 
  <ErrorCode>0x800f0922</ErrorCode> 
  <Client>Windows Optional Component Manager</Client> 
  </CbsUpdateChangeState>
  </UserData>
  </Event>

I used to be able to activate hyper-v running windows 8.1 on the same hardware, then I switched to xamarin programming for a while, and had to disable it. Since then I updated to windows 10 and also cloned my 256mb ssd to a 512mb ssd.

The internet says, when cloning a drive, one shoukd run

bcdedit /set {current} hypervisorlaunchtype auto

On my maschine, this outputs

Falscher Parameter.

It's a german os, so it probably means

Invalid parameter.

After a restart, and running bcdedit without a parameter i get the following output

Windows-Startladeprogramm
-------------------------
Bezeichner              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  de-DE
inherit                 {bootloadersettings}
recoverysequence        {b6488dab-f6aa-11e2-91cc-edc2952261ad}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {b6488da9-f6aa-11e2-91cc-edc2952261ad}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Off
Falscher Parameter.

So Falscher Parameter. (Invalid parameter.) keeps showing up.

Any ideas how to solve my problem?

Answer 1

At the end, it seems that my windows was somehow broken. I updated to 'Windows 10 – Version 1607'. After that, Hyper-V works as expected. The update may repaired some windows files/settings. bcdedit no longer show the falscher parameter error. So maybe reparing windows will fix this problem in general.