- File Path:
- Description: Diagnostics Troubleshooting Wizard
- Status: Signature verified.
- Issuer: CN=Microsoft Windows Production PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
- Subject: CN=Microsoft Windows, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
- Original Filename: msdt.exe.mui
- Product Name: Microsoft Windows Operating System
- Company Name: Microsoft Corporation
- File Version: 10.0.18362.1 (WinBuild.160101.0800)
- Product Version: 10.0.18362.1
- Language: English (United States)
- Legal Copyright: Microsoft Corporation. All rights reserved.
The following table contains possible examples of
msdt.exe being misused. While
msdt.exe is not inherently malicious, its legitimate functionality can be abused for malicious purposes.
Invokes a troubleshooting pack at the command line or as part of an automated script, and enables additional options without user input.
msdt </id <name> | /path <name> | /cab < name>> <</parameter> [options] â€¦ <parameter> [options]>>
||Specifies which diagnostic package to run. For a list of available packages, see Available Troubleshooting packs.|
||Specifies the full path to a diagnostic package. If you specify a directory, the directory must contain a diagnostic package. You cannot use the /path parameter in conjunction with the** /id, **/dci, or /cab parameters.|
||Prepopulates the passkey field. This parameter is only used when a support provider has supplied a passkey.|
||Displays the troubleshooting history in the specified directory. Diagnostic results are stored in the userâ€™s %LOCALAPPDATA%\Diagnostics or %LOCALAPPDATA%\ElevatedDiagnostics directories.|
||Specifies an answer file in XML format that contains responses to one or more diagnostic interactions.|
||Makes the troubleshooting pack modal to a window designated by the parent Console Window Handle (HWND), in decimal. This parameter is typically used by applications that launch a troubleshooting pack. For more information about obtaining Console Window Handles, see How to Obtain a Console Window Handle (HWND).|
||Enables (true) or suppresses (false) the final troubleshooting screen that asks if the user wants to explore additional options. This parameter is typically used when the troubleshooting pack is launched by a troubleshooter that isn’t part of the operating system.|
||Specifies a set of interaction responses at the command line, similar to an answer file. This parameter isn’t typically used within the context of troubleshooting packs created with TSP Designer. For more information about developing custom parameters, see Windows Troubleshooting Platform.|
|/advanced||Expands the advanced link on the Welcome page by default when the troubleshooting pack is started.|
|/custom||Prompts the user to confirm each possible resolution before it is applied.|
Troubleshooting packs comprise a set of root causes, each of which describes a specific technical problem. After completing the troubleshooting pack tasks, each root cause returns a state of fixed, not fixed, detected (but not fixable), or not found. In addition to specific results reported in the troubleshooter user interface, the troubleshooting engine returns a code in the results describing, in general terms, whether or not the troubleshooter fixed the original problem. The codes are:
|-1||Interruption: The troubleshooter was closed before the troubleshooting tasks were completed.|
|0||Fixed: The troubleshooter identified and fixed at least one root cause, and no root causes remain in a not fixed state.|
|1||Present, but not fixed: The troubleshooter identified one or more root causes that remain in a not fixed state. This code is returned even if another root cause was fixed.|
|2||Not found: The troubleshooter did not identify any root causes.|
MIT License. Copyright (c) 2020-2021 Strontic.