Home › Microsoft Outlook › 0x8004010F

Microsoft Outlook · 0x8004010F · Microsoft 365 Apps / Outlook 2019 / Outlook 2021

Outlook Error 0x8004010F: Send/Receive Failed (M365/2019)

Caused by corrupted OST/PST or invalid profile paths. Fix by running scanpst.exe or creating a new Outlook profile.

Error Details

FactValueSourceNote
Exact error stringThe operation failed. An object cannot be found.Outlook UI Error Bar / PopupAppears during Send/Receive
Affected build rangeMicrosoft 365 Apps, Outlook 2019, Outlook 2021Product DocumentationApplies to all modern Outlook versions
Registry key involvedHKCU\Software\Microsoft\Office\16.0\Outlook\ProfilesWindows Registry Editor (regedit)Contains profile configuration data
Relevant service/endpointExchange ActiveSync / MAPI over HTTPOutlook Connectivity DiagnosticsRequired for OST synchronization
Log line signatureEvent ID 39, Source: OutlookWindows Event Viewer > ApplicationIndicates application error during startup or sync

Log Files to Check

What This Error Actually Means

The error code 0x8004010F, accompanied by the literal string "The operation failed. An object cannot be found," is a critical failure within the Microsoft Outlook client's MAPI (Messaging Application Programming Interface) subsystem. This specific HRESULT indicates that the Outlook process attempted to access a COM object or a file system resource that it expected to exist but could not locate or instantiate. In the context of email transmission and reception, this almost invariably points to a disconnect between the Outlook profile configuration stored in the Windows Registry and the actual state of the local data files (.ost or .pst) on the disk.

Unlike transient network timeouts, which might yield different HTTP status codes or MAPI_E_NETWORK errors, 0x8004010F is a structural integrity error. The component raising this exception is typically the Outlook Data File manager (MAPI32.dll) when it attempts to bind to the default delivery folder defined in the user's profile. When the path specified in the registry points to a null location, a deleted file, or a file that has been locked by another process (such as OneDrive sync), the MAPI subsystem throws this exception because the "object" (the data store) is effectively missing from the runtime environment.

Affected Versions and Scope

This issue is prevalent across the modern Microsoft 365 Apps suite, specifically affecting Outlook 2019, Outlook 2021, and the continuously updated Microsoft 365 (Office 365) builds. It is particularly common in environments utilizing Cached Exchange Mode, where the local .ost file serves as the primary interface for user interaction. The error does not typically manifest in Outlook on the Web (OWA) or mobile clients, as those platforms do not rely on local MAPI profile structures in the same manner.

The scope of impact is highest in tenants enforcing aggressive roaming profile policies or those using OneDrive Known Folder Move (KFM). When KFM redirects the Documents or Desktop folders, it can inadvertently conflict with Outlook's default data file storage locations if not configured correctly. Additionally, organizations migrating from on-premises Exchange to Exchange Online may see spikes in this error during the transition period if profile caches are not properly invalidated. It is important to note that this error is distinct from authentication failures (such as 0x8004011D) and is strictly related to object resolution and file system accessibility.

Where To Look First: Logs and Event IDs

When diagnosing 0x8004010F, immediate inspection of the Windows Event Viewer is required. Navigate to Windows Logs > Application and filter for Source: Outlook. You are looking specifically for Event ID 39. This event log entry will often contain the exact HRESULT and a brief description of the failed operation, confirming that the issue is internal to Outlook rather than a network connectivity problem.

For deeper diagnostics, enable verbose logging in Outlook by holding the CTRL key while launching the application and selecting "Turn on verbose logging." The resulting log file will be located at %LOCALAPPDATA%\Microsoft\Outlook\Outlook.log. Search this file for the string 0x8004010F or MapiExceptionNotFound. Additionally, check the Click-to-Run logs at C:\ProgramData\Microsoft\Office\ClickToRun\Logs\OfficeC2R.log to rule out any background update interference that might be locking the .ost file during a sync cycle.

Root Causes

Corrupted or Missing Default Data File (.ost/.pst)

The most frequent cause is that the default data file referenced in the Outlook profile has been deleted, moved, or corrupted. This often occurs after a forced logoff during an active sync, a power failure, or an aggressive antivirus scan quarantining the .ost file. If the file system path no longer resolves to a valid MAPI store, Outlook cannot initialize the session.

