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~~10.0.1.2752.4486167-538_neutral' 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~~10.0.1.2752.4486167-538_neutral' 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~~10.0.1.2752.4486167-538_neutral' 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)
[gle=0x80004005]
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)
[gle=0x800736b3]
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.
3 Answers
Introduction
Hyper-V is a virtualization technology that allows users to run multiple operating systems on a single host machine. It is one of the most popular hypervisors available, and it is used by many professionals and organizations worldwide. However, some users have reported issues with enabling Hyper-V on Windows 10 due to the presence of the Japanese language on their computers.
In this blog post, we will explore the reasons why Hyper-V cannot be enabled in Windows 10 due to the Japanese language and provide some solutions to the problem. We will also discuss the importance of Hyper-V and its benefits.
What is Hyper-V?
Hyper-V is a virtualization technology developed by Microsoft that allows users to create virtual machines on a single physical host machine. With Hyper-V, users can run multiple operating systems on a single computer, which is useful for testing software, running legacy applications, and isolating workloads.
Hyper-V is included in Windows Server and Windows 10 Pro and Enterprise editions. It is also available as a standalone product called Hyper-V Server. Hyper-V supports various operating systems, including Windows, Linux, and FreeBSD.
Hyper-V provides many benefits, including improved hardware utilization, reduced costs, and increased flexibility. It also allows users to create and manage virtual machines using Microsoft’s System Center Virtual Machine Manager (SCVMM) and PowerShell.
The Error Message
When attempting to enable Hyper-V on Windows 10, some users have reported encountering an error message accompanied by a failure. The error message is recorded in the CBS.log file and indicates that the Hyper-V package is missing. Here is an example of the error message:
2019-11-19 12:34:20, Error CSI 000067a7@2019/11/19:11:34:20.604 (F) onecorebasewcpcomponentstorecsd_locking.cpp(95): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)[gle=0x80004005]
This error message indicates that the Hyper-V package is missing, and as a result, Hyper-V cannot be enabled on the system.
The Cause of the Error
The cause of the error is the presence of the Japanese language on the computer. The error occurs because the Hyper-V package is not available in the Japanese language, and as a result, it cannot be installed or enabled.
Even after running lpksetup /u to uninstall the language, the process fails, and the user receives a “Failed to Uninstall” message. This failure occurs because some system files required for the removal of the Japanese language are missing or corrupted.
Solutions to the Problem
There are several solutions to the problem of Hyper-V not being enabled due to the Japanese language:
1. Install the English Language Pack
One solution is to install the English language pack on the system. This will replace the Japanese language with English and allow the Hyper-V package to be installed and enabled.
To install the English language pack, follow these steps:
1. Press the Windows key + I to open the Settings app.
2. Click on Time & Language.
3. Click on Language.
4. Click on Add a language and select English.
5. Click on Set as default to make English the default language.
6. Restart the computer.
2. Repair the Windows Image
Another solution is to repair the Windows image using the Deployment Image Servicing and Management (DISM) tool. This tool can repair corrupted system files and restore missing components.
To repair the Windows image using DISM, follow these steps:
1. Open Command Prompt as an administrator.
2. Type the following command and press Enter:
Dism /Online /Cleanup-Image /RestoreHealth3. Wait for the process to complete.
4. Restart the computer.
3. Perform a Clean Install of Windows
If the above solutions do not work, the last resort is to perform a clean install of Windows. This will remove all data and applications from the computer and install a fresh copy of Windows.
To perform a clean install of Windows, follow these steps:
1. Back up all important data to an external drive.
2. Create a Windows installation media using the Media Creation Tool.
3. Boot the computer from the installation media.
4. Follow the on-screen instructions to install Windows.
5. Install the necessary drivers and applications.
6. Enable Hyper-V.
Conclusion
Hyper-V is an essential virtualization technology that allows users to run multiple operating systems on a single host machine. However, some users have reported issues with enabling Hyper-V on Windows 10 due to the presence of the Japanese language on their computers.
The error message indicates that the Hyper-V package is missing, and as a result, Hyper-V cannot be enabled on the system. The cause of the error is the absence of the Hyper-V package in the Japanese language.
There are several solutions to the problem, including installing the English language pack, repairing the Windows image using DISM, and performing a clean install of Windows. By following these solutions, users can enable Hyper-V on their Windows 10 systems and enjoy its benefits.
It looks like you are trying to enable Hyper-V on a Windows 10 system with the Japanese language pack installed, and are encountering an error due to a missing assembly.
One potential solution is to try uninstalling and reinstalling the Japanese language pack. To do this, you can follow these steps:
- Press the Windows key + X to open the Start menu, and then select “Control Panel”.
- In the Control Panel, go to “Clock, Language, and Region”, and then select “Language”.
- Click on the “Advanced settings” link on the right side of the window.
- In the “Language for non-Unicode programs” section, click on the “Change system locale” button.
- In the “System Locale” window, select “English (United States)” from the drop-down list, and then click “OK”.
- Restart your computer.
After the restart, try uninstalling the Japanese language pack again using the “lpksetup /u” command. If this still fails, you may need to try repairing or reinstalling Windows to resolve the issue.
If these steps do not help, you may want to try performing a search for the error message you are seeing (e.g. “STATUS_SXS_ASSEMBLY_MISSING Hyper-V Windows 10”) to see if there are any other potential solutions available. You may also want to consider seeking help from Microsoft support or from a trusted technical support provider.
It is possible that the error you are encountering when trying to enable Hyper-V on your Windows 10 system is related to the Japanese language pack installed on your system. Uninstalling and reinstalling the language pack, or changing the system locale to English, may help resolve the issue. If these steps do not work, you may need to try repairing or reinstalling Windows.
If you are still unable to enable Hyper-V after trying these steps, it is possible that there may be another issue causing the problem. In this case, you may want to consider seeking help from Microsoft support or a trusted technical support provider. They may be able to help you identify and resolve the issue.
The error code 0x80073701, also known as ERROR_SXS_ASSEMBLY_MISSING, indicates that certain essential system files are absent, thereby preventing any modifications to Windows from being successful. To recover these missing files, the most effective solution may be to perform an In-place Upgrade, which involves upgrading Windows to the latest version through an offline installation.