OneDrive Not Running on PC: Service Dependency Check for Hidden Conflicts

If any of these services are stopped, disabled, or delayed, OneDrive may fail to initialize.

For example, if the Windows Update Service is paused (e.g., due to a manual stop or Group Policy restriction), OneDrive might silently stall during startup, appearing "not running" even though it’s technically in a limbo state.

Why it happens: Windows services have a hierarchy. If a parent service (like RPC Endpoint Mapper) fails, dependent services (like OneDrive’s OneDrive.exe) won’t launch. Use sc query in Command Prompt to check service statuses.

🛡️ Permission or User Profile Corruption

OneDrive ties directly to your Windows user profile. If your profile is corrupted—or if OneDrive lacks the right permissions—it can’t access critical folders (like %LocalAppData%\Microsoft\OneDrive). Common triggers include:

• Partial Windows updates leaving registry keys in an inconsistent state.
• Antivirus software blocking OneDrive’s access to %UserProfile%.
• A failed OneDrive reinstall that didn’t clean up old permissions.

Why it happens: OneDrive requires read/write/execute permissions on your user folder. If your profile is marked as "read-only" (e.g., due to a takeown command gone wrong) or if the SYSTEM account lacks inheritance, OneDrive’s background process (OneDrive.exe) will crash on startup. Check with icacls "%LocalAppData%\Microsoft\OneDrive" to verify.

🔌 Network or Proxy Interference

OneDrive is a cloud-dependent app, so network restrictions can halt it before it even starts. Common offenders:

• Corporate firewalls – Blocking OneDrive’s endpoints (.onmicrosoft.com, .skydrive.com).
• Proxy settings – Misconfigured proxy servers forcing OneDrive to retry failed connections indefinitely.
• VPN conflicts – Some VPNs (like those using Split Tunneling) may isolate OneDrive traffic, causing timeouts.
• Metro Offline Mode – If your network is marked as "public" or "limited," OneDrive may disable sync entirely.

Why it happens: OneDrive’s Network Location Awareness (NLA) service detects your connection type. If NLA classifies your network as "untrusted," OneDrive’s OneDrive.exe process may enter a waiting state, appearing frozen. Use netsh winsock reset to reset network stacks if DNS or proxy issues are suspected.

💾 Storage or Disk Errors

OneDrive needs a healthy disk to sync files. If your system drive (C:) has errors, fragmentation, or low space, OneDrive may fail to launch. Key triggers:

• Low disk space – OneDrive requires at least 1GB free on C: for temp files.
• File system corruption – Bad sectors or NTFS errors in %LocalAppData%.
• BitLocker encryption – If BitLocker is enabled but not fully unlocked, OneDrive may block access to encrypted folders.

Why it happens: OneDrive’s OneDrive.exe process checks disk health during startup. If chkdsk detects errors or if the Page File is corrupted, OneDrive’s initialization thread may fail with Error 0x80070005 (Access Denied). Run chkdsk C: /f in an admin Command Prompt to scan for issues.

🔄 Conflicting Third-Party Software

Security tools, backup apps, or even other cloud services can interfere with OneDrive. Examples:

• Antivirus real-time scanning – Some AVs (like McAfee or Kaspersky) flag OneDrive’s OneDrive.exe as a "suspicious process," quarantining it.
• Disk cleanup tools – Apps like CCleaner may delete OneDrive’s cache (%LocalAppData%\Microsoft\OneDrive\*.dat), forcing a reset.
• Group Policy restrictions – Enterprise policies may block OneDrive’s Windows Shell Extension, preventing it from integrating with File Explorer.

Why it happens: OneDrive’s OneDrive.exe runs in the context of your user session. If another app hooks into DLL files like OneDriveShellExtension.dll, it can cause a DLL conflict, crashing the process. Check Event Viewer (Application Logs) for errors like 0x80004005 (Class Not Registered).