Anatomy of file deletion (there's a search event previously?)

[ng80092a]

I usually delete files using shift-delete
I've noticed that if it's a big folder, or a entire hard drive it processes some kind of search previously to deletion.

Can anyone confirm this?

I acidentally did it, but i'm unsure if any file was deleted before canceling the supposed search
(i didnt had time to read, i just instintively canceled the operation)

Thank you

 

[MilesAhead]

If you have Restore Points you may use Shadow Explorer to compare folder contents from a restore point to what you have on disk now. It's free.

 

[Alejandro85]

I have an idea of what it does there, if I understood correctly.
Apparently, and this is only a guess of mine, it's part of the normal behavior of Windows Explorer, not Windows itself. I think the "search" just assembles a list of files that it will delete for internal use, then it ask if you're sure (if you've keep that confirmation enabled) and then it proceeds to delete the files from that internal cache, so during the "search", it does NOT deletes anything really.
Other file managers, command line or whatever will not do that, so after confirmation they'll begin deleting right away.

BTW, another option to undelete anything in case of accidents that I like to use is Recuva

 

[MilesAhead]

I think the "search" just assembles a list of files that it will delete for internal use

Sounds right to me. It does something similar during copy. It counts all the files before it starts to copy. That's why it's not feasible to use Explorer to copy Windows.old folder. It will count for hours.