Windows 7 seems to report incorrect idle times for the console session

[GoogleCodeExporter]

Not sure about remote sessions.

Original issue reported on code.google.com by danports on 7 Aug 2009 at 12:40

[GoogleCodeExporter]

May not be Windows 7. Windows Server 2003 is reporting an incorrect login time 
for the 
console session when it is disconnected.

Original comment by danports on 29 Sep 2009 at 2:22

[GoogleCodeExporter]

Server 2003 does have this issue with active remote sessions. I see about a 7 
minute "jump" backward in the CurrentTime property every so often. Sometimes 
the idle timespan is represented by a negative value! 

Here is a short printout from the console showing this odd jump:

CurrentTime           LastInputTime         IdleTime
6/24/2010 3:22:19 PM, 6/24/2010 3:14:28 PM, 00:07:50.9363880
6/24/2010 3:22:24 PM, 6/24/2010 3:14:28 PM, 00:07:55.9523340
6/24/2010 3:22:29 PM, 6/24/2010 3:14:28 PM, 00:08:00.9682800
6/24/2010 3:22:34 PM, 6/24/2010 3:14:28 PM, 00:08:05.9842260
6/24/2010 3:22:39 PM, 6/24/2010 3:14:28 PM, 00:08:11.0001720 <<<
6/24/2010 3:29:54 PM, 6/24/2010 3:14:28 PM, 00:15:25.5128476 <<<
6/24/2010 3:29:59 PM, 6/24/2010 3:14:28 PM, 00:15:30.5287936
6/24/2010 3:30:04 PM, 6/24/2010 3:14:28 PM, 00:15:35.5447396
6/24/2010 3:30:09 PM, 6/24/2010 3:14:28 PM, 00:15:40.5606856

Original comment by [email protected] on 24 Jun 2010 at 8:38

[GoogleCodeExporter]

Clifton, the problem you are describing has been fixed on the trunk; see issue 
20. The trunk is quite stable, so if you'd like, you can grab the latest build 
from the build server 
(http://teamcity.codebetter.com/project.html?projectId=project51 -- use the 
artifacts link).

Original comment by danports on 25 Jun 2010 at 12:09

[GoogleCodeExporter]

More data points: 
http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/beca90b0-8ab
d-4f26-a3bb-a146e11da1b6/

Original comment by danports on 15 Apr 2011 at 1:37

[GoogleCodeExporter]

I'm not sure that there is anything we can do about this issue, given that it 
appears to be an issue with the underlying Windows API.

Original comment by danports on 8 May 2011 at 12:44

• Changed state: New