Each attempt I make to activate Hyper-V results in a failure accompanied by an error message recorded in the CBS.log:

2019-11-19 12:34:20, Info                  CBS    Exec: Resolving Package: HyperV-UX-PowerShell-Module-HyperV-WOW64-servercommon-Package~31bf3856ad364e35~amd64~ja-JP~10.0.17763.1, Update: acc2e8a20c76ffe3547579459bc35e3a, PinDeployment: amd64_hyperv-ux-powershel..oyment-languagepack_31bf3856ad364e35_10.0.17763.1_ja-jp_759d6514b48b8eca
2019-11-19 12:34:20, Info                  CBS    Exec: 84 deployments need bulk staging
2019-11-19 12:34:20, Error                 CSI    000067a7@2019/11/19:11:34:20.604 (F) onecore\base\wcp\componentstore\csd_locking.cpp(95): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)[gle=0x80004005]
2019-11-19 12:34:20, Error                 CSI    000067a8 (F) STATUS_SXS_ASSEMBLY_MISSING #50936360# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2019-11-19 12:34:20, Error                 CSI    000067a9 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #50936202# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = HyperV-UX-PowerShell-Module-HyperV-vm-Deployment-LanguagePack, version 10.0.17763.1, arch amd64, culture [l:5]'ja-JP', nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'HyperV-UX-PowerShell-Module-HyperV-vm-Package~31bf3856ad364e35~amd64~ja-JP~10.0.17763.1.882ec3c0a4ad38131b14954a45d63426', rah = (null), manpath = (null), catpat[gle=0x80073701]
2019-11-19 12:34:20, Error                 CSI    h = (null), ed = 0, disp = 0)[gle=0x80073701]

I assume that the error is caused by the presence of the Japanese language on my computer, but I am unable to remove it. Even after running lpksetup /u to uninstall the language, the process fails and I receive a “Failed to Uninstall” message. Once more, the CBS.log file shows a similar error message:

2019-11-19 12:39:07, Info                  CSI    e35}]) ref: ( flgs: 00000000 guid: {d16d444c-56d8-11d5-882d-0080c847b195} name: [l:79]'Package_2_for_KB4486167~31bf3856ad364e35~amd64~~' ncdata: [l:0]'')
  (1684)  MarkUnstaged: flags: 0 tlc: [018e321f53db726f5b2fb527205ef28b, version 4.0.15744.161, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) ref: ( flgs: 00000000 guid: {d16d444c-56d8-11d5-882d-0080c847b195} name: [l:79]'Package_2_for_KB4486167~31bf3856ad364e35~amd64~~' ncdata: [l:0]'')
  (1685)  Unpin: flags: 0 tlc: [018e321f53db726f5b2fb527205ef28b, version 4.0.15744.161, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) ref: ( flgs: 00000000 guid: {d16d444c-56d8-11d5-882d-0080c847b195} name: [l:79]'Package_2_for_KB4486167~31bf3856ad364e35~amd64~~' ncdata: [l:0]'')
2019-11-19 12:39:07, Error                 CSI    000067b1 (F) The TLC was not marked by this installer[gle=0x80004005]
2019-11-19 12:39:07, Error                 CSI    000067b2@2019/11/19:11:39:07.726 (F) onecore\base\wcp\componentstore\csd_pin.cpp(624): Error STATUS_SXS_ASSEMBLY_NOT_FOUND originated in function CCSDirectTransaction::MarkTlcUnstaged expression: (null)
2019-11-19 12:39:07, Error                 CSI    000067b3 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #51154315# from CCSDirectTransaction::OperateEnding at index 1 of 1686 operations, disposition 2[gle=0xd0150004]
2019-11-19 12:39:07, Error                 CSI    000067b4 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #51154111# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x800736b3]
2019-11-19 12:39:07, Error                 CSI    000067b5 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #51154109# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 102, pSink = NULL, disp = 0)[gle=0x800736b3]
2019-11-19 12:39:07, Error                 CSI    000067b6 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #51154108# 41041 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000066, pSink = NULL, disp = 0)

I attempted numerous solutions to resolve the issue, but none of them were successful. These included running the commands DISM /Online /Cleanup-Image /ScanHealth, DISM /Online /Cleanup-Image /RestoreHealth, and sfc /scannow, deleting the registry key for the language, reinstalling the Japanese language, and manually deleting packages one by one (although some of them resulted in “Access Refused” errors while others produced “Assembly not found” errors).

It is important to note that my computer is capable of running Hyper-V, and virtualization has been enabled.

Askify Moderator Edited question April 26, 2023