I was running TFS MSSCCI Provider v11 to integrate with RoboHelp 10 on Windows 7. I would open an RH project by selecting the TFS version control option, which would eventually open the Choose Folder in Team Foundation Server dialog. Then I would drill down to the relevant project folder on the server side. When I selected a folder, the proper Local Path was populated (as defined in the workspace via VS Team Explorer (2013)).
Now in Windows 10, I have two major problems:
But in this case, no folders are mapped in Source Control.
The other problem is that in other cases when I map a folder with Source Control Explorer and open a project with RH, the Local Path either defaults to C:\ or C:\WINDOWS\system32 instead of what I defined in the workspace. Plus this path is uneditable. However, it also creates a new workspace with a _1 extension to my existing workspace, in which I can edit the path, but I don't want an extra workspace.
So how do I get the Visual Studio interface and RoboHelp back in synch?
I always avoid the open from version control option. I always set the paths in VS and do a get to my local disk. I then open the project from the local disk and RH recognises the project's source control status. I have used this way of working for different client and I never had issues like you describe.
To fix it in your case: Remove all local projects. Set up the workspace and do a get. Then open the project from the local disk.