Windows 7, Deleting Large files is extremely slow. (Not going to recycle bin, permanent delete)

Anonymous
2009-12-13T14:37:28+00:00

It is taking a huge amount of time to delete files.

The files are not going to recycle bin (I am hold shift while hitting the Delete key)

Also I have even tried shutting off the recycle bin

I have timed a few of these

Single file delete, 2.6 gb, 2 minutes 14 seconds

Single file delete, 1.9 gb, 1 minutes 44 seconds

Single file delete, 230 mb, 0 minutes 24 seconds

Most of the time the dialog window that pops up says "Calculating..."

Judging by the times, This has something to do with file size.

I get similar time when I delete from the command prompt.

Windows XP would do permanent deletes and moves (on the same drive) in a split second, especially since we are talking about one file.

I work with large image files regularly. I can't wait 2 plus minutes every time I delete one of these files when I may have to move or delete a few hundred at a time.

I am getting very frustrated with Windows 7.

So far...

I have disabled Remote Differential Compression (RDC)

I have disabled TCP AutoTuning and Receive Side Scaling

                netsh interface tcp set global autotuninglevel=disabled (AND)

                netsh interface tcp set global rss=disabled  (And rebooted)

There are no removable drives, USB devices, or other attached devices other that the keyboard and mouse.

I have disabled

Windows Search and Indexing

I am viewing "Details" only in windows explorer (No Thumbnails)

I have shut off IPv6 support (I read about it somewhere but I believe it was to do with network operations, but I tried it anyway)

Teredo Tunneling Pseudo-Interface is disabled

All Drivers are up to date.

I have completely wiped the drive and reloaded the OS.

This is on a 1tb storage drive, no RAID, 3gb SATA drive (Seagate 7200.12)

Windows 7 64bit (Windows experience is listed as 6.1)

Intel i5 processor with 4gig memory

Fresh install, fast hard drive (OS).

Avast AV

Not much else running

Windows for home | Previous Windows versions | Files, folders, and storage

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 No comments

76 answers

Sort by: Oldest
  1. Anonymous
    2015-06-19T19:54:36+00:00

    Don't use the library location to delete...... instead go to   "Computer  C:\  users "  and find the appropriate directory which is where the actual file is stored and delete.  I am amazed that it is just like XP again with instant deletes..  I have now put a shortcut to the location on the desktop so I can go right to the files to be deleted.  Try it!!!!!!!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-09-03T13:22:31+00:00

    Hi

    For what it is worth, I am currently in hour 14 of a delete operation, with supposedly 3 more hours to go. I say 'supposedly', but it could be any number really because the delete dialog jumps anywhere between 2 hours and 12 hours at the moment.  I am using Win 8.1 on a Surface Pro 3, wireless connection via my router to a NAS.

    Foolishly, I set the File History utility to store on the NAS, accepting the default settings. After using my system for about 4 months, I finally had a look and discovered I had 110GB of historic files in the backup.

    I tried the 'clean up' option to eliminate older copies, setting to 'all but the latest', and set it off to do its job. It was doing the delete at 2/3/4 files per second, sometimes rising to the dizzy heights of 7/8 files per second.  At this point, I figured I would be faster just deleting the whole thing and restarting with more suitable settings for the File History, so, I stopped the File History completely and through Windows Explorer, just set off on the epic journey as stated above. I quickly discovered that the operation was just exactly the same as the File History - Clean Up operation. As it was I was already way past my bed time so I thought I would leave it overnight.  Now, some 14 hours later with a further 3 hours (or much more who knows), I have google and found this thread.

    Some of the methods mentioned may in fact be a better solution, but for the moment I think I am better off just letting this current delete operation reach it's final conclusion.

    Anyone know if:   I did just cancel the job after 14 hours - would the files supposedly already deleted remain so? Or, would Windows in all its wisdom think I meant not to delete them and restore them from some magic cache somewhere?

    MS really do need to offer users some means of 'I just want to get rid of these files - I accept full responsibility for this operation' option!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-09-03T23:41:35+00:00

    That is excessive for sure, and as said, the estimated time remaining can be all over the chart. I would suggest placing all the files to be deleted in one folder, and then  and then installing Unlocker,  but make sure that you deselect the Bing toolbar and other add on option when that window comes up during installation. 

    Then open up the location of your files, right click on the folder and choose Unlocker, and then delete.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-09-04T00:23:56+00:00

    Hi

    Thanks for your reply.  I will have a look at that application you posted a link for.

    As it happens, I finally waited it out - all 17 hours of it! I have set the File History to  a 1 month period now so I am hopeful that it is more manageable now. If it still proves to be of a silly size I will just do without File History completely. It would be much more sensible if MS had allowed a 'keep X number of files' instead of just a time period.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-10-19T14:25:17+00:00

    "You can boot the system into Safe Mode and [run] some tests."

    So, what you are saying is, "You need to reboot your system to delete large files." Is this a new feature or an enhancement? (Maybe we should patch this?) 

    I run into this very frequently. I do not believe that this is an acceptable performance behavior.

    Was this answer helpful?

    0 comments No comments