Fix Office Click-to-Run Errors 30029-1007 and 30029-1011
Question details
Resolve Office Click-to-Run deployment errors affecting a language or proofing-tools package.

- Product
- Microsoft 365 Apps and Office Deployment Tool
- Device & OS
- not provided
- Scenario
- An Office administrator is deploying multiple languages or standalone proofing tools using the Office Deployment Tool.
- Observed behavior
- One language or proofing-tools package fails with error 30029-1007 or 30029-1011 while other languages may install successfully.
Locate your Office Deployment Tool setup.exe file and configuration XML. Check which language package failed and whether the configured source folder is accessible from the affected computer.
Check the deployment configuration and download the required files
Use this approach to correct an invalid source path or obtain missing language and proofing-tool files.
Open the deployment XML in a text editor and check the SourcePath, Office architecture, product IDs, and language IDs. Make sure SourcePath points to the intended accessible installation folder.
Use the Office Customization Tool to create or revise the configuration, including the required languages or ProofingTools product. Save the XML alongside setup.exe or note its full path.
Open Command Prompt as administrator, change to the folder containing setup.exe, and run setup.exe /download configuration.xml, replacing configuration.xml with your file name or full path. Let the download finish before installing.
In the same Command Prompt, run setup.exe /configure configuration.xml. Check whether the previously failing language or proofing-tools package installs.
Remove conflicting Office installations and retry
Use this if another Office installation conflicts with the intended deployment.
Add an installed proofing language in Office
Use this when proofing tools install successfully but the language is not yet listed in Office.
Work on Office documents with WPS Office
WPS Office is a free, lightweight alternative with a familiar interface for working on documents, spreadsheets, and presentations. Its Microsoft Office format compatibility makes it easier to move existing files while you resolve Office deployment issues.

Frequently Asked Questions
Why does only one Office language package fail to install?
The files for that language may be missing, the source path may be incorrect, or the language ID may not match the configuration. Check the XML and run setup.exe /download configuration.xml before retrying setup.exe /configure configuration.xml.
How do I check the Office Deployment Tool source path?
Open the configuration XML in a text editor and look for SourcePath in the Add element. Confirm that the folder exists, is accessible, and contains the required downloaded installation files.
Why isn't an installed proofing language listed in Office?
Installing standalone proofing tools may not automatically add the language to the Office language list. Open File > Options > Language in an Office app and add it under Office authoring languages and proofing.
Can I automate adding proofing languages to the Office language list?
The reported deployment confirms that standalone proofing tools can be installed, but it does not establish a tested way to add them automatically to the Office language list. For now, add each language through File > Options > Language, or review Microsoft's current Office language deployment and policy documentation for your environment.




