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.
Very generous attitude - very commendable. With respect, try to imagine someone who uses hundreds of scripts and small programs to add, copy, rename, move, and delete files, and ALL of them stop working because the file system reports bogus data. Create a file, pass the file name to another program, and that program fails with a "File not found" error, although the file most certainly exists. Or, delete a work file, try to open a new one, and the program fails with a "Duplicate file name" error, although the first file was most certainly deleted. Oh, this is much more than "annoying" to some of us.
As for "we can't blame this 100% on Microsoft", read some of the threads and you will find that the effected people (including myself) encountered this problem on systems as vanilla as any you're likely to find. This indicates that (1) test scenarios were seriously flawed or (2) the operating system was released in spite of this deadly bug (much more likely).
When you're the only game in town, I guess you can afford to give your customers the finger.
And so it goes.
Don