This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(38.4, 48%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDS%3C/text%3E%3C/svg%3E)
Windbg show this info dialog with below message when single stepping through MFC code:
The file 'https://devdiv.visualstudio.com/DevDiv/_apis/git/repositories/msvc/items?path=src/vctools/VC7libs/Ship/ATLMFC/Src/MFC/wincore.cpp&versionDescriptor[versionOptions]=0&versionDescriptor[versionType]=2&versionDescriptor[version]=0a7a0c7ef973187f59b10575b76ab07d8e7b3bbe&resolveLfs=true&$format=octetStream&api-version=5.0&download=false' cannot be opened
Have you told Windbg where the MFC source files are located? You can do this with File->Source File path and giving the paths in the dialog that opens as shown below -
You should also consider setting up Windbg so that it can load the symbol files for the MFC dlls. Refer to Using a Symbol Server
Im aware of the symbol and source file path settings in windbg. I just want to know about the info message. Thought MS now supports opening MFC source directly without me setting a local path and that its broken on my windbg and needs to be fixed.
Had also posted this on stackoverflow and got reply that MS must have left the internal paths in pdb by mistake.
I used the same version of Windbg as was shown in your posted error message. How does the debugger need to be configured to reproduce your error message?
you can also try with the same version of mfc in a sample:
0:006> lmvm mfc140
Browse full module list
start end module name
00007fff`df2c0000 00007fff`df822000 mfc140 (deferred)
Image path: C:\Windows\SYSTEM32\mfc140.dll
Image name: mfc140.dll
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 01879FBB (This is a reproducible build file hash, not a timestamp)
CheckSum: 0055AFE4
ImageSize: 00562000
File version: 14.32.31332.0
Product version: 14.32.31332.0
File flags: 0 (Mask 3F)
File OS: 4 Unknown Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Visual Studio®
InternalName: MFC140.DLL
OriginalFilename: MFC140.DLL
ProductVersion: 14.32.31332.0
FileVersion: 14.32.31332.0
FileDescription: MFCDLL Shared Library - Retail Version
LegalCopyright: © Microsoft Corporation. All rights reserved.
You can also use the same version of mfc in a sample:
0:006> lmvm mfc140
Browse full module list
start end module name
00007fff`df2c0000 00007fff`df822000 mfc140 (deferred)
Image path: C:\Windows\SYSTEM32\mfc140.dll
Image name: mfc140.dll
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 01879FBB (This is a reproducible build file hash, not a timestamp)
CheckSum: 0055AFE4
ImageSize: 00562000
File version: 14.32.31332.0
Product version: 14.32.31332.0
File flags: 0 (Mask 3F)
File OS: 4 Unknown Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Visual Studio®
InternalName: MFC140.DLL
OriginalFilename: MFC140.DLL
ProductVersion: 14.32.31332.0
FileVersion: 14.32.31332.0
FileDescription: MFCDLL Shared Library - Retail Version
LegalCopyright: © Microsoft Corporation. All rights reserved.
I'm using VS2022 17.4.4 and the version of MFC is not the same as yours -