cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
gundul
SCSI Port
Posts: 31
Registered: ‎03-26-2016
Location: ID
Views: 4,411
Message 1 of 5

[P50] Unable to enable Hyper-V feature (Windows 10 Pro)

Hi All,

 

I am having difficulties on enabling Hyper-V on my P50.

 

I have enabled the Virtualization setting within P50 BIOS. Have also turned off the P50, wait for a minute and then turned it back on. Everytime I enabled the Hyper-V feature, during the required restart Windows Update process shows failure to update and performed a rollback.

 

My P50 system info is as below:


Host Name: P50
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.10586 N/A Build 10586
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Product ID: 00330-80106-07335-AA055
System Manufacturer: LENOVO
System Model: 20ENCTO1WW
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 94 Stepping 3 GenuineIntel ~2492 Mhz
BIOS Version: LENOVO N1EET41W (1.15 ), 12/31/2015
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Total Physical Memory: 65,402 MB
Available Physical Memory: 60,918 MB
Virtual Memory: Max Size: 75,130 MB
Virtual Memory: Available: 70,661 MB
Virtual Memory: In Use: 4,469 MB
Page File Location(s): E:\pagefile.sys
Logon Server: \\MicrosoftAccount
Hotfix(s): 6 Hotfix(s) Installed.
[01]: KB3116278
[02]: KB3120677
[03]: KB3140743
[04]: KB3149135
[05]: KB3167685
[06]: KB3163018
Hyper-V Requirements: VM Monitor Mode Extensions: Yes
Virtualization Enabled In Firmware: Yes
Second Level Address Translation: Yes
Data Execution Prevention Available: Yes

 

The reason I have 64GB RAM on P50 is to have many VMs. Please help.

 

Regards,

Arief

 

Using: P51/i7/64GB/FHD, X230/i5/16GB/WXGA, M58p/Core2Duo/2GB, Q190/i3/4GB, Q190/Celeron/4GB. Gone: S110/Celeron/2GB/WSVGA, W510/i7/16GB/FHD, W520/i7/32GB/FHD, W530/i7/32GB/FHD, P50/i7/64GB/FHD, E330/i3/8GB/WXGA, E440/i5/8GB/WXGA, E440/i5/16GB/WXGA, E460/i5/16GB/FHD, Yoga2 10/Atom/2GB/WUXGA.
Puppy
Bit Torrent
Posts: 1,822
Registered: ‎11-28-2007
Location: CZ
Views: 4,404
Message 2 of 5

Re: [P50] Unable to enable Hyper-V feature (Windows 10 Pro)

Is there any detailed error message in System Event Log ?

 

Check this https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_compatibil... namely the Verify Hardware Compatibility paragraph.

__________________________________
ThinkPad (1992 - 2012): R51, X31, X220, Tablet 8.
Do you care about privacy and security ? Leave Google behind
gundul
SCSI Port
Posts: 31
Registered: ‎03-26-2016
Location: ID
Views: 4,391
Message 3 of 5

Re: [P50] Unable to enable Hyper-V feature (Windows 10 Pro)

Hi Puppy,

 

Thanks for the link. I have checked the compatibility and as shown on systeminfo, all requirements have Yes on them.

I checked Event Log and found no event showing the installation failure. However, looking at CBS log shows as below (Sorry for the long details):

 

2016-07-12 00:48:58, Info CBS Progress: UI message updated. Operation type: Foundation. Stage: 1 out of 1. Percent progress: 95.
2016-07-12 00:48:59, Error CSI 0000015c@2016/7/11:17:48:59.183 (F) base\boot\bcd\tools\bcdedit\ai\bcdeditai.cpp(235): Error E_INVALIDARG originated in function Windows::WCP::BcdEdit::BasicInstaller::Install expression: InnerStatus
[gle=0x80004005]
2016-07-12 00:48:59, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2016-07-12 00:48:59, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160706021310.cab to WER report.
2016-07-12 00:48:59, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160705171701.cab to WER report.
2016-07-12 00:48:59, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2016-07-12 00:48:59, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-07-12 00:48:59, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-07-12 00:48:59, Info CSI 0000015d Performing 1 operations as follows:
(0) LockComponentPath: flags: 0 comp: {l:16 b:a6022f819cdbd101c000000090054807} pathid: {l:16 b:a6022f819cdbd101c100000090054807} path: [l:115]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.10586.0_none_68f8bc40b518838f" pid: 590 starttime: 131127329258912822 (0x01d1db9c78d2bc36)
2016-07-12 00:48:59, Error [0x018050] CSI 0000015e (F) Failed execution of queue item Installer: Boot Configuration Installer ({3eca0b00-79bb-42b9-8421-a26a5cbb37e4}) with HRESULT E_INVALIDARG. Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
2016-07-12 00:48:59, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2016-07-12 00:48:59, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160706021310.cab to WER report.
2016-07-12 00:48:59, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160705171701.cab to WER report.
2016-07-12 00:48:59, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2016-07-12 00:48:59, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-07-12 00:48:59, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-07-12 00:49:00, Info CBS Startup: Changing logon timeout to a static timeout: 10800000
2016-07-12 00:49:00, Info CSI 0000015f Creating NT transaction (seq 2), objectname [6]"(null)"
2016-07-12 00:49:00, Info CSI 00000160 Created NT transaction (seq 2) result 0x00000000, handle @0x2c4
2016-07-12 00:49:00, Info CSI 00000161@2016/7/11:17:49:00.245 Beginning NT transaction commit...
2016-07-12 00:49:00, Info CSI 00000162@2016/7/11:17:49:00.261 CSI perf trace:
CSIPERF:TXCOMMIT;17376
2016-07-12 00:49:00, Info CSI 00000163@2016/7/11:17:49:00.261 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{3eca0b00-79bb-42b9-8421-a26a5cbb37e4};Microsoft-Hyper-V-Drivers-Hypervisor-Bcd, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};3742993us
2016-07-12 00:49:00, Info CSI 00000164 End executing advanced installer (sequence 344)
Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)

