

Step 1: Download the Platform-Tools Package The required platform works with the three most popular computer operating systems, too, which is good news for everyone. This paves the way for many new tweaks and customizations that weren't possible before. They can do everything from backing up your device to unlocking your bootloader with a few simple steps. There are still a few "minor"(?) files and directories on c: drive that I'm not really sure belong to Android Studio, but I'm too chicken/lazy to set up the symbolic links for them.ADB and Fastboot are probably the most essential tools for any Android aficionado. The bottom line is that apparently I'm not the only one with limited space on C: drive who had to struggle with the IDE install.Īfter 5 install/uninstall attempts, each time changing all "c:" text box prompts to "d:" and learning more and more about the various libraries and folders that STILL went to c: drive, I've finally found all the big ones, and set symbolic links for them, and moved their contents over to d: drive targets. Reading over the other stackoverflow questions by searching for "android install d drive" yield several hits, which talk around this higher-level concept, but are about more detailed issues, such as where to put the jdk and/or the sdk, missing gradle libraries, tinkering with environment variables and such, but the central theme in them appears (to me at least) to be about putting the IDE on the d: drive (fully or partially), and the consequent errors encountered while attempting that.(I will ignore the "separation of 'code' and 'data' design paradigm, which would rightfully require a third P: 'PROGRAM' drive, and I'll just focus on the lack-of-space problem.) The obvious intent was for all third-party (non-OS) programs to live on D: drive, or at least not on C: "OS" drive.

The D: drive is orders of magnitude larger. The C: drive has just enough room for Windows 10 plus some buffer for future "OS" upgrades.


I'm going to start with the high-level "common sense" question and then get into the tech details:
