Hi,
I already noticed it before, that sometimes the System Information dialog of TC reports some pretty large value in the "time since win start" field, but I thought maybe it was really just me who forgot to turn off the notebook (although I turn it off almost everytime @ night).
Now I am sure that I turned it off 2 days ago, but still TC reports incorrect runtime value. Picture attached, AIDA64 reports correct information.
Maybe something has changed in Win10 that affects the runtime calculation module?
TC (incorrect)
Image: http://s30.postimg.org/5wbnp1d8h/tc_runtime.png
AIDA64 (correct)
Image: http://s15.postimg.org/ko3xa1eqj/aida_runtime.png
SW info: Win10 ver1511 b10586.164, TC 8.52a(x64), Hungarian locale, AIDA64 5.70.3800
[8.52a] Incorrect system uptime value @ System info dialog
Moderators: Hacker, petermad, Stefan2, white
In Windows 8, Microsoft has changed meaning of "Shut down". It puts your PC into a special kind of hibernation instead of actually shutting down everything. The reason is to make it look like the Windows 8 boots faster than Windows 7.
Only "Restart" actually turns everything off to allow us install Windows updates modifying kernel.
I guess TC uses an API that is not reset during this "Shut down", only during "Restart".
EDIT:
After a quick check of API, it looks like MS doesn't directly provide last power up time. Even Win32_OperatingSystem.LastBootUpTime shows time of last full restart.
Since TaskManager shows the same thing, is this an error or actually an intended behavior?
umbra
Only "Restart" actually turns everything off to allow us install Windows updates modifying kernel.
I guess TC uses an API that is not reset during this "Shut down", only during "Restart".
EDIT:
After a quick check of API, it looks like MS doesn't directly provide last power up time. Even Win32_OperatingSystem.LastBootUpTime shows time of last full restart.
Since TaskManager shows the same thing, is this an error or actually an intended behavior?
umbra
Windows 10 Pro x64, Windows 11 Pro x64
- ghisler(Author)
- Site Admin
- Posts: 50386
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
TC is using the GetTickCount() function, which is the time since the last reboot. It has a maximum of 49.7 days until it wraps around to 0. However, since monthly Windows updates require a reboot, this shouldn't be a problem.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- ghisler(Author)
- Site Admin
- Posts: 50386
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
I'm aware of GetTickCount64, but that wasn't the question here. It will have the same effect as the thread starter reported (putting PC to sleep doesn't count as fresh start).
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com