I have an annoying delay on the use of my computer since upgrading to Windows 10. The most obvious place is when using the file explorer. I get a 2 to 3 second delay on most operations. These would include: dragging a file into a folder, renaming a file, naming a new folder, etc. When I drag a file into a folder, it does not sort the new file, but the file stays at the bottom of the list. Pretty annoying. I see this same delay in quite a few operations.
I have an i7-2700K processor, 16GB ram, a 250 GB Samsung SSD 840 Pro along with a 2 TB storage drive with ample space on both. I did not have this delay in Windows 7 that I upgraded from.
I've the same problem, i7- 3.2 Ghz, 12 GB RAM, SSD 250 Samsung SSD 840 Pro!!! Do U have mapped drives?
Also my Win 10 file explorer does not refresh automatically the folder view.
I fund problem with 3rd party software installed on my PC, that includes a context menu extension. Excellent solution here:
I fund problem with 3rd party software installed on my PC, that includes a context menu extension. Excellent solution here:I have an annoying delay on the use of my computer since upgrading to Windows 10. The most obvious place is when using the file explorer. I get a 2 to 3 second delay on most operations. These would include: dragging a file into a folder, renaming a file, naming a new folder, etc. When I drag a file into a folder, it does not sort the new file, but the file stays at the bottom of the list. Pretty annoying. I see this same delay in quite a few operations.
I have an i7-2700K processor, 16GB ram, a 250 GB Samsung SSD 840 Pro along with a 2 TB storage drive with ample space on both. I did not have this delay in Windows 7 that I upgraded from.
check 3rd party software installed that includes a context menu extension. excellent solution here:I've the same problem, i7- 3.2 Ghz, 12 GB RAM, SSD 250 Samsung SSD 840 Pro!!! Do U have mapped drives?
Also my Win 10 file explorer does not refresh automatically the folder view.
It's mostly due to default handlers that generate previews for things like images and avi's/mkv's/mp4's etc. Set to Detail View and set it to "all folders" and it might speed up a bit. Also, change the default player of video content from Movies and TV to VLC-Not the tile version, the regular desktop version, because that app can handle all content types easily - Movies and TV chokes on several codec types and that probably affects Explorer.I have an annoying delay on the use of my computer since upgrading to Windows 10. The most obvious place is when using the file explorer. I get a 2 to 3 second delay on most operations. These would include: dragging a file into a folder, renaming a file, naming a new folder, etc. When I drag a file into a folder, it does not sort the new file, but the file stays at the bottom of the list. Pretty annoying. I see this same delay in quite a few operations.
I have an i7-2700K processor, 16GB ram, a 250 GB Samsung SSD 840 Pro along with a 2 TB storage drive with ample space on both. I did not have this delay in Windows 7 that I upgraded from.
I do have mapped drives. Somehow, the problem seems to have resolved itself. Updated driver?I've the same problem, i7- 3.2 Ghz, 12 GB RAM, SSD 250 Samsung SSD 840 Pro!!! Do U have mapped drives?
Also my Win 10 file explorer does not refresh automatically the folder view.
Yes, That was my post in 8 forum. However, step 5 in that post will not work with Windows 10. I updated here:check 3rd party software installed that includes a context menu extension. excellent solution here:
Right Click on Desktop take long time to show up - Windows 10 blog
In addition. Incompatible Shell extensions is one of the cause. Delay can be caused by other things such as:
- Explorer is busy re-discovering the mapped drive because the DNS Cache was not up to date.
- Corrupted Systems Files
- Corrupted HD drives
- External HD need time to wake up
- Corrupted Video/Audio files which explorer is busy trying to build the thumb nails
- etc...
It resolved by itself because the DNS was updated.I do have mapped drives. Somehow, the problem seems to have resolved itself. Updated driver?
