Charles
When I am looking at a directory view of a folder on a networked drive, the Refresh Directory does not update file dates or sizes. I have to view a file before the details will update.
I am running V15 SR2 on 32-bit Windows 7. The networked folder is on a server running Windows 2012.
I have not ticked the Disable Automatic Refresh on Network Drives
Chris
Refresh Directory not working on network folder
Moderator: vuser
Refresh Directory not working on network folder
- Attachments
-
- RefreshDirectory_after.jpg (113.52 KiB) Viewed 47891 times
-
- RefreshDirectory_before.jpg (103.91 KiB) Viewed 47891 times
Re: Refresh Directory not working on network folder
Charles
I have found this occurs because of a setting on the server, and it is not a problem in V. The same thing occurs in Explorer on the server.
The registry key HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisableLastAccessUpdate determines whether the timestamp is updated whenever a file is changed.
If this flag is 1 (disabled) the time and size only change when the file is opened or the file properties are checked.
Changing the value to 0 (enabled) means the file time and size are updated regularly.
I need to check whether this is a significant overhead on the system - I may need to disable this.
Chris
I have found this occurs because of a setting on the server, and it is not a problem in V. The same thing occurs in Explorer on the server.
The registry key HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisableLastAccessUpdate determines whether the timestamp is updated whenever a file is changed.
If this flag is 1 (disabled) the time and size only change when the file is opened or the file properties are checked.
Changing the value to 0 (enabled) means the file time and size are updated regularly.
I need to check whether this is a significant overhead on the system - I may need to disable this.
Chris
-
- Site Admin
- Posts: 287
- Joined: Fri Apr 30, 2010 5:50 pm
Re: Refresh Directory not working on network folder
Thanks for letting me know.i have found this occurs because of a setting on the server, and it is not a problem in V.
I couldn't reproduce the problem and was going to suggest it was either a Windows bug or a configuration issue.