Member Avatar for Tazzy-Devil

I'm having problems running sfc. Well, I'm also having problems running msinfo32.exe and the Help & Support feature, but from what I have been able to find out on all the various forums is that if I run SFC I may be able to fix the other problems.

When I try to run sfc /scannow via Run->CMD->sfc /scannow it comes up with the following error:

Windows File Protection could not initiate a scan of protected system files
The specific error code is 0x000006ba [The RPC server in unavailable]

If I go into Start->Control Panel->Administrative Tools->Services and check on the Remote Procedure Call (RPC) it says is is "started". The Remote Procedure Call Locator is also started.

I have no idea what to do next, or how to fix this ****-ing problem!!!!

  • 3 Contributors
  • 3 Replies
  • 339 Views
  • 4 Years Discussion Span
  • Latest Post Latest Post by gurukid22

Dani AI

Generated

A short, practical summary and checklist

Error 0x000006ba means the local RPC subsystem is unreachable, so any tool that talks to RPC (System File Checker, Help & Support, System Information) will fail. Common root causes are: the RPC service or a dependent service is stopped or misconfigured; a third‑party installer changed the Windows directory value in the registry (the cause in ’s case); or NTFS ACLs on the Windows folder block the LocalSystem account (noted by ). ’s signature/timestamp idea is possible in certificate-related failures, but not the usual cause of the RPC 0x6ba symptom.

Quick diagnostic checklist (run as Administrator)

Open Services and confirm the RPC‑related services are Running and set to Automatic:

services.msc

Confirm service status from an elevated command prompt:

sc query rpcss

Look for RPC or Service Control Manager errors in the event log (Event ID 1722 is an RPC failure):

eventvwr.msc

Verify the system Windows folder variable points at the real install folder (a wrong WINDIR/SystemRoot will break RPC access):

echo %windir%

Also inspect NTFS permissions on C:\Windows and C:\Windows\System32 (Security tab) and ensure the SYSTEM account and Administrators have appropriate access; do not add Everyone/Full Control.

Targeted fixes (order of preference)

  1. If a recent installer (like Protel 99 SE) is the trigger, roll back with System Restore or uninstall it and check the WINDIR value (export the registry key first).
  2. Restore default ACLs rather than granting broad rights; on modern Windows use icacls to reset ACLs, on older XP systems use GUI or Microsoft tools designed for ACL repair.
  3. If the registry and ACLs look correct but RPC still fails, consider a repair install of Windows to restore damaged RPC components.

Always export/backup registry keys and create a restore point before editing system settings.

Recommended Answers

All 3 Replies

Member Avatar for jkdas

think it has got to do something with verisign time stamping.

Member Avatar for Tazzy-Devil

Actually, it turned out to be as a result of Protel 99 SE. I don't really understand what it did when I installed it, but this link gives details of what I had to do to fix the problems.
http://www.mail-archive.com/peda@techservinc.com/msg02950.html
(you need to scroll down to the part about WINDIR in the Registry)

I now have Help & Support, System Information and SFC all working perfectly!! Hooray :-)

Member Avatar for gurukid22

For others having this problem, this error can also be due to file permissions on the the windows folder where services files are stored in %system32% folder. I think protel 99 se had restricted access to this folder to protect your computer. Giving local system read / write permission will allow access but do not give full access or you will leave your system open to attacks.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.