2016-07-12 00:49:00, Info CSI 00000165 Begin executing advanced installer phase 38 (0x00000026) index 306 (0x0000000000000132) (sequence 345)
Old component: [l:0]""
New component: [l:172 ml:173]"Microsoft-Hyper-V-Management-Clients-FirewallRules, Culture=neutral, Version=10.0.10586.0, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
Install mode: install
Smart installer: FALSE
Installer ID: {68ce8d69-26ae-4f9f-bea7-50613e7ab5c1}
Installer name: [13]"Firewall Rule"
2016-07-12 00:49:00, Info CSI 00000166 Performing 1 operations as follows:
(0) LockComponentPath: flags: 0 comp: {l:16 b:317963819cdbd101c300000090054807} pathid: {l:16 b:317963819cdbd101c400000090054807} path: [l:117]"\SystemRoot\WinSxS\amd64_microsoft-hyper-v-m..ients-firewallrules_31bf3856ad364e35_10.0.10586.0_none_777b8f52cb78fc09" pid: 590 starttime: 131127329258912822 (0x01d1db9c78d2bc36)
2016-07-12 00:49:00, Info CSI 00000167@2016/7/11:17:49:00.277 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{68ce8d69-26ae-4f9f-bea7-50613e7ab5c1};Microsoft-Hyper-V-Management-Clients-FirewallRules, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};32492us
2016-07-12 00:49:00, Info CSI 00000168 End executing advanced installer (sequence 345)
Completion status: S_OK

2016-07-12 00:49:00, Info CSI 00000169 Begin executing advanced installer phase 38 (0x00000026) index 307 (0x0000000000000133) (sequence 346)
Old component: [l:0]""
New component: [l:156 ml:157]"Microsoft-Hyper-V-Drivers-VmSwitch, Culture=neutral, Version=10.0.10586.0, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
Install mode: install
Smart installer: FALSE
Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
Installer name: [15]"Generic Command"
2016-07-12 00:49:00, Info CSI 0000016a Performing 1 operations as follows:
(0) LockComponentPath: flags: 0 comp: {l:16 b:90db65819cdbd101c500000090054807} pathid: {l:16 b:90db65819cdbd101c600000090054807} path: [l:111]"\SystemRoot\WinSxS\amd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_10.0.10586.0_none_f590d1dc2a741ba2" pid: 590 starttime: 131127329258912822 (0x01d1db9c78d2bc36)
2016-07-12 00:49:00, Info CSI 0000016b Calling generic command executable (sequence 1): [30]"C:\Windows\System32\netcfg.exe"
CmdLine: [51]""C:\Windows\System32\netcfg.exe" -e -c s -i VMS_VSF"
2016-07-12 00:49:00, Info CSI 0000016c Done with generic command 1; CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Process output is throttled for successful Generic Commands
2016-07-12 00:49:00, Info CSI 0000016d Calling generic command executable (sequence 2): [30]"C:\Windows\System32\netcfg.exe"
CmdLine: [50]""C:\Windows\System32\netcfg.exe" -e -c p -i VMS_PP"
2016-07-12 00:49:00, Info CSI 0000016e Done with generic command 2; CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Process output is throttled for successful Generic Commands
2016-07-12 00:49:00, Info CSI 0000016f Calling generic command executable (sequence 3): [30]"C:\Windows\System32\netcfg.exe"
CmdLine: [51]""C:\Windows\System32\netcfg.exe" -e -c p -i VMS_VSP"
2016-07-12 00:49:00, Info CSI 00000170 Done with generic command 3; CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Process output is throttled for successful Generic Commands
2016-07-12 00:49:00, Info CSI 00000171@2016/7/11:17:49:00.339 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Hyper-V-Drivers-VmSwitch, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};64737us
2016-07-12 00:49:00, Info CSI 00000172 End executing advanced installer (sequence 346)
Completion status: S_OK

