4,375 questions
This is where you instruct the VS2022 debugger to only load symbols for those modules you specify -
How to debug the "wow64.pdb is not loaded" error during DLL project debugging in Visual Studio 2022?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(48, 25%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHJ%3C/text%3E%3C/svg%3E)
HY Jeong
0
Reputation points
I am trying to debug a DLL project used within Excel VBA using Visual Studio 2022, but I am encountering the "wow64.pdb is not loaded" error, which prevents me from debugging. The DLL is intended to be used in 32-bit Excel, and my computer is offline for security reasons. How can I handle this error? I have already tried turning on the Microsoft symbol server in Debug -> Options -> Symbols.
Microsoft 365 and Office Development Other
Microsoft 365 and Office Excel For business Windows
3,888 questions
{count} votes
-
RLWA32 49,536 Reputation points2024-02-14T14:47:30.2033333+00:00 As long as you have a pdb for your dll you should be able to debug it. Symbol files for Windows system dlls are not required for the visual studio debugger. In the visual studio 2022 options for debugging you can tell it to not attempt to load symbol files for all modules by default.
-
HY Jeong 0 Reputation points
2024-02-16T04:34:52.65+00:00 did you mean option-> debuggin-> symbol? i tried both options and both did not work
-
HY Jeong 0 Reputation points
2024-02-16T04:37:47.1033333+00:00 did you mean option-> debugging-> symbol? i tried both options and both did not work.
Sign in to comment
1 answer
Sort by: Most helpful
-
RLWA32 49,536 Reputation points
2024-02-16T09:38:38.7866667+00:00 -
HY Jeong 0 Reputation points
2024-02-19T07:19:15.4266667+00:00 I tried it but it did not work. I also tried "load all moduls, unless excluded" and it did not work.
-
RLWA32 49,536 Reputation points
2024-02-19T11:16:04.28+00:00 Exactly what do you mean when you say "prevents me from debugging." I have never seen the error you describe when using the visual studio debugger.
-
HY Jeong 0 Reputation points
2024-02-19T23:39:06.26+00:00 Sorry for my vague explanation. the error message is "wow64.pdb is not loaded". Due to this error I am not able to debug the project
-
RLWA32 49,536 Reputation points
2024-02-20T00:05:49.0266667+00:00 That's the same vague description that you previously gave. Does the debugger fail? If yes, in what way? Is there an error code? Does the debugger terminate? Is there some debugger function or facility that you cannot use while debugging? Please be specific. I cannot reproduce your issue. Have you tried using a different debugger such as Windbg?
-
HY Jeong 0 Reputation points
2024-02-20T00:41:27.7166667+00:00 When I used visual studio 2019, when i clicked the debug button then it process something( probably building project and files for debugging) then it automatically started Excel. When i select the specific excel file that i want to open and run the vba code that use dll file then i can run the code line by line as normal debugging. However, this time (using visual studio 2022) when i clicked the debug button, visual studio start checking the code and making files for debugging (such as pdb file) and suddenly stop and show the error message "wow64.pdb is not loaded".
-
RLWA32 49,536 Reputation points
2024-02-20T09:41:24.0533333+00:00 The posted image shows that an unhandled exception (code 0x4000001f) came from the EXCEL.EXE process. This exception code is STATUS_WX86_BREAKPOINT with the minimal explanation "An exception status code that is used by the Win32 x86 emulation subsystem."
Have you tried to ignore the message about the missing wow64.db symbol file and continue execution under the debugger? Also, have you tried running Excel normally, load the worksheet and then Attach the debugger to the Excel process before using the dll through VBA? -
HY Jeong 0 Reputation points
2024-02-21T01:20:30.7+00:00 I clicked the continue button but still the same error happened like the picture i added above. I tried to run the excel file first and clicked the debugging button but same thing happened.
-
RLWA32 49,536 Reputation points
2024-02-21T09:14:13.7266667+00:00 I tried to run the excel file first and clicked the debugging button but same thing happened.
I think you have misunderstood. Start Excel normally, not under the VS debugger, and load your worksheet. With VS open and your project loaded I expect you will see a menu and toolbar that looks like this -
Do NOT click the button (red outline) for the Local Windows Debugger.
Instead, click the main menu Debug item (yellow outline) and then select "Attach to process" in the submenu that opens. After clicking to attach a process a dialog box should open that looks like this -Find the Excel process and select it and then press the "Attach" button. The dialog will close and the VS debugger should attach itself to the already running Excel process. If this is successful try running the Excel VBA that uses your dll. Several years ago a similar problem was reported at https://developercommunity.visualstudio.com/t/Visual-C-cant-debug-a-specific-32-bit/1579204 Its possible that this bug has resurfaced. I suggest you use the VS2022 feedback mechanism (Help->Send Feedback->Report a Problem) to report this issue to Microsoft.
Sign in to comment -