A family of Microsoft word processing software products for creating web, email, and print documents.
Hi Kaas
The .NET Runtime Event ID 1022 does not establish a direct relationship between the .NET runtime event and the Word hang. However, the issue no longer reproducing on Windows 11 after installation of KB5126052, while remaining reproducible on Windows Server 2019 with KB5126048, points to a difference in platform behavior that may warrant further investigation.
The documentation for KB5126052 includes a .NET reliability improvement for certain 64-bit scenarios, whereas KB5126048 does not list a corresponding reliability improvement.
At this time, based on my research, there is no published Microsoft documentation describing a specific fix for Word becoming unresponsive when modifying styles on Windows Server 2019, and there is no documentation indicating that the reliability improvement included in KB5126052 is available for KB5126048.
For troubleshooting purposes, it may be useful to review:
- Office COM/VSTO add-ins
- Endpoint security or DLP software
- Application monitoring or profiling tools
- .NET profiler-related settings (COR_* or CORECLR_* variables)
Testing Word in Safe Mode (winword.exe /safe) and temporarily disabling non-Microsoft add-ins may also help determine whether an external component is involved.
If the behavior continues, collecting a hang dump of WINWORD.EXE while Word is unresponsive may provide additional information about the module or component involved in the hang.
Based on the currently available documentation, there does not appear to be a separately documented reliability update for Windows Server 2019 that addresses this scenario in the same manner as the improvement described for KB5126052.
I hope this information is helpful. If you have any further questions, please feel free to reply in the comments.