We’re releasing an application to public, in which we don’t want to include full symbols. So we’re stripping them as mentioned in official docs (Debugging with symbols, PDBstripped). Both full and stripped symbols are correctly generated, we store full symbols in private location (share drive) and ship the product with stripped ones. So far all good.

Issue happens when we want to debug released app (i.e. crashdump) – we open the dump from Visual Studio and it automatically loads local symbols inclided with the application (the stripped version). Once we remove those (delete local pdbs), because local symbols weren’t found, it will start searching the network path and properly loads correct full symbols from there.

Attaching generic VS’s Options form, we’re having our path correctly specified below “Microsoft Symbol Servers” and works:

Is there any way to override the behavior and load full symbols with priority? I.e. give local symbols lower priority than the ones from network location? Or can we somehow force search loading on network location when we have just stripped symbols?