Home › Microsoft 365 Apps › 0xC0000034

Microsoft 365 Apps · 0xC0000034 · Windows 10 / Windows 11

M365 Apps Install Fail 0xC0000034 Win10/11 ODT

Caused by missing source files or corrupted registry state from prior installs. Fix by scrubbing Office with SDS tool and verifying CDN connectivity.

Error Details

FactValueSourceNote
Exact error string0xC0000034 (Object Name not found)%temp%\OfficeMsi\Office\Data\OfficeMsi.logIndicates missing source or registry corruption
Affected OS Build RangeWindows 10 / Windows 11System InfoApplies to all supported builds
Registry Key InvolvedHKLM\SOFTWARE\Microsoft\Office\ClickToRunRegistry EditorOrphaned MSI entries block installer
Relevant Endpoint URLofficecdn.microsoft.com:443PowerShell Test-NetConnectionCDN must be reachable for download
Log Line SignatureMsiInstaller Event ID 1004Event Viewer > ApplicationMarks installation failure in logs

Log Files to Check

What This Error Actually Means

The error code 0xC0000034, formally defined as STATUS_OBJECT_NAME_NOT_FOUND, is a low-level Windows NT status code indicating that the system attempted to access an object (file, registry key, or network resource) by name but failed to locate it. In the context of Microsoft 365 Apps deployment via the Office Deployment Tool (ODT), this is not merely a generic "file missing" error; it signifies a critical failure in the Click-to-Run (C2R) installer's ability to resolve its source path or validate its local state against the expected configuration. The component raising this error is typically the Windows Installer service (MsiInstaller) interacting with the Office C2R engine. When the ODT attempts to execute a /configure action, it queries the local registry and file system for existing installation states or source files defined in the configuration.xml. If the specified path—whether a local network share, a CDN endpoint, or a cached download directory—does not exist or is inaccessible due to permission or network constraints, the installer throws 0xC0000034. This error often masks deeper issues such as corrupted registry hives under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun where version strings point to non-existent update channels, or scenarios where a previous uninstallation process was interrupted, leaving orphaned references that the new installer cannot resolve.

Affected Versions and Scope

This error is prevalent across both Windows 10 (versions 1809 through 22H2) and Windows 11 (versions 21H2 through 23H2), particularly in environments utilizing semi-annual or monthly channel updates for Microsoft 365 Apps. It frequently affects tenants that have recently migrated from perpetual licenses (Office 2019/2021) to subscription-based models, as the residual registry entries from the MSI-based installations can conflict with the C2R architecture. The scope is broad but specific: it primarily impacts devices managed via Microsoft Intune or Group Policy where the deployment XML explicitly defines a Version attribute that has since been retired from the CDN, or where the SourcePath points to a network share that is currently offline or experiencing latency issues. Devices enrolled in Autopilot scenarios are particularly susceptible if the initial provisioning package references a local content source that was not properly staged on the device before the installation trigger fired. Conversely, this error is rare in environments using the "Current" channel without hardcoded version constraints, as the ODT dynamically resolves the latest available build from officecdn.microsoft.com, bypassing static path resolution failures.

Where To Look First: Logs and Event IDs

To diagnose this issue effectively, you must correlate data from multiple logging sources. The primary source of truth is the Office MSI log file located at %temp%\OfficeMsi\Office\Data\OfficeMsi.log. Search this file for the literal string 0xC0000034 to identify the exact moment the installer failed to resolve an object. You will often see preceding lines indicating a failure to open a file handle or a registry key. Additionally, check the Windows Event Viewer under Applications and Services Logs > Microsoft > Office > ClickToRun for detailed C2R engine events. Crucially, monitor the Application log for MsiInstaller Event ID 1004, which indicates a fatal error during installation. The event description will often reference the specific product code or feature that failed. For network-related causes, verify connectivity to the CDN using PowerShell: Test-NetConnection officecdn.microsoft.com -Port 443. If this test fails, the issue is likely network-based rather than local corruption. Also, inspect C:\Windows\Temp\OfficeMsi\*.log for any additional verbose output that may have been generated during the failed attempt.

Root Causes

Orphaned Registry Entries from Previous Installations

A common cause is an incomplete removal of a previous Office installation. If the uninstall process was interrupted or failed, registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun may remain, pointing to version numbers or update channels that no longer exist. The ODT reads these keys to determine the current state and attempts to apply updates or patches based on this stale data, resulting in a "not found" error when it tries to access resources associated with those invalid versions.

