I experienced the same problem as some others here (pounding my head on the table 
through the night), I could not find the CSConfigFlags key, nor could I make changes 
to my registry. Working at Microsoft I contacted the RPC and SCM developers, and 
was able to obtain a workaround that solves this issue.

If you can boot into Windows (regular or safe-mode), open a command window (windows 
key + run, type cmd.exe) and type the following text:

reg.exe delete "HKLM\SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Enum\ROOT\LEGACY_RPCSS\0000" 
/v CsConfigFlags

You may also be able to use the recovery console to edit the above key manually (note 
it is different than the key previously mentioned in this thread).

Please don't send me hate mail regarding the RPC problem, I am as frustrated as all 
of you are :-(.

Good luck everyone!
-Scattman





On Thursday, July 31, 2003 at 6:56 am, Anton B wrote:
>I am rather happy at the solution I stumbled on to.
>
>I hypothesized that the reason behind the non-compliance of RPC from starting was 
>the hardware profile not being selected.
>
>I modified the following registry key:
>HKEY_CURRENT_CONFIG\System\CurrentControlSet\Enum\ROOT\Legacy_RPCSS\0000
>
>Then I changed the CSConfigFlags from 1 to 4 (choosing my hardware profile). 
>
>After changing it, I tried to start the RPC service and it did. I restarted the 
computer 
>and everything came back to normal. 
>
>Hopefully people who have the same problem may refer here for a possible solution 
>:) 
>
>Many thanks :) 
>
>