Windows 10: Can't save to c: root

The OP asked a question. He/she had a reason to do so because he/she wanted to be able to do this. This response is a totally subjective one, imposing a subjective view on what the OP should or should not be doing. The question was "how do I do this?" NOT "Should I do this?" If you can't attempt to answer the question why bother posting? Or at least preface your opinion with IMHO or suchlike.

 

First of all, this thread is six month old. Now, suppose a kid tells you he wants to jump out of the window, but can't open it. Would you explain to him how to open the window or would you rather ask why would he want to jump and explain that maybe that's not such a good idea?

 

*Thumbs*Thumbs*Thumbs

 

I came to this forum with the same question. First of all I'm an adult and an experienced computer user back to the days of CP/M, so I think I'm smart enough to be able to manage files in my root drive. What I don't need is someone telling me how I should set up my system, or where I should save my files. A computer that I have to shadow box with to do things its way instead of how I want to do them does not help me. And the "our way or the highway" attitude belongs over at Apple and MacOS, not here.

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.

 

Great! As a CS graduate that's been programming since the TRS-80 came out, I fully understand the reasons behind the Windows security and their reason for protecting the root folder. However, many people have to upgrade systems (business requirements, no exceptions allowed) yet continue to run older software.

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.
Thanks

 

I think the ultimate solution for this, for all systems running 10, especially laptops with only one HDD, is simply create a small partition, maybe 10-20Gb and then set up a share for Networking. Then, you can just dump whatever you need there, and use any hand device's LAN browsing app (FileExplorer/ES Explorer) to move it elsewhere.

It's why I always get high capacity hand devices, most Androids allow a 32gb SDcard to be added. You'll note that those devices also strictly forbid you from dumping files into the root folders, even if you are rooted. But there is a nice "downloads" folder that shows up and you can put them there, then you can move them out using the same method and/or using the USB mounting option from said device.

:/ :\

 

First, to all of you people who feel the need to tell others how to manage their computers, would you also tell them that they shouldn't make a change to their house that you don't think they should make? Answer the question. If you can't or won't, quit wasting people's time.

THE SOLUTION TO SAVING A FILE TO THE C: DRIVE:

I have full admin rights on a Windows 10 Home laptop. For a work-around to program, I needed to save a text file to the C: drive. Do get around the permissions issue I simply created the file in a folder within the C: drive, then in Windows Explorer, simply copied the file from that folder to the C: drive. A message popped up saying I needed to provide administrator permission to move the file. I clicked on the Continue button with the shield on it and it moved the file. DONE.

So to all of you people that clogged up this thread spouting your holier-than-thou "This is how you need to manage your computer" advice, *Roflmao2

 

Of course. If they come here asking how to rewire their electricity circuit breakers we will tell them not to and seek professional help. The same applies here. I'm not going to tell a user to mangle the security, or permissions just so they can continue their bad habits.

As such the original poster that asked, was trying to create documents, pictures in places they shouldn't. We have a user directory for a reason, it is our place to do whatever.

Look the number one flaw of Windows though out the years of Windows always cited was, it is insecure. You know why? Because of us the users. We would run Windows with god level power all the doors unlocked, we gave every application the keys to the kingdom they could do anything, everything. Even the Internet connected applications, our browsers had full access, so did their exploits and the malware, viruses, etc. We didn't care we wanted to run as Administrator we wanted to have access to everything just because. However, this model is no longer viable in an internet connected world.

 

I am going to break the mould here.

If I want to write and then place a batch file in the root directory, I open an admin command prompt, and enter notepad. An admin elevated notepad opens, and I type my batch file, and save to c:\mybat.bat with no problem.

If I want to put an image file there, instead of notepad, I use MSPaint.exe, again opened with elevated privileges.

If I use Word to put a copy of my will in a nice safe place, where one of my nosy heirs will find it in the future, I'll open Word with an elevated command, and Bobs your beneficiary. *Smile

 

Hi, I have set all my permissions to full control/administrator and it is still not allowing me to save to Programs or Programsx86. This is a massive nuisance when I'm downloading (surprise!) program files and end up with the installers all over my desktop instead of in Programs where they belong. It's a brand new Acer AspireS13 with Win7/Win10 upgrade.

 

Welcome to TenForums @Guin,

Downloaded installers don't belong in Program Files!

The install package should be downloaded somewhere else, Downloads is the usual default location, but the Desktop will do. Wherever you have downloaded the installer, when it is run it will have the required privileges to unpack and created the required folders and files within the Program Files folder.

Once properly installed you could delete the installer, its job has been done. Or better, move it and keep it somewhere safe in case you ever need to reinstall it.

 

gpedit.msc > Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

find and disable: User Account Control: Run all administrators in Admin Approval Mode

 

Thank you, thank you, thank you capella for a simple solution that quickly solved my problem! I fully agree with your comment that wasting time preaching to the choir is pointless! I needed an XML file in the root directly because the poorly written application that I am forced to support requires that I have this XML file there. Not doing this would require a rewrite which currently is not possible. Easy for the holier-than-thous to criticize but sometimes you have to do what you have to do! Thanks for helping me get "DONE" in minutes and move on to more important things!!!