The error "Setup cannot locate toolkit documentation-x86-en-us.msi" is a known issue typically encountered when installing or updating the Windows Assessment and Deployment Kit (ADK). It often occurs because the installer UI incorrectly lists 32-bit (x86) components that have been removed or moved in newer versions, or because the installation media is incomplete. Common Fixes
If you encounter this error, try the following solutions in order:
Use the Offline Installer: Many users report that the online "stub" installer fails to fetch specific components. Download the full Windows ADK Offline Installer to ensure all required MSI files are present on your local drive before starting setup.
Run as Administrator: Right-click the adksetup.exe and select Run as administrator. Some systems block the creation of the required temp folders if the installer lacks elevated permissions.
Change the Download Path: If you are downloading the kit for later installation, avoid using deeply nested folders or protected system directories. Users have found success by setting the download directory to a simpler path, like their Documents folder or the root of the C: drive.
Verify Component Support: In newer versions of the ADK (such as for Windows 11), the 32-bit (x86) version of WinPE and certain toolkits has been removed. If your setup is failing on an x86-specific MSI, check the official Microsoft ADK documentation to see if that component is still supported for your target version.
Check Temporary Folder Permissions: The installer needs full access to the Windows Temp folder to cache MSI files. You can manually grant "Full Control" to "Everyone" for the C:\Windows\Temp folder temporarily to see if it bypasses the "cannot locate" error. Advanced Troubleshooting
If the basic steps do not work, consider these technical workarounds: Download and install the Windows ADK | Microsoft Learn
If you are trying to install or update software and hit the error "Setup cannot locate toolkit documentation-x86-en-us.msi," you aren't alone. This is a common hiccup, usually occurring during the installation of Microsoft SQL Server or various developer toolkits.
The installer is essentially asking for a specific file it needs to complete the process, but the path it's looking at is empty or redirected. 🛠️ Why This Error Happens
Corrupted Download: The original installation media is missing files.
Incomplete Extraction: The setup files weren't fully unpacked. Path Mismatch: You moved the installer after starting it.
Registry Errors: Old installation data is confusing the new setup. ✅ How to Fix the MSI Missing Error 1. Re-Download the Full Installer
Often, "web installers" fail because of a temporary network blip. Go back to the official source.
Choose the Full ISO or Standalone Installer instead of the "Web" version. Ensure the file size matches the documentation. 2. Extract Files Manually
If you are running an .exe, it might be failing to extract the .msi to your temp folder. Use a tool like 7-Zip or WinRAR. Right-click the installer and select "Extract to folder." Run the setup.exe from the newly created folder. 3. Point the Installer to the File When the error box pops up: Click Browse. Navigate to the folder where you extracted the setup files. Look for a subfolder named x86, redist, or 1033. Select toolkit documentation-x86-en-us.msi manually. 4. Clear the Windows Installer Cache Old "ghost" installations can block new ones.
Download the Microsoft Program Install and Uninstall Troubleshooter. Run it and select "Installing."
Find the software you are trying to install in the list and let the tool repair the registry. 💡 Pro-Tip for SQL Server Users
If this happens during a SQL Server setup, it is often because the Documentation feature was selected but the media only contains the engine. Try de-selecting "Documentation" or "Books Online" during the feature selection screen to bypass the requirement.
The error "Setup cannot locate toolkit documentation-x86-en-us.msi" typically occurs when installing the Windows Assessment and Deployment Kit (ADK). This happens because the installer cannot find a specific component, often due to an incomplete download, restricted folder permissions, or attempting an offline installation without all required files. 1. Perform an Offline Download (Most Reliable)
The most common cause is a timeout or corruption during a direct online installation. Instead of running the installer directly, download all files first. Run the adksetup.exe file.
In the Specify Location screen, select "Download the Windows Assessment and Deployment Kit for installation on a separate computer".
Choose a local path (like a folder on your desktop) to save the files.
Once the download completes, go to that folder and run adksetup.exe from there to finish the installation. 2. Check Folder Permissions
The installer may fail if it doesn't have permission to write to or read from the download directory.
Change Download Path: Avoid installing directly to system folders or network drives. Try a simple path like C:\ADK_Files.
Run as Administrator: Right-click adksetup.exe and select Run as administrator to ensure it has full system access.
Verify User Rights: Ensure your account has "Back up files and directories" rights, or try installing via the SYSTEM account if you are on a restricted corporate machine. 3. Manually Install the Missing Component
If you have already downloaded the ADK files, you can try to install the specific missing piece manually.
Navigate to your ADK download folder (often found in Installers or a sub-folder).
Search for the file named toolkit documentation-x86_en-us.msi. Double-click this file to install it individually. After it installs, restart the main adksetup.exe. 4. Download a Fresh Installer
If the steps above fail, your initial installer file might be corrupt. Delete your current adksetup.exe.
Download the latest version directly from the official Microsoft ADK download page.
Ensure you are downloading the version that matches your Windows OS (e.g., Windows 10 vs. Windows 11). Install the Windows ADK offline - Microsoft Learn
Conclusion
The "setup cannot locate toolkit documentation-x86-en-us.msi" error is a classic Windows Installer path resolution problem. While it looks intimidating, it is almost always fixable without reinstalling your entire operating system.
Start with Method 1 (locating the file manually), then proceed to Method 3 (Windows Installer cache), and finally Method 4 (registry cleanup) if necessary. In 90% of cases, one of these three methods will resolve the issue.
If you are still stuck, check the Windows Event Viewer (under "Applications and Services Logs" > "Microsoft" > "Windows" > "Installer") for the exact ProductCode GUID. Copy that GUID and search Microsoft’s support forums for a version-specific solution.
Have a different version of this error? Look for variations like toolkit documentation-x64-en-us.msi or toolkit documentation-ja-jp.msi – the same solutions apply; just substitute your language and architecture.
Last updated: October 2024. This guide is maintained for Windows 10/11 and Visual Studio 2010-2022.
Method 3: Manually Edit the Registry (For Advanced Users)
If you know exactly which product is broken:
- Press
Win + R, typeregedit, and press Enter. - Navigate to:
HKEY_CLASSES_ROOT\Installer\Products - This folder contains GUIDs (long strings of characters). This is tedious, so instead, search for the file name:
- Press
Ctrl + Fand search fortoolkit documentation.
- Press
- Delete the registry key that contains the reference to the missing
.msi. - Backup your registry first!
Fix: “Setup Cannot Locate Toolkit Documentation-x86-en-us.msi” Error
There is nothing more frustrating than a clean installation or an important software update grinding to a halt because of a missing file. If you are a developer working with Microsoft Visual Studio, Windows SDK, or Intel Parallel Studio, you might have encountered this cryptic error message:
"Setup cannot locate toolkit documentation-x86-en-us.msi"
Don’t worry. This isn’t a sign that your hard drive is failing. It is a specific, well-known pathing issue related to Windows Installer caching. Here is why it happens and, more importantly, how to fix it.