2016-07-12 00:49:00, Info CSI 00000173 Begin executing advanced installer phase 40 (0x00000028) index 338 (0x0000000000000152) (sequence 379)
Old component: [l:0]""
New component: [l:162 ml:163]"Microsoft-Hyper-V-Drivers-Hypervisor-Bcd, Culture=neutral, Version=10.0.10586.0, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
Install mode: install
Smart installer: FALSE
Installer ID: {084acfba-714f-4d8a-a69a-fe4e9c8ce62d}
Installer name: [19]"FveUpdate installer"
2016-07-12 00:49:00, Info CSI 00000174 Performing 1 operations as follows:
(0) LockComponentPath: flags: 0 comp: {l:16 b:e7636f819cdbd101c700000090054807} pathid: {l:16 b:e7636f819cdbd101c800000090054807} path: [l:116]"\SystemRoot\WinSxS\amd64_microsoft-windows-servicingstack-boot_31bf3856ad364e35_10.0.10586.424_none_5f5e90820435bb10" pid: 590 starttime: 131127329258912822 (0x01d1db9c78d2bc36)
2016-07-12 00:49:00, Info CSI 00000175 Loading installer DLL from explicit path: [l:132]"C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack-boot_31bf3856ad364e35_10.0.10586.424_none_5f5e90820435bb10\fveupdateai.dll
2016-07-12 00:49:00, Info CSI 00000176 Performing 1 operations as follows:
(0) LockComponentPath: flags: 0 comp: {l:16 b:e7636f819cdbd101c900000090054807} pathid: {l:16 b:e7636f819cdbd101ca00000090054807} path: [l:117]"\SystemRoot\WinSxS\amd64_microsoft-hyper-v-drivers-hypervisor-bcd_31bf3856ad364e35_10.0.10586.0_none_a247819592df0c76" pid: 590 starttime: 131127329258912822 (0x01d1db9c78d2bc36)
2016-07-12 00:49:00, Info CSI 00000177 Install called with flags 0 in phase 40 (0x00000028)

2016-07-12 00:49:00, Info CSI 00000178 Install called with command \ua480\u4e05\u7ffe

2016-07-12 00:49:00, Info CSI 00000179 BitLockerUpdate: Running.

2016-07-12 00:49:00, Info CSI 0000017a BitLockerUpdate: Service request is for winload.exe/winresume.exe.

2016-07-12 00:49:00, Info CSI 0000017b BitLockerUpdate: BitLocker Drive Encryption is not turned ON on the OS volume.

2016-07-12 00:49:00, Info CSI 0000017c BitLockerUpdate: No servicing was performed on the OS volume.

2016-07-12 00:49:00, Info CSI 0000017d BitLockerUpdate: Done.

2016-07-12 00:49:00, Info CSI 0000017e@2016/7/11:17:49:00.339 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{084acfba-714f-4d8a-a69a-fe4e9c8ce62d};Microsoft-Hyper-V-Drivers-Hypervisor-Bcd, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};9310us
2016-07-12 00:49:00, Info CSI 0000017f End executing advanced installer (sequence 379)
Completion status: S_OK

2016-07-12 00:49:00, Info CSI 00000180 Begin executing advanced installer phase 50 (0x00000032) index 0 (sequence 0)
Old component: [l:0]""
New component: [l:0]""
Install mode: delta
Smart installer: FALSE
Installer ID: {d4486727-4d36-45a5-bc81-b8935aed1429}
Installer name: [27]"Ngen Task Scheduler Tickler"
2016-07-12 00:49:00, Info CSI 00000181@2016/7/11:17:49:00.339 Executing Process [76]"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Ngen.exe Update /Queue /Delay"
2016-07-12 00:49:00, Info CSI 00000182@2016/7/11:17:49:00.355 Executing Process [78]"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Ngen.exe Update /Queue /Delay"
2016-07-12 00:49:00, Info CSI 00000183@2016/7/11:17:49:00.355 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{d4486727-4d36-45a5-bc81-b8935aed1429};(null);10771us
2016-07-12 00:49:00, Info CSI 00000184 End executing advanced installer (sequence 0)
Completion status: S_OK

2016-07-12 00:49:00, Info CSI 00000185 Begin executing advanced installer phase 50 (0x00000032) index 0 (sequence 0)
Old component: [l:0]""
New component: [l:0]""
Install mode: uninstall
Smart installer: FALSE
Installer ID: {4006c604-9280-4d68-b731-2fe3d02e84bf}
Installer name: [16]"Shortcut Tickler"
2016-07-12 00:49:00, Info CSI 00000186@2016/7/11:17:49:00.355 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{4006c604-9280-4d68-b731-2fe3d02e84bf};(null);94us
2016-07-12 00:49:00, Info CSI 00000187 End executing advanced installer (sequence 0)
Completion status: S_OK

