IEDiagCMD – Inbuilt Tool to Diagnose & Troubleshoot Internet Explorer problems

IEDiagCMD.exe is a small utility that generates logs requires to troubleshoot issues with Internet Explorer in Windows. It is typically located under C:\Program Files\Internet Explorer on a x86 OS install and C:\Program files (x86)\Internet Explorer on an x64 OS install and can prove to be a very useful tool while troubleshooting Internet Explorer problems.


To bring it up, just type IEDiagCMD.exe in start search and hit Enter. When you execute IEDiagCMD.exe you will see a black window that stays open for few seconds and then closes by generating a cab file on your desktop. Double-click and open the files and you will notice that it contains a few logs and files.


> Ad


  • The first file we know it’s the CBS log that generates mostly after running a system integrity check (sfc /scannow).
  • The second file is Windows Update Log which would have you Windows update history and related information.
  • The third file is the Compatibility View (CV) list. If you want to know more about it check this MSDN article.
  • The next one is Branding log file that helps us in troubleshooting issues with IE
  • The next one Windows_panther_unattend.xml I believe  it an answer file generated at unattended install
  • The next two files are related information about you IE version etc. you can open and view it in Notepad.

Here is what my C__Program Files (x86)_Internet Explorer_signup_install.ins file looks like:

CompanyName=Microsoft Corporation
IE4 Welcome Msg=1

When you need support or help while troubleshooting  Internet Explorer issues in forums or from your IT support, it is a good idea to include this file with it so that it will  make the troubleshooting process easier.

Thanks to my eightforums co-member Bill2 for telling me about this tool.

Posted by on , in Category IE with Tags
Shyam aka “Captain Jack” is a Microsoft MVP alumnus and a Windows Enthusiast with an interest in Advanced Windows troubleshooting. Suggestions made and opinions expressed by him here are his personal one's and not of his current employers. He blogs at