Ah you can't have to much security It's Windows 7 rc way or the Highway
I had this issue with vista ultimate too I re-install windows and all my persinal Documents if you will all the stuff I maged in previous profile on another build and install all those files video pictures music keep getting locked down by the security controls in Windows See My personal stuff is on a 2nd hard drive nothing ever moves. Granted I know why this is Happening New profiles created when I re-install windows don't have the right permissions so the files can only be looked at. I can't edit or save things to documents once I link it over to the exsisting folder and files. I take ownership through the security tabs on thiose files . but windows 7 rc is ignoring the peocess I have to set and exsisting permission certificate systemName\Profile exsample to re gain access to my files some times I've been having to do this on every folder so I can save stuff where I want it and not have windows pester me about this you don't have permission to acces or save files in this folder (see your adminstator for Help. Well to simply put it. I'm the Admistator of this computer I want access to my files I should only have to take ownership once and not on every file in documents Posted By Mikro
May 24th, 2009 11:13am

Mikro,Since windows Vista microsoft changed the user profile structure.You might read the following KB to get some more insight why you have no access to those folders.http://support.microsoft.com/kb/930128/en-usDoes this resolve your question.Kind RegardsDFTIM me
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2009 5:35pm

Mikro, when you took ownership of the parent folder, did you remember to check the box that says "replace owner on subcontainers and objects"? ;)The default (box-not-checked) setting in that dialog only replaces the owner on the folder that you're dealing with; it does not change the permissions on anything within it.HTH,Chris[If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
June 21st, 2009 12:37am

I got itPosted By Mikro
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2009 5:08am

No offense, but could you at least try punctuation? It would be a lot easier to determine what you've tried and what might be a solution, or if there is even a problem at all, if one could tell what is meant to be part ofeachsentence. I can't tell whether you have a problem or you just don't like the way Vista and Windows 7 handle permissions....Stephen
June 22nd, 2009 8:58pm

I stopped reading after the first sentence, i get enough of that headache teaching my sixth graders.. As for me, I have the a similar problem with a folder in my x64 program files folder. I cannot copy an executable file into a folder in my program files (x86). I have taken ownership of the folder and all of the subfolders files using my the methods stated above and the "take ownership with right click tool" to no effect. It still is telling me that I need permission to copy the file, and to make changes to the folder. this is very frustrating because this was one of the main reasons I really hated Vista. It's my computer, and I am the one and only administrator. I am running Windows 7 x64 RC Q9550 4 gigs DDR2
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2009 8:25am

I suspect that Microsoft will not listen until some kind of protest is organized. The problem is not security, it is that it is applied witlhout ADIMISTRATIVE PERMISSION--as if the operating system is the owner. They can ship all the security gizmos they like, as long as I have the simple choice of denying the operating system from using it. I do not need it, I do not want it. In the long run, the quest for security has actually caused more damage that that which it is trying to protect.
July 22nd, 2009 2:23am

johnclark, no answer can be given to your question/comment unless you specify exactly which directory(s) you're referring to.Some directories actually are owned by the OS's system accounts. Examples: %systemroot%\Windows, %Program Files%, and %Program Files (x86)% (for 64-bit systems) are owned by TrustedInstaller. And, IMHO, this is A Good Idea - no local admin needs ownership of those directories - it's a rather large security risk (refer to XP, and how easy it is to bork the OS in various ways (infections.))Refer also to the *nix world, where users have only Read/Traverse/List/Execute rights to system directories, and are denied Write access there. Same thing, for the same reasons.HTH,Chris[If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
July 22nd, 2009 5:32am

Mikro, Occasional punctuation would go a long way to making your posts more readable. Maybe an linefeed here and there.nativeson, I've been involved in projects where the language was set at the 6th grade reading level. Of course, we had to use standard punctuation and spacing :-)
July 22nd, 2009 3:30pm

When one starts thinking anthropomorphically, as if our things own us, we need to talk to someone. And if you are talking security of one's own files, and this was an open directory of my personal files in question, one has to look at the big picture. The greatest destroyer of information to date has been Microsoft-through evolution--not maintaining compatability with files written on Windows from the start. This has generated countless lifetimes of human effort trying to salvage that that information.
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2009 1:52pm

