Fix 0X000019DB Log Policy Already Installed

I know this error is infuriating. You're trying to set up a log policy, and Windows just says nope, it's already there. But you didn't install it. Or maybe you did, and you forgot. Either way, this error shows up when you try to add a policy with the same type as one that's already registered on your machine.

This usually happens in event log management or when using wevtutil to configure log settings.

Let's fix it. Start with the quick stuff, then work up to the heavy tools.

Step 1: The 30-Second Fix – Check for Existing Policies

Before you do anything drastic, just look at what's already there. Open a command prompt as administrator. Hit Win, type cmd, right-click Command Prompt, and choose Run as administrator.

Now run this to list all installed log policies:

wevtutil gl

That command lists all the log names. Look for a log that matches the one you're trying to add. If you see it, you already have the policy. You don't need to add it again.

If you were trying to create a custom log with a specific name, and it shows up in the list, then you're done. Just use the existing one.

But if you really wanted to replace it, you need to remove the old one first. That's Step 2.

Step 2: The 5-Minute Moderate Fix – Remove the Duplicate Policy

So you've confirmed the policy exists. Now you have two choices:

Delete the old one and recreate it with your new settings.
Just change the existing policy to match what you need.

Let's delete it first. Use wevtutil with the sl (set log) command, but to delete, you actually need to unregister the log. Here's the command:

wevtutil ul <logname>

Replace <logname> with the actual log name you saw in Step 1. For example, if the log is called MyAppLog, run:

wevtutil ul MyAppLog

That removes the log and its policy. Then you can add your new one:

wevtutil el MyAppLog

Wait, that's not right. To create a new log, you use wevtutil cl for an empty log, or you can set one up with wevtutil sl after creating it. Actually, let me be precise:

wevtutil cl creates a new log.
wevtutil sl sets log properties.
wevtutil ul unregisters a log.

The proper sequence to replace a policy:

Unregister the existing log: wevtutil ul MyAppLog
Create a fresh log: wevtutil cl MyAppLog
Then set your custom policy properties: wevtutil sl MyAppLog /p:<path> /r:<retention> /a:<autoBackup>

But slow down. Before you delete anything, make sure you're not deleting an important system log. The error usually happens with custom logs, not the built-in ones. If it's a system log, don't delete it. You'll break things.

If you can't delete it because it's protected, then you need to use the advanced fix.

Step 3: The 15+ Minute Advanced Fix – Registry Cleanup

Sometimes wevtutil won't let you remove a policy because it's locked or registered somewhere deep. The registry is the last stand.

Open Registry Editor. Press Win + R, type regedit, and hit Enter. Accept the UAC prompt.

Now navigate to this key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog

Under EventLog, you'll see a list of subkeys—each one is a log name. Find the log that matches the one causing the error. Right-click it and select Delete.

But be careful. Deleting a system log key here can cause problems. Only delete custom logs that you know are safe to remove. If you're not sure, back up the key first.

To back up, right-click the key, choose Export, and save a .reg file somewhere.

After you delete the key, close Registry Editor, then restart the Windows Event Log service to make sure everything updates:

Press Win + R, type services.msc, hit Enter.
Find Windows Event Log in the list.
Right-click it and choose Restart.

Then try to add your log policy again. It should work now.

Why This Happens

This error trips up a lot of admins. It usually happens when you run a script or tool that tries to create a log that already exists, maybe from an earlier setup or a leftover from an uninstalled program. The error code 0X000019DB is just the system's way of saying “duplicate detected”.

In my experience, the most common trigger is when you import a custom log configuration from another machine, and that config includes a policy that's already present on the target machine. The fix is always the same: find it, remove it, recreate it.

Skip This If…

If you don't actually care about the policy, and you just want the error to stop, then don't install the log policy at all. Just use the existing log. That's the simplest path. But if you need a specific policy, then go through the steps above.

Final Word

I've seen this error on Windows Server 2016 and 2019, also on Windows 10 21H2. The fix is always the same. Start with wevtutil gl, then remove the duplicate, then recreate. The registry step is the last resort, but it works.

Now go fix that error. It won't take long.