Tools > Options > Import and Export Settings > Import and Export Settings Path Error

Cody Beyer [MSFT] reported Jul 10, 2017 at 09:25 PM

Show comments 2

This issue is read only, because it has been in Closed–Fixed state for over 90 days. It was closed for 671 days.

Add comment

Joyce Liang🌵 [MSFT] Jul 14, 2017 at 08:59 PM

John Catenzaro - MSFT [MSFT] Jul 24, 2017 at 05:19 PM

Comments are read only

Remove the extra slash from the path, such that:

c:\users\%username%\appdata\local\microsoft\visualstudio\15.0_6d072ecf\\settings\CurrentSettings.vssettings

becomes

c:\users\%username%\appdata\local\microsoft\visualstudio\15.0_6d072ecf\settings\CurrentSettings.vssettings

Add comment

Comments are read only

This issue has been fixed and is now available in our latest update. You can download the update via the in-product notification or from here:　https://www.visualstudio.com/vs/ Thanks to everyone who provided feedback, votes and solutions for this problem.

Add comment

Comments are read only

Solutions are read only

Developer Community

Get help from our community supported forum

Tools > Options > Import and Export Settings > Import and Export Settings Path Error

Add comment

I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:

Solutions

Add comment

I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:

Add comment

I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:

Developer Community

Get help from our community supported forum

Tools > Options > Import and Export Settings > Import and Export Settings Path Error

Add comment

I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:

Solutions

Solution

Add comment

I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:

Solution

Add comment

I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:

Related Problems