Logs created (by Click to Run?) in Windows Temp Directory

Question

_{Saturday, October 12, 2019 12:36 PM | 1 vote}

See update below!

The problem of excessive logs created by Click-to-run does not seem to be resolved by explaining that Click-to-run is an important component in Microsoft Office.

I have installed office 2016 about a month ago, and in the last 10 days it has created more than 300 Gigabytes of log files. This is extremely annoying.

There must be some way to limit this excess logging.

My hard drive is an SSD, and this rate of logging is unacceptable.  

Update:

My initial diagnosis (That Click To Run is to blame for generating thousands of files a day in Windows/Temp was wrong. Most files that I saw (in the format of *_C022F270-7A28-0002-810A-23C0287AD501.evtx) are generated because of some problems with the Microsoft Store. 

The solution I found was thanks to AlainD, as described in the following link in superuser dot com, questions 1371229 (google "low-disk-space-after-filling-up-c-windows-temp-with-evtx-and-txt-files").

As he writes in his post: "My problem appears to be related to the in-built Windows Store app and the AppX Deployment Service. I disabled both as follows"

I did the same, and the file fuddling stopped.

All replies (1)

_{Monday, October 14, 2019 9:08 AM}

Hi,

Thanks very much for your sharing. It would be helpful to other users who encounter the same issue and read this thread. Your contribution is highly appreciated.

Best Regards,

Emily 

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Office 2019.