Strange File dddLog_0.bin created by Everything

[nekonull]

I use Everything every day, and is works great. However, after I installed Everything on my new laptop, I observed a strange behavior: Everything would create a file called dddLog_0.bin under the path of C:/Windows/Temp/DDDLogs.

Creating a temp file would not be an issue, but the file tends to grow as time goes. It usually grows to 30GiB after 10 days, and I have to manually delete it every week.

I searched the file on Google but found nothing, so I used ProcMon from Microsoft SysInternels to find out the creator of the file, which turns out to be Everything. (Link to ProcMon records: https://1drv.ms/f/s!Ag_BoBikZ9WEje9_vueKb5MOnkIbfw)

I'd like to know the answer of following questions:
1. Is the file really created by Everything, or the way Everything indexes files lead me to a wrong conclusion?
2. If the file is indeed created by Everything, is there any method to stop the file from being created?
3. If the file has to be created, is there any method to limit the size of the file?
4. If the size can not be limited, is there any method to delete the file automatically?

[void]

Thanks for the PML logs and feedback.
Everything is not creating this file.

Everything is opening this file to read the file size and date modified timestamp due to modification.
You can see in the Process Monitor log CreateFile is called with the Read Attributes access. (no write access)
CreateFile really means create a handle to a file. Not create a new file on disk.

It's not clear from the log what is writing to this file.
It might be related to Intels PROSet Wireless Wifi / CCG Wireless Marketing?

Please try Process Explorer and see what has open handles to this file. Find menu -> Find handle or dll... -> search for: dddLog_0.bin

[nekonull]

Thank you! I tried ProcMon again, and unfiltered System, which points me to my Intel network driver. It seems like the driver file Netwtw06.sys is the real creator of the file.

Sorry for my incorrect conclusion of Everything creating this giant file, and wish everything goes well while creating great software.

I just updated my driver to the newest version (21.50.1), and this seems to solved the problem. I will update this post tomorrow to see if this really works.