I've got the following problem: Windows 7 does not refresh automatically the folder view (until I manually refresh by pressing F5) after the following file operations: Create/delete/rename/move files or folders Windows 7 Professional final release, international English version. No upgrade, clean install. It seems to me it's a delay in my case: if I wait for approximately 30 secs, the refresh is done automatically. There are shared folders on the volumes. I've done the followings: deleted IconCache - did not help reset folder views - did not help turned off file sharing and network discovery - did not help made a clean boot - did not help ran sfc - did not found any violations created new user account - did not help updated the BIOS to the latest version - did not help updated the VGA driver to the latest version - did not help turned off file indexing - did not help - ran Windows 7 in Safe Mode (without Networking): it seems the issue does not occur I could be satisfied with Windows 7 but this issue is terribly annoying cause I work with a lot of files day by day. Could anybody help me?

I have had the same problem recently. Here's what I discovered, FWIW: After reading all of these responses it seemed that, at the core, this is related to the Windows UI shell and how it tries to "reach out" to other systems. Fixes included disabling the Windows Client, disabling home groups, disabling file shares, etc. I discovered that I have the problem only in certain folders. For example, if I try to create a folder in my DOCUMENTS folder, the problem occurs, but if I create the folder in a random folder on the C: drive (e.g. C:\MyTest), no problem! I discovered that the folder DOES eventually appear--it just takes 30+ seconds. By pressing F5 I was "rushing" the process. This also sounds like a network client timeout kind of thing. I wanted to start with the simplest, lowest-impact solution. It worked: I opened COMPUTER and removed a "Network Connection" that pointed to a server that is not currently available. That solved the problem completely. Dan Holme, Intelliem

No solution here, but an observation. I'm not an engineer or a card carrying member of the power users club, but I have some problem solving skills and I think most users involved in this thread, including MS support are hopelessly lost down a rabbit hole and have become entangled in the details of where the problem evidently is not. After reading 5 years and 50 pages worth of issues and solutions one common theme surfaced. The common theme is the file system, or potentially in one of the gazillion layers in the Windows OS that takes part in manipulating the file system. The issues occur when there is a corrupt, missing, or otherwise inaccessible file or file link that points to an SD card, a DVD, a CD, a local folder, a network folder, etc. These are all different file locations with different drivers and different subsystems. How could they all be suffering from the same problem? The answer is, they are not. A layer of the OS that accesses them all via the broken link is having the problem. Any fix to a broken link to one of those mediums is temporary until a new broken file link exists, then the user gets hit with the delayed refresh again. The common thread is the file system, not the networking system, not the optical disk system, not the SD card reader system, etc. So while the workarounds correct the symptom for the specific file medium involved in the refresh issue, the issue almost always returns when another file or file location link breaks. Time to stop looking at the file locations and start looking at the file system, or the Windows 7-layer bean dip of protocols and subsystems that take part in accessing the file locations. If you are lucky and remove the links to the failed file locations, the problem is corrected immediately. If your are even more lucky and don't experience a missing or failed file link again, the refresh issue never comes back. For those of us who do a ton of file manipulations across a wide variety of file locations, not so lucky. The issue usually returns in a short time and we start losing data, again, before we figure out the refresh issue is back. The reason these remedies (workarounds) are temporary is because the file system or the Windows 7-layer bean dip interface to the file system is the problem and it fails to handle the very common condition of a file location link becoming invalid. Actually it does handles it. It just takes 30+ seconds to choke on it before it refreshes your screen allowing you to accidently delete data. Unfortunately I don't find it hard to believe that after this many years and this much data collected (I'm only looking at one single forum thread. I'm sure M$ has a zillion other threads and help desk cases just like this), M$ has not figured out they need to stop looking at the separate file locations involved, but need to determine what the common thread is. Frustratingly, as so many have pointed out, M$ has determined that spending their time and money screwing up perfectly good user interfaces, taking functionality away, adding functionality we don't need, and hopelessly hiding the functionally they leave behind in the most obscure and irrelevant places is more important to their bottom line. Until that changes, we probably wont see this issue resolved in future releases of the OS and will be left with frequently losing data and MS support wasting our time chasing the symptoms and not the problem. Good luck to all of you new to this issue. Hopefully the data you've lost is recoverable. Huge thanks to the folks who've devoted much time and effort trying to figure this out and are keeping the masses forewarned. RJ Barber

