When you contact Microsoft Support for a OneDrive for Business issue, the first request is often to collect and share diagnostic logs. These logs contain detailed records of sync operations, file conflicts, authentication errors, and system events that help engineers identify the root cause. Without these logs, support teams cannot see what the OneDrive client is actually doing behind the scenes. This article explains how to generate a complete set of OneDrive logs, how to attach them to a support case, and what each log file contains so you can provide the right information the first time.
Key Takeaways: Collecting OneDrive Logs for Support
- OneDrive Settings > Help & Settings > Collect logs: Generates a ZIP file containing all sync logs, registry snapshots, and system information for the current user.
- Windows Event Viewer > Applications and Services Logs > Microsoft > Windows > OneDrive > Operational: Contains real-time sync events that complement the collected logs.
- %localappdata%\Microsoft\OneDrive\logs: The default folder where OneDrive stores individual log files; you can also manually copy these for analysis.
What OneDrive Logs Contain and Why They Are Needed
OneDrive for Business logs capture every action the sync client performs, including file uploads, downloads, conflict resolution, and error messages. The logs are stored as plain-text files with a .log extension and are rotated automatically to prevent disk space issues. When you use the built-in log collection tool, OneDrive packages the following items into a single ZIP file:
Sync Client Logs
These files, named OneDrive.log and OneDrive.1.log through OneDrive.9.log, record every file operation. Each entry includes a timestamp, a thread ID, a severity level, and a description of the action. Support engineers use these logs to trace a specific file through the sync pipeline and identify where it failed.
Registry and System Information
The collection tool exports a snapshot of OneDrive-related registry keys under HKEY_CURRENT_USER\Software\Microsoft\OneDrive. It also captures the current Windows version, OneDrive client version, and installed updates. This data helps support determine whether the issue is caused by a known bug that was fixed in a later version.
Network and Authentication Details
Some log files include HTTP request and response headers, authentication token status, and proxy configuration. These details are essential for diagnosing connectivity problems, such as when OneDrive cannot reach Microsoft 365 servers or when an authentication prompt loops repeatedly.
Steps to Collect and Share OneDrive Logs
Follow these steps to generate a complete log package and attach it to your support case. Perform these steps on the computer where the problem occurs, while the issue is still happening if possible.
- Open OneDrive Settings
Right-click the OneDrive cloud icon in the Windows system tray notification area. Select Help & Settings from the menu, then choose Settings from the submenu. If the icon is missing, open OneDrive from the Start menu or search for OneDrive in Windows Search. - Navigate to the Help tab
In the OneDrive Settings window, click the Help & Settings tab. This tab contains links to support resources and diagnostic tools. The exact label may read Help or About depending on your OneDrive version. - Click the Collect logs button
Under the Help section, click Collect logs. OneDrive immediately begins gathering all log files, registry snapshots, and system information. A progress indicator appears and typically completes within 30 seconds. - Locate the generated ZIP file
After collection finishes, a File Explorer window opens automatically. The ZIP file is named OneDriveLogs- followed by a date and timestamp, for example OneDriveLogs-2025-04-01-143200.zip. The file is saved to your Desktop by default. Do not rename or modify the ZIP file. - Upload the ZIP file to your support case
Sign in to the Microsoft 365 admin center or the Microsoft Support portal where your service request is open. Locate the option to attach files, which is usually under the Files or Attachments section of the case. Select the ZIP file and upload it. If the file is larger than 250 MB, compress it further using a tool like 7-Zip, or contact support for an alternative upload method.
If OneDrive Logs Are Not Enough: Additional Diagnostic Data
In some cases, the standard log collection does not capture enough detail for complex issues. Microsoft Support may request additional data, including Windows Event Viewer logs and network traces. The following subsections explain how to provide these extra diagnostics.
OneDrive Stops Syncing Without Error Messages
When OneDrive appears to be running but files do not sync and no error is shown, the issue is often a stuck sync engine or a corrupted database. The standard logs may not contain the exact failure point. In this scenario, open Windows Event Viewer by pressing Windows Key + R, typing eventvwr.msc, and pressing Enter. Navigate to Applications and Services Logs > Microsoft > Windows > OneDrive > Operational. Right-click the Operational log and select Save All Events As. Save the file as an .evtx file and attach it to your support case along with the standard ZIP.
OneDrive Fails to Start or Crashes Repeatedly
A crash at startup typically points to a corrupted OneDrive installation or conflicting third-party software. In addition to the standard logs, collect a Process Monitor trace. Download Process Monitor from the Microsoft Sysinternals website. Run it as administrator, start the trace, reproduce the crash, then stop the trace and save the log as a .pml file. Compress the .pml file with ZIP before uploading, as these files can be large.
OneDrive Shows Incorrect File Status Icons
If the green checkmark, blue cloud, or red X icons do not match the actual sync state, the issue may be a stale icon cache. Standard logs include registry data that can confirm this. To provide more detail, run the OneDrive Diagnostic Tool by right-clicking the OneDrive icon, selecting Help & Settings, then Diagnostic Tool. Click Create diagnostic report and save the resulting .zip file. This report includes additional performance counters and service status information.
OneDrive Built-In Log Collection vs Manual Log Collection
The built-in log collection tool is the recommended method because it gathers all necessary files in a single step. However, you may need to collect logs manually if the OneDrive client cannot start or if the Settings window is inaccessible. The table below compares the two approaches.
| Item | Built-In Log Collection | Manual Log Collection |
|---|---|---|
| Method | OneDrive Settings > Help & Settings > Collect logs | Copy files from %localappdata%\Microsoft\OneDrive\logs |
| Files Collected | All .log files, registry snapshot, system info | Only .log files |
| Registry Snapshot | Included automatically | Not included |
| System Information | Included automatically | Not included |
| When to Use | OneDrive is running and responsive | OneDrive crashes on startup or Settings is broken |
For manual collection, open File Explorer and paste %localappdata%\Microsoft\OneDrive\logs into the address bar. Select all files with the .log extension, right-click, and choose Send to > Compressed (zipped) folder. Name the file and attach it to your support case. Note that this method does not include registry or system information, so support may still request the built-in collection later.
After you have submitted the logs, monitor your support case for follow-up questions. Microsoft Support may ask you to reproduce the issue while a remote diagnostic tool is running. Keep the OneDrive client open and do not restart the computer until the case is resolved.