RPC Fails To Start After Volume Corruption

Consider the following scenario:

• A system shuts down inelegantly, either from power failure or other STOP error.

• Then it continually reboots on startup, either normally or in safe mode.

• The volume is mounted offline and repaired with chkdsk, and chkdsk resets all or most of the security descriptors.

• The system then starts up, but the Start Menu and taskbar do not appear or don't function, and many applications that require RPC do not run.

This may be resolved by resetting the system's permissions to those created at the system's installation.

See How to apply predefined security templates in Windows Server 2003.

The process is:

1. Use MMC to open the Security Configuration and Analysis snap-in.

2. Choose Open Database and create a new file.

3. Import the file C:\Windows\Security\Templates\Setup security.inf.

4. Choose Configure Computer Now.

5. Reboot.

   It may also be neccesary to configure the Remote Procedure Call (RPC) service to run under the Local System account (then reboot again).