Can i delete msdtc log

What's New. Driver Reference Table. Everywhere Threads This forum This thread. Advanced search Latest activity. JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding. You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser. Weetje Contributor. Joined Jan 24, Posts Hello, I'm new here as I'm experiencing a problem with msdtc.

Went through some of the other forums: like it! Anyway, after installing a bunch of windows updates two days ago I got a blank screen or black screen, with a cursor, but no desktop. After trying many different things, I couldn't get it fixed. I already played around with some updates that wouldn't install the day before the big one: KB , so was getting tired of it and at some point I decided to go back to a restore point.

This brought back the desktop and I could make the changes I planned by doing things a bit differently. I'm a little reluctant to run all the updates given that I may get a black screen again; I figured out afterwards the program startisback was the LIKELY culprit, as I hadn't updated that to the latest version, but I'm not sure and I'm sort of done for now with all the updating spending the whole weekend trying to fix things.

Normally I'm able to fix things myself, even though it takes time, but this one is beyond me. No change. So, I hope you guys can help me. I ran the sfcfix.

The issues in that thread were very similar. Hello and welcome Weetje! Hi zcomputerwiz, Thanks for the response and help. I did run the procedure in that sticky thread as it matches my error , and if I remember correctly also after changing back the registry value described above.

Just to be sure, I ran the procedure again, and it still gives an error. The CBS. Hi zcomputerwiz, Thanks for the quick reply. I really appreciate your help. I ran the new sfcfix. SFCFix version 2. Specifies a DTC instance. The cmdlet resets the log file for this instance. If you do not specify this parameter, or if you specify a value of Local, this cmdlet resets the log file for the local DTC instance.

Specifies the maximum number of concurrent operations that can be established to run the cmdlet. The throttle limit applies only to the current cmdlet, not to the session or to the computer. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.

Privacy policy. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. The program attempts to listen on port This behaviour, ordinarily is perfectly normal, however, because of the sensitive nature of this process, it is important that you ensure your system is not infected with a malicious file.

The process will execute when Visual Basic 6 is compiling a program This behaviour is normal. That said, I recommend you continue reading for the various solutions that have helped to solve the many problems you may be having on your computer system. Many users may fear that the process running on their computer is a malicious file, because of its ability to listen on a port.

However, this fear is unfounded, because msdtc. However, given the number of viruses that disguise themselves as Msdtc. You can check by evaluating the file size and install location on your computer. Users should also run a full virus scan of their systems. This tool is specifically designed to detect and remove these malicious files, while restoring previously damaged Windows components in the process.

This makes SpyHunter one of the very best antimalware tools available. To fix the error message associated with the msdtc. In order to do that, do the following:. This will load up Command Prompt , from here, type msdtc —resetlog and press Enter. Note: make sure you type the command correctly, as you do not want to corrupt any data on your computer. Once you have successfully reset the log file, simply type start msdtc and press Enter.

If resetting the log file in Command Prompt fails to fix the error.