Jump to content

Featured Replies

Posted

After an sfc scan reports corrupted system files that it can't fix, the CBS

log shows nothing except a lot of windows\system32 folders with duplicate

ownership. A typical message is

CSI 00000036 Ignoring duplicate ownership for file

[l:58{29}]"\??\C:\Windows\System32\ja-JP" in component

Microsoft-Windows-comdlg32.Resources, Version = 6.0.6000.16386, pA =

PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"ja-JP", VersionScope =

1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName

neutral, PublicKey neutral

 

Most folders mentioned have TrustedInstaller as owner, but I can't find any

duplication. Is it necessary to fix this?

 

Another entry is

32: Set Key Value: Key =

[l:168{84}]"\Registry\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Generalize",

Value = [l:76{38}]"{2bc9942c-1914-981d-d3d1-771286930ef6}", Type = REG_SZ

(1), Data = {l:106

b:43003a005c00570069006e0064006f00770073005c00530079007300740065006d00330032005c00770075006100750065006e0067002e0064006c006c002c00470065006e006500720061006c0069007a00650046006f00720049006d006100670069006e0067000000}

 

Neither of these entries are mentioned in the Microsoft Article on the CBS

log of a sfc scan, so I have no idea what they mean. I can't find any

reference to corrupted files in the log.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...