Menu

Event ID 4673 flood: why the Security log is full and the PC is slow
📰

Event ID 4673 flood: why the Security log is full and the PC is slow

DEV Community: security·Coinetic AI Security·2 days ago
#3WP9mjga
#devtosecurity#devto#dev#security#windows
Reading 0:00
15s threshold

Originally published at coinetic.io .

Event 4673 is Windows saying "A privileged service was called" . A few a day are normal. Dozens per second, from chrome.exe , msedgewebview2.exe or Code.exe , make the Windows Event Log service eat whole processor cores – and the log falls minutes or hours behind.

In short

What it is: a program asked for a special Windows right (a privilege ), and an audit policy logs it.

Typical flood: Audit Failure entries for SeProfileSingleProcessPrivilege from Chromium-based programs: Chrome, Edge, Edge WebView (used by Teams, Outlook, widgets) and VS Code. They ask for memory figures, Windows refuses, they ask again.

The cause: almost always a Group Policy with Audit privilege use = Success, Failure .

The fix: in that policy, untick Failure and keep Success . Then gpupdate /force , and give the log time to catch up.

1.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.