0 Sign In to Vote Windows 7, Explorer is showing a -6 hour difference in time from my actualfile date. This is NOT simply the time difference between my computer (in Central time zone) and the server (on Eastern time). Explorer is ignoring the server's time stamp and subtracting exactly 6 hours from the time of the what the server should say. I know this because I'm also looking at the exact same folder and files using XP and the time stamps are exactly as they should be. I modified a file locally (on Windows 7) and copied it up to the server. The time stamp local is 9:36a. The time stamp on the server should be 10:36a, but instead it says 4:36a. So, I copied a file from the server back to here and it reports locally 6 hours later (10:38a) than what is on the server (4:38a). Looking at the exact same files through explorer on XP shows that the time should have been 10:38a. If it wasn't for time showing correctly on XP, I'd assume it was a problem at the server, but there seems to be something in either the display of time, or in the way it sends thefile'stime-stamp. And now I'm testing it on another ftpserver, which I think has their time set to UTC (my 10:00a is their 4:00p). Using XP, I create a brand new file locally, and transmit it to this server. It initially appears with the same timestamp as the original file (10:16a). I then do a refresh of the server list (in XP) and it jumps forward 6 hours (4:16p). I look at this server with Windows 7 and it shows that the file has a timestamp of 10:16a. So I copy that file (using Windows 7) to its local drive and it tells me that the timestamp is 4:16p (later today). I've triple-checked my PC's time settings (set to UTC-06:00 Central Time). I've verified with the first server's techies that the PC is in Eastern time (I've not reached the other server's people yet). In both cases, however, Windows 7 is showing the time of the files on the ftp servers to be 6 hours earlier than their actual time-stamp.

Hi, I found this is a known issue in windows 7; our development is investigating the problem right now. If they find any solution, it would adjust this performance by update next time. Thank you for your understanding. Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

As some of our customers are also facing this same problem & I didn't find any solution yet, I've raised it with Microsoft premier support for answers & possible fix (or schedule thereof).

Hi Alex, Can I follow up if your Development Team managed to fix this issue please? If you have a hotfix please do let me know. Thanks, Ray

Dears, I am also facing same problem, please let me know if it has a solution. Regards, Joe

We are also seeing this behavior. Is there a fix or work-around available? Thanks.

Have you found a solution yet? We are experiencing the same problem. Any work around? natusikyagusik

No solution.

Alex- I have the same problem - any update on the fix for this?