Has anyone out there played with the “SFC” command in Windows 2000? If you know what I am talking about ... read on. I have installed this copy Windows 2000 on several different types of computers. They all exhibit the same behavior with the “SFC” command. What I normally do immediately after a fresh install is run the following commands in sequence: sfc /enable sfc /quiet sfc /scanonce After I have run these commands, I reboot the computer and let it run through the file scan. It completes the scan without any problems, however, when I look in the event viewer I see all kinds of “information” entries pertaining to “Windows File Protection.” These entries all pretty much have the same information: Event Type: Information Event Source: Windows File Protection Event Category: None Event ID: 64021 Date: 5/23/2000 Time: 11:43:53 AM User: N/A Computer: PATRICK Description: The system file c:\winnt\system32\chsbrkr.dll could not be copied into the DLL cache. The specific error code is 0x000004c7 [The operation was canceled by the user. ]. This file is necessary to maintain system stability. The only thing that changes is the file name itself, and at no point do I even interfere with, much less cancel the operation. What’s even more distressing is the result I get when I do this procedure without the “sfc /quiet” command. The scan starts normally and gets about a third of the way through the scan and then pops up with this error message: "Files that are required for Windows to run properly must be copied to the DLL Cache. Insert your Windows 2000 Professional CD-ROM now.” Needless to say, the CD is already in the drive, hitting the “Retry” button does nothing. So I hit the “More Information” button and it shows me this: Possible reasons for this problem: - you have inserted the wrong CD (i.e., a different Windows 2000 product CD than the version installed) - the CD-ROM drive in your system is not functioning. Both of these possibilities are utterly false. The CD-ROM drive is functioning perfectly and the CD is the same CD that I bought from the store and the same CD that was used for the installation. It was never even removed from the drive. So I am left with no other choice but the “Cancel” button. It pops up another window telling me that I can skip the file, but it is not recommended because the file is necessary for system stability. The file name is never shown until I check the event viewer. I must repeat this “cancel, skip file” process many times until the scan is completed. So what’s the deal here? Could this be some bug that Microsoft overlooked? Or am I missing something here? Originally I assumed that the files just had something to do with IIS and the system was purposely overlooking them. But why, then, would it generate a message saying that I have the wrong CD? Maybe the “sfc” command and all it’s associated files is expecting some earlier, beta version of Windows 2000? Perhaps. If anyone knows about this, please share your knowledge. At the end of this message, is a complete list of files mentioned in the event viewer entries. PLEASE NOTE: The computer that I am using to write this is using a totally fresh installation (NO PROGRAMS INSTALLED) of “Microsoft Windows 2000 [Version 5.00.2195]” as reported by the “ver” command. Curiously, properties for the KERNEL32.DLL file report file version 5.00.2191.1 … is this right? Thanks alot, Patrick FILE LIST: c:\winnt\system32\uniime.dll c:\winnt\system32\thawbrkr.dll c:\winnt\system32\softkey.dll c:\winnt\system32\pyime.exe c:\winnt\system32\phime.exe c:\winnt\system32\multibox.dll c:\winnt\system32\msir2jp.dll c:\winnt\system32\korwbrkr.dll c:\winnt\system32\kbdth3.dll c:\winnt\system32\kbdth2.dll c:\winnt\system32\kbdth1.dll c:\winnt\system32\kbdth0.dll c:\winnt\system32\kbdintam.dll c:\winnt\system32\kbdinmar.dll c:\winnt\system32\kbdinhin.dll c:\winnt\system32\kbdindev.dll c:\winnt\system32\kbdheb.dll c:\winnt\system32\kbdfa.dll c:\winnt\system32\kbda3.dll c:\winnt\system32\kbda2.dll c:\winnt\system32\kbda1.dll c:\winnt\system32\imeskf.dll c:\winnt\system32\imeskdic.dll c:\winnt\system32\imepad.dll c:\winnt\system32\imejputy.dll c:\winnt\system32\imejpuex.exe c:\winnt\system32\imejpmgr.exe c:\winnt\system32\imejpknl.dll c:\winnt\system32\imejpdct.dll c:\winnt\system32\imejpcus.dll c:\winnt\system32\hwxjpn.dll c:\winnt\system32\ftlx041e.dll c:\winnt\system32\ftlx0411.dll c:\winnt\system32\cplexe.exe c:\winnt\system32\cjime.exe c:\winnt\system32\chtbrkr.dll c:\winnt\system32\chsbrkr.dll

Your "BETA" copy is way past it's time. You are running on fumes in order to allow you to upgrade or dump it in an orderly fashion. hint: 2600

How do you know for sure? I know that 2195 is the latest build. What do you mean by 2600? I thought for sure that i had a final copy. Please tell me more!!!

You have a "hacked" version: 5.00.2191.1

What is the version of your kernel32.dll file? Should it be 5.00.2195.1 or 5.00.2195.3 ??? I remember that controversey a little while back. I will admit that i got the ISO from some warez site. But it is a bootable iso that boots right into the setup program. What do you mean by 2600? Please help. Do you frequent an irc server? Email it to me. I left my hotmail account. appye@hotmail.com

I think you are fullof it. Tell me the version numbers of your file kernel32.dll

He is full of it.....I am running Win2k Professional installed from a Microsoft Select CD that is ver 5.00.2195 and kernel32.dll is 5.00.2191.1