I need to install Visual Studio 2022 for Unity. I specified the installation location in my D drive
but C drive's space runs low. Thus, I could not install it. I don't know what components get installed. I've looked for many methods, and mklink caught my eye but not confident about it. If there was any other way to, I would be glad to hear it.
No, unfortunately most of Visual Studio still gets installed on the main drive. Regarding to this forum thread 75% of VS gets installed on the main drive and just 25% on the chosen drive.
So you have no choice but to make space on your c drive.
Related
This is primarily a question focused on recent tooling I've been trying to get an installer to place components on a separate drive, but it's notably been an issue a few times in the past, and as I've not been the only person to
encounter this particular type of issue, I'm trying to keep this a bit open on the general case for this situation.
So, with that caveat in consideration, I noticed this recently while trying to repair a Visual Studio installation, and found that it was trying to install components to the "System drive", despite having an installation directory that explicitly isn't on the system drive, which is a little annoying given that I don't have a lot of space on that drive left before I run out of space.
While I am interested in a solution for Visual Studio in this case, I was wondering what the root cause of having configurable software requiring installation to bleed over into unrelated systems drives regardless of the preference of installation location - is this a result of system commands being expected to be on the same drive as the shared tool itself, and is there a way to develop software to reduce the footprint of this where possible relatively generally?
For Visual Studio(2017, 2019) the installation locations can be changed in Visual Studio Installer > VS > Modify > Installation locations, the first time you install Visual Studio, but after you finish installing VS, the locations cannot be changed. And generally, there are three locations can be changed, they are
1). Visual Studio IDE
2). Download cache
3). Shared components, tools, and SDKs
Though these locations can be changed, some files will still be installed in C Drive.
What I think:
This is by design, or can be considered as some necessary files need to be installed in C drive to let them be “closer” to the system(or system files). Perhaps for security reasons, for sharing libraries(dlls), for registering into Windows…
I think this is not a specific condition for VS, other applications may also have some files installed to C drive.
While I am interested in a solution for Visual Studio in this case.
I’m afraid there is no solution in this case, I mean, at least, from some VS settings/options, change those files’ locations or move them from C Drive to another drive is not possible, or will cause error.
I was wondering what the root cause of having configurable software requiring to bleed over into unrelated systems drives regardless of the preference of installation location.
Perhaps, the “unrelated” is not unrelated. The better way to confirm this, I think you can ask Visual Studio Product Team, they are active on Microsoft Developer Community.
I just downloaded Visual Studio 2017 community and tried to install it but when I did I made directory D: separate from main directory C:
Everything I had in installation had message not enough space even tho i have around 300GB free space in D: and around 50GB in C:
Installationg has around 50GB and it is showing me the C: drive memory with that message that I don't have enough space even tho it is changed to be installed into drive D:
Here is an screen shot of installation:
When we choose another drive to install VS, it still requires the space on the system drive, please have a look at this: Why Visual Studio 11 Requires Space on the System Drive, because the shared components, packages and Windows Installer and package caches still need to install on the system drive.
From the screenshot, it looks like you choose all workloads or most of them, it is huge and usually we can select the needed workloads per your development requirement, you can refer to Visual Studio Community 2017 workload and component IDs to know the detail description of those workloads, then uncheck some workloads to make it small.
After the initial installation, we still can modify it to install more workloads through run this installer and click the icon beside ‘Launch button, choose ‘Modify’ to select more workloads or individual components to install.
I have a pc with a C:/ drive that can only handle 100GB. For school I needed to download Xamarin for Visual Studio 2015 for a hackaton (so I only needed it 1 day). It took a while to get 20GB of free space in my C:/ drive (because of course, it wouldn't just download on my D:/ or an external drive), after the installation, less than 1 GB remained. But I still needed to do an update for Xamarin... after deinstalling some Adobe programs, I still didn't get enough memory for that update, so I gave up and ended up pair programming.
Now, after the hackaton, I wanted to remove Xamarin as quickly as possible. I looked up what I had to remove and I did, now only 6,3GB free space remains. Meaning that more than 15GB is still taken by something.
I looked up several sites, I even tried to find hidden files in my regedit, but I didn't succeed in getting my space back. It seems that no one really wants to get rid of Xamarin alone.
The problem is that I still need Visual Studio 15 for ASP.NET for school, so I would rather not deinstall my visual Studio completely as it takes a while to completely install it again.
Has anyone an idea what files I can remove that is installed together with Xamarin, or what I can try to get my C:/ drive to breathe again?
I recently had to replace my hard disk on my laptop, which contained my Visual Studio installation. When the new hard disk was added, unfortunately the person involved in setup has put Windows 8.1 on an internal SSD (I am using Dell XPS) and made this the system drive -- since this is ~30GB only, re-installing Visual Studio is not an option it seems, as my understanding is that even if the install path is changed to the new hard drive, VS will still need significant space on the system drive (I have ~6GB left).
My old hard drive is being used as an external drive, and it seems all the data is fine, and can see that the VC compilers work fine via the command line. My question is, if there is a method by which I can get the Visual Studio installation up and running on my old hard drive(external), as all the components needed are present -- is there a config file or some such that I could use, and manually enter the registry information to make it work? Is there anything else I could do?
I've download VS 11 Developer preview. I do not have sufficient disk space in my C drive, so I entered "E:\Program Files\Visual Studio 11\" as the install location and the installer continues, but after a while, my C: drive goes out of disk space and I get the following error in the log file:
(vs_professionalcore) failed: Error: 1601 ErrorMessage: Out of disk
space -- Volume: 'C:'; required space: 606,561 KB; available space:
178,516 KB. Free some disk space and retry.
Note that no files gets copied to my E: drive during the installation process. What's the solution?
This isn't unique to VS 2011. All versions of Visual Studio (at least all the .NET flavors I have used since 2002) have strong dependencies that can only installed onto the C: drive.
These dependencies can be stuff like the .NET 4.5 and various runtime components. The IDE itself is all that can be placed on another drive.
You usually see this in the installer where it will show that after changing the drive letter still large parts of the C: drive will be used.
I decided to fire up a VM and see what the difference was between C drive install and E drive install on VS 2010 Ultimate. As you can see the difference was only ~2GB with the bulk being on the C drive still as I stated above.
Visual Studio 2010 Ultimate C Drive Full Install
Visual Studio 2010 Ultimate E Drive Full Install
Unfortunately I don't believe there is a solution here. This sounds like a simple bug in the installer. The only real option is to file a bug on Visual Studio Connect to ensure it's fixed for RTM
http://connect.microsoft.com/visualstudio
Note: This is a preview release so quality is not that of RTM. It's certainly a case I would expect to be fixed for RTM though. When I worked in Visual Studio QA in particular often installed to non-default locations.