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).
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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:
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:
- 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.
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).
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:
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.
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.
sfc /scannow
Beginning the system scan. This process will take some time.
Beginning verification phase of system scan.
Verification % complete.
Regards,
Savan – Microsoft Support.
I have had the same problem recently. Here's what I discovered, FWIW:
I wanted to start with the simplest, lowest-impact solution. It worked:
That solved the problem completely.
Dan Holme, Intelliem
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
Just to update my posting, I applied these fixes on 03/12 and as of today 08/12 the problem has not returned.
Okay, New system, iBuyPower, just installed Windows 7 (64 bit). Ran great for about 8 days. Then I got hit with this same problem. Would take about 30 seconds for folders to refresh. I removed old programs, disabled then removed antivirus (after doing full sweep with Kaspersky then later with clean MSE) nothing worked. Pulled the wireless network card, bingo, problem solved. Switched to Ethernet to go online and get a new driver, and problem hit again. Swapped out drivers, 3 different cards - long story short, if I disable the adapters, everything runs perfect, otherwise 30 second refresh. Reading these posts I did notice I had mapped network locations on my desktop and on "Computer". I pulled those. It's been only a few hours, but the problem appears to have vanished. Seems every network location MUST be valid or this happens. I had installed KB980408 BEFORE the problem happened (as part of my updates as soon as I installed the system). This problem has been KILLING my experience, 2 days looking for solution. Thank god for this thread. I highly recommend removing ANY SHORTCUTS to any network locations, as well as mapped networked drives.... Just tested again, still working... B
This post is a good example of the gravity this issue represents. Most of us technical folk are used to finding workarounds for weird OS behavior and will re-install an OS multiple times, swap NICS, try driver version regression, any other examples of the dozens of random things people have noted have changed this behavior. That, in itself indicates the complexity of whatever underlying issue causes it. I don't envy the QC people digging out the root cause of this one. Nonetheless they absolutely must do so.
My wife is an end user, so are the kids. They, like the 2000+ users I support at my fortune 500 workplace are utterly at a loss to understand the symptom, let alone catch on to the 'fix' of mashing F5 whenever things 'get weird' as some kind of solution. What they DO report is that this 'new 7 thing' doesn't work. Somewhere between 20% and 60% of my users are reporting this problem. That huge margin of error is partly due to the 'fix' getting around and people walking by other peoples keyboards and pressing F5.
In corporate america we rely on things like Network Cards, Shared Folders, Mapped Network Drives, Shortcuts to those drives, etc... We can't turn them off. This hurts the reputation of the OS far more than any other thing we support and it saddens me greatly that I am about to be forced to give up all the advancements Windows 7 has brought my workflow and policy administration because my users are begging for XP back.
Why? So they can get some work done. Before I rolled out 7 these folks didn't even know there were function keys on the keyboard, let alone what F5 did.