Inaccessible Source Path or CDN Connectivity Issues

If your configuration.xml specifies a SourcePath (e.g., a local network share like \\server\office_source) and that path is unreachable due to network latency, firewall rules, or authentication failures, the installer cannot locate the required files. Similarly, if the device cannot reach officecdn.microsoft.com:443, the fallback mechanism may fail if the local cache is empty or corrupted.

Hardcoded Version Mismatch

Specifying a specific Version in your deployment XML that has been superseded and removed from the CDN will cause this error. Microsoft regularly retires older builds, and if your configuration requests a version that is no longer available, the installer cannot find the object (the specific build files) and fails with 0xC0000034.

Fix Procedure

  1. Verify Network Connectivity: Ensure the device can reach the CDN. Run Test-NetConnection officecdn.microsoft.com -Port 443 in an elevated PowerShell session. If this fails, troubleshoot network proxies or firewall rules.
  2. Remove Orphaned Office Installations: Use the Microsoft Support and Recovery Assistant (SaRA) or the Office Scrub Tool to completely remove any existing Office installations. This ensures that all registry keys and files are cleaned up. Do not manually delete registry keys unless you are certain of their contents.
  3. Update Deployment Configuration: Edit your configuration.xml to remove the hardcoded Version attribute. Instead, use the Channel attribute (e.g., Current, SemiAnnual) to allow the ODT to pull the latest available build. Ensure the SourcePath is correct and accessible if using a local source.
  4. Pre-cache Source Files: Run the ODT with the /download switch before configuring. This ensures all necessary files are downloaded to the local cache, reducing the risk of network-related failures during installation. Example: setup.exe /download configuration.xml.
  5. Reinstall Microsoft 365 Apps: Run the ODT with the /configure switch using your updated XML file. Monitor the logs at %temp%\OfficeMsi\Office\Data\OfficeMsi.log for successful completion.
  6. Verify Installation: Check the Microsoft 365 Apps admin center Deployment Health dashboard to confirm the device is now reporting as healthy. Additionally, verify that the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun contains valid version information.
Warning: Manually deleting registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun can cause further instability and may prevent future installations. Always use the official Office Scrub Tool or SaRA for removal.

Error Code Variants

Error Code Description Distinguishing Factor
0xC0000034 Object Name not found Specifically indicates a missing file, registry key, or network resource referenced by name.
0x80070002 File not found Generic Windows error for missing files; often seen in earlier stages of installation before C2R engine engagement.
0x80070005 Access Denied Indicates permission issues rather than missing objects; usually related to user rights or file locks.
0x80072EE2 Network Connection Failed Specifically indicates a failure to connect to the internet or CDN, rather than a missing object on a reachable path.

Verification

To prove the fix worked, first check the %temp%\OfficeMsi\Office\Data\OfficeMsi.log for the absence of 0xC0000034 errors and the presence of successful installation markers. Next, verify that MsiInstaller Event ID 1004 is no longer appearing in the Application log. In the Microsoft 365 Apps admin center, navigate to Deployment > Deployment Health and confirm that the device status has changed from "Failed" to "Healthy." Additionally, run Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to ensure no related Intune management errors are occurring. Finally, open any Microsoft 365 application (e.g., Word) and check the account information to verify that the correct version is installed and activated.
Tip: Use dsregcmd /status to quickly verify device enrollment status and Azure AD join state, which can sometimes impact ODT behavior if the device is not properly authenticated with Entra ID.

Prevention

To prevent recurrence, avoid hardcoding specific version numbers in your configuration.xml files. Instead, rely on the Channel attribute to automatically pull the latest stable build from the CDN. Regularly update your local content sources if you are using network shares, ensuring they contain the most recent builds. Implement a monitoring solution that alerts you to MsiInstaller Event ID 1004 errors in real-time, allowing for proactive intervention. Additionally, configure Intune policies to ensure that devices have consistent network access to officecdn.microsoft.com:443. Use the OMA-URI ./Device/Vendor/MSFT/Office/UpdateSettings/UpdateChannel to enforce update channels via policy, ensuring consistency across the tenant. Finally, schedule regular maintenance tasks to run the Office Scrub Tool on devices that have failed installations, ensuring a clean slate for future deployments.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.