Windows Event 4673 flood from Chromium apps can slow the PC and delay the Security log

Windows Event ID 4673 logs when a program requests a privileged right, and a few per day is normal. When Chromium-based apps such as Chrome, Edge WebView, and VS Code repeatedly request the SeProfileSingleProcessPrivilege right, which Windows refuses for regular users, audit policy writes a flood of Audit Failure entries. This can consume whole processor cores in the Windows Event Log service and cause the Security log to fall minutes or hours behind. The article attributes the usual cause to a Group Policy setting that audits privilege use for both Success and Failure. The suggested fix is to disable auditing of Failure while keeping Success, then run gpupdate /force and allow the log time to catch up. The article also notes that a lagging Security log can delay detection of events such as failed logins and firewall blocks.