Why I Want To Smash Vista!!!!!!!!

Ok iam trying to add a file to program files in my computer and guess what I DONT HAVE PERMISION when iam in the administrator account. is up with vista and all of its permisssions even though iam the freakin owner of the computer.

Thank you

MIke

 

Okay i found out a way to trick this ty os, i just made a folder in one of the program files and copy it to the main folder of the program. But i still cant understand this os why does it have permisions when iam the full owner?

 

Unlock Vista's supersecret Administrator account

 

i just use the TakeOwnership registry tweak for stupid permissions like that.

 

i have the same problem before.

 

McGrady's right - however I would add that it helps to use the Vista "Help" function, which is a lot better than XP ever was, to find out how to deal with small issues like this. That's all I did - and I've been a Tech for over 35 years. Sometimes you just need to step back and think - the obvious sometimes eludes even the best of us.

All you need to do:

1. On the file/folder in question, right click and select Properties.
2. Click on the Security tab.
3. Click on the "Learn About Access Control and Permissions". That will open up the tutorial and How To about changing permission settings.

If you've ever dealt with Unix/Linux file/folder permissions, it's the same thing, only in XP there wasn't any way to effectively change those settings. The ability to change Owner/Group/User permissions at the file/folder level gives you at lot more individual security control over your system, particularly if you're on a shared network that's setup for file sharing.

Don't want the wife, girlfriend (or wife's girlfriend) or the kiddies stumbling onto (or purposely searching for and finding) your P0rn Downloads stash? Lock 'em out of the folder.

 

Just gotta love it. What really bothered me is that, even as administrator, I couldn't access certain folders. But I've been given to understand that these are merely "links" or something like that, and I can access the actual folders. Whatever.

Point is, it's a hassle.

 

now guess what happens if you, the admin, click on some funky sexybritney.jpg.exe and it can manipulate your programs folder...

you're still the admin and you can change and edit everything, but not without UAC first. it's the last savety for the os to make sure you know what you do. it's allowing you into it's "body", messing up it's "organs". and all it asks is a simple "are you sure?". i want to see any human being that polite to you when you try to mess with his organs

 

It's a minor inconvenience but worth it. Many times I've been burned installing questionable programs under XP and crashing afterwards. Some programs will install in the background without you knowing it.

 

I would second that.. a little bugging is better than screwing the OS..i have forgotten how often i had to reinstall the XP while school days...

 

They do this because the vast majority of users have no need to be tinkering around in \Program Files. Users that do tinker in here tend to break stuff. It also helps prevent apps from sneaking stuff in there.

You're not supposed to be using "\Program Files" for regular file storage.

 

Especially since Vista virtualizes the program folders to create a place for users files. It does this for each individual user so that, for example, one persons game save files don't overwrite those saved by other users. And these virtual folders are shown to the application as if the files were really in the program files application folder itself. These magic folders are in the folder called "ProgramData".

Gary

 

I love that registry tweak!

 

Interesting... I didn't know that.

Also, another reason for protecting the Program Files folder is that a malicious program could circumvent UAC by writing to the Program Files folder. Instead of just requesting elevated privileges, causing a UAC prompt, a malicious program could overwrite one of your executables with its own .exe file and wait until the user runs that program. Then the user might think that it's their trusted program that requested elevated privileges.