RogerSC

No, I've been using Nod32 for some time now (years, but just re-installed this computer a couple of months ago, the first scan was slow *smile*), and the in-depth scan time is about 30 minutes. That isn't bad, but this is a fast computer (SSD and Core i7 processor), so it should scan quickly. And thanks for the tips on file system cleanup...I'll look into that, but what amazes me is that Nod32 says that it is scanning 1.1 million files, while only 140,000 files (closer to the actual number of physical files, I'm sure) are found on my computer. I'm going to play around and see if I can find files to scan that Nod32 reports more than 1 file for. I can assess what's going on when I identify those files (I expect that they are archives of some sort).

Nod32 reports scanning about 1.1 million files on my computer. As far as I can see, I don't have nearly that many files on my computer. The reason that I mention this is because I'd like the scan to go faster, but with that many files reported, I don't see how it could. This raises these questions: 1. How does Nod32 count files? Can one physical file count for more than one file to Nod32, like maybe some kind of archive files or cabinet files or something? 2. Is there a tool for identifying where these files are on my computer's file system? If I have over 1 million files, it seems like a large fraction must be able to be removed, like temporary files. I use the Windows Disk Cleanup, and that doesn't really change this situation materially. Anyone else have this large number of files reported scanned by Nod32 and ask the same question, and figure out what's happening? Just seems crazy. I'd like to add that I just used Agent Ransack to search for all files on my C: and D: drives, and it reports around 140,000 files. So a factor of 8 more files reported by Nod32? Interesting.