It must be said that intermittent hardware glitches will also hang the OS, and should be disregarded for the purposes of this test since it has nothing to do with the software. What I'm saying is that the 5.5 files are correct while the 6.x ones contain a bug. I just prefer 4-digit groupings. Just ignore the commas if it seems odd. Why I suggest such a high number of files, and also files with content in them (1 byte, but nonetheless content) is because testing in more extreme situations guarantees correct operation in normal usage. I find 2500 to be a bit low, since I have several directories containing 4000+ image files (total number of files on one of my HDDs approximately 25,0000). A more realistic limit would be 1,0000.This post will be edited to display the results of 65535 files test. Edit: The limit is actually 65533, since entry 65535 is the highest and two are taken by . and .. already (unless working in the root directory, although I didn't want to add 64 thousand files to the root of any of my existing drives). This limit is further lowered by long filenames, which take up their own directory entry. "So, what's the result of the test?" Explorer handled up to ~32K files with no noticeable delay, but beyond that point refreshes became gradually slower and slower - the final refresh, to show the full 65533 files, took almost a full minute. However, the OS remained fully functional throughout. I copied the files to another directory, which took approximately 20 minutes. Once again the refresh at the end took nearly a minute to complete. I then deleted the files in the original directory - here is where the first bug occurred - selecting all the files and pressing the Delete button caused explorer to IPF somewhere in the kernel32. Gradually lowering the number of files confirmed that this may have to do with the file count being considered as negative, as it worked fine with deleting ~32000 files at once. Thus I deleted in two chunks, and proceeded to copy the other set of files back - once again, no problems. Deleting again this set in two chunks also free of any problems. So, it seems to work.