title: How to resolve Visual Studio TFS Mapping Error (The working (phantom) folder is already in use by workspace...)
body: <p>I am at wits end on this one and I believe I've searched every resource available including SO but nothing is working.</p>
  
  <p>I presumably had some folder which was previously mapped at some point in time to a location which no longer exists; but Visual Studio and/or TFS is holding this phantom reference somewhere that I cannot find. So the error dialog looks like this:</p>
  
  <p><a href="https://i.stack.imgur.com/E7j0y.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/E7j0y.jpg" alt="enter image description here"></a></p>
  
  <p>So in short, the issue isn't that I cannot remove (delete) the workspace but rather that when I attempt to add the workspace when there clearly isn't one and subsequently map to this particular folder; I am presented with a dialog nagging about a workspace that I can't validate to even exist.</p>
  
  <p>The things I've already tried are:</p>
  
  <p>Delete the workspace from the TFS Server (using the tf utility)</p>
  
  <ul>
  <li><p>tf workspace /delete [WORKSPACE]
  Delete the workspace from my local workstation </p></li>
  <li><p>tf workspace /delete /server [SERVER/Collection] /[WORKSPACE]</p></li>
  <li>Other variations of the delete workspace command as well</li>
  </ul>
  
  <p>Removed the workspace from within the VS2015 UI </p>
  
  <ul>
  <li>File -> Source Control -> Advanced -> Workspaces</li>
  <li>Workspace (drop down) -> Workspaces -> Remove</li>
  </ul>
  
  <p>Delete cached TFS data</p>
  
  <ul>
  <li>"%localappdata%\Microsoft\Team Foundation\6.0\Cache\"</li>
  </ul>
  
  <p>Removed and re-installed Visual Studio 2015 from ground up</p>
  
  <p>There have also been a plethora of other suggestions I've tried but those were the most popular mentioned; and I still get this annoying dialog.</p>
  
  <p>If I knew where the information was being stored I believe I'd be at the door of resolution but I cannot find any resources that I haven't already covered to determine where its getting this information.</p>
  
  <p>I could venture into the registry but I dare not without having at least a clue as to where I need to look.</p>
  
  <p>So are there any other locations where this information could potentially be getting pulled?</p>