Troubleshoot Microsoft 365 Office 365 ProPlus SCCM Installation Errors
Question details
The user needs to resolve Office 365 ProPlus deployments through SCCM that fail when the Click-to-Run bootstrapper exits with a nonzero error code.

- Product
- Microsoft 365 / Office 365 ProPlus
- Device & OS
- not provided
- Scenario
- An IT administrator is deploying Office 365 ProPlus through Microsoft Endpoint Configuration Manager and needs to diagnose a failed deployment.
- Observed behavior
- The Click-to-Run bootstrapper exits with a nonzero error code, causing the SCCM deployment to report failure.
Before troubleshooting, collect the complete bootstrapper log, SCCM deployment configuration, and Office installation XML from the failing deployment. Also confirm the exact nonzero error code and verify that the Office 365 ProPlus Click-to-Run source content is available on the distribution points.
Collect SCCM and Click-to-Run Deployment Logs for Root Cause Analysis
Use this first when Office 365 ProPlus exits with a nonzero error code so you can identify the cause or get accurate community support.
Microsoft Office 365 ProPlus deployments through SCCM are managed by the Click-to-Run bootstrapper. The bootstrapper and SCCM logs together show whether the failure occurs during content download, configuration parsing, or Click-to-Run installation.
In the Configuration Manager console, go to Monitoring > Deployments and locate the failing Office 365 ProPlus deployment.
On the affected client, open C:\Windows\CCM\Logs and review AppEnforce.log for the returned exit code and command line.
Open %temp% and collect the Office Click-to-Run bootstrapper log named with the deployment timestamp, then save it with the SCCM deployment configuration and Office installation XML.

Verify SCCM Deployment Type, Content Distribution, and Office Installation XML
Use this when the deployment fails before the Office application is installed, or when the error points to missing or invalid source content.
Use WPS Office as a Free Microsoft Office Alternative When SCCM Deployments Fail
When Office 365 ProPlus SCCM deployments repeatedly fail, WPS Office provides a free, lightweight alternative that opens and saves Microsoft Word, Excel, and PowerPoint files with a familiar ribbon interface, reducing deployment overhead and avoiding Click-to-Run bootstrapper errors.
- 1. Download WPS Office: Go to the WPS Office download page and get the free installer for Windows.
- 2. Open existing Microsoft Office files: Launch WPS Writer, Spreadsheets, or Presentation and open your .docx, .xlsx, or .pptx files directly.
- 3. Set WPS Office as the default: In Windows Settings > Apps > Default apps, choose WPS Office for Word, Excel, and PowerPoint file types.

Frequently Asked Questions
Why does Office 365 ProPlus fail in SCCM with a nonzero exit code?
The Click-to-Run bootstrapper can fail because of content distribution, XML configuration, update settings, or client prerequisite issues. Check AppEnforce.log on the client and the bootstrapper log in %temp% for the specific return code.
Which logs do Microsoft support communities need for Office 365 ProPlus SCCM errors?
Include the complete Click-to-Run bootstrapper log, SCCM deployment configuration, Office installation XML, and the exact error code when posting in Microsoft TechNet or the Configuration Manager community.
Can WPS Office open and save Microsoft Office 365 files?
Yes. WPS Office supports Word .docx, Excel .xlsx, PowerPoint .pptx, and other Microsoft Office formats, so existing documents can be opened and edited without conversion.
Is WPS Office easier to deploy than Office 365 ProPlus through SCCM?
WPS Office uses a standard Windows installer that can be deployed with SCCM or installed directly, without the Office Click-to-Run bootstrapper that causes the nonzero exit code issue.
What should I do if I must continue using Office 365 ProPlus?
Open a case in Microsoft TechNet or the Configuration Manager community and provide the deployment logs and Office installation XML. WPS does not modify Microsoft Office Click-to-Run installation behavior.




