This guide shows you how to change where Windows 10 stores its Event Log files (the .evtx files that contain system, application, and security logs). By default, these files are stored in C:\Windows\System32\winevt\Logs, but you can move them to another drive or folder—useful if you want to free up space on the system drive, keep logs on a faster SSD, or centralize them for easier backup. You’ll need administrative access to your PC, and you’ll be editing the Windows Registry, so proceed carefully.
What You’ll Need
- An account with administrator privileges on the Windows 10 PC.
- A destination folder that already exists (or you’ll create one during the steps).
- Basic comfort with the Registry Editor (regedit).
Step-by-Step
- Create the new folder where you want the Event Logs to live. For example, create
D:\EventLogsusing File Explorer. Make sure the drive has enough free space—logs can grow large over time. - Open Registry Editor by pressing
Win + R, typingregedit, and pressing Enter. Click “Yes” if prompted by User Account Control. - Navigate to the Event Log registry key by pasting this path into the address bar and pressing Enter:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog - Find the log you want to move. Under the
EventLogkey, you’ll see subkeys likeApplication,System,Security,Setup, and others. Each represents a separate log. To move all logs, you’ll repeat the next steps for each subkey, but you can start with one to test. - Modify the
Filevalue. In the right pane, double-click theFilevalue (it’s of type REG_EXPAND_SZ). In the “Value data” field, enter the full path to your new folder, including the file name. For example:D:\EventLogs\Application.evtx. Click OK. - Repeat for other logs as desired. For each subkey (e.g.,
System,Security), change theFilevalue to point to your new location, using a unique file name for each log (e.g.,System.evtx,Security.evtx). - Restart the Windows Event Log service for the changes to take effect. Open an elevated Command Prompt (right-click Start > “Windows Terminal (Admin)” or “Command Prompt (Admin)”) and run:
net stop eventlogthennet start eventlog. Alternatively, restart your PC. - Verify the new location. Open Event Viewer (press
Win + Xand select “Event Viewer”), then look at any log. The logs should now be stored in your new folder. You can also check the folder to see the .evtx files appearing.
Common Mistakes
- Typing the path incorrectly—a single wrong character will prevent the service from starting. Double-check the path in the registry.
- Forgetting to include the .evtx extension—the File value must end with .evtx, or Windows may not recognize it.
- Moving only one log—if you want all logs moved, you must change each subkey individually. Missing one leaves that log in the old location.
- Not creating the destination folder—if the folder doesn’t exist, the service may fail to start. Create it before editing the registry.
- Editing the wrong registry key—make sure you’re under
Services\EventLog, notEventLog\Securityor similar. The path must be exact.
Tips
- Back up the registry before making changes. In Registry Editor, right-click the
EventLogkey and select “Export” to save a .reg file. If something goes wrong, you can double-click that file to restore. - Use a dedicated drive for logs to avoid filling up the system drive. Logs can grow to several gigabytes over time.
- Consider the impact on performance—if you move logs to a slower drive, writing events may take slightly longer, though for most systems this is negligible.
- Test with one log first to ensure the process works before changing all logs.
- Keep the original folder in place—don’t delete the old .evtx files immediately. After confirming the new location works, you can delete old files to free space, but keep a backup if you need historical logs.
Troubleshooting
If the Event Log service fails to start after making changes, here’s what to check:
- Event Log service won’t start—open Event Viewer (if it opens) or check the system event log via a different method. The most common cause is an invalid path in the registry. Reopen Registry Editor and verify the
Filevalues match the exact folder path and file name, including the .evtx extension. - Old logs still appear in Event Viewer—this is normal. Event Viewer reads from the new location after the service restarts. If you still see old logs, ensure the service actually restarted. Run
net stop eventlogandnet start eventlogagain, or restart the PC. - Permission errors—the new folder must allow the SYSTEM account full control. Right-click the folder in File Explorer, go to Properties > Security, and ensure SYSTEM has “Full control”. If not, click Edit, add SYSTEM, and grant full control.
- Logs are not being written—if new events are not appearing, the service may be running but unable to write to the new location. Check the folder’s permissions and also ensure the drive is not full.
- Reverting changes—if you can’t fix the issue, restore the registry backup you made, or manually change the
Filevalues back to the original paths (e.g.,%SystemRoot%\System32\winevt\Logs\Application.evtx), then restart the service.
Frequently Asked Questions
Can I move the Event Log to a network drive?
Technically yes, but it’s not recommended. The Event Log service runs under the SYSTEM account, which may not have access to network shares. If you must, you’d need to configure the service account and permissions, but it’s fragile and can cause delays or failures.
Will moving the Event Log affect performance?
Minimally. Writing logs is a low-frequency operation. If you move to a slower drive, you might notice a tiny delay when events are written, but it’s usually imperceptible. Moving to a faster drive (like an SSD) can slightly improve performance.
Do I need to move all logs at once?
No, you can move individual logs. For example, you might move only the Security log to a separate drive for compliance reasons. Just change the File value for that specific subkey.
Can I use environment variables in the path?
Yes, the File value is of type REG_EXPAND_SZ, so you can use variables like %SystemDrive%\Logs\Application.evtx. However, be careful—if the variable expands to a path that doesn’t exist, the service may fail.
What happens to the old .evtx files?
They remain in the original folder. Windows will not automatically delete them. You can manually delete them after confirming the new location works, but consider backing them up if you need historical logs.
Is this change permanent?
Yes, until you change it back. The registry values persist across reboots. To revert, simply set the File values back to the default paths and restart the service.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- MacBook Charger Not Working? Fix It Now
- Fix Windows Cannot Be Installed to This Disk
- Zoom on iPhone & iPad: Host or Join a Meeting
- Fix iPhone SE 4 Unable to Activate: Step-by-Step
- Keep Important Emails From Getting Buried in iPhone Mail Categories
- How to Clear RAM on iPhone: Speed It Up