Microsoft Message Analyzer will be discontinued

[German]A brief message for people who may use the Microsoft Message Analyzer to analyze network data. The product will be discontinued soon and the download will be removed from the Microsoft pages. There is probably no replacement for the free analysis tool.


I noticed this information by chance because Aryeh Goretsky from ESET mentioned it on Twitter. 

In the linked article of Microsoft in the Microsoft Message Analyzer Blog it says in addition:

Microsoft Message Analyzer (MMA) will be retired and its download packages removed from sites on November 25 2019. There is currently no Microsoft replacement for Microsoft Message Analyzer in development at this time. For similar functionality, please consider using a 3rd party network protocol analyzer tool such as WireShark.

In short: The Microsoft Message Analyzer (MMA) will be discontinued and the download will be removed from Microsoft servers on November 25, 2019. There is no replacement.

What does the Microsoft Message Analyzer do?

The Microsoft Message Analyzer is a free tool from Microsoft. It makes it possible to capture, display and analyze the data traffic of a network (protocol messaging, protocol messages, network traces). System events and other messages from Windows components can also be tracked and evaluated.

The Message Analyzer allows users to choose whether they want to capture data live or load archived message collections from multiple data sources (such as log files and Windows Event Tracing (ETW) data) simultaneously.


The Message Analyzer used to be a key component of the Protocol Engineering Framework (PEF) developed by Microsoft to improve protocol design, development, documentation, testing, and support. For more information, see the download page and the Microsoft Message Analyzer Blog.

Cookies helps to fund this blog: Cookie settings

This entry was posted in Software and tagged . Bookmark the permalink.

2 Responses to Microsoft Message Analyzer will be discontinued

  1. Thomas K says:

    Sehr schade, Wireshark kann den Prozess nicht mitloggen, der den Datenverkehr verursacht.

Leave a Reply

Your email address will not be published. Required fields are marked *