Johnclark,you are WAY off base here, the locking down of the OS is NEEDED for 90 % of the end clueless users out there, there is no good reason for your comments, no one is forcing you to use windows or is Bill Gates standing over you with a gun?? If so give the word and I will send out the swat team.What does this mean???not maintaining compatability with files written on Windows from the startAnd unless you enabled the administrator and logged in as administrator, you are not the administrator.You should really learn a little bit about windows, life will get better. you do not impress with your ...having my own network, with two multiboot systems, I think I know how to uninstall a system.... my 8 year nephew can install win7 in a dual boot (and yes he has all by hisself), he can map drives, share folders, install printers...blah..blah.. no big deal in a windows world.Just so you understand..you do not own windows you have a license to use it, so if do not like it move on, we will not miss you.Here is wannbe windows http://www.ubuntu.com/
July 26th, 2009 4:54pm

Obvously you are not very attentive. These are my files it is locking down. Directories it has no biz in. And by the way, I was a beta tester a long time ago. I beta tested, and failed dos 6-but MS was too much in a hurry, and did not wait for the beta testing to finish, and a lot of people lost a lot of data--including me. I beta tested Ms first Multimedia pack. I do know a little bit about what I do. No operating system has any biz messing with long standing directories THAT ARE NOT PART OF THE OPERATING SYSTEM. And so I am failing this release. j.c.
Free Windows Admin Tool Kit Click here and download it now
July 27th, 2009 5:00am

I'm so sorry I'm late to this discussion, having just been told (by my shiny new Windows 7 PC) that even though I've logged in under my Admin rights, I do not have PERMISSION to use/alter certain files. So, as with all things Microsoft... it's Google time and multiple hours to find the 'work around'/'fix'/'idioticrhetoric'. So, on to the idiotic rhetoric: 1st, @ Johnclark... basically I totally agree. 2nd, @ Chris Cupler "no local adminneedsownership of those directories"... if not local, then network? What if you are THE network, meaning this is your only system or you are trying to maintain your own home system? Keep'em lock'd out of files that they own? This makes absolutely no sense. The only thing that saves you, IMHO, it that you have the ability to self reflect and actually use 'IMHO'... humility goes a long way. 3rd, @ Bubbapcguy... ?!?! "locking down of the OS is NEEDED for 90 % of the end clueless users out there"?!?! ... This has to be one of the A-typical answers from one of those A-typical, self-indulged,wannabe computer experts out there. Please throw your very single-minded opinions into the vat of useless perspectives that are provided by A-typical people like you. Basically I love to laugh at comments from individuals like you, and simply vent and ignore them. Finally, yea... there is a work around. Found it. Oddly enough it didn't take too much time, but I can still state the following: "Epic Fail MicroStuff"
November 19th, 2009 10:53am

<I'm so sorry I'm late to this discussion, having just been told (by my shiny new Windows 7 PC) that even though I've logged in under my Admin rights, I do not have PERMISSION to use/alter certain files. >Examples? Full paths? Need context.-Chris[If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2009 7:58pm

<I'm so sorry I'm late to this discussion, having just been told (by my shiny new Windows 7 PC) that even though I've logged in under my Admin rights, I do not have PERMISSION to use/alter certain files. >Examples? Full paths? Need context.-Chris [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.] sigh... this explains allot ... No you don't need Examples, nor do you need Full paths, or Context (from me)... you simply need to read the full post... "Finally, yea... there is a work around. Found it. Oddly enough it didn't take too much time, " This would imply that, YES, I've fixed my little problem. The rest of the 'idiotic rhetoric' is simply a rant to expound upon the audacity of the posts to a simple problem. Sorry, no 5th badge here.
November 20th, 2009 5:40am

