3

A couple of months back, most probably in November last year, I had to install Microsoft Visual Studio on a drive(D) other than C because my C drive did not have enough space to host the software. Two weeks ago I cleaned up my C drive and now I want to move the Visual Studio installation to the C drive because the C drive is located on an SSD drive, and the other drives are on HDD.

vs-ent-2022-installation-location

The Microsoft Official Document reference says that I have to reinstall my Visual Studio. But always there are some exceptional experiences for the users other than the official documentation statements.

ms-doc-ref

One very important cause for my avoiding this reinstallation is, that I live in such a corner of the globe where 30GB will take me like 3 to 4 days to download. Moreover, it will also hamper regular tasks and the custom settings and tweaks I have applied to my development environment.

That's why I am writing this to avail community help if anyone has ever experienced such an issue and solved it anyhow.

Yasir Arafat
  • 131

2 Answers2

1

While I don't have a solution to avoid reinstalling, I used to have a similar situation, and the one thing I recommend you do for a better experience is to create an offline installer, aka local layout, and use that as needed. It has been so long since I had to do this but you might be able to download in small parts if I remember correctly; running the same command continues from where it last stopped.

HUSMEN
  • 111
0

Something that may be pertinent: after experiencing repeated crashes I started running Windows from SSD instead of HDD. My previous Windows installation remained on the HDD, and I was able to run the VS 2022 copy I'd installed there by running devenv.exe in /IDE folder. The implication is that if you have your paths straight you can indeed run VS 2022 in full from any device-- you just need to make sure you transfer every necessary part. Try copying your Windows folder, Program Data folders, and make a Program Files folder on the SSD and see if that helps. (if you don't want to copy entire Windows folder, try running devenv.exe, note the files it complains about, and copying just those files to folder named Windows and faking the folder hierarchy as needed so VS knows where to find those files.) You may also have to do this for .Net runtimes also.

Anthony Caudill
  • 1
  • 1