Now that the command is a feature i though i would script FileSeek checking each folder in a directory. Scanning an entire drive, at least on Server 2003, usually crashed. I figured it was too much information for the computer to handle so i broke up the scan into smaller single scans. What seems to be happening now is that some of the scans are crashing and im not sure why. Has anyone seen this before:

.NET-BroadcastEventWindow.2.0.0.0.33c0d9d.0: FileSeek.exe - Application Error

The instruction at OxO3eeF516” referenced memory at “0x00001158. The memory could not be “read.
Click on OK to terminate the program

I get a bunch of these and i dont know why its failing.
Here are the details of the search if you are curious

Regex Query = "\b(4(?:\d[ -]*?){12}(??:\d[ -]*?){3})?|5[1-5](?:\d[ -]*?){14}|3[47](?:\d[ -]*?){13})\b"
Exclude Query = "(\.pst|\.lnk|\.msi|\.exe|\.dll)"
Include Query = "*.*"

if it helps i caught one of the failures. It got stuck trying to read a 100MB AVI. I closed the fileseeek since it had been stuck there for 8 hours. When i closed it the error occured. While i could omit that file type from the search i would rather not since i am doing PCI Compliance scans and ommisions can be considered against compliance. They could hide data in an AVI since i ommited it from a scan. Im already skipping files like exe and dll. The more ommisions i have to more risk i create.

I look forward to the resolution. Let me know if you would like me to test a beta release. Thanks Keith.