It's not a matter of "Why", it's a matter of getting your work done with the least amount of hate and discontent.
So I take my own advise, "stop grumbling and jousting with windmills and find another way around the problem".
MS doesn't like us saving files to the root directory of C:, so why not save them somewhere else?
While setting up a new PC, or installing a new OS, I run a set of batch files, to install several of my programs into Windows.
The root of C: would be an ideal place, but since it's forbidden territory, I just modify my batch files to Create a new directory under C: and then load my files there. No harm, no foul and Job Done.
Live is too short to dual with the MS Gremlins. Just go around them. Eh?
OH....and if you've not installed "Grant Admin Full Control" yet, it's about time you did!
I call that "Take Ownership" on Steroids!
It lets you right click on any file or folder in the PC, except C:\, and then become the Owner of it.
That just makes Life With Windows so much easier.
So, 6 months later I'll pose the same question as the OP did once again, and if you don't have an answer as to HOW, please keep your opinions on how I should set up my computer to yourself
It's isn't about my way or the highway. It's about common sense and following good computer practices. That has always been a sign of a computer novice to try to or want to save files to the root of C. There's simple no reason for doing so, and it leaves the door open for many other issues. When you buy groceries, you don't try to store them in the engine compartment of your car, right? The only thing results that can come of this are negative. There are user folders, the Desktop, or a second data drive (in some computers) available for use.
When someone asks how to do something that is contrary to standard practice it is more than reasonable to point this out. That is providing responsible advice. In many cases the op simply wasn't aware of the situation and was grateful for the information.
Standard practice in Windows has always been to put files in folders, not the root of C. It is not a good idea to depart from standard practice unless you have a really good reason for doing so. If someone is able to provide such a reason I would consider explaining how. I haven't seen that happen in this thread.
I'm upgrading a stand-alone system in a physically controlled space (no Internet connection, no risk of Malware or Virus, etc.) from Windows XP to Windows 10. Part of the systems function is to generate a report. The report generator creates a PDF file, unfortunately, in the root folder. The report generator was created long ago (not by me, I never would have done that) and the source code is not available. The report generator works from an Admin account, but not from a User account. Policy does not allow me to grant Admin privileges to all the individuals who may need to generate a report.
So LMiller7, if you actually know how to configure Windows 10, so that a User account can create a file in the root folder, that would be awesome.