This article helps resolve an issue in which Windows Server stops responding on startup when applying Group Policy if System Monitor (Sysmon) is installed.
Sysmon driver (SysmonDrv.sys) intercepts the transition from user mode to kernel and then sends work to its user mode process Sysmon64.exe. Most Sysmon64.exe threads are stuck waiting on a critical section. The critical section owner is waiting on a Local Security Authority Subsystem Service (LSASS) thread. However, the LSASS owner thread is trying to acquire a different critical section. Many other LSASS threads are blocked waiting on this critical section.
The critical section owning thread is blocked in SysmonDrv's kernel to the user mode communication to process Sysmon64.exe, which is observed to be stuck waiting on the LSASS thread. This results in a deadlock.
You can resolve this issue by upgrading Sysmon to the latest version, or work around this issue by disabling FileBlockShredding.
Disable FileBlockShredding
To work around this issue, follow these steps:
-
Find the XML config file by running the following cmdlet:
PS C:\Sysmon> .\Sysmon64.exe -c Sysmon (internal) v15.00 - Monitors system events By Mark Russinovich and Thomas Garnier Copyright (C) 2014-2023 Microsoft Corporation Using libxml2. libxml2 is Copyright (C) 1998-2012 Daniel Veillard. All Rights Reserved. Sysinternals - www.sysinternals.com (http://www.sysinternals.com/) Current configuration: - Service name: Sysmon64 - Driver name: SysmonDrv - Config file: .\file-delete.xml -
Eliminate the following condition:
<FileBlockShredding onmatch="..."> ... </FileBlockShredding>
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
