A: You need to run the deployment tools command prompt and use the command copype to create the working directory. The files are not automatically extracted to your desktop; they are generated based on your architecture choice ( x86 , amd64 , or arm64 ).
Before installing any downloaded deployment assets into an enterprise network, ensure their integrity:
: Use the /layout command shown above on a stable internet connection to pre-download the files, then run the installation locally from that folder. Hash Mismatch / Corrupt Installation Files
The WinPE add-on might download and try to install 32‑bit components on your 64‑bit Windows system (which is a known bug). While the installer should fetch the correct architecture, you can try to manually copy the amd64 files to the path where the installer is looking for the x86 files. windows pe boot files -onecoreuap--x86-en-us.msi download
Instead of tracking down a single isolated MSI file, you should resolve the issue by installing the official Microsoft deployment packages that contain these files natively. Step 1: Install the Correct Windows ADK and WinPE Add-on
The specific file is an official installer package from Microsoft used to deploy the 32-bit (x86) Windows Preinstallation Environment (Windows PE) boot files for English (US) systems.
Even as modern environments transition fully to 64-bit (amd64) operating systems, x86 (32-bit) boot files remain critical for legacy hardware support, specific recovery partitions, and cross-architecture deployment scripting. Why Do You Need This MSI File? A: You need to run the deployment tools
If an installation aborts halfway through, it may leave behind a corrupted, partially downloaded .msi file in your temporary directories. :
Open the and navigate to Programs and Features . Locate Windows Assessment and Deployment Kit in the list. Right-click it and select Change , then choose Repair .
Do not search for the specific MSI file. Go to the official Microsoft Learn page: https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install . Download the latest version of the Windows ADK ( adksetup.exe ) that matches your operating system. Hash Mismatch / Corrupt Installation Files The WinPE
: While modern systems are primarily 64-bit, the x86 version is essential for servicing older hardware or specific UEFI 32-bit tablets.
If the repair fails because it still asks for the missing .msi package:
One user reported that they ran the installer over and over. "Around the 10th time it just didn't error out and installed."
Go to the official Microsoft ADK download page. Run the Installer: Launch adkwinpesetup.exe .
In recent versions of the Windows ADK, Microsoft has begun deprecating 32-bit Windows PE components in favor of x64. If you install the latest ADK and find the x86 folder missing, you may need to download an older baseline version of the ADK (such as the Windows 10, version 2004 or 11 21H2 ADK) which still natively packages the x86 OneCoreUAP files. Verifying Your Installation