When another program, such as REGEDIT during an "Export...", is writing to a file, the command line FIND program give the infuriating File not found message.
The problem is actually that the file is BUSY, and unavailable to be read by the FIND program.
During REGEDIT's export to dump.reg (see the changing size of the file), we get this error message.
C:\WINDOWS\system32>dir /od
[... many lines ...]
10/21/2011 04:43 PM <DIR> ..
10/21/2011 04:43 PM <DIR> .
10/21/2011 04:43 PM 57,671,680 dump.reg
2705 File(s) 707,559,960 bytes
61 Dir(s) 5,861,949,440 bytes free
C:\WINDOWS\system32>find /i "qrp" dump.reg
File not found - DUMP.REG
C:\WINDOWS\system32>dir dump.reg
Volume in drive C has no label.
Volume Serial Number is 10F7-FE2B
Directory of C:\WINDOWS\system32
10/21/2011 04:43 PM 67,436,544 dump.reg
1 File(s) 67,436,544 bytes
0 Dir(s) 5,850,415,104 bytes free
C:\WINDOWS\system32>find /i "qrp" dump.reg
File not found - DUMP.REG
C:\WINDOWS\system32>
=========================================================================================
After REGEDIT is done, we get what we expect. Note the increased file size.
C:\WINDOWS\system32>find /i "qrp" dump.reg
---------- DUMP.REG
"ComputerName"="QRP32"
^C
C:\WINDOWS\system32>dir dump.reg
Volume in drive C has no label.
Volume Serial Number is 10F7-FE2B
Directory of C:\WINDOWS\system32
10/21/2011 04:45 PM 92,578,603 dump.reg
1 File(s) 92,578,603 bytes
0 Dir(s) 5,820,424,192 bytes free
C:\WINDOWS\system32>