Discussion:
WMP "date last played" is inaccurate
(too old to reply)
mattjackson07
2010-06-03 02:08:53 UTC
Permalink
Hi, I'm using WMP 11 and Vista. I just noticed when I played a song at 8pm
on June 2nd, it updated the "date last played" to June 3rd. Is there a time
zone setting that can be changed? I've looked seemingly everywhere. Thanks
for anyone's help.
Dylan
2010-06-04 03:05:58 UTC
Permalink
Same here, I think it's a Windows update bug. Probably will be fixed soon. Hopefully!

---
frmsrcurl: http://msgroups.net/microsoft.public.windowsmedia.player/WMP-date-last-played-is-inaccurate
Tim De Baets
2010-06-05 15:35:41 UTC
Permalink
What time zone are you in? Date last played is actually a combination of
date and time, and WMP always seems to use GMT time to set it,
regardless of the time zone that is set in Control Panel.

If there's a significant difference between your time zone and GMT, then
this would explain why it's setting the wrong date. For example, when
it's 8 PM in the US, it's already the next day in the GMT time zone (8+6).

Regards

--
Tim De Baets
http://www.bm-productions.tk
Post by mattjackson07
Hi, I'm using WMP 11 and Vista. I just noticed when I played a song at 8pm
on June 2nd, it updated the "date last played" to June 3rd. Is there a time
zone setting that can be changed? I've looked seemingly everywhere. Thanks
for anyone's help.
Dylan
2010-06-05 15:41:20 UTC
Permalink
Eastern Daylight Time for me.

---
frmsrcurl: http://msgroups.net/microsoft.public.windowsmedia.player/WMP-date-last-played-is-inaccurate
e***@sympatico.ca
2016-07-02 01:36:26 UTC
Permalink
Post by mattjackson07
Hi, I'm using WMP 11 and Vista. I just noticed when I played a song at 8pm
on June 2nd, it updated the "date last played" to June 3rd. Is there a time
zone setting that can be changed? I've looked seemingly everywhere. Thanks
for anyone's help.
Understandably, no one uses GMT time except Department of Defence or airlines. Why can't West Coast tech companies just adapt to the realities of the rest of the world? This is not a Windows bug, just lazy programming.
Loading...