mat-debug-xxxx.log files

Hi, this worked for me as well. Not sure exactly when it started, I think around the launch of 1909, which I am running. I just kept deleting them daily and could never figure it out. They were never locked, so they were easily cleaned up.

I did the MSConfig.exe, Safe mode -> Minimal, rebooted and then cleaned up the temp folder while in Safe Mode. I then ran MSConfig.exe again, unchecked Safe Mode and checked Normal boot and restarted and it's fixed! It hasn't come back. Not sure what was causing it or why this works. I am running Windows x64 1909 and have Office 2019.

Hello ---  do you have a alternative fix for this ---  I was posted earlier in this thread that localbridge was creating these files

It's created by a Microsoft Program called LocalBridge.exe

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?