How to Profile Outlook Startup With Trace Logging Enabled

When Outlook takes too long to start, finding the root cause can feel like guessing in the dark. The problem is often a slow add-in, a corrupt profile, or a network timeout during the initial connection. This article explains how to enable trace logging in Outlook to capture a detailed startup profile, then shows you how to analyze the log file to pinpoint exactly what is slowing down your launch.

Trace logging writes every action Outlook performs during startup to a text file. You can see each module load, registry read, and network call with timestamps. By reading this log, you can identify the specific component that is causing the delay and decide whether to disable an add-in, repair a data file, or reconfigure a mail server setting.

The method described here works for Outlook 2016, Outlook 2019, Outlook 2021, and Outlook for Microsoft 365 on Windows 10 and Windows 11.

What Trace Logging Captures During Outlook Startup

Trace logging records every major event that occurs from the moment you launch Outlook.exe until the interface becomes ready. The log includes the following categories of data.

Module Loading Events

Each DLL and executable that Outlook loads during startup appears in the log with a timestamp. If a module takes more than a few hundred milliseconds to load, that entry indicates a potential bottleneck. Common slow modules include antivirus add-ins, PDF converters, and third-party CRM extensions.

Registry and File Access

Outlook reads its settings from the Windows Registry and from profile files such as NK2 (nicknames), XML, and OST files. Trace logging shows every registry key and file path that Outlook accesses. A delay in reading a large OST file or a corrupted NK2 file shows up as a long gap between two log entries.

Network and Server Requests

Outlook contacts the Exchange server, Autodiscover service, or IMAP/POP3 server during startup. The log records each network request and the time it takes to complete. If the Autodiscover lookup fails or times out, the log contains error codes and retry attempts.

Add-in Initialization

Every COM add-in registered in Outlook has a LoadBehavior value in the registry. Trace logging shows when Outlook attempts to load each add-in and whether the load succeeded or failed. Add-ins that crash or hang during load produce a log entry with a failure code.

Steps to Enable Trace Logging and Capture a Startup Profile

1. Close Outlook completely
   Make sure Outlook is not running. Open Task Manager with Ctrl+Shift+Escape and end any Outlook.exe process on the Details tab.
2. Open a Command Prompt as administrator
   Click Start, type cmd, right-click Command Prompt, and select Run as administrator. Click Yes on the User Account Control prompt.
3. Navigate to the Outlook program folder
   Type cd "C:\Program Files\Microsoft Office\root\Office16" and press Enter. For 32-bit Outlook on 64-bit Windows, use cd "C:\Program Files (x86)\Microsoft Office\root\Office16". Adjust the version number if you use Office 2016, 2019, or 2021.
4. Launch Outlook with the trace logging switch
   Type outlook.exe /log:startup_profile.log and press Enter. Outlook starts normally. The log file is written to your user profile folder, for example C:\Users\YourName\AppData\Local\Microsoft\Outlook\startup_profile.log.
5. Wait for Outlook to fully load
   Let Outlook finish its startup sequence. Do not interact with Outlook during this time. Wait until the status bar shows Connected or Ready.
6. Close Outlook
   Click File > Exit. Closing Outlook finalizes the log file and flushes all buffered entries to disk.
7. Locate and open the log file
   Press Windows+R, type %localappdata%\Microsoft\Outlook, and press Enter. Find the file named startup_profile.log. Open it with Notepad or a text editor that supports large files.

How to Analyze the Startup Log for Slow Components

1. Search for “Duration”
   Press Ctrl+F in the log file and type Duration. Each line that contains Duration shows how long a specific operation took. Large values, anything over 1000 milliseconds, indicate a slow step.
2. Search for “LoadBehavior”
   Add-in loading events appear with the word LoadBehavior. The line shows the add-in CLSID and the time it took to load. Note the CLSID so you can identify the add-in in the registry.
3. Look for gaps between timestamps
   Scan the log for two consecutive entries where the timestamp difference exceeds 2 seconds. That gap represents a blocking operation, such as a network timeout or a file read delay.
4. Identify the specific add-in or service
   If the slow step is an add-in load, open Registry Editor (regedit.exe) and navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Addins. Find the CLSID from the log and read the FriendlyName value to see the add-in name.
5. Disable or repair the offending component
   For a slow add-in, disable it in File > Options > Add-ins > Manage COM Add-ins. For a corrupt OST file, close Outlook, delete the OST file from %localappdata%\Microsoft\Outlook, and let Outlook rebuild it. For a network timeout, check your DNS settings and firewall rules for the Autodiscover endpoint.

If Trace Logging Does Not Capture Enough Data

Outlook starts too fast to capture a meaningful log

If Outlook starts in under 5 seconds, the log may be short and contain few events. In that case, add a startup delay by launching Outlook with the /safe switch first, then close it and relaunch with trace logging. Alternatively, use the registry method to enable logging permanently. Set HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options\Mail\OPMLogEnabled to DWORD value 1, restart Outlook, and then check the log file in %temp% named OPMLog.log.

The log file is empty or contains only header information

This usually means Outlook did not fully close before you launched it with the /log switch. Ensure all Outlook.exe processes are terminated in Task Manager. Also verify that you are running the command prompt as administrator. If the problem persists, delete the existing log file, restart your computer, and repeat the steps.

Trace logging causes Outlook to crash on startup

A very slow or crashing startup may be caused by a corrupted profile or a malfunctioning add-in. In this case, start Outlook in safe mode by holding Ctrl while clicking the Outlook icon, then run trace logging from safe mode. Safe mode disables all add-ins, so the log will be smaller but will not show add-in load times. You can then enable add-ins one by one to isolate the crash.

Item	Trace Logging via Command Line	Trace Logging via Registry
Activation method	outlook.exe /log:filename.log	Set OPMLogEnabled DWORD to 1
Log file location	%localappdata%\Microsoft\Outlook	%temp% folder
Persistence	One session only	Until you delete the registry key
Best for	One-time profiling of a specific issue	Ongoing monitoring of slow startups

You can now enable trace logging, capture a detailed startup profile, and identify the specific component that is delaying Outlook. After you find the slow add-in, profile, or network call, apply the appropriate fix such as disabling the add-in, repairing the OST file, or adjusting your DNS settings. As an advanced tip, you can automate the log capture by creating a batch file that runs outlook.exe /log:profile_%date:~-4,4%%date:~-10,2%%date:~-7,2%.log and saves logs with date-stamped filenames for comparison across multiple startup attempts.