Hello, I think I figured out the problem. I disabled all the tasks in the Task Scheduler and voila - problem solved. There are many applications running in the background and some of them are repeatable every 10-60 minute. I think that one of them was responsible for the opening cmd console and running 5379 event, but I don't know which one.
Excessive Security Log Events - Event ID 5379 - Windows 10
I have been experiencing Windows Application crashes on my 3 month old Windows 10 install. While troubleshooting, I noticed that there 50+ security events each minute in the Event Viewer under Windows Logs > Security.
Is this normal?
The majority are Audit Success Messages with the Event ID 5379. There are approximately 50 of these identical messages every minute. Thanks for any insight on this.
See below for typical Message:
Credential Manager credentials were read.
Subject:
Security ID: DESKTOP\*****
Account Name: *****
Account Domain: DESKTOP
Logon ID: 0x354889
Read Operation: Enumerate Credentials
This event occurs when a user performs a read operation on stored credentials in Credential Manager.
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
52 answers
Sort by: Newest
-
Anonymous
2021-09-28T11:06:07+00:00 -
Anonymous
2021-09-18T23:39:13+00:00 Having the same issue here. Got here because some of my games were crashing, straight to desktop with no error messages. Upon checking the event viewer, every time I see a crash, I see event 4624, immediately followed by event 4672 and then a big list of event 5379. This causes my games to crash every time it happens, multiple times per hour. My gaming PC is basically unusable. Haven't found a fix anywhere.
As someone else pointed out, yes we know that event 5379 is not the CAUSE of the issue, but it has to be related or caused by that same issue because it wouldn't be there for every crash otherwise.
I now ran sfc /scannow and it found some corrupt files, I will update if this ended up fixing the issue but somehow I doubt it will be this easy.
-
Anonymous
2021-08-14T13:33:57+00:00 @nathanhowell3 - have you checked that things like Windows updates, Windows store, and ONeDrive still work? How about Windows Security (Defender) does it still open?
-
Anonymous
2021-08-13T05:04:57+00:00 Hey guys, sorry I'm a bit late to this thread, I've been having this issue for about 3 months now and its been driving me insane, however I think I've found a workaround solution that doesn't require installing new hardware.
First of all, I removed my Microsoft account from my PC and left only a local account, from there go to control panel and go to credentials manager, then remove all of the access' listed. Then in services, disable credential manager and credentialenrollmentmanager. After that navigate to system32 and disable auditing of the applications rooted to the services - lsass.exe and credentialenrollmentmanager.exe, I also disabled inheriting and revoked access to read and write by taking ownership of the applications.
I do not know for sure whether each step is necessary, however this has stopped the excessive amounts of 5379 audits completely, and my pc is running much more smoothly because of it ( I was getting about 10 new audits whenever a window or overlay opened or was switched to/brought to front). Also disabling the server service might be important as well, I'm unsure of whether it impacted the results.
-
Anonymous
2021-08-11T08:21:21+00:00 @David Salmon - even fresh installs will have 5379 events. It is a NORMAL "info" event, just a standard audit event, for user activity that uses credentials. It is NOT signifying any problem - it is just annoying and a bit excessive for normal home systems.