Difficulty loading symbols

[machish]

I loaded up a .etl trace (recorded with wpa.exe), loaded it in Profile Explorer, but the function names won't resolve.

I've confirmed under Profiling -> Profile Report -> Modules that the PDB is listed under Debug file. The path to the file also looks correct.

Is there a trick to tirggering the number to function name mapping, so that the Flame Graph view (as well as the Function panel) are meaningful?

[machish]

Copilot CLI found the problem: msdia140.dll needed to be `regsvr32'ed. This fixed it.

● Read latest ProfileExplorer log tail
  $ Get-Content "C:\Users\REDACTED\AppData\Local\Microsoft\ProfileExplorer\ProfileExplorer.log" | Select-Object -Last 60
  └ 76 lines...

● Found it! Every PDB fails with the same error:

   Retrieving the COM class factory for component with CLSID {E6756135-1E65-4D17-8576-610761398C3C} failed: 800700c1 is not a valid Win32 application

  That CLSID is msdia140.dll (the DIA SDK COM component for PDB parsing). Error 0x800700C1 means "not a valid Win32 application" — this is an architecture
  mismatch. ProfileExplorer is a 64-bit .NET 8 app, but the registered msdia140.dll is likely 32-bit (or vice versa), or it's not registered at all.

  Fix: Register the 64-bit msdia140.dll. It should be in your VS installation:

   # Find the 64-bit msdia140.dll
   dir "c:\bin\MicrosoftVisualStudio" -Recurse -Filter "msdia140.dll" | where { $_.FullName -match "amd64" }

   # Register it (run as admin)
   regsvr32 "C:\bin\MicrosoftVisualStudio\18\Insiders\DIA SDK\bin\amd64\msdia140.dll"

  After registering, restart ProfileExplorer and reload the trace — all symbols should resolve.