I tried to use Spy++ to gather WM_SYSCOMMAND and it is presented like below:
Not sure if it is possible to connect it with specific software\application
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am looking for a way to find out why sometimes screensaver is not activated on our Windows 10 1809 VDI (virtual machines). So the question is how Windows is calculating idle time which is taked for starting screensaver? We have a GPO configured to start screensaver after 15min of idle time (User Configuration - Administrative templates - Control Panel - Personalization - Screen saver timeout). It happens (especially when machines have longer uptime) then screen saver is not activated. I found out this nice script https://gallery.technet.microsoft.com/Checking-the-session-idle-06350f77
but tested it with active skype call which last more than 15 minutes and during this time I was not touching mouse or keyboard. Script was counting to 15 mins but screensaver was not activated. Why? How skype is preventing it?
I tried to use Spy++ to gather WM_SYSCOMMAND and it is presented like below:
Not sure if it is possible to connect it with specific software\application