I would still like to find out what application generates "mat-debug-xxxxxx.log" files, however.
Me too! And also to find out how to make sure it doesn't happen again.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Why are these files appearing in quantity (every 15 minutes), while running Windows 10 home, in my /apps/local/temp folder? They did not appear before the last 3 days ago.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I would still like to find out what application generates "mat-debug-xxxxxx.log" files, however.
Me too! And also to find out how to make sure it doesn't happen again.
Hello --- do you have a alternative fix for this --- I was posted earlier in this thread that localbridge was creating these files
I'm running Win 10 Pro 1809, Build 17763.914, on home built machine. Running MS Office Pro Plus 2019, version 1903, Build 11425.20244. I started noticing these mat-debug-xxxx.log files about two weeks ago. This fix worked perfectly! Thank you.
Hello — Thanks for your reply. I am not sure if it’s the difference, but I have win10/1909 running on older hardware — which the OS has been updated XP > Vista > Win7 > Win10 — it’s a 32bit OS so that I maybe why the file was in-use
as noted, unlike the common window user I work in a cmd shell (like unix) and when I issued the “del” command on the mat-debug-xxxx.log file the command reported it busy — so that is when I was able to locate it with procexp
now, I have office 2010 on the 32bit os and office 2013 on win10/1909/64bit (this version of office is 64 bit ) and, lastly office 2010 (32bit verison) on another win10/1909 64bit OS
in all these cases the mat-debug-xxxx.log are created, so the logical conclusion is that a office patch did this –
I just hope that MS steps up to the plate and fixes this – Does MS “watch” these forums or does this have to be reported in a more formal way?
Hello --- if you start cmd.exe as admin you can look into windowapps --
I discovered that it was local bridge by trying to delete the mat-debug files -- but it was inuse -- so I then use the process explorer to file out with process was using it
does anyone what changed to now have these mat-debug files multiply like rabbits??