How to Fix OneDrive SyncEngineDatabase.db Write Spikes on C Drive
Question details
The user is experiencing continuous write spikes on their primary drive caused by the OneDrive synchronization database, even when no files are actively syncing.

- Product
- OneDrive
- Device & OS
- Windows
- Scenario
- Monitoring system performance via Resource Monitor and noticing frequent disk I/O spikes every 30 seconds from OneDrive background processes.
- Observed behavior
- The C drive experiences recurring write spikes originating from OneDrive SyncEngineDatabase.db, its WAL file, and temporary etilqs files, despite the OneDrive folder being stored on a separate drive and reporting that synchronization is complete.
Before proceeding, confirm whether you are using a personal or business OneDrive account, and temporarily pause syncing from the OneDrive taskbar icon to see if the disk activity immediately stops.
Restart Your Computer and Install Pending Updates
Background sync loops are often caused by pending system or application updates. A simple restart is the most common and effective fix.
Many users report that recurring write spikes from the OneDrive SyncEngineDatabase resolve themselves unexpectedly after a system reboot. This is frequently tied to background updates applied to Windows or the OneDrive client itself during the restart process.
Press the Windows key + I to open Settings. Click on 'Update & Security' (or 'Windows Update'), and select 'Check for updates' to ensure no updates are stalled in the background.
Click the Start button, click the Power icon, and select 'Restart'. Allow the computer to boot up completely without opening any applications.
Press Ctrl + Shift + Esc to open Task Manager, navigate to the 'Performance' tab, and check your C drive activity to verify if the 30-second write spikes have stopped.

Perform a Windows Clean Boot
A clean boot helps determine if third-party background software (like antivirus or backup tools) is interfering with the OneDrive database.
Create a New Local Administrator Account
If the OneDrive database is stuck in a loop, your Windows user profile might be corrupted. Testing on a new profile can isolate the problem.
Switch to WPS Office for Lightweight File Management
If background sync engines and heavy Microsoft background processes are slowing down your computer and causing high disk I/O, consider switching to WPS Office. It provides a lightweight, fast, and free alternative to Microsoft Office, allowing you to manage your documents without aggressive system resource consumption.
- 1. Download the Installer: Visit the official WPS Office website and download the free version for your operating system.
- 2. Install WPS Office: Run the setup file and follow the quick installation prompts to add the software to your device.
- 3. Enjoy Lightweight Editing: Open any existing Microsoft Office file in WPS Office and experience fast, resource-friendly document editing.

Frequently Asked Questions
Why is SyncEngineDatabase.db writing to my C drive when my OneDrive folder is on the D drive?
By default, OneDrive stores its internal application data, including synchronization databases and transaction logs, in the local AppData directory on your primary system drive (usually the C drive). This happens regardless of where you choose to store your actual synced files.
What are the etilqs files showing up in Resource Monitor?
The etilqs files are temporary SQLite database files generated by the OneDrive sync engine during background transactions. They are normally created and deleted rapidly, but frequent syncing or database loops can cause them to appear prominently in disk usage monitors.
Can I safely delete the SyncEngineDatabase.db file to stop the spikes?
It is not recommended to manually delete this file while OneDrive is running, as doing so can corrupt your synchronization state. If you need to fix a corrupted database, it is much safer to use the official reset command by pressing Windows + R and running '%localappdata%\Microsoft\OneDrive\onedrive.exe /reset'.




