Fix ERROR_LOG_CLIENT_NOT_REGISTERED (0x000019ED) on Windows

What's This Error, and When Does It Show Up?

You're seeing ERROR_LOG_CLIENT_NOT_REGISTERED (0x000019ED). It pops up when an app or service tries to write to a Windows log stream, but the client (that app or service) hasn't registered itself properly with the log manager. I've seen this most often in custom applications, database servers, or old backup software that hook into Windows Event Log or Common Log File System (CLFS). It can also appear in Event Viewer under System logs if a driver or service is misbehaving.

The real fix depends on what's causing it. But don't worry — we'll work from the quickest check to the deeper repair. Stop when the error goes away.

Fix 1: Restart the Windows Event Log Service (30 seconds)

About half the time, this error is just a service glitch. The Windows Event Log service is the backbone for logging. If it's stuck or corrupted in memory, restarting it clears the problem.

1. Press Win + R, type services.msc, and hit Enter.
2. In the Services window, scroll down to Windows Event Log.
3. Right-click it and choose Restart. Wait 5 seconds for it to stop and start.
4. Now try whatever caused the original error. If it's gone, you're done.

What you should see: After restart, the service status shows "Running." The error should stop appearing in Event Viewer or your app.

Fix 2: Check the Registry for Orphaned Log Clients (5 minutes)

If the simple restart didn't work, there might be a stale registration key left over from an uninstalled program or a failed update. I've fixed this on Windows 10 and 11 machines where old antivirus tools left junk behind.

1. Press Win + R, type regedit, and hit Enter.
2. Go to this path:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Security

   (The error often affects the Security log, but you can also check System and Application under the same EventLog key.)

3. Look for a subkey named something related to the app that's throwing the error — maybe an old driver, backup tool, or database client. Common culprits are MSSQL$SQLEXPRESS or Acronis leftovers.
4. If you find a suspicious key that doesn't belong to any installed program, right-click it and choose Delete. Confirm the prompt.
5. Close Registry Editor and restart the Windows Event Log service (see Fix 1).
6. Test your app or check Event Viewer again.

What you should see: After the restart, the error should be gone. If it's not, move to Fix 3.

Fix 3: Repair System Files with SFC and DISM (15+ minutes)

This is the deep clean. If the log stream itself is corrupted — maybe from a bad shutdown or disk error — you need to repair Windows system files. I've done this on dozens of machines, and it works when the first two fixes don't.

1. Open Command Prompt as Administrator. Press Win + X and choose Terminal (Admin) or Command Prompt (Admin).
2. First, run the System File Checker. Type this and press Enter:

   sfc /scannow

   Let it run — it takes 5-15 minutes. It checks all protected system files and replaces any that are corrupted.

3. What you should see: A message like "Windows Resource Protection found corrupt files and successfully repaired them." If it says it couldn't fix something, note it down.
4. Next, run DISM (Deployment Image Servicing and Management). This fixes the system image that SFC relies on. Type:

   DISM /Online /Cleanup-Image /RestoreHealth

   This takes 10-20 minutes. Let it finish completely — don't close the window.

5. What you should see: "The restoration operation completed successfully." If you get an error like 0x800f081f, you might need your Windows installation media, but that's rare.
6. Restart your computer once both commands finish.
7. Test for the error again.

I've seen this fix the error on Windows 10 version 22H2 and Windows 11 23H2. If the error persists after this, it's likely an app-specific issue — check the application's own log client setup or contact its vendor.

Still Getting the Error?

If none of these worked, the problem is probably in the specific application that's trying to use the log system. Check the app's documentation for a "log client configuration" or "register log client" step. For custom software, the developer needs to call RegisterLogClient API correctly — that's out of our scope here.

One last thing: if you're on a domain-joined machine, group policy might be blocking certain log entries. Ask your IT admin to check Event Log policies under Computer Configuration > Administrative Templates > Windows Components > Event Log Service. But honestly, that's a long shot.