I ran sfc /scannow and extracted the relevant results from CBSlog It looks like it tried twice but failed to repair a file "chtbrkr.dll" Reading through a lot of verbiage, it seems one way of "fixing" this is to replace the file on my computer with one that is not corrupt. But where do I get a good copy of this file? Is it on my Windows install disk? If so, how do I locate it? Thanks. -- Ron Extract of log file: =============================== 2010-12-09 20:48:47, Info CSI 00000177 [SR] Verify complete 2010-12-09 20:48:48, Info CSI 00000178 [SR] Verifying 100 (0x0000000000000064) components 2010-12-09 20:48:48, Info CSI 00000179 [SR] Beginning Verify and Repair transaction 2010-12-09 20:48:49, Info CSI 0000017b [SR] Cannot repair member file [l:22{11}]"chtbrkr.dll" of Microsoft-Windows-WordbreakerStemmer-ChineseTraditional, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2010-12-09 20:48:53, Info CSI 0000017d [SR] Cannot repair member file [l:22{11}]"chtbrkr.dll" of Microsoft-Windows-WordbreakerStemmer-ChineseTraditional, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2010-12-09 20:48:53, Info CSI 0000017e [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery" 2010-12-09 20:48:53, Info CSI 00000181 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"chtbrkr.dll"; source file in store is also corrupted 2010-12-09 20:48:54, Info CSI 00000183 [SR] Verify complete . . . . 2010-12-09 20:55:35, Info CSI 000002f7 [SR] Beginning Verify and Repair transaction 2010-12-09 20:55:36, Info CSI 000002f9 [SR] Verify complete 2010-12-09 20:55:36, Info CSI 000002fa [SR] Repairing 1 components 2010-12-09 20:55:36, Info CSI 000002fb [SR] Beginning Verify and Repair transaction 2010-12-09 20:55:36, Info CSI 000002fd [SR] Cannot repair member file [l:22{11}]"chtbrkr.dll" of Microsoft-Windows-WordbreakerStemmer-ChineseTraditional, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2010-12-09 20:55:36, Info CSI 000002ff [SR] Cannot repair member file [l:22{11}]"chtbrkr.dll" of Microsoft-Windows-WordbreakerStemmer-ChineseTraditional, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2010-12-09 20:55:36, Info CSI 00000300 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery" 2010-12-09 20:55:36, Info CSI 00000303 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"chtbrkr.dll"; source file in store is also corrupted 2010-12-09 20:55:36, Info CSI 00000305 [SR] Repair complete 2010-12-09 20:55:36, Info CSI 00000306 [SR] Committing transaction 2010-12-09 20:55:36, Info CSI 0000030a [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired ============================================= Ron

if you have installation disk, you can boot from that disk, use ImageX to mount the Install.wim file from Disk\Sources folder, and copy chtbrkr.dll file to your windows folder."Everything we do is dictated by motive."

On Fri, 10 Dec 2010 05:51:31 +0000, BlueW_Ryan wrote: if you have installation disk, you can boot from that disk, use ImageX to mount the Install.wim file from Disk\Sources folder, and copy chtbrkr.dll file to your windows folder. Thank you for that information. I'll give it a try. Ron

On Fri, 10 Dec 2010 05:51:31 +0000, BlueW_Ryan wrote: if you have installation disk, you can boot from that disk, use ImageX to mount the Install.wim file from Disk\Sources folder, and copy chtbrkr.dll file to your windows folder. As I consider this, I note two possible problems. 1. I don't have ImageX on my system. Will it load if I boot from the installation disk? 2. What if this file has been updated by one of the many upgrades MS has pushed to us? There was an update affecting this dll about a year ago, having to do with (if I remember correctly) SQL server 2005. Ron

You can also use 7-Zip to extract the files: http://blog.nirsoft.net/2009/09/17/how-to-extract-missing-system-files-from-the-dvd-of-windows-7vista/"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

On Sat, 11 Dec 2010 15:51:32 +0000, Andre.Ziegler wrote: You can also use 7-Zip to extract the files: http://blog.nirsoft.net/2009/09/17/how-to-extract-missing-system-files-from-the-dvd-of-windows-7vista/ Thank you for that. Made the extract and copying much simpler. Unfortunately, that did not work. By that I mean: 1. The file that was listed as a "cannot repair" by sfc is "chtbrkr.dll" 2. I extracted that file from my W7 installation disk, and, using the procedure here: http://support.microsoft.com/kb/929833 replaced the original file. (Of note is that they were exactly the same size). 3. I then ran sfc /scannow but it flagged the same file again as "cannot repair". I guess all I can do is ignore the sfc results. Maybe someone will see this and explain what is going on. Ron

Can you please upload the complete CBS.log after running sfc /scannow?"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

On Sun, 12 Dec 2010 00:36:14 +0000, Andre.Ziegler wrote: Can you please upload the complete CBS.log after running sfc /scannow? I don't see how to attach a file, so I've just included it in this message. Am I correct in assuming that you only are really interested in the sfc /scannow reports from today in that log? Or do you really want the whole thing? Immediately below are the results for scannow from the most recent scan. The complete CBS.log is quite a bit larger. Is there a better way to upload it then just print it out in a message? Thanks for your help. Hmmm. I've tried several times to send the entire listing of the sfc /scannow entries for this latest scan in CBS.log but the forum keeps rejecting it. I will edit out the repetitious rows. Each of the two sequences of three dots represent many repetitions of the three lines above them. ========================== 2010-12-11 19:00:42, Info CSI 00000009 [SR] Verifying 100 (0x0000000000000064) components 2010-12-11 19:00:42, Info CSI 0000000a [SR] Beginning Verify and Repair transaction 2010-12-11 19:00:44, Info CSI 0000000c [SR] Verify complete . . . 2010-12-11 19:07:50, Info CSI 00000178 [SR] Verifying 100 (0x0000000000000064) components 2010-12-11 19:07:50, Info CSI 00000179 [SR] Beginning Verify and Repair transaction 2010-12-11 19:07:51, Info CSI 0000017b [SR] Cannot repair member file [l:22{11}]"chtbrkr.dll" of Microsoft-Windows-WordbreakerStemmer-ChineseTraditional, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2010-12-11 19:07:55, Info CSI 0000017d [SR] Cannot repair member file [l:22{11}]"chtbrkr.dll" of Microsoft-Windows-WordbreakerStemmer-ChineseTraditional, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2010-12-11 19:07:55, Info CSI 0000017e [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery" 2010-12-11 19:07:56, Info CSI 00000180 [SR] Verify complete 2010-12-11 19:07:56, Info CSI 00000181 [SR] Verifying 100 (0x0000000000000064) components 2010-12-11 19:07:56, Info CSI 00000182 [SR] Beginning Verify and Repair transaction 2010-12-11 19:08:01, Info CSI 00000186 [SR] Verify complete . . . 2010-12-11 19:14:56, Info CSI 000002f3 [SR] Verifying 44 (0x000000000000002c) components 2010-12-11 19:14:56, Info CSI 000002f4 [SR] Beginning Verify and Repair transaction 2010-12-11 19:14:57, Info CSI 000002f6 [SR] Verify complete 2010-12-11 19:14:57, Info CSI 000002f7 [SR] Repairing 1 components 2010-12-11 19:14:57, Info CSI 000002f8 [SR] Beginning Verify and Repair transaction 2010-12-11 19:14:57, Info CSI 000002fa [SR] Cannot repair member file [l:22{11}]"chtbrkr.dll" of Microsoft-Windows-WordbreakerStemmer-ChineseTraditional, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2010-12-11 19:14:57, Info CSI 000002fc [SR] Cannot repair member file [l:22{11}]"chtbrkr.dll" of Microsoft-Windows-WordbreakerStemmer-ChineseTraditional, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2010-12-11 19:14:57, Info CSI 000002fd [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery" 2010-12-11 19:14:57, Info CSI 000002ff [SR] Repair complete 2010-12-11 19:14:57, Info CSI 00000300 [SR] Committing transaction 2010-12-11 19:14:57, Info CSI 00000304 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired ============================================== Ron

2010-12-11 19:07:51, Info CSI 0000017b [SR] Cannot repair member file [l:22{11}]"chtbrkr.dll " of Microsoft-Windows-WordbreakerStemmer-ChineseTraditional, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 Are you sure that you extracted the correct DLL (64Bit) and not the 32Bit DLL?"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Are you sure that you extracted the correct DLL (64Bit) and not the 32Bit DLL? The file was in the system32 folder on my 64-bit W7 install disk, just like the file referenced in CBS.log So I assume it was the correct one.Ron

To repair the system you can simply run In-place Upgrade.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The file was in the system32 folder on my 64-bit W7 install disk, just like the file referenced in CBS.log So I assume it was the correct one. Ron make the InPlace upgrade: http://www.sevenforums.com/tutorials/3413-repair-install.html How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2 http://support.microsoft.com/kb/2255099 to repair the Windows."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

On Mon, 13 Dec 2010 15:40:46 +0000, Andre.Ziegler wrote: > > >The file was in the system32 folder on my 64-bit W7 install disk, just like the file referenced in CBS.log > > So I assume it was the correct one. >Ron > >make the InPlace upgrade: > >http://www.sevenforums.com/tutorials/3413-repair-install.html How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2 > >http://support.microsoft.com/kb/2255099 > >to repair the Windows. >"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ In the midst of all this, my computer crashed (bad hard drive) and I have to reinstall everything. So I guess the question is now moot. Thanks anyway. Ron