2016-07-12 00:49:00, Error CBS Startup: Failed to process advanced operation queue, startupPhase: 0. A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]
2016-07-12 00:49:00, Info CBS Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed
2016-07-12 00:49:00, Info CBS SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed, SubStage: 0
2016-07-12 00:49:00, Info CBS Progress: UI message updated. Operation type: Foundation. Stage: 1 out of 1. Rollback.
2016-07-12 00:49:00, Info CBS Setting original failure status: 0x800f0922, last forward execute state: CbsExecuteStateResolvePending
2016-07-12 00:49:00, Info CBS Attempting to remove poqexec from SetupExecute
2016-07-12 00:49:00, Info CBS Removed poqexec from SetupExecute.
2016-07-12 00:49:00, Info CBS Configured poqexec to not pend to SetupExecute.
2016-07-12 00:49:00, Info CSI 00000188 Rolling back transactions...

 

It seems the issue is on BCD entry on my P50. I have used EaseUS ToDo Backup clone feature to migrate the OS from original 500GB HDD from Lenovo to a Samsung 850 EVO 500GB. So this could be the issue. I read just now and found an link about rebulding BCD https://support.microsoft.com/en-us/kb/927392 and not sure how safe it is to proceed.

 

Just found another link about this also http://superuser.com/questions/1082894/we-couldnt-complete-the-features-undoing-changes-when-removin.... It seems repairing BCD is the way to go. Now I'm just trying to find out what this thing called Windows RE is. Oh my....

Using: P51/i7/64GB/FHD, X230/i5/16GB/WXGA, M58p/Core2Duo/2GB, Q190/i3/4GB, Q190/Celeron/4GB. Gone: S110/Celeron/2GB/WSVGA, W510/i7/16GB/FHD, W520/i7/32GB/FHD, W530/i7/32GB/FHD, P50/i7/64GB/FHD, E330/i3/8GB/WXGA, E440/i5/8GB/WXGA, E440/i5/16GB/WXGA, E460/i5/16GB/FHD, Yoga2 10/Atom/2GB/WUXGA.
gundul
SCSI Port
Posts: 31
Registered: ‎03-26-2016
Location: ID
Views: 4,382
Message 4 of 5

Re: [P50] Unable to enable Hyper-V feature (Windows 10 Pro)

Tried to go to Window RE to run bootrec.exe, and it seems this step needs installer CD which I'm not sure whether to use Windows 10 Pro CD from MSDN which I used to upgrade Windows 10 Home from Lenovo, or to use Windows 10 Home CD from Lenovo which I do not have.

 

Tried by running 'BCDEDIT /set {current} hypervisorlaunchtype auto' to change the hypervisorlaunctype on BCD entry from off to auto. I was changed succesfully, however still led to rollback on Hyper-V feature installation.

Any suggestions are appreciated. Thanks.

Using: P51/i7/64GB/FHD, X230/i5/16GB/WXGA, M58p/Core2Duo/2GB, Q190/i3/4GB, Q190/Celeron/4GB. Gone: S110/Celeron/2GB/WSVGA, W510/i7/16GB/FHD, W520/i7/32GB/FHD, W530/i7/32GB/FHD, P50/i7/64GB/FHD, E330/i3/8GB/WXGA, E440/i5/8GB/WXGA, E440/i5/16GB/WXGA, E460/i5/16GB/FHD, Yoga2 10/Atom/2GB/WUXGA.
gundul
SCSI Port
Posts: 31
Registered: ‎03-26-2016
Location: ID
Views: 4,356
Message 5 of 5

Re: [P50] Unable to enable Hyper-V feature (Windows 10 Pro)

Fixed just now by running 'BCDEDIT /set {current} hypervisorlaunchtype auto', run EasyBCD tool and did a re-create/repair boot files. Enabling Hyper-V feature no longer rollback after hitting 95% update percentage.

 

Thanks, all.

Using: P51/i7/64GB/FHD, X230/i5/16GB/WXGA, M58p/Core2Duo/2GB, Q190/i3/4GB, Q190/Celeron/4GB. Gone: S110/Celeron/2GB/WSVGA, W510/i7/16GB/FHD, W520/i7/32GB/FHD, W530/i7/32GB/FHD, P50/i7/64GB/FHD, E330/i3/8GB/WXGA, E440/i5/8GB/WXGA, E440/i5/16GB/WXGA, E460/i5/16GB/FHD, Yoga2 10/Atom/2GB/WUXGA.

Check out current deals!


Shop current deals

Top Kudoed Authors