# System clock resolution not stable

Hi, i have a weird situation.

When i spawn a Windows7-SP1 virtual machine, if i connect via RDP and i run Clockres (from Sysinternals), i obtain those value;

ClockRes v2.0 - View the system clock resolution
SysInternals - www.sysinternals.com

Maximum timer interval: 15.600 ms

Minimum timer interval: 0.500 ms

Current timer interval: 1.000 ms


However, if i close the session, and i'm connecting via VNC from Horizon Dashboard, i obtain those value

ClockRes v2.0 - View the system clock resolution
SysInternals - www.sysinternals.com

Maximum timer interval: 15.625 ms

Minimum timer interval: 0.500 ms

Current timer interval: 15.625 ms


Problem: When a user execute some automatic script, the VNc current value (15.625) is used, so their script take really longer that they should be. When they connect via RDP, everything works correctly.

I think VNC is changing the Current timer interval, but i wonder why and how? Also, can we edit those value into VNC directly?

Do you think is possible to edit those value for VNC (I know we can't edit RDP, but it's okay) ?

edit retag close merge delete

Sort by » oldest newest most voted

Hello Sam!

I suspect it is RDP that is changing the timer interval. Check this out

Further, since I have had very little dealings with Windows in the past few years, I am unsure how to go further with this issue. I will say that I have not noticed a significant different between using RDP and VNC with script speeds as I have just tested.

Perhaps you can give me a sample script the reproduces your issue? I am intrigued.

more