Windows Forum

Ask something
Discussion Locked

Auto Refresh of Network Drives

0 helpful
7 replies

by mark 3 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
When I create a folder or file on a network drive, it does not show up until I hit F5 to refresh it. Same thing if I rename a folder or file, the old name goes back in until I hit F5. If I click on the folder or file before hitting F5, it says it can't find it cause it's looking for the old name. This doesn't happen on the local drive, only network drives. How can I fix this annoying problem?

7 replies

by hal 9000

Refresh the Window before using the New or Renamed Folder. This happens because it's not Local and you need to refresh the Network Drive before you can access an new or Renamed Folders.

Col

by mark

This is not normal behvior. My other computers do not behave this way. It is annoying. I have to hit F5 constantly after creation, renaming, etc.

by mark

This is not normal behvior. My other computers do not behave this way. It is annoying. I have to hit F5 constantly after creation, renaming, etc.

by achoo54321

Mark,

True that it's not a direct fix, however I would recommend using FreeCommander instead of Windows Explorer when you can. It's a more powerful file manager, with tabbed (Firefox-like) browsing that doesn't have this problem. I know the latter because I've just had to install FreeCommander to work around the situation you mentioned. I've read quite a bit on the issue and even tried a registry fix that seemed promising, and nada.

by twist944

Hi, We also have the same problem.

When creating new folders on a browsed network path, f5/refresh needs to be done before the folder shows up. However, we have discovered that is the network location is mapped rather than using \\ the new folder appears instantly.

We are using server 2008 - We do not have this issue on any of our local machines.

by spokey

I remember reading a while back that there is a Microsoft update that needs to be applied to the remote server to correct this action. I'm actually searching for that update now and came upon this post. If I find it, I'll post it here also.

This discussion is closed to new replies.