DapperMan, I don't care about the badges - really, I don't give a hoot one way or the other.However, sharing the specifics of your issue, as well as the workaround that you found, goes a long way to help others in the future.That is the primary purpose of an open support forum, as opposed to one-on-one chat, email, IM, etc - it's there for everyone, and can often answer a question before it's asked.In other words, it might keep someone else from posting "how do I fix this / why is this like this?" (and, someone from posting "this is how/why") for the 267th time. ;)Regards,Chris[If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
November 20th, 2009 6:17am

OH! So your confused as to how this is fixed as well? Well judge'n by the response from Bubbapcguy, I would argue that this forum (and many many others) are for belittling users and expressing opinions. I'm probably wrong here, but the proof is in the trail of endless jibber-jabber and convoluted 'work-around' solutions that the so called 'experts' retort. I'll put that aside for a second though, but really, all you needed to say is 'hey, I can't figure this out, how did you do it, maybe it'll fix my problem'. I'm not saying that this is the end-all beat-all solution, but your posts above suggest that you already had a solution to what seems like a simple fix, you just required more input. So check out: http://social.technet.microsoft.com/Forums/en-IE/w7itprosecurity/thread/16b604f7-75fe-41e0-81cd-303b43ed32a5 Which represents my only other post after wade'n through 'give me more info' reply's and 'try this solution - wipe your OS and reinstall' answers that litter the net, when people try to understand WHY they have no true ADMIN rights after installing Win7. Basically I only use Window's machines for unimportant non-critical work. When I attempted to update a Window's only software package and was told that I could not change the directory on the C:Users/Public folder (due to lack of permission when logged in as Admin)... after just populating the file with software data files required to enable the program... I became curious/angered and simply not surprised that MS would would once again try to think for us ['BING.. it's not a search engine... it's a decision engine "because we all know that you don't know/understand what you're looking for"]. Enjoy P.S. I'm just as crass to the other MVP's and "Pro's" there as well. Also, it appears there are already well over 267 posts on this topic and there will be more (there's always more); it took me a little trial and error to weed through the complete BS and find what worked, but then again... it worked for me and may not for others.
November 20th, 2009 9:38am

<I'll put that aside for a second though, but really, all you needed to say is 'hey, I can't figure this out, how did you do it, maybe it'll fix my problem'.>Mine's not broke. :PAnd, yes - a little more info tends to be helpful. Helps with making sure one posts the correct solution (we do want to make it better, not worse), helps with tailoring a response to an individual (in other words, more specifics, fewer generalities.)Regards,Chris[If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
November 20th, 2009 4:19pm

<I'll put that aside for a second though, but really, all you needed to say is 'hey, I can't figure this out, how did you do it, maybe it'll fix my problem'.>Mine's not broke. :PAnd, yes - a little more info tends to be helpful. Helps with making sure one posts the correct solution (we do want to make it better, not worse), helps with tailoring a response to an individual (in other words, more specifics, fewer generalities.)Regards,Chris [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.] "Mine's not broke. :P"... are you serious, or just playing around? 'Broke' would imply that this is a fundamental software bug and therefore your posts will have to be negated. So I'm going to assume that you're just playing around, but that imply's that you're not taking the problems of others seriously. I guess we have aconundrumhere. And, no, you don't need 'a little more info' as long as you just read the very 1st post and pull out the problem. Here, let me break it down... "Post title" - Apparently it's a problem with Window's 7 security... hmmmm "Main body" - part vent, part narrative... something about being lock'd out ofpersonalfiles... hmmm "Conclusion" - "Well to simply put it. I'm the Admistator of this computer I want access to my files I should only have to take ownership once and not on every file in documents" ... ah! Admin rights with no access... hmmm ... ah yes that stupid 'default' UAC setting. * insert ANSWER (maybe it's right, maybe it's wrong, maybe the poster will learn something which leads to THEIR right answer) Finally, "(we do want to make it better, not worse)"... seriously, this is a Microsoft OS... I'll give them this, Window's can be mounted on virtually any piece of silicone trash out there. It's veryversatile, and widely used, but because of this, IMHO, it's also riddled with complexity and problems that come to light once a month when critical patches are pushed out. Don't make it sound like you're saving a post by seeking data; read the problem and answer the question. Empower the user to learn and enrich their experience through their own investigation.
November 21st, 2009 1:15am

I was being serious. Let me rephrase, then: I am not having the issue which you describe. I am not having it on my desktop (Pro x86), laptop (Pro x86), or Media Center server box (Ultimate x64.)I have not ever, on any of these machines, had that issue which you (loosely) describe. I did not have that issue in the Beta or RC, either.The closest that I've come to (maybe) having the issue which you (loosely) describe was on my old desktop, and it occured when it was necessary to reinstall the OS. On that machine (user data was on a secondary partition), it was necessary to take ownership of my 'stuff' (new install = new user token.) Explainable (and, easily fixable) "problem."I do take the problems that people post here seriously. If I didn't, then, frankly, there would be no reason for me to have an account here. I'm here to help others, not to troll. If you read back to the very first post in the thread, as well as my response to Mikro, you'll see that the OP's question was resolved with my first (actually, only) reply to him.His post was complete, in terms of information provided(albeit lacking in things like punctuation and formatting, making it a PITA to read.) But, the info needed to resolve the issue was there. Little things, like where the issue was (in his case, things in his user folder), as well as what he had already done or tried in an attempt to fix the problem.Re-reading your earlier post.... did you actuallyinstall a program to C:\Users\Public? It reads like you did - and, therein lies the problem. TrustedInstaller (the Windows system account that actually runs program installs) has no rights on C:\Users\Public. While you might have been able to install the app (because it would have been done under your (possibly your Elevated) credentials), you wouldn't have been able to use that app's update utility (because that would call TrustedInstaller, who wouldn't be able to write to that directory.)If I'm mistaken, please clarify. :)DapperMan, I've read and re-read your posts in this thread multiple times; and, I keep coming back to the same problem:If you don't say just where your issue is, no specific answer can be given to your post. Only general answers can be given:%windir%, %ProgramFiles%, %ProgramFiles (x86)% are owned by TrustedInstaller; Users (even Administrators) have only read/traverse/execute rights.C:\Users\Public is owned by Administrators. By default, the Everyone group has Full Control rights here. TrustedInstaller has no rights on this directory.C:\Users\<username> is owned by <username>. By default, no other users (save for System, and the HomeUsers group) has any access rights on another user's home folder.You never said - not once - that you were/are locked out of your personal files. Mikro said that he was, yes; you, however, did not. It would not be wise of me to make any assumptions here (you know what they say about what happens when you make an assumption....)I'm not trying to be argumentative. I'm not trying to be 'cute.' Occasionally, I may try to inject a bit of levity into the discussion, though. ;)I truly am here on this forum (as well as several others) to share the knowledge and experience that I've accumulated, and help others out.-Chris [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
November 21st, 2009 3:09am

