Error 0x800f0203 when enabling Hyper-V on 8.1

Question

I had Windows 8.0, disabled Hyper-V, and upgraded to Windows 8.1.  
I'm trying to re-enable Hyper V now.  I've successfully enabled / installed Hyper-V Manager, but Hyper-V Platform is errorring out.  
I'm on a Lenovo W530 with updated drivers.  
Relevant parts from my CBS log: 
2014-01-27 17:00:05, Info CSI 000000a4 Begin executing advanced installer phase 38 (0x00000026) index 123 (0x000000000000007b) (sequence 162)
Old component: [l:0]""
New component: [ml:332{166},l:330{165}]"Microsoft-Hyper-V-Drivers-VmSwitch-Common, Culture=neutral, Version=6.3.9600.16384, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
Install mode: install
Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}
Installer name: [6]"Events"
2014-01-27 17:00:05, Info CSI 000000a5 Performing 1 operations; 1 are not lock/unlock and follow:
(0) LockComponentPath (10): flags: 0 comp: {l:16 b:5f4cee22ab1bcf015d00000080059405} pathid: {l:16 b:5f4cee22ab1bcf015e00000080059405} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-hyper-v-d..ers-vmswitch-common_31bf3856ad364e35_6.3.9600.16384_none_20abdb73d34c8801" pid: 580 starttime: 130353335013267072 (0x01cf1baae4c0d680)
2014-01-27 17:00:05, Info CBS Progress: UI message updated. Operation type: Foundation. Stage: 1 out of 1. Percent progress: 92.
2014-01-27 17:00:05, Info CBS Winlogon: TiCoreOnCreateSession has been called
2014-01-27 17:00:06, Info CSI 000000a6@2014/1/27:22:00:06.065 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{3bb9fd2b-351e-4b9c-b1fc-ed0758805998};Microsoft-Hyper-V-Drivers-VmSwitch-Common, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;609232us
2014-01-27 17:00:06, Info CSI 000000a7 End executing advanced installer (sequence 162)
Completion status: S_OK
2014-01-27 17:00:06, Info CSI 000000a8 Begin executing advanced installer phase 38 (0x00000026) index 124 (0x000000000000007c) (sequence 163)
Old component: [l:0]""
New component: [ml:318{159},l:316{158}]"Microsoft-Hyper-V-Drivers-VmSwitch, Culture=neutral, Version=6.3.9600.16423, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
Install mode: install
Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
Installer name: [15]"Generic Command"
2014-01-27 17:00:06, Info CSI 000000a9 Performing 1 operations; 1 are not lock/unlock and follow:
(0) LockComponentPath (10): flags: 0 comp: {l:16 b:cd0f3123ab1bcf015f00000080059405} pathid: {l:16 b:cd0f3123ab1bcf016000000080059405} path: [l:226{113}]"\SystemRoot\WinSxS\amd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.16423_none_5a097ab253e42b0f" pid: 580 starttime: 130353335013267072 (0x01cf1baae4c0d680)
2014-01-27 17:00:06, Info CSI 000000aa 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"
2014-01-27 17:00:06, Info CBS Progress: UI message updated. Operation type: Foundation. Stage: 1 out of 1. Percent progress: 93.
2014-01-27 17:00:06, Info CBS Winlogon: TiCoreOnCreateSession has been called
2014-01-27 17:00:06, Info CSI 000000ab Performing 1 operations; 1 are not lock/unlock and follow:
(0) LockComponentPath (10): flags: 0 comp: {l:16 b:baf6b823ab1bcf016100000080059405} pathid: {l:16 b:baf6b823ab1bcf016200000080059405} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_6.3.9600.16384_none_cd3183f2deb856d2" pid: 580 starttime: 130353335013267072 (0x01cf1baae4c0d680)
2014-01-27 17:00:07, Info CSI 000000ac Creating NT transaction (seq 3), objectname [6]"(null)"
2014-01-27 17:00:07, Info CSI 000000ad Created NT transaction (seq 3) result 0x00000000, handle @0x3fc
2014-01-27 17:00:07, Info CSI 000000ae@2014/1/27:22:00:07.049 Beginning NT transaction commit...
2014-01-27 17:00:07, Info CSI 000000af@2014/1/27:22:00:07.205 CSI perf trace:
CSIPERF:TXCOMMIT;208698
2014-01-27 17:00:07, Error CSI 000000b0 (F) Done with generic command 1; CreateProcess returned 0, CPAW returned S_OK
Process exit code 515 (0x00000203) resulted in success? FALSE
Process output: [l:74 [74]"Trying to install VMS_VSF ...
... failed. Error code: 0x800f0203.
"][gle=0x80004005]
2014-01-27 17:00:07, Info CSI 000000b1 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"
2014-01-27 17:00:08, Error CSI 000000b2 (F) Done with generic command 2; CreateProcess returned 0, CPAW returned S_OK
Process exit code 256 (0x00000100) resulted in success? FALSE
Process output: [l:73 [73]"Trying to install VMS_PP ...
... failed. Error code: 0x800f0100.
"][gle=0x80004005]
2014-01-27 17:00:08, Info CSI 000000b3 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"
2014-01-27 17:00:08, Info CSI 000000b4 Done with generic command 3; CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Note: 
"Trying to install VMS_VSF ...
... failed. Error code: 0x800f0203.
When I restart after enabling the feature, I get "Could not complete the updates" and everything rolls back.
I've tried to search for a solution, I've done the DISM /RestoreHealth, to no avail.  What could be causing this?  

Answer 1

After making the BIOS changes the box needs to be cold booted.
Some BIOS options will not become available without a cold boot.  And with laptops this can equal pulling the battery.
Also, don't miss updating the BIOS.
And last, ensure that the flavor of the chipset that you have really does support the feature.  As there are cases where the motherboard supports it, or the BIOS allows enabling it, but the chipset does not actually have it.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.