Registry Profile Corruption

The user profile configuration stored under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Profiles may contain stale references. If an administrator changed the mailbox location via Group Policy or Intune, but the local registry was not updated correctly, Outlook will attempt to access a non-existent object path.

OneDrive Sync Conflicts

If OneDrive is syncing the folder containing the .ost file (often due to misconfigured Known Folder Move), it may lock the file or replace it with a placeholder. This results in the "object not found" error because the MAPI subsystem cannot obtain an exclusive handle on the data file.

Fix Procedure

  1. Verify Device Enrollment and Management Status: Before modifying local profiles, ensure the device is properly managed to prevent policy reversion. Run the following PowerShell cmdlet to check the enrollment type: Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
  2. Check for Active Sync Conflicts: Use the Graph API to verify the device's last sync status and ensure no pending configuration profiles are blocking Outlook. Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices"
  3. Inspect Autopilot Configuration: If this is a newly imaged device, verify that the Autopilot profile did not interfere with local user data paths. Get-AutopilotDevice | Where-Object serialNumber -eq $serial
  4. Review Device Management Logs: Check for any recent policy application errors that might have corrupted the Outlook configuration. Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50
  5. Warning: Do not manually delete the HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook key while Intune is actively pushing a configuration profile. This can cause the device to enter a repair loop, potentially breaking other Office applications. Always disable the relevant Intune policy temporarily if you must perform manual registry edits.
  6. Repair or Rebuild the Profile:
    • If the .ost file is corrupted, run C:\Program Files (x86)\Microsoft Office\root\Office16\SCANPST.EXE. Locate the .ost file (usually in %LOCALAPPDATA%\Microsoft\Outlook) and repair it.
    • If repair fails, create a new profile: Control Panel > Mail > Show Profiles > Add. Configure the account anew and set it as default.
  7. Apply OMA-URI Configuration: To prevent future cache inconsistencies, enforce a specific OST size limit via Intune. Navigate to Intune admin center > Devices > Configuration profiles > Create profile. Use the following OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Outlook~policy~config~cache/MaxCacheSizeMB Set the value to an appropriate integer (e.g., 5000) to ensure consistent cache behavior.
  8. Verify Domain Join Status: Ensure the device is correctly joined to Entra ID, as hybrid join issues can sometimes affect profile loading. dsregcmd /status
Tip: Use the Outlook /cleanviews switch from the Run dialog to reset all view settings. While this does not fix 0x8004010F directly, it eliminates view corruption as a secondary symptom that often accompanies profile issues, speeding up post-fix verification.

Error Code Variants

Error Code Description Distinguishing Factor
0x8004010F Object not found Local file/registry mismatch. No network dependency.
0x8004011D Authentication failed Credential issue. Usually resolves with password reset or MFA prompt.
0x80072EE2 Network timeout Connectivity issue. Resolves when network is restored.
0x8004060C MAPI_E_NOT_FOUND Similar to 10F, but often relates to specific item IDs within a valid store, not the store itself.

Verification

To confirm the resolution, launch Outlook and initiate a Send/Receive cycle. Monitor the Windows Event Viewer for the absence of Event ID 39. Additionally, check the %LOCALAPPDATA%\Microsoft\Outlook\Outlook.log file to ensure no new instances of MapiExceptionNotFound are logged. In the Intune admin center, navigate to Devices > Monitoring > Device compliance to verify that the device remains compliant and no configuration drift has occurred due to the profile rebuild.

Prevention

To prevent recurrence, enforce a standardized Outlook configuration via Intune. Navigate to Intune admin center > Devices > Configuration profiles and deploy an ADMX-backed policy for Outlook. Specifically, configure "Set the default data file path" to a location outside of OneDrive sync folders (e.g., %LOCALAPPDATA%\Microsoft\Outlook). Additionally, implement a scheduled task or Intune script that runs SCANPST.EXE periodically on detected .ost errors, or configure Group Policy to disable roaming profiles for Outlook data files entirely. Regularly audit the HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Profiles registry key via PowerShell scripts deployed through Intune Proactive Remediations to detect and correct path mismatches before they cause user-facing errors.

Sources & References

Get new error code fixes by email

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