CHKDSK /R or CHKDSK /F permission issues.

Sponsored Links

It appears that CHKDSK will not repair files in certain sections of a VISTA
install... I've got 2 bad $I130 indexes that CHKDSK will identify, but
refuses to actally fix (gives an "Access Denied" message...). Scheduling via
Drive | Properties fails to fix the problem also. The former was done from a
CMD prompt from the VISTA media DVD at a command prompt with "Administrator"
privilage... The latter from an "Administrator" account... What I've managed
to find out so far is that the ONLY account with "FULL" permissions is
"TrustedInstaller" everyone else ONLY has READ/LIST/EXEC.

So my question is this... How can I fix this? As "Administrator" I can't
even "Take Ownership" of any file or FOLDER "Owned by TrustedInstaller"... I
would think that the MS Tools should have the "Critical" Authorities needed
to REPAIR ($I30) indexes... Why doesn't it?

Index entry CbsMsg.dll in index $I30 of file 1373 is incorrect.
Index entry TrustedInstaller.exe in index $I30 of file 1373 is incorrect.

Can't touch anything here because it's owned by "TrustedInstaller"

C:\Windows\winsxs
C:\Windows\servicing


--
Vista User

http://forum.sysinternals.com/forum_...TID=10591&PN=1
According to this post, you take ownership of the file, then change the
rights to full for you. I assume they mean to use the 'takeown' utility.
Some Windows Vista functions may not work, or Windows Vista may stop
responding: http://support.microsoft.com/kb/929833
-

Include (add yourself as a user) yourself in Group ****Administrators*****
in Local Users and Groups.

No I meant at the folder (right-click | Properties | Security Tab) or File
(right-click | Properties | Security Tab)...

Will read up on the KB artical an let you know if it solves the problem.

I'm already running these a "Machine Admin"... CMD promtp with elevated
permissions seems to be superfluous... but I did it anyway...

This suggestion isn't helping any.
-

I read through your suggestion of KB929833... That only addresses primarily,
the case where Windows Resource Protection (WRP) file is missing or is
corrupted. That realy isn't the issue here... I want CHKDSK to fix the bad
$I30 index... This is the normal method that the OS invokes by itself if it
'detects issues' or that users can invoke. It's a question of either fixing
the antiquated CHKDSK or providing a new tool that is allowed to fix $I30
index issues in the protected areas of the OS... And when a situation arises
where an item in the protected area is not recoverable, it spells out
possible solutions or says that the OS needs to be reinstalled in order to
recover.

Right now, I'm in this update install loop... Where Windows Update is
constantly tryinig to install KB938371... and is constantly failing because
of the $I30 index inconsistancy.