Windows 7 does not refresh folder views

Anonymous

I've got the following problem:

Windows 7 does not refresh automatically the folder view (until I manually refresh by pressing F5) after the following file operations:

Create/delete/rename/move files or folders

Windows 7 Professional final release, international English version. No upgrade, clean install.

It seems to me it's a delay in my case: if I wait for approximately 30 secs, the refresh is done automatically. There are shared folders on the volumes.

I've done the followings:

deleted IconCache - did not help
reset folder views - did not help
turned off file sharing and network discovery - did not help
made a clean boot - did not help
ran sfc - did not found any violations
created new user account - did not help
updated the BIOS to the latest version - did not help
updated the VGA driver to the latest version - did not help
turned off file indexing - did not help

- ran Windows 7 in Safe Mode (without Networking): it seems the issue does not occur

I could be satisfied with Windows 7 but this issue is terribly annoying cause I work with a lot of files day by day.

Could anybody help me?

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

I've narrowed down more the possible causes of the issue:

If You disable the Client for Microsoft Networks in properties of Local Area Connection - the issue disappear (maybe only in my case).

0 comments

Answer accepted by question author

Anonymous

Hello,

Welcome to Microsoft answers forum for Windows Vista Community!

What happens when you try to boot in safe mode?

To start your computer in safe mode, you can refer the below link:

http://windowshelp.microsoft.com/Windows/en-US/help/323ef48f-7b93-4079-a48a-5c58eec904a11033.mspx

I would suggest you to place the computer in a clean boot state and check if the issue resolved:

Log on to the computer by using an account that has administrator rights.
Click Start, type msconfig.exe in the Start Search box, and then press ENTER to start the System Configuration Utility. If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
On the General tab, click Selective Startup, and then click to clear the Load startup items check box. (The Use Original Boot.ini check box is unavailable.)
On the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all.
Click OK, and then click Restart.
Check if you still have the issue.

Refer the link below for more details:

How to troubleshoot a problem by performing a clean boot in Windows Vista

http://support.microsoft.com/kb/929135

Reset the computer to start as usual After you have finished troubleshooting, follow these steps to reset the computer to start as usual:

a. Click Start , type msconfig.exe in the Start Search box, and then press ENTER.

If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
On the General tab, click the Normal Startup option, and then click OK.
When you are prompted to restart the computer, click Restart.

e. If this does not help, try to run a SFC scan. To do a SFC scan follow the steps below:

Use system file checker tool which is also called SFC scan.

System File Checker (SFC) checks that all Vista system files are where they should be as they were by default and not corrupted, changed, or damaged.

Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as Administrator.
Click Continue or supply Administrator credentials if prompted.
In the Command Prompt window type the following, and press Enter:

sfc /scannow

You should see the following on-screen messages:

Beginning the system scan. This process will take some time.

Beginning verification phase of system scan.

Verification % complete.

Once the scan has completed, test to see whether the issue that you are experiencing is resolved or not.

Regards,

Savan – Microsoft Support.

0 comments

Answer accepted by question author

Anonymous

I have had the same problem recently. Here's what I discovered, FWIW:

After reading all of these responses it seemed that, at the core, this is related to the Windows UI shell and how it tries to "reach out" to other systems. Fixes included disabling the Windows Client, disabling home groups, disabling file shares, etc.
I discovered that I have the problem only in certain folders. For example, if I try to create a folder in my DOCUMENTS folder, the problem occurs, but if I create the folder in a random folder on the C: drive (e.g. C:\MyTest), no problem!
I discovered that the folder DOES eventually appear--it just takes 30+ seconds. By pressing F5 I was "rushing" the process. This also sounds like a network client timeout kind of thing.

