Delete folder under C:\Program Files

  • Thread starter Thread starter Scott
  • Start date Start date
S

Scott

As an administrator right, how can I delete the folders under C:\ Program
Files? The folders left there was due to the weakness of program
uninstallation.

Thanks,

Scott
 
Well, there are multiple things you may need to try. One is to take
ownership of the folder and all subfolders. This should allow you to delete
the files, but I've noticed that sometimes it doesn't. This does require
administrative privileges because this is a protected system folder.

Robert Firth
http://www.winvistainfo.org
 
Hi,

Click start, type CMD. Right click the entry in the menu and use 'run as
administrator'. From the prompt, run:

CD C:\Program Files
DEL /y <unwanted_program_folder_name>

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
Scott

Try turning off UAC (User Access Control). You will need to log on
as Administrator. Start, Settings, Control Panel, User Accounts,
Turn User Account Control Off. Then try deleting.

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
They shouldn't do that, Gerry. It's simply a matter of having the proper
permissions. There is no need to disable UAC for any task.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
Yes Rick <G>!

How do you convert several hundred excel files created in Windows XP
in a partition shared with Vista from a Read only status? UAC is
causing the problem? Turn it off no problem. That may not be the
answer but other options are very tiresome!

--


Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
It's still a permissions issue, and it's as simple as either taking
ownership or adding your user account to the full rights level. Disabling
UAC is a) dangerous for the average user and b) can cause other software to
fall over and function incorrectly.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
They shouldn't do that, Gerry. It's simply a matter of having the proper
permissions. There is no need to disable UAC for any task.

Oh,I agree totally that's what is SUPPOSE to happen. The reality is
something else often does making UAC garbage.

I've asked before, never got a answer from anybody. How do you change
permissions on a file when the option to do so is missing or grayed
out even when you attempt to take over the owner using the edit
permissions tab under "advanced"?

The response; DEAD SILENCE. You see lots of things that aren't suppose
to happen, happen every day, just that some don't like to talk about
those kind of things happening. Any day now somebody will pipe up and
say its early, wait to the first service pack or anyone of a dozen
other excuses the Microsoft faithful haved used for over 21 years to
try to explain why Windows remains broken in some areas. Think about
it, over 7,600 days "in development" and Windows still has bugs.
Amazing. But the faithful have an answer for that too, all software
has bugs. That is partially true, but most companies fix bugs when new
versions are released. Not Microsoft. Not all of them. There hasn't
been a "clean" version of Windows yet. Worse, Microsoft knowingly
released Vista in spite of it having 500 bugs it knew about. Think
about that.
 
Rick

The more I find out about UAC the more I think it is not a clever
feature. Combining the two aspects, security and compatibility is
bound to lead to problems.

However, you did not answer my question!

--


Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Gerry said:
Rick

The more I find out about UAC the more I think it is not a clever
feature. Combining the two aspects, security and compatibility is bound
to lead to problems.

Yes, correct. MS has neglected security in favor of compatibility for
decades and (thankfully!) that era is now over.

You do, in fact, need to take ownership of the files you want before you
can use them freely in Vista. This is not difficult. Just right-click
on the files, and then Properties>Security. Edit the privileges on
those files as needed so you can change the owner to whomever you want.

This is a small price to pay for the increased security you gain.
 
In message <[email protected]> "Gerry Cornell"
The more I find out about UAC the more I think it is not a clever
feature. Combining the two aspects, security and compatibility is
bound to lead to problems.

Sure, the other option is to choose between security (run as a limited
user at all times) or compatibility (run as a full administrator)

UAC is a middle-road compromise, and does far behind the scenes then
prompt you when elevating.
 
Yes, correct. MS has neglected security in favor of compatibility for
decades and (thankfully!) that era is now over.

You do, in fact, need to take ownership of the files you want before you
can use them freely in Vista. This is not difficult. Just right-click
on the files, and then Properties>Security. Edit the privileges on
those files as needed so you can change the owner to whomever you want.

This is a small price to pay for the increased security you gain.

What security are you gaining? By clicking ok, you in effect REMOVE
the security and Vista responds exactly like XP would and lets you do
anything because you just agreed to elevate whatever process was
running as a standard user to now have full administrative rights. For
all practical purposes all UAC adds is a nag screen and a warning that
you're about to do something riskly, regardless if it is or not. Again
I refer to the movie, LISTEN to what the team that wrote UAC actually
admits in the interview. Only if you stop what you planned to do are
you "protected".

I grow weary of trying to reason with unruly children that are too
foolish to listen and too dumb to understand.

If you watch the movie of the two UAC authors you understand alright.
Well I did. Microsoft in effect is saying, look, we know all prior
versions of Windows have been a horrible security risk. So here's the
deal, we'll put up a barrier, its just a nag screen that halts
execution until you decide what to do, but hey, it warns you. If you
click to proceed you do so at your own risk. We started to "fix" the
thousands and thousands of legacy applications that break under UAC,
but geez, we had no idea what a job that would be. So we stopped. Oh
we fixed, I think oh about a thousand. These are hard wired within
Vista to sneak past UAC, just so you don't see any nag screens. The
rest? Oh, you'll have to deal with those on your own. If enough people
squeal, maybe will patch those someday. Have fun, your Vista team.

As far as editing privileges file by file, you nuts man? Maybe for
those with a handful of files, not that big a deal. You want to come
over and fix my million plus files? No? I didn't think so. Now I'm not
saying by any stretch my million plus files need a permission change.
The point is I have no idea which ones need changing until I try to
access them. Some I won't need for months, maybe a year or more down
the road. Worse, as I've said over and over and now confimed by
Microsoft there are issues and sometimes you can't change permissions
on some files. Oh... what do I do with those?
 
Back
Top