So if I understand you correctly, you have removed the permission on all
files except for some system files, which have returned an access denied
error.
It sounds like Windows Resource Protection is blocking the changes to the
protected system files.
You will need to take ownership of the files left in order to be able to
edit their permissions. To do that, click advanced on the security
properties page, click the owner tab, click edit, select administrators, (do
NOT check the box next to replace owner on subcontainers and objects if it
is there), and then keep clicking ok until all the properties windows are
gone. Re-open the security properties screen, and you should now be able to
remove the permission.
Ideally, you should change the ownership back to the owner that was there
before, once you are done changing permissions (unless of course the owner
was the unknown account). To reference the trustedinstaller user, you must
use "nt service\trustedinstaller" for the user name.
I would point out too that this extra permission is harmless, it sounds like
it's just a side effect of the way they imaged the recovery CD, though
there's nothing wrong with removing the permission, as long as you keep the
rest of the security settings intact (including the inheritance structure).
--
- JB
Microsoft MVP Windows Shell/User
Ben Ramsay said:
I have tried to remove is as perscribed in windows help, however when the
files, as described before, are encountered windows returns a access denied
error but it soes allow me to continue. Widows warns me at the end of the
procedure that the permission may not be set correctly for some files and
windows basically dosen't like this.
As far as I can see it is a standalone with not inherited attachments.
Even if I change it to my security setting that wass setup when i
configured windows after using the recovery disks, windows will allow it
but some files still remain on this setting.
I have also checked on my other computer and found that this setting does
not exist in it, so I am thinking that it must be somthing to do with the
Recovery disks as my laptop has a fresh install on it and the origginal
installation disk was used not a recovery disk.
Hope this helps
--------------------------------------------------------------------------------------------