Crash on Audit Failure Even Though I have Security Logs Set to Archive When Full

Why do I get a Crash on Audit Failure when the security logs are set to Do not overwrite, Archive when Full?  Should't the logs archive automatically and start new logs automatically when the security logs are full?

This of course causes my applications and websites to not allow my users to log on.   Any ideas on how to prevent this in the future would be greatly appreciated?
Who is Participating?
Rich RumbleConnect With a Mentor Security SamuraiCommented:
There does seem to be a hotfix that affects 2008, it's just how you described: You may want to try that.
Windows 2008R2 boxes we don't have any Windows 7 boxes deployed yet and as I stated originally the settings as decribed work fine on XP/Win2003. We also never deployed Win2008/Vista.
The LSA\CrashOnAuditFail registry key is not needing to be reset when the system comes back up.
I had the following hotfix provided to me via another source
Conrad_BelAuthor Commented:
This happened last on a 2008 R2 server.  Not really sure what our telling me w_richard?
Conrad_BelAuthor Commented:
Thanks for the info.  I will research further.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.