Took me a while to figure out how to get the full installer to install to my faster and larger D drive, but I finally did.
Then I discovered it was still accessing C: un… (read more)
Took me a while to figure out how to get the full installer to install to my faster and larger D drive, but I finally did.
Then I discovered it was still accessing C: under:
D:\Users\[Username]\AppData\Local
D:\Users\[Username]\AppData\Roaming
So I now have my Mozilla folders in both locations pointed to D: with a symbolic link or whatever.
But it STILL seems to be accessing C: to do SOMETHING, and I'm not sure what or where, as searching C: for Firefox or Mozilla turns up nothing.
It still thrashes my C: drive though, especially noticeable if I'm using it for something else at close to 100% and Firefox for example loads a Youtube page that was unused/not in focus for a while.
Somehow it's STILL causing as much activity on C as D and I'm not sure why...if I was maybe I could point more directories to D with more Symbolic links (or whatever they're called...I may be misremembering since I set this up a few weeks ago, but they seem to work fine).
(I gave up on Chrome...I can point a bunch of stuff at D, but sooner or later it breaks its ability to do updates until I move stuff to C...I'm guessing maybe the updater "fixes" something in the background that breaks it. Thankfully Firefox seems to update just fine (I do NOT use the background process, I just check every day), and I got 122 today seemingly fine. No idea why browsers are so weird about getting installed on an alternative drive compared to other programs...it's a pretty common thing to want!)