MCMADM_I_NO_EVENTS (0X400D0069) – Fix Event Init Failed

What Causes This Error

Error 0X400D0069 (MCMADM_I_NO_EVENTS) appears when the Windows Event Log service can't initialize the MCM (Microsoft Configuration Manager) event channel. You'll see this error in Event Viewer under Windows Logs > System, usually after a failed software install, a disk write error, or a sudden power loss that corrupted the event log file.

The most common trigger is a corrupted %SystemRoot%\System32\winevt\Logs\Microsoft-Windows-MCMADM%4Operational.evtx file. But sometimes it's a permissions problem on the log folder, or the Event Log service itself is stuck. Let's walk through each fix in order.

Fix 1: Clear the Corrupted MCM Event Log

This solves about 70% of cases. The MCM operational log file gets corrupted and won't load. The fix is to delete it — Windows will recreate it automatically.

Step-by-step

1. Press Windows Key + R, type services.msc, press Enter.
2. Scroll down to Windows Event Log. Right-click it and select Stop. Wait for the service to show "Stopped".
3. Open File Explorer. In the address bar, paste: %SystemRoot%\System32\winevt\Logs and press Enter.
4. Find the file named Microsoft-Windows-MCMADM%4Operational.evtx. Right-click it and choose Delete. If you're nervous, just rename it to Microsoft-Windows-MCMADM%4Operational.old instead.
5. Go back to services.msc, right-click Windows Event Log, and select Start.
6. Open Event Viewer (eventvwr.msc) and check if the error is gone. Look under Applications and Services Logs > Microsoft > Windows > MCMADM > Operational. You should see a clean log.

After step 5, the service should start immediately. If it hangs for more than 10 seconds, go to Fix 2 first — the service might have a permissions issue that stops it from creating a new log file.

Fix 2: Reset Permissions on the Event Logs Folder

Sometimes the Event Log service can't write to the Logs folder because the permissions got messed up — maybe a user account or a group policy change did it. This happens more often on domain-joined machines where group policies push restrictive permissions.

Step-by-step

1. Open an administrator Command Prompt (right-click Start > Command Prompt (Admin) or Windows Terminal (Admin)).
2. Run this command to take ownership and reset permissions:

icacls %SystemRoot%\System32\winevt\Logs /grant "SYSTEM":(OI)(CI)F /grant "Administrators":(OI)(CI)F /grant "Event Log":(OI)(CI)F /T

This command gives Full Control to SYSTEM, Administrators, and the built-in Event Log account (that's the service account). The /T flag applies it to all files inside the folder.

3. When it finishes, restart the Windows Event Log service (as in Fix 1, steps 2 and 5).
4. Check Event Viewer again. If the error persists, move to Fix 3.

Pro tip: If you see "Access Denied" when running icacls, you're not running as true Administrator. Right-click the prompt and pick "Run as Administrator".

Fix 3: Re-register the MCM Event Provider

If the log file is clean and permissions are fine, but the error still shows up, the event provider itself might be unregistered or corrupted. This can happen after a Windows update that removed or replaced the MCM component.

Step-by-step

1. Open an administrator Command Prompt.
2. Run this command to unregister the MCM event provider:

wevtutil um "C:\Windows\System32\Microsoft-Windows-MCMADM.man"

If that file doesn't exist, you might have a different version of MCM. Search for any file matching *MCMADM*.man in C:\Windows\System32\. If none, skip this step — the provider might be in a different location. On some systems, it's in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config.

3. Now re-register it:

wevtutil im "C:\Windows\System32\Microsoft-Windows-MCMADM.man"

4. Restart the Windows Event Log service one more time.
5. Open Event Viewer and verify the MCM Operational log loads without errors.

If the wevtutil command gives you a "file not found" error, the MCMADM.man manifest isn't on your system. That usually means the MCM component wasn't installed properly, or it's part of a larger application like Configuration Manager (SCCM). In that case, you might need to repair the SCCM client, but that's rare — Fix 1 and Fix 2 cover the vast majority of cases.

Quick-Reference Summary Table

One last thing: if none of these work, run a System File Checker scan. Open admin Command Prompt and type sfc /scannow. Let it finish, reboot, and test. That catches the rare case where a core system file is busted. But honestly, Fix 1 is your money shot — try it first.