Fix to sfc /scannow (System File Checker) error “The specific code is 0x000006ba [The RPC Server is unavailable.] “

I had to fix one Windows XP computer today. The computer was in a terrible state (meak to say), the system was hanging during boot,

None of Windows recovery modes worked,  except when running it through:

Windows Safe Mode (With Command Prompt) mode (pressing F8 before Windows boot with Windows flag screen).


I followed some Usual commands to repair broken Windows XP, as the system was hanging during boot there was obviously some issues with corrupt by Viruses and Malware system binary (.exe) files or some .DLL was substituted in (C:WindowsSystem32 and C:WindowsSystem32DllCacache) with a trojanned version by some "bad ware". 

Thus the logical thing to do was to try:

sfc /scannow


from Safe Mode's cmd prompt. Instead of starting its work as usual System File Checker spitted an error:
 

Windows File Protection could not be initiate a scan of protected system files. 
The specific code is 0x000006ba [The RPC Server is unavailable.]

You can guess my amazement as I see this error for a first time in my life. Actually I don't remember if I run System File Checker scan from a Safe Mode With only Command Prompt ever so I'm not sure if this error was caused by some Virus activity which broke up the Win host, or it is due to the fact RCP Services are not loaded in Safe Mode – With Command Prompt Only.

As the message implies RCP Server is not running and sfc depends on it.

The reason for the error is Windows File Protection (WFP) was disabled by some of the Spyware or Viruses which infested the poor Win PC.

As the problem consisted in unworking RPC Services I tried launching RPC manually with command:

> net start rpcss  

This unfortunately did not succeeded (dunno why).

I've later seen another fix pointed on a couple of forums around, which is using Registry to enable SFC.

Re-enabling SFC is done by:

1. Launching regedit

2. Once launched go to the following reg settings (sub-values)

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon

Use modify on it and change value to be "0"
3. Restart windows and launch again Safe Mode With (Command Prompt Only)

There execute:

> sfc /purgecache
> sfc /scannow

This solves it however, as you never can be sure if the Install time .DLLs are not already rootkited by the Virus-es and Spywares which "posessed" the computer. It is generally a good idea to Launch the Windows Install CD, recovery console and launch SFC using it, or even try using the Windows CD (Repair) mode. Though this is a temporary work around, this system will need a re-install in very short future, or it will most likely came in the same broken state in a very while – I don't believe such an infested computer can be "cured" except with a clean CD Windows re-install.
If this method didn't work for you but something else worked for you, whether you had to fix a Win PC please drop a comment with the solution.

Share this on

Download PDFDownload PDF

Tags: , , , , , , , , , , , , , ,

8 Responses to “Fix to sfc /scannow (System File Checker) error “The specific code is 0x000006ba [The RPC Server is unavailable.] “”

  1. admin NETHERLANDS Epiphany Debian GNU/Linux says:

    A sfcenable.reg file is here – http://www.pc-freak.nt/files/sfcenable_windows_registry_file.zip

    Alternative way to enable sfc is to simply run sfcenable.reg file and restart

    • hip0 says:

      The same computer happened to have a small problem with hardware too. I removed memory from memory slot and reattached, because computer was sometimes booting and sometimes not. After it was booting every time. Eventually I re-installed the Windows, just few days later, because it was too slowly working for a normal use. (the machine is old), but it seems some kind of badware was again crawling, so I was tired of trying to work it around thus re-installed.

  2. Vikram says:

    Hi, I have been fixing people's computers before I came into web development business. My way of approach was to just reformat the computer with a windows installation disk and run a boot time scan on other drives in most cases. If I knew a particar cure for a problem that I would have used that. Reformating is the best if the machine it fast enough it only takes an hour or so.

    • ConnDublin says:

      This will not offer the user any access to his data so I would be slow to classify this as “fixing people’s computer”. Indeed, they might have been able to do that themselves?

  3. […] Fix to sfc /scannow (System File Checker) error “The … – Fix to sfc /scannow (System File Checker) error “The specific code is 0x000006ba … You can guess my amazement as I see this error for a first time in my life…. […]

  4. […] Fix to sfc /scannow (System File Checker) error “The … – I had to fix one Windows XP computer today. The computer was in a terrible state (meak to say), the system was hanging during boot, … 3 Responses to “Fix to sfc /scannow (System File Checker) error “The specific code is 0x000006ba … […]

  5. Sniffa says:

    Sorry Vikram but that is not fixing someone’s computer. A wipe of the hard drive and a fresh reinstall of windows should be the last resort, not the first.

  6. […] Fix to sfc /scannow (System File Checker) error “The … – Error 0x000006ba | FixError.net says: October 7, 2014 at 5:56 am […] Fix to sfc /scannow (System File Checker) error “The … – Fix to sfc /scannow (System File Checker) error “The specific code is 0x000006ba … You can guess my amazement as I see this error for a first time in my life … […]

Leave a Reply