I'm glad to hear you take this issue seriously... This leads me to think why you bothered responding to the comment by Johnclark, since this is where the thread went wrong IMO. Further, I think yourstillmissing the point I have been trying to make (and have apparently failed). It's not the fact that: "I am not having the issue which you describe. I am not having it on my desktop (Pro x86), laptop (Pro x86), or Media Center server box (Ultimate x64.)" (seriously; why do individuals feel the need to regurgitate the quantity of hardware they possess or serve? It seemsnarcissistic, and it really has no bearing on the amount of help aside from basically stating that ... well... theyownallot of hardware.) It's that: "DapperMan, I've read and re-read your posts in this thread multiple times; and, I keep coming back to the same problem: Ifyoudon't say just whereyourissue is, no specific answer can be given to your post. Only general answers can be given:%windir%, %ProgramFiles%, %ProgramFiles (x86)% are owned by TrustedInstaller; Users (even Administrators) have only read/traverse/execute rights.C:\Users\Public is owned by Administrators. By default, the Everyone group has Full Control rights here. TrustedInstaller has no rights on this directory.C:\Users\<username> is owned by <username>. By default, no other users (save for System, and the HomeUsers group) has any access rights on another user's home folder.Younever said - not once - thatyouwere/are locked out ofyourpersonal files. Mikro said that he was, yes; you, however, did not. It would not be wise of me to make any assumptions here (you know what they say about what happens when you make an assumption....)" Here your argument falls apart; I did state that I was having a similar issue ("I've logged in under my Admin rights, I do not have PERMISSION to use/alter certain files."), I then follow up with ("yea... there is a work around. Found it.")... In my very 1st post. I then freely admit that the rest is just "idiotic rhetoric". You, however, persist in trying to peel away the issue and get to the root of the problem which... to use your own words..."Mine's not broke. :P". The basis for my post is to simply point out that the answers to many issues that are posted seem to end with more questions andfrustratedusers. A simple push (which I do admit, you did provide in your 1st post... bravo) is far morehelpful than requests for 'Why do you want to access that' and 'you shouldn't have to do that'. So, basically this is where we diverge... you state that: "I do take the problems that people post here seriously. If I didn't, then, frankly, there would be no reason for me to have an account here. I'm here to help others, not to troll." Where I honestly state: "I'm just as crass to the other MVP's and "Pro's" there as well." ... which should be a fantastic clue for you ... This is oratory, opinion, idiotic rhetoric, or simply ... editorial. Now the simple fact that you persist in your aimless quest to find the end to mysarcasm/retortleads me to conclude that ... well... you arewasting time.
November 23rd, 2009 1:10am

DapperMan,My reply to JohnClark was an attempt to get some solid information out of him ("where is the issue?"), as well as to (hopefully) educate ("this is how some things are, and why they are the way they are.")Had he replied to (as well as to BubbaPCGuy) with any kind of actual information (as opposed to his rants), we could have helped him. His choice.I layed out what I'm running to show that it's not "an inherent flaw in the OS" (what many people seem to imply, whenever they haveany kind of issue, and with any version of Windows. I'm not saying that youfall into that camp, though.) If it were "an inherent flaw", don't you think I would have been hit by it at some point?That was why I stated what I'm running. I had no narcissistic intent in that statement.FWIW, only one of those machines is new-ish - the desktop was built in January of this year. The laptop is 4 years old now, and the MC server box was built in March '06.I'm done. Good day, sir.-Chris[If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2009 2:18am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics