How to Clear SCOM Console Alerts (Corrupted Cache Fix)

If old, no-longer-relevant alerts in the System Center Operations Manager (SCOM) console refuse to clear — every attempt throws a generic error and can even crash the console — a corrupted local console cache is the usual culprit rather than a problem with the alerts or the management group itself.

The Fix

1. Open an elevated Command Prompt on the machine where the SCOM console is installed.
2. Run:

"C:\Program Files\Microsoft System CenterOperations ManagerConsoleMicrosoft.EnterpriseManagement.Monitoring.Console.exe" /clearcache

Adjust the path if your SCOM console is installed somewhere other than the default location. This clears the console’s local cache and reloads it from a clean state. Once it’s back up, try clearing the problem alerts again — this resolves the vast majority of cache-related console errors without needing to touch the management server or database at all.

Why the Cache Gets Corrupted

The SCOM console maintains a local cache of management pack data, views, and console layout so it doesn’t have to re-download everything from the management server on every launch. This cache can end up in a bad state after an abrupt console crash, an interrupted management pack import while the console was open, or simply after a large management pack update lands on the server mid-session. None of these actually damage anything on the management server or in the operations database — the corruption is entirely local to the machine running the console, which is exactly why clearing it is safe and non-destructive.

If /clearcache Doesn’t Resolve It

On the rare occasion the cache clear alone doesn’t fix the issue, try these before escalating to the management server side:

• Fully close all open SCOM console windows (including any minimised instances) before running the command — a console instance still running in the background can recreate the corrupted cache immediately after it’s cleared.
• Confirm the account running the command has write access to the console’s local cache folder under the user profile — a permissions problem can produce a similar-looking failure to a genuinely corrupted cache.
• If multiple users on the same machine hit this, check whether it’s specific to one Windows profile or affects every account — a per-profile issue points back to the local cache, while an every-account issue is more likely a genuine management-group-side problem worth investigating separately.

Resources

• SCOM
• guide