Recently I found that my lowly 128GB SSD was filling up to the point where I had to uninstall old games to install new games. That wasn't bad until I had to install some other applications for actual doing work and now I just don't have enough space to even do that anymore
So I know the solution to what I want to do. It's the same thing I did when I was building disaster recovery into my system, just create a junction point and point it to a 1TB HDD in the computer. So just like creating a junction for c:\users and pointing it to the internal HDD I would just copy the Program Files (x86) folder over to the HDD, reboot into safe mode w/ command prompt, rename Program Files (x86), then create a junction with that folder name. I found something that I'm sure is a windows issue, and since i'm a Linux admin I figured I would take to the boards since I couldn't find a problem similar on google.
TLDR; I can't rename Program Files (x86) from within windows so I restarted into safe mode w/ command and was able to rename it, and I was able to create a junction point with the same name...
rename "Program Files (x86)" "Not_Program Files (x86)" mklink /J "Program Files (x86)" "D:\Program Files (x86)"
Now it gets weird. I boot back into windows and see Program Files (x86) directory is still there, and any directory with what it SHOULD be named now doesn't exist. But wait.... there's more! When I look at the file properties of Program Files (x86) the object is being referred to as what I renamed it to.
My question REALLY is why won't windows rename this directory and how can I accomplish what I'm expecting?
here is a link to the properties of the folder which shows that the "object name" is an expletive that I made kid friendly. ( no rep to include in post )