SOLVED! ‘‘No Export Analyze Found’’

Nowadays, people could use quite a few tools to analyze issues on Windows computers but Windows Debugger (WinDbg) is always a safe bet. Designed by Microsoft, WinDbg is able to help Windows users identify and fix problems on their devices. Still, despite its usefulness,  WinDbg remains far from perfect and reports of oddities appear from time to time. Check out this article if WinDbg keeps returning “No export analyze found” as you use it to troubleshoot Windows problems. 

What Is Going On

The Microsoft Store version of WinDbg, WinDbg Preview, has a bug that prevents it from loading a dll file that exports the Analyze function. That makes WinDbg Preview less useful for debugging purposes compared to its Windows 10 SDK counterpart. On the bright side, it’s possible to circumvent the “No export analyze found” issue if you know what must be done. 

‘‘No Export Analyze Found’’: Fixes 

Apply Changes To Startup Settings 

  • Step 1: Open WinDbg.
  • Step 2: Go to  File > Settings > Debugging settings.
  • Step 3: Under Startup, copy and paste the command .load C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2110.27001.0_neutral__8wekyb3d8bbwe\amd64\winext\ext.dll then hit OK.

After you finish, close WinDbg and open a dump file. Assuming that things proceed smoothly, you could run  !analyze -v like usual. 

Switch To Windows 10 SDK WinDbg

“No export analyze found” is an issue that plagues WinDbg Preview of Microsoft Store. Thus, if you want to locate the root cause of an error and address it in a hurry, use Windows 10 SDK WinDbg. 


How should I use WinDbg?

WinDbg is a powerful Microsoft Windows debugger that can be used to debug both user-mode and kernel-mode code. Unlike other Windows debuggers, WinDbg is capable of attaching to a running process and can also be used to launch a program under debug. WinDbg also provides a number of features that make it ideal for use in a production environment, such as its ability to generate crash dumps and its support for remote debugging. 


While WinDbg is primarily used by developers to debug software problems, it can also be used by system administrators to troubleshoot system issues. In addition, WinDbg can be used by law enforcement and security professionals for forensic analysis of software vulnerabilities.

What must be done to install WinDbg?

  • Step 1: Go to Microsoft WinDbg
  • Step 2: Hit Get/Install/ Open button
  • Step 3: Pick Open Microsoft Store in the popup window
  • Step 4: Click Install button
  • Step 5: Once the installation concludes, hit Launch

Where is WinDbg on my computer?

After you finish installing WinDbg, you can locate it at:

  • C:\Program Files (x86)\Windows Kits\10\Debuggers\x64
  • C:\Program Files (x86)\Windows Kits\10\Debuggers\x86

How could I read a dump file?

  • Step 1: Type WinDbg in the Search bar, right-click WinDbg and click Run as an administrator
  • Step 2: Navigate to File menu, select Start debugging and choose Open Dump File
  • Step 3: Choose the dump file from the folder location i.e %SystemRoot%\Minidump
  • Step 4: Click Open, type !analyze-v in the run command and hit Enter
  • Step 5: The moment the analysis completes, WinDbg is going to display the results of the analysis for review.

Why is debugging necessary?

Debugging is an essential part of the software development process. Without it, developers would be unable to identify and fix errors in their code. Debugging can be a challenging process, but it is essential for ensuring that software works as intended. There are a variety of different debugging techniques, but the most important thing is to have a clear understanding of the code and the system. By taking the time to debug code, developers can save themselves a lot of time and frustration in the long run.

What does enable debugging mean?

Enable debugging means turning on the feature in the software that provides more information about operations. The information can be useful when people want to know why the software is not working correctly. 

It’s noteworthy that the level of detail of the information provided by the debug feature varies depending on the software. Sometimes, debugger may only provide a basic log of events that occurred while the software was running. In other cases, debugger could compile a detailed report that shows exactly what each line of code is doing.

Debugger can be turned on by setting a specific flag or option in the software’s configuration file. The debug feature can also be turned off by setting the flag or option to false or 0. When debugger is up and running, it usually slows down the software due to the need to generate and store the information. Thus, debugger is usually only turned on when there is a problem and when everything returns to normal, it would be turned off again.

Tips And Tricks

  • Use the command .cmdtree <file> if you want to bring up another window that displays commonly used commands. 
  • Use Cygwin to grep the list of allocations, grouping them by size:

grep “busy ([[:alnum:]]\+)” DumpHeapEntries.log \

| gawk ‘{ str = $8; gsub(/\(|\)/, “”, str); print “0x” str ” 0x” $4 }’ \

| sort \

| uniq -c \

| gawk ‘{ printf “%10.2f %10d %10d ( %s = %d )\n”, $1*strtonum($3)/1024, $1, strtonum($3), $2, strtonum($2) }’ \

| sort > DumpHeapEntriesStats.log

Leave a Comment