I wanted to start with the simplest, lowest-impact solution. It worked:

I opened COMPUTER and removed a "Network Connection" that pointed to a server that is not currently available.

That solved the problem completely.

Dan Holme, Intelliem

0 comments

Answer accepted by question author

Anonymous

Hi Nucleo,

Thanks for posting in Microsoft answers!

The issue you've posted seems to be a known issue.

Please refer the link below for a similar issue and check if that helps you:

http://social.technet.microsoft.com/Forums/en/w7itproui/thread/8afb8b65-900c-4f42-b1df-3c2394417b6e

Also, if you have any concerns or feedback, please visit the link below:

Microsoft Connecthttp://connect.microsoft.com/

Regards,

Gokul - Microsoft Support

0 comments

Answer accepted by question author

Anonymous

Just to update my posting, I applied these fixes on 03/12 and as of today 08/12 the problem has not returned.

0 comments

536 additional answers

Anonymous

2015-05-14T18:12:42+00:00

No solution here, but an observation. I'm not an engineer or a card carrying member of the power users club, but I have some problem solving skills and I think most users involved in this thread, including MS support are hopelessly lost down a rabbit hole and have become entangled in the details of where the problem evidently is not.

After reading 5 years and 50 pages worth of issues and solutions one common theme surfaced. The common theme is the file system, or potentially in one of the gazillion layers in the Windows OS that takes part in manipulating the file system. The issues occur when there is a corrupt, missing, or otherwise inaccessible file or file link that points to an SD card, a DVD, a CD, a local folder, a network folder, etc. These are all different file locations with different drivers and different subsystems. How could they all be suffering from the same problem? The answer is, they are not. A layer of the OS that accesses them all via the broken link is having the problem.

Any fix to a broken link to one of those mediums is temporary until a new broken file link exists, then the user gets hit with the delayed refresh again. The common thread is the file system, not the networking system, not the optical disk system, not the SD card reader system, etc. So while the workarounds correct the symptom for the specific file medium involved in the refresh issue, the issue almost always returns when another file or file location link breaks. Time to stop looking at the file locations and start looking at the file system, or the Windows 7-layer bean dip of protocols and subsystems that take part in accessing the file locations.

If you are lucky and remove the links to the failed file locations, the problem is corrected immediately. If your are even more lucky and don't experience a missing or failed file link again, the refresh issue never comes back. For those of us who do a ton of file manipulations across a wide variety of file locations, not so lucky. The issue usually returns in a short time and we start losing data, again, before we figure out the refresh issue is back.

The reason these remedies (workarounds) are temporary is because the file system or the Windows 7-layer bean dip interface to the file system is the problem and it fails to handle the very common condition of a file location link becoming invalid. Actually it does handles it. It just takes 30+ seconds to choke on it before it refreshes your screen allowing you to accidently delete data.

Unfortunately I don't find it hard to believe that after this many years and this much data collected (I'm only looking at one single forum thread. I'm sure M$ has a zillion other threads and help desk cases just like this), M$ has not figured out they need to stop looking at the separate file locations involved, but need to determine what the common thread is. Frustratingly, as so many have pointed out, M$ has determined that spending their time and money screwing up perfectly good user interfaces, taking functionality away, adding functionality we don't need, and hopelessly hiding the functionally they leave behind in the most obscure and irrelevant places is more important to their bottom line.

Until that changes, we probably wont see this issue resolved in future releases of the OS and will be left with frequently losing data and MS support wasting our time chasing the symptoms and not the problem.

Good luck to all of you new to this issue. Hopefully the data you've lost is recoverable. Huge thanks to the folks who've devoted much time and effort trying to figure this out and are keeping the masses forewarned.

RJ Barber
Was this answer helpful?

0 comments No comments