That you for update. I am sorry that I could not help better, but sometimes it is like that...

Hello,

it is unlikely that the older version install is causing this. But it is difficult to say, because I really do not know what the cause may be.

Have they tried to post it through relevant Microsoft venues?

Do they have any antivirus, and if so, have they tried to disable it, and what were the results?

Do they have more computers and if so, what is the behavior on them?

Best regards

Hello.

The path in the error message comes from our assemblies, and corresponds to a path used when the product was built.The compiler puts it there automatically, so that the debugger has easier just finding the corresponding symbol files (PDB) for the assemblies. It is meant as "hint" only.

The way it is supposed to work is, I think, that the debugger tries to find the PDB file at the hinted location, and if it is there, it loads it; otherwise, it should skip it.
I have no idea why the path should be of any use during building of the customer's product, though.

If the PDB file is not present, as is the case on all our customer's computers, the expected behavior is that this condition is silently "swallowed" by Visual Studio. of course the user won't get the ability to debug (with symbol) *into* our assemblies, but that's how it was meant to be.

The bottom line, I'am afraid I won't be able to help here. It looks like something that should rather be reported to Microsoft. I would be slightly suspicious if the customer had some kind of virus scanner or similar software that hooks to the file system, because that could then have bugs that cause other software to misbehave.

I do get similar messages (with other libraries) from time to time as well. Pressing Cancel then allows VS to proceed. You have not written what happens if they press Cancel?

There may also be a setting in VS to disable the symbol loading.

Regards