The following has been happening since updating to 19.1.2360 (build 19.1.4142.0):
On start up I get 165 files in the above folder, all approx 1.5 mb in size (total of 254 mb).
I also get two tmp-shm files on every start up. These are not deleted on restart so the folder is growing and growing.
Can anyone please explain what they are, why they are there and how I can stop them being created.
I assume I can delete them without a problem.
Thank you
Edit: the file format is ‘prbxxxx.tmp’ (where x = ?)
I am getting new ones and the previous ones are still there.
I have now successfully stopped this happening with the prbxxxx.tmp files but am still getting the tmp-shm files (which are being added two at a time with the old ones still there).
To stop this happening I went to the add/modify components section and removed the components shown in the attached screen print.
When there will be a new prbxxxx.tmp file save procmon log. Menu → File → Save… → check all events, check native procmon format and select path where you want to save a procmon log.
I reinstated the options, rebooted but the problem did not reappear.
I then did another clean reinstall, as outlined above, and the problem was back.
I ran procmon as suggested but it was over 3 Gb so I filtered it to show only prb and tmp-shm.
I have zip’d the file but am unsure how to FTP it to the address given so I have attached it to this post (please note I have changed the extension from zip to txt).
Hopefully it will shed some light on the problem although I will do as above (turn off certain options) to stop the build up of files (256 mb per startup).
Please let me know the outcome and also if I can assist with anything.
For what it is worth, I too seem to be getting the same effect on my Win10 (1809, 64 bit) system.
It is not at all clear what event creates the files as (from the time stamps) they seem to appear in batches - I have 25 with the same time stamp, each 1579 kb - and the batches seem to appear once or twice a day, not regularly throughout the day as (for example) vps streaming updates are picked up.
I don’t know whether they are from Avast or not, but I didn’t see them before updating to 19.1.2360. The names are of the form prbE6D6.tmp with the 4 capitals/numbers changing.
The positive is that ccleaner (mostly) removes them.
Michael529 - It may be worthwhile trying my fix in Reply #4 (in Troubleshooting). As I mentioned in #6 I reinstated them and the ‘rogue’ files stopped.
This is only a stopgap (if it works for you) until a proper fix is made. From my research it seems that the Avast service is creating them…
Sorry I did not disable Avast self-defence before running ProcMon. Do you want me to do it again ?
To be clearboth the prbXXXX.tmp and appXXXX.tmp-shm were left behind.
If possible, yes please… it would show us where (i.e. from what piece of code) the files are actually created without subsequent removal. (The filter for prb and tmp-shm only is fine.)
Sorry for the delay - have to do a clean reinstall first to get the problem back.
Have ftp’d yeoldebowler_2_2019 (with self defense off !)
Hope it helps.
