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: Most helpful
  1. Anonymous
    2016-05-23T13:52:48+00:00

    I have not had this issue since Windows 7.  Windows 8, 8.1, and 10 work fine.  No issues deleting large files or any files for that matter.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-05-21T23:24:12+00:00

    Just use the command line - works for me every time: always did - right back to the original windows when the command line was all we had.

    Left pane in explorer,

    right click on the folder containing the file you want to delete

    click on 'open command window here'

    command window opens

    type "del <filename>" 

    gone

    And if you want to copy files quicker and simpler than the windows copy function, use Ice Mirror (google it).  I've used it for years to do backups/block copy.  

    Tried Tera Copy years ago, pretty good too.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-02-24T03:29:54+00:00

    It did not work for me on 32-bit Windows 7. Still getting that ridiculous long time to perform this simple task.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-10-19T14:30:50+00:00

    Ha. I didn't read the other responses until now. I guess I'm not the only one really frustrated with the lameness of Windows 7 file management. I tried the "right-click, properties" method... didn't work for a 20GB vm (CentOS). The delete dialogue is still spinning as I write.

    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