OneDrive Sync Client Crashing on Windows 11 Startup

When the OneDrive sync client crashes on Windows 11 startup, the application icon either flashes briefly in the system tray before disappearing or terminates immediately upon user sign-in without displaying an error message. Because the background sync process (OneDrive.exe) fails to stay running, changes made across your paired devices or cloud applications stop synchronizing with your local drive.

Fast Fix:

Perform a full sync client reset to clear corrupted startup cache files. Press Windows Key + R, paste %localappdata%\Microsoft\OneDrive\onedrive.exe /reset, and press Enter. Wait two minutes for the application to reinitialize. If the icon does not reappear in your system tray, manually launch it by running %localappdata%\Microsoft\OneDrive\onedrive.exe.

Diagnostic Snapshot

• Common Root Causes: Corrupted local telemetry logs or sync catalog (SyncEngine.odc), damaged registry startup run keys, file system permission blocks within the user profile, or conflicts with the Windows 11 Cloud Files Filter driver (cldflt.sys).
• Operational Risk: Low risk to stored cloud assets. However, local modifications made while the client is down will remain unsynced until the background engine stabilizes.
• Escalation Indicator: If the application crashes silently with Event ID 1000 (faulting module ntdll.dll or KERNELBASE.dll) across all user profiles on the device, a full binary reinstallation is required.

Why OneDrive Crashes During Windows 11 Startup

During the Windows 11 login sequence, OneDrive initializes through the user’s startup registry entry (HKCU\Software\Microsoft\Windows\CurrentVersion\Run), hooks into the File Explorer namespace, and mounts the local cache database.

The startup sequence collapses when:

• The Local Metadata Cache is Corrupted: If the sync engine encounters an unreadable database transaction log or invalid file hashes during initial enumeration, it may throw an unhandled exception and shut down rather than proceeding to Scanning Files.
• Cloud Files Filter Initialization Fails: Windows 11 relies on the cldflt.sys mini-filter driver for Files On-Demand placeholders. If this service fails to attach during early system boot, OneDrive cannot bind its virtual root and exits, occasionally surfacing.
• Corrupted Windows Credentials: If stored authentication tokens in Windows Credential Manager become malformed, the client’s silent background authentication sequence can terminate abruptly instead of displaying the standard login dialog.

Step-by-Step Resolution Path

Follow these actions in order, moving from lightweight cache resets to startup configuration fixes and complete reinstallation.

1. Execute a Clean Sync Engine Reset

Resetting OneDrive rebuilds the local metadata index and purges corrupted configuration cache files without deleting your local documents or cloud data.

1. Press Windows Key + R to open the Run dialog box.
2. Enter the following command and click OK:DOS %localappdata%\Microsoft\OneDrive\onedrive.exe /reset
3. The OneDrive icon will disappear from your taskbar.
4. Wait approximately two minutes. If OneDrive does not restart automatically, open Run again and execute:DOS %localappdata%\Microsoft\OneDrive\onedrive.exe

2. Repair Corrupted Windows Startup Entries and Shortcut Hooks

If the application launches manually from the Start Menu without issues but consistently crashes upon automatic system boot, the startup trigger is misconfigured.

1. Press Ctrl + Shift + Esc to open Task Manager and navigate to the Startup apps tab.
2. Locate Microsoft OneDrive, right-click it, and toggle it to Disabled.
3. Press Windows Key + R, type shell:startup, and press Enter.
4. Check if an outdated or invalid OneDrive shortcut exists in this folder; if present, delete it.
5. Launch OneDrive manually from the Windows Start menu, open Settings (gear icon) > Settings > Sync and backup, and toggle Start OneDrive when I sign in to Windows back on. This rebuilds the official Run registry key cleanly.

3. Clear Stale Windows Credentials and Identity Tokens

Damaged authentication payloads can crash the silent boot process:

1. Press Windows Key + S, type Credential Manager, and select Windows Credentials.
2. Under Generic Credentials, locate and remove all entries beginning with:
   • OneDrive Cached Credential
   • MicrosoftAccount:user=
3. Restart your computer and launch OneDrive to sign in with fresh authentication tokens.

4. Perform a Clean Reinstallation of the 64-bit Client

If the sync executable crashes across system reboots due to damaged application binaries:

1. Press Windows Key + R, type appwiz.cpl, and press Enter.
2. Locate Microsoft OneDrive in the program list and select Uninstall.
3. Clear remaining local application remnants by deleting the following temporary directories (your synchronized files will remain unaffected):
   • %localappdata%\Microsoft\OneDrive
   • %programdata%\Microsoft OneDrive
4. Download the latest 64-bit production build directly from Microsoft’s official deployment portal.
5. Run the installer, sign in to your Microsoft account, and re-link your existing OneDrive sync folder.

Escalation & Enterprise Admin Checks

• Windows Event Viewer Diagnostic (Event ID 1000): If OneDrive continues crashing after a clean reinstall, open Event Viewer (eventvwr.msc), navigate to Windows Logs > Application, and filter by Error source Application Error. Check whether third-party endpoint security software or shell extensions (such as external backup utilities or DLP agents) are hooking into FileSyncShell.dll and causing stack corruption.
• Group Policy / Intune Restrictions: On organization-managed PCs, verify whether a conflicting Intune configuration profile or Group Policy setting has disabled personal account syncing while attempting to enforce single-sign-on (SSO).