Hi,
Understand reading the article:
https://support.microsoft.com/en-us/...shes-in-window
Yesterday I witnessed a possible crash in a client using the service Terminal, when using the Winprint2.
The report creates a process cover, which basically consists of reading 1 main record and some other children.
The crash occurred before the report was presented on the screen below, which is successfully completed:
Today I witnessed another eventual crash.
I clicked on the Clear button of my application, which was running on the Terminal Service and Bang!.
Look at the damn splwow64.exe as the child process of my application and consuming 25% CPU-Fatal for Windows Server 2012.
I can click a million times and repeat both operations without causing a crash.
There are reports of virus, acting on this module called: splwow64.exe.
If possible DAW could confirm, if the module: splwow64.exe is called at low-level Runtime?
Thank