Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.62.0
• OS Version: Windows 10
• Extensions: Debugger (C# and C/C++ from Microsoft)

Steps to Reproduce:

1. Create a Workspace with a '#' in the path
2. Create a project (C# or C++) which contains an intentional error
3. Run the project, the "error" occurs (this is normal, we wanted it)
4. Open the 'Problems' menu, the file with the "error" can't be opened because the path is cut before the '#'

Example:

I create a project with C:\Code\C#\tools\main.cpp

#include <iostream>
int main()
{
	std::cout << "Hello world!" << std::endl;
	int foo = "bar";
	return 0;
}

Then I execute the project using VS Code (with tasks.json and launch.json) to get the "error" ("bar" can't be converted to int, legit)

• What happens:
  I got the "error", but the path is C:\Code\C and I can't open it because this file doesn't exist.
  
• What I expected:
  When I rename the folder C# to CS, the "error" opens C:\Code\CS\tools\main.cpp as expected.
  

I guess this also happens for '?' characters, but I